-
Notifications
You must be signed in to change notification settings - Fork 23
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Create new baselines #184
Comments
@ligiabernardet The app is updated (ufs-release-v1.1 branch) and we have following issues,
Besides those problems that could be platform specific, the app is ready for your test. I also tested with three different input types (GRIB2, NEMSIO and NETCDF). Please let me know how it goes. |
The failed test on Cheyenne uses 252 core for C384 and 180 core for C192. It is strange that other tests with same resolution passes without any problem, that indicates system issue. |
@ligiabernardet @climbfuji Here is the instructions to run full test suite.
To compare against exiting baseline the command look like following,
To generate new baseline,
I'll make PR soon for the app. |
@climbfuji is there any NCEPLIBS installation on Orion that I could use for UFS MR app? |
No, orion is a configurable platform and it is up to the user to install the NCEPLIBS him/herself following the instructions in the usual place (NCEPLIBS-external, tag ufs-v1.1.0, doc/README_orion_intel.txt). |
@climbfuji Okay. Thanks |
We decided that we will NOT provide baselines for the users to compare the new runs against. There were no baselines with v1.0.0 and we'll keep it that way for ease of maintenance. Users can always create their own baselines. |
Create new baselines on the machines for which the App regression test is setup (Cheyenne and Stampede) so that user's runs can match the baselines.
The text was updated successfully, but these errors were encountered: