DKRZ projects: Issueshttps://swprojects.dkrz.de/redmine/https://swprojects.dkrz.de/redmine/redmine/favicon.ico?17095821032013-07-02T11:34:57ZDKRZ projects
Redmine ScalES-PPM - Feature #322 (Closed): Add general MPI datatype-based access to distributed multi-arrayhttps://swprojects.dkrz.de/redmine/issues/3222013-07-02T11:34:57ZThomas Jahnsjahns@dkrz.de
<p>The multi-array could provide access to types not directly supported via an interface that looks like this:</p>
<pre>
subroutine dist_mult_array_get_cache_val_mpidt(dm_array, sub_array_idx, &
cache_idx, coord, v)
TYPE(dist_mult_array), INTENT(in) :: dm_array
INTEGER, INTENT(in) :: sub_array_idx, cache_idx
INTEGER, INTENT(in) :: coord(:)
TYPE(C_PTR) :: v
</pre>
<p>and write to <code>v</code> via MPI_Sendrecv on MPI_Comm_self.</p> Quick Enqueue - Feature #275 (Closed): Add default wall time limit argument to configure script.https://swprojects.dkrz.de/redmine/issues/2752011-06-03T16:10:35ZThomas Jahnsjahns@dkrz.deQuick Enqueue - Feature #274 (Closed): Add default SMT-setting argument to configure script.https://swprojects.dkrz.de/redmine/issues/2742011-06-03T15:58:14ZThomas Jahnsjahns@dkrz.deQuick Enqueue - Feature #273 (Closed): Add default memory-limit argument to configure script.https://swprojects.dkrz.de/redmine/issues/2732011-06-03T15:43:51ZThomas Jahnsjahns@dkrz.deQuick Enqueue - Feature #272 (Closed): Add default class argument to configure script.https://swprojects.dkrz.de/redmine/issues/2722011-06-03T15:42:32ZThomas Jahnsjahns@dkrz.deQuick Enqueue - Bug #271 (Closed): Catch SIGINT and cancel jobhttps://swprojects.dkrz.de/redmine/issues/2712011-06-03T14:12:42ZThomas Jahnsjahns@dkrz.de
<p>The job is currently not cancelled automatically, but this would be desirable on signal exit.</p> Quick Enqueue - Feature #270 (Closed): Improve site-configuration.https://swprojects.dkrz.de/redmine/issues/2702011-06-01T16:35:59ZThomas Jahnsjahns@dkrz.de
<p>Some aspects of per-site-configuration should be improved by providing optional switches to configure:</p>
<ul>
<li>The method for establishing the temporary directory, which must be available on submit and execution host, should be configurable.</li>
<li>The following should be configurable:
<ul>
<li>default class</li>
<li>default per-task memory limit</li>
<li>default smt-mode</li>
<li>default wall clock time limit</li>
</ul></li>
</ul> Quick Enqueue - Feature #268 (Closed): Let user choose the job-namehttps://swprojects.dkrz.de/redmine/issues/2682011-06-01T16:25:19ZThomas Jahnsjahns@dkrz.de
<p>Currently the job name is derived from the first argument. It should be adjustable via optional arguments to distinguish separate tasks running with the same command.</p> ScalES-PPM - Bug #261 (Closed): Check wether make dist-check workshttps://swprojects.dkrz.de/redmine/issues/2612011-03-24T16:25:28ZThomas Jahnsjahns@dkrz.deScalES-PPM - Feature #240 (Closed): Complete implementation of hierarchical decomposition varianthttps://swprojects.dkrz.de/redmine/issues/2402011-02-03T12:38:32ZThomas Jahnsjahns@dkrz.de
<p>To use a different decomposition in the COSMOS-prototype, the code needs to be integrated with the models ECHAM6 and MPIOM.</p> ScalES-PPM - Feature #212 (Closed): Add cache database to dependency trackerhttps://swprojects.dkrz.de/redmine/issues/2122010-11-19T10:18:40ZThomas Jahnsjahns@dkrz.de
<p>On platforms where the Fortran compiler is slow (I'm looking at you xlf) to generate preprocessor output, it would be highly desirable to cache the dependency results, and not reparse the source code of unchanged files. Such an approach would have to account for several preconditions:</p>
<ul>
<li>The environment and flags between runs would ideally be unchanged, perhaps excluding known problem cases.</li>
<li>The source file in question must not have changed, as well as any file it includes.</li>
</ul>
<p>Please add further conditions to account for.</p> getrusage - Feature #20 (Closed): Add aggregate computation for run-scripts.https://swprojects.dkrz.de/redmine/issues/202010-03-12T16:01:43ZThomas Jahnsjahns@dkrz.de
<p>Users typically only care about aggregated values, not individual resource use in big parallel jobs.</p>
<p>A script should be delivered that produces just such metrics.</p> getrusage - Feature #9 (Closed): Optionally print executed command to output.https://swprojects.dkrz.de/redmine/issues/92009-06-18T16:44:57ZThomas Jahnsjahns@dkrz.de
<p>When multiple commands are executed via getrusage in parallel it might be useful to distinguish by command executed.</p>
<p>Thus a command option should be available that prepends the command run to the diagnostic output.</p> getrusage - Feature #7 (Closed): Allow writing to file name with pid replacement.https://swprojects.dkrz.de/redmine/issues/72009-06-12T16:35:35ZThomas Jahnsjahns@dkrz.degetrusage - Feature #6 (Closed): Compute wallclock time.https://swprojects.dkrz.de/redmine/issues/62009-06-12T16:31:55ZThomas Jahnsjahns@dkrz.de