YAXT: Issueshttps://swprojects.dkrz.de/redmine/https://swprojects.dkrz.de/redmine/redmine/favicon.ico?17095821032015-04-27T12:34:37ZDKRZ projects
Redmine Feature #337 (New): check possibility of usage of mpi_type_create_hvector in xt_redist_collection...https://swprojects.dkrz.de/redmine/issues/3372015-04-27T12:34:37ZJoerg Behrensbehrens@dkrz.de
<p>If the sequence of redists given in the constructor always uses the same redist then we should reduce the created datatype to a simple form (using mpi_type_create_hvector instead of MPI_Type_create_struct).</p> Feature #321 (New): runtime switch for the generation of MPI datatypeshttps://swprojects.dkrz.de/redmine/issues/3212013-06-27T13:32:47ZJoerg Behrensbehrens@dkrz.de
<p>There are now two ways to generate dataypes (src/xt_mpi.c)</p>
<p>(a) fast, but without exploiting potential for a compact description<br />(b) less fast, but with ...</p>
<p>So far the switch is a cpp symbol: COMPACT_DT in src/xt_mpi.c</p>
<p>We need a runtime switch in order to test both versions without recompilation</p> Feature #310 (New): new xmap constructor: xt_xmap_dist_dir_dim_newhttps://swprojects.dkrz.de/redmine/issues/3102012-11-26T15:15:33ZJoerg Behrensbehrens@dkrz.de
<p>The implementation should use the routine xt_idxlist_get_bounding_box (see issue <a class="issue tracker-2 status-5 priority-4 priority-default closed" title="Feature: new idxlist method: xt_idxlist_get_bounding_box (Closed)" href="https://swprojects.dkrz.de/redmine/issues/309">#309</a>) in order to efficiently preselect intersection candidates coming from the distributed directory bucket lattice for later intersection computation.</p>
<pre>
Xt_xmap xt_xmap_dist_dir_dim_new(Xt_idxlist src_idxlist, Xt_idxlist dst_idxlist,
int ndim, Xt_int global_size[ndim],
Xt_idx global_start_index, MPI_Comm comm);
</pre> Feature #307 (New): idxsection_get_index_stripes_consthttps://swprojects.dkrz.de/redmine/issues/3072012-10-25T15:13:33ZJoerg Behrensbehrens@dkrz.de
<p>Implement const version of idxsection_get_index_stripes (like get_indices_const).</p> Feature #306 (New): garbage collectorhttps://swprojects.dkrz.de/redmine/issues/3062012-10-25T15:11:10ZJoerg Behrensbehrens@dkrz.de
<p>Since we have an idxlist-internal cache that we might not need at some point, we might consider implementing a garbage collector to minimize the memory footprint of idxlists.</p> Feature #305 (New): fundamental vector typehttps://swprojects.dkrz.de/redmine/issues/3052012-10-15T12:11:57ZJoerg Behrensbehrens@dkrz.de
<p>It might be useful to have a fundamental vector type</p>
<p>struct vec_DATA_TYPE { int n; int cap; DATA_TYPE *p;};</p>
<p>in order to simplify the code, e.g. to reduce the number of arguments when vector-like information is passed (DATA_TYPE *p, n)</p> Feature #304 (New): basic warning/error managementhttps://swprojects.dkrz.de/redmine/issues/3042012-10-15T12:07:59ZJoerg Behrensbehrens@dkrz.de
<p>basic warning/error management => summary at finalize?</p> Feature #301 (New): support for elemental post-processing https://swprojects.dkrz.de/redmine/issues/3012012-03-27T09:25:11ZJoerg Behrensbehrens@dkrz.de
<p>Depending on the special features of the global index space (map to physical space, incomplete subspaces) it would be nice to have elemental post-processing.</p>
<p>Optional features:</p>
<ul>
<li>Assign an undef value (given by the user) to points that could not be assigned during the transfer (instead of making this a fatal error). The user should also be able to query the number of local undef values. This is of general interest.</li>
</ul>
<ul>
<li>Accept a sign change property of <em>pairs</em> of global index points - this allows us to correctly transform directed physical quantities if the map to physical space includes point symmetries. This is really special but has one important use case: MPIOM.</li>
</ul>