Skip to content
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

UKMO staging [develop] #237

Closed
wants to merge 4 commits into from
Closed

Conversation

ukmo-ccbunney
Copy link
Collaborator

This staging branch is simply a branch from develop that is used to stage multiple PRs in the UKMO repo to facilitate a merge to the authoritative NOAA develop branch.

This staging branch contains changes from the follow UKMO PRs:

See the individual PRs for specific regtest output.

All tests compared as OK with the following expected differences:

  • all tests are showing changes in *mod_def* and *ww3_grid*out* due to the addition of the calendar option Fb 360 calendar ukmo-waves/WW3#8.
  • the ww3_tp2.14 tests are showing a difference inTOY_OUTPUT.txt (extra line saying APPLE Partitioning); this line was originally output randomly (processor dependant), but is now always output.
  • ww3_tp2.18/work_TIDE_MPI/ww3_prtide_current.out_diff.txt shows lots of differences - this is a known issue (see Regtest tp2.18: ww3_prtide_current screen output not reproducible with MPI #225)
  • The usual differences with mww3_test_03

The complete regtest suite output is provided in the attached zip file: matrixComp.zip

UKMO-lsampson and others added 4 commits July 22, 2020 11:44
to ensure they comply with the limits of the nameslist.
Changes to add support to 360-day and 365-day (no leap year) calendar - see ticket NOAA-EMC#209
  * Additional CALTYPE namelist parameter in MISC section
  * New ww3_tc1 regtest.
* Updated ww3_bound and ww3_bounc to handle model grids formulated on a rotated pole.
* Manual and nml/inp files to updated clarify that ww3_bound/ww3_bounc only accept input spectra formulated on a standard pole grid.
Updates to allow a coupling time step that is different from the model time step. 
* Includes new regtest (in ww3_tp2.14) for non-default oasis time step.
* ww3_tp2.14 regtest added to matrix.base.
@ukmo-ccbunney ukmo-ccbunney added bug Something isn't working enhancement New feature or request labels Jul 30, 2020
@aliabdolali
Copy link
Contributor

Hi @ukmo-ccbunney and team,
Thanks for doing this great enhancement and fixes.
I ran the matrix on noaa hpc as a double check and noticed a couple of things.
As you reported, all mod_def* are not identical as expected, mww3_test_03 and ww3_tp2.18 carry the known issue.
See the matix.comp outputs matrix_diff_ncep.zip

Here I have a question and one comment:

  1. I could not run the following tests:
./bin/run_test -b slurm -c hera -S -T -s OASACM -w work_OASACM -C OASIS -f -p mpirun -n 24 -o netcdf ../model ww3_tp2.14
./bin/run_test -b slurm -c hera -S -T -s OASACM2 -w work_OASACM2 -C OASIS -f -p mpirun -n 24 -o netcdf ../model ww3_tp2.14
./bin/run_test -b slurm -c hera -S -T -s OASOCM -w work_OASOCM -C OASIS -f -p mpirun -n 24 -o netcdf ../model ww3_tp2.14
./bin/run_test -b slurm -c hera -S -T -s OASICM -w work_OASICM -C OASIS -f -p mpirun -n 24 -o netcdf ../model ww3_tp2.14

Do I need to do sth on our hpc for coupling or I cannot test the COU OASIS OASACM switches?
2. We have two miles stones for your developments, please modify the header accordingly for version 7.10 (coupled model) and 7.11 (rotated grid).

Other than that, I am quite happy with all the changes.
Regards,
AA

@chrisbunney
Copy link

@ukmo-juan-castillo Are you able to answer Ali's question above in my absence? It is regarding running the ww3_tp2.14 regtest.

@ukmo-juan-castillo
Copy link
Collaborator

What is the error you receive when running the ww3_tp2.14 test? It is probably something to do with netcdf or other libraries.

@aliabdolali
Copy link
Contributor

Hi @ukmo-juan-castillo
Those tests did not run because of -C OASIS so I thought we need to have this coupling option on our HPC.
AA

@ukmo-juan-castillo
Copy link
Collaborator

In matrix.base the -C OASIS option is added to all the ww3_tp2.14 tests. This test should compile the oasis library and link it properly to the executables that require it. If this is not happening then there is something in the ncep matrix file that needs updating. Did you set oasis=y in your matrix file to run the ww3_tp2.14 tests, and if you did, did you receive any error message?

@aliabdolali
Copy link
Contributor

Hi @ukmo-juan-castillo
Yes, I set oasis='y'
in matrix_ncep, we define the cmplr=hera, therefore the command line is
./bin/run_test -b slurm -c hera -S -T -s OASICM -w work_OASICM -C OASIS -f -p mpirun -n 24 -o netcdf ../model ww3_tp2.14
it comes with the following error:
ERROR: cmplr.hera not found

if I change cmplr=intel, then it ran fine, but the rest of matrix is broken.

@ukmo-juan-castillo
Copy link
Collaborator

Could you try to add the hera compiler to the list of accepted compilers in the script:

regtests/ww3_tp2.14/input/prep_env.sh

and try again?

https://github.com/ukmo-waves/WW3/blob/5c361aaf3085bb5ac04931493b9c1eae1c15b5d9/regtests/ww3_tp2.14/input/prep_env.sh#L29-L42

@aliabdolali
Copy link
Contributor

Thanks, @ukmo-juan-castillo
Now it is running fine.
There is one last issue:
cp: cannot stat ‘../input/r-ww3.nc.OASACM2’: No such file or **directory
Could you add it?

Also, have you updated the headers following milestones:
version 7.10 (coupled model) and 7.11 (rotated grid).

@ukmo-juan-castillo
Copy link
Collaborator

You can copy the r-ww3.nc.OASACM file, it should be the same. The script ww3_from_ftp.sh should be copying it to the right place. In fact, most of the OASACM and OASACM2 files required are the same.

aliabdolali added a commit that referenced this pull request Aug 10, 2020
* Added boundary checks to the SMC grid input files for ww3_grid,
to ensure they comply with the limits of the nameslist.

* Fb 360 calendar (#8)

Changes to add support to 360-day and 365-day (no leap year) calendar - see ticket #209
  * Additional CALTYPE namelist parameter in MISC section
  * New ww3_tc1 regtest.

* RTD support for ww3_boun[dc] (#10)

* Updated ww3_bound and ww3_bounc to handle model grids formulated on a rotated pole.
* Manual and nml/inp files to updated clarify that ww3_bound/ww3_bounc only accept input spectra formulated on a standard pole grid.

* Fb coupling time (#9)

Updates to allow a coupling time step that is different from the model time step. 
* Includes new regtest (in ww3_tp2.14) for non-default oasis time step.
* ww3_tp2.14 regtest added to matrix.base.

* bug fix for ukmet development

Co-authored-by: lewis.sampson <lsampson@vld240.cmpd1.metoffice.gov.uk>
Co-authored-by: Juan Manuel Castillo Sanchez <48921434+ukmo-juan-castillo@users.noreply.github.com>
Co-authored-by: Chris Bunney <48915820+ukmo-ccbunney@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working enhancement New feature or request
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants