<div dir="ltr"><div dir="ltr"><div>Hi all,</div><div><br></div><div>As you know, all NOAA R&D machines are moving away from Moab/Torque/ALPS to SLURM. The changes to NEMS, NEMSfv3gfs, NCEPLIBS-pyprodutil, and Rocoto for SLURM on Jet and Theia are all working. The changes still support non-SLURM Jet and Theia. However, Theia's SLURM is misconfigured; if you ask for complex task geometry, then it think Theia has 12 cores per node instead of 24. I'm waiting to hear back from the admins on that. Once that bug is fixed, I'm planning on committing the SLURM support to the relevant repositories.<br></div><div><br></div><div>Sincerely,</div><div>Sam Trahan<br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, 20 Dec 2018 at 20:54, Samuel Trahan - NOAA Affiliate <<a href="mailto:samuel.trahan@noaa.gov" target="_blank">samuel.trahan@noaa.gov</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr">Hi all,<div><br></div><div>In an earlier email, I mentioned that I was going to commit a change to allow NEMS to use SLURM. I will delay this commit until further notice.</div><div><br></div><div>The system SLURM configuration keeps changing, so it is not possible to keep a stable NEMSCompsetRun implementation for it. I'm going to keep updating the "slurm" branch as the SLURM systems update, but I'll wait to commit to NEMS "master" until the SLURM systems are stable.</div><div><br></div><div>I should mention that the SLURM systems are being reconfigured out of necessity, to fix problems and add missing features. Decisions are made in collaboration with technical contacts in various parts of NOAA. These are critical changes that cannot be skipped or delayed, and you would sorely regret not having them. For example, in the past few weeks, admins achieved fully-functional task affinity, correct resource accounting, and support for complex task geometries. Getting those features to work together properly required using some of the more advanced aspects of SLURM, plus some bug reports to the developers of SLURM.</div><div><br></div><div>Sincerely,</div><div>Sam Trahan</div></div>
</blockquote></div>
</div>