<div dir="ltr"><div>Hi all,</div><div><br></div><div>Update on the aforementioned issues:</div><div><br></div><div>1. The WCOSS Cray license server issues are resolved. You can compile how you always did. Please file a WCOSS helpdesk ticket if the problem reoccurs.</div><div><br></div><div>2. I'm still working on the NEMS nightly test scripts, so the website will still display gibberish. Due to the Jet downtime tomorrow, I won't finish this until at least Wednesday.<br></div><div><br></div><div>3. The Jet account_params issue is resolved.</div><div><br></div><div>Sincerely,</div><div>Sam Trahan<br></div></div><br><div class="gmail_quote"><div dir="ltr">On Fri, 7 Dec 2018 at 13:02, Samuel Trahan - NOAA Affiliate <<a href="mailto:samuel.trahan@noaa.gov">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"><div dir="ltr"><div>Hi all,</div><div><br></div><div></div><div>I want to alert you to three problems that have been reported:</div><div><br></div><div>1. It is no longer possible to compile on WCOSS Cray, except on login nodes. That is almost certainly not intentional; it appears to be a networking or firewall issue. The NEMSCompsetRun compiles inside of batch jobs, so it is broken on WCOSS Cray at the moment. There are multiple tickets in from various users, asking WCOSS admins to fix this. There are potential workarounds we could put in the apps. The workarounds are messy, so I will hold off on using them unless the admins take too long to fix the problem.<br></div><div><br></div><div>2. I am in the middle of rewriting the NEMS nightly test scripts, so if you go to the nightly test webpage, you will see all sorts of gibberish. It should normalize sometime early next week once the rewrite is done.<br></div><div><br></div><div>3. Briefly, on Jet, the account_params program was broken. That problem has been resolved. The failure resulted in a variety of strange error messages. The NEMSCompsetRun, by default, will use account_params to find the project with the most available core-hours, so the auto-detection failed when account_params was broken. You can bypass that step by manually specifying the project:</div><div><br></div><div>./NEMS/NEMSCompsetRun --project=hfv3gfs ... options ...</div><div><br></div><div>Disk space decisions can be overridden as well:</div><div><br></div><div>./NEMS/NEMSCompsetRun --temp-dir=/path/to/somewhere ... options ...<br></div><div><br></div><div>Sincerely,</div><div>Sam Trahan<br></div></div></div>
</blockquote></div>