HWRF on HERA initial items

[jimfrimel]

An initial commit and run of HWRF on Hera #10 has been implemented The following is a list of remaining items.

NOTE: Possible Impacts from Changes that may effect other HPC systems.. CRTM 2.2.6 (only effects Hera), Replaced Deprecated Compiler Flag openmp with qopenmp* copygb code mods initializing variables, safer if statement hwrf_gsi code mods initializing pointers hwrf_input.conf theia reference replace with hera (only effects WCOSS)

*Note: I think qopenmp became avaialbe in the intel compiler 15 family so all our HPC systems "should" be covered.

RESOLVED

• FIXcrtm conf variable for HERA points to 2.2.6 and is using fix directory hwrf-trunk-20191011-fix. FIXcrtm and fix_version config variables, are temporarily being over-ridden in the system.conf.hera file, until all clusters move to the same version again.
  • hwrf.conf:FIXcrtm={FIXhwrf}/hwrf-crtm-2.2.3/
  • hwrf_basic.conf:fix_version=20171129
  • hwrf_2km.conf:FIXcrtm={FIXhwrf}/hwrf-crtm-2.2.3/
  • Regarding hwrf_2km.conf ... My understanding is, it is no longer being used. If it is than that file will HAVE TO BE MODIFIED when running on HERA, since it's conf variable for crtm is still referenceing 2.2.3.

TESTING

• [passed] Initial build and Run 12hour cycled forecast, Input Data was already staged.
• [passed] Test on Hera running and pulling Data from HPSS. FULL FORECAST
• [passed] Test on Hera with crtm 2.2.6 fix files ?
• [inprogress] Test rebuild/run on Hera with Current Trunk changes.
• [passed] Test on Jet, CC with current trunk, all defaults, 2 cycles. (qopenmp, copygb, hwrf_gsi) 24hr fcst - NO differences.
• [inprogress] Test on WCOSS (qopenmp, copygb, hwrf_gsi, hwrf_input.conf) wcoss_cray (Luna), A one-cycle technical test

ProdGSI

• [x] Confirm Library versions selected in Makefile.conf.hera
• [x] Confirm crtm 2.2.6 Library.

WCOSS Just a mention: Since Untested. I don't expect this to be an issue but it is a change that may impact WCOSS, when changes work there way to trunk. In the hwrf_input.conf file ... I made the following changesfrom theia to hera ... https://heradocs.rdhpcs.noaa.gov/wiki/index.php/Transferring_data  [wcosssurge_sources_PROD2016]  hera_hist_PROD2016%location = sftp://{hera_user}@dtn-hera.fairmont.rdhpcs.noaa.gov/ hera_hist_PROD2016%histprio=81

[wcossluna_sources_PROD2016] hera_hist_PROD2016%location = sftp://{hera_user}@dtn-hera.fairmont.rdhpcs.noaa.gov/ hera_hist_PROD2016%histprio=81

[jimfrimel]

Bring Hera Changes in to a branch

Hera changes "should" be compatible on all systems. Changes were Tested on Hera, WCOSS luna, and (Jet - CC 48hour forecast cycled, showed no differences).

Changes for Hera were made to the following repositories. HWRF trunk (HWRF scripts) pomtc hwrf-utilities ProdGSI

To Bring in Hera Only changes to your branch .... For example the HB20baseline branch:

a) I would checkout a clean copy of your HB20baseline branch, perform the following commands below, build, and run test, than commit the merged changes back to your branch ... then update your working branch when you are satisfied ....

Want to see what has been merged ? svn propget svn:mergeinfo

b) Cherry Pick - Bring only Hera changes.

prompt> svn co https://svn-dtc-hwrf.cgd.ucar.edu/branches/HB20baseline

prompt> cd HB20baseline

HB20baseline> svn update

HB20baseline> svn merge -c6450,6449 ^/trunk .

cd HB20baseline/sorc/hwrf-utilities HB20baseline/sorc/hwrf-utilities> svn merge -c1527 ^/branches/HWRF .

cd HB20baseline/sorc/pomtc HB20baseline/sorc/pomtc> svn merge -c448 ^/branches/HWRF .

NOTE: It looks like you are using the HWRF branch for ProdGSI SO YOU DO NOT NEED TO CHERRY PICK for ProdGSI ... But if you were working in your own ProdGSI branch ... This would be the cherry pick command: HB20baseline/sorc/ProdGSI> git cherry-pick -x 66f27a6851d701e2 - DO NOT DO THIS.

However ... You WILL WANT TO PULL IN THE latest updates when you move your working ProdGSI branch HB20baseline/sorc/ProdGSI> git pull origin HWRF