[Ncep.list.nems.announce] Upcoming NEMS commits due to Theia & Jet changes
Samuel Trahan - NOAA Affiliate
samuel.trahan at noaa.gov
Fri Jun 2 19:20:07 UTC 2017
I'm going to wait until after Jun's NEMSfv3gfs commit. I will merge her
changes and retest. That means my commit may go in tomorrow.
Jun's branch contains the one and only change needed to NEMSfv3gfs to
ensure that app works on Theia. We know this because we tested NEMSfv3gfs
on Selene (Theia test machine). However, none of the other apps were
tested, and the one change needed to NEMSfv3gfs is not enough for other
apps. The other changes are needed for other possible configurations. I
have a few changes that should work in most cases, but I want to fully test
before I commit.
On Fri, Jun 2, 2017 at 1:23 PM, Samuel Trahan - NOAA Affiliate <
samuel.trahan at noaa.gov> wrote:
> Hi all,
> Recent changes on Theia and Jet have broken those platforms. I'm going to
> do an emergency commit later today to fix these problems.
> NEMSfv3gfs is fully tested on all platforms. I have merged the changes to
> the trunk at this directory:
> I'm re-testing NEMSGSM now and will send a directory for that soon. There
> is a bug in the CHEM external that will also need to be corrected.
> 1. Stack size - jet forces an initial stack size limit of 10MB on all
> jobs, no matter what you put in your rc files. The scripts will obtain a
> higher stack limit.
> 2. Batch queue - The NEMSCompsetRun runs on the batch queue instead of the
> service queue on Theia. This is because the "module" command allocates
> vast amounts of memory when run in the service queue under NEMSAppBuilder.
> 3. Update to top of produtil.
> Sam Trahan
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Ncep.list.nems.announce