richamp-support

ASGS Post-Processing Setup Instructions on Hatteras & Unity

NOTE: You should already have set up an ASGS instance before you go through this setup. If you haven’t, do that first.

1. Contact Josh Port (joshua_port@uri.edu) and ask him for the URI MetGet API key. If Josh is unavailable, try reaching out to Zach Cobell (zcobell@thewaterinstitute.org).
2. Navigate to the output subfolder within your main ASGS directory (i.e. SCRIPTDIR/output)
3. Run “git clone git@github.com:StormSurgeLive/richamp-support”. This will pull down the latest post-processing code from GitHub. The folder this command creates will henceforth be referred to as the “post-processing directory”.
   • You should have already set up SSH keys for GitHub when you configured ASGS, but if not use “git clone https://github.com/StormSurgeLive/richamp-support” instead. You may also need to do some git configuration if you haven’t used it on hatteras yet. Git should prompt you if so. Just follow the instructions.
   • If you ever need to pull down updates to the code in the future, you can do this via “git pull”.
4. Copy the following two NetCDFs from /home/joshua_p/postprocess (Hatteras) or /work/pi_iginis_uri_edu/joshua_port_uri_edu/postprocess (Unity) to your richamp-support directory:
   • gfs-roughness.nc
   • NLCD_z0_RICHAMP_Reg_Grid.nc
5. Copy the following two files from /projects/ees/dhs-crc/dcrowley/c_PWM/b_RIC_TEST (Hatteras) or /work/pi_iginis_uri_edu/joshua_port_uri_edu/postprocess (Unity) to your richamp-support directory:
   • diag_parm.nml
   • windgfdl
6. From within ASGSH run the following:
   • “pip3 install pandas pyproj requests scipy”
   • “export METGET_API_KEY=[URI MetGet API key from step 1]”
   • “export METGET_ENDPOINT=https://api.metget.zachcobell.com”
7. Open your ASGS config file
   • If you don’t know what your ASGS config file is, run “echo $ASGS_CONFIG” via ASGSH.
8. Add "richamp-support/richamp_scale_and_subset.sh" to the front of the POSTPROCESS list and "richamp-support/richamp_scale_and_subset_post_init.sh" to the front of the INITPOST list. (Hatteras only through the end of #8) Also add at a minimum RICHAMP_fort63.nc, RICHAMP_wind.nc, Track.dbf, Track.shp, and Track.shx to the postAdditionalFiles list. createOPeNDAPFileList.sh and $OPENDAPPOST should already be in the POSTPROCESS list, but if not, add those after richamp_scale_and_subset.sh and add another line above that to set OPENDAPPOST=opendap_post2.sh. Save and close the file. The final configuration might look like this:
   • OPENDAPPOST=opendap_post2.sh
   • INITPOST=( richamp-support/richamp_scale_and_subset_post_init.sh )
   • POSTPROCESS=( richamp-support/richamp_scale_and_subset.sh createOPeNDAPFileList.sh $OPENDAPPOST )
   • postAdditionalFiles=( RICHAMP_fort63.nc RICHAMP_wind.nc Track.dbf Track.shp Track.shx )
9. (Hatteras only) Open richamp_scale_and_subset.scr. Make the following changes:
   • Uncomment the "##SBATCH --constraint=hatteras" and "##SBATCH -p lowpri" lines (i.e. change them from ## to #; one # is still needed)
   • Comment out the "#SBATCH -p uri-cpu" line
   • Either update output_dir to a directory to which the output files should be copied, or comment out the relevant cp command if you don't need the files to be copied
10. (Unity only) First, run "module avail matlab" and take note of the available versions. Open richamp_scale_and_subset.scr. If needed, update the Matlab [VERSION] in "module load matlab/[VERSION]" to an existing module version everywhere it occurs in the script. Repeat this step for richamp_scale_and_subset_post_init.scr.
    • The post-processing code has been tested on r2021b and r2022b. If neither of these versions exists, feel free to try another version. Just be aware that you may need to make updates to the relevant .m files if you encounter errors using untested versions of Matlab.
11. Ensure that the output_dir variables in richamp_scale_and_subset.scr and richamp_scale_and_subset_post_init.scr are set appropriately. Both scripts can point to the same folder. That folder should exist, though, and be unique to an ASGS instance so files from different instances never overwrite each other. So, if you're configuring this post-processing code as part of a new instance, you may want to create another output folder and use that as your output_dir. If you do this, make sure to create subfolders within your output_dir for each ENSTORM scenario you configure in your config file (e.g. forecast, veerLeftEdge, veerRightEdge).
12. You are now set up! Just run ASGS as you would normally.
    • If you need to troubleshoot, refer to uri_post.[err/out] and uri_post_init.[err/out], which will be generated in the ASGS scenario directory, and richamp_scale_and_subset.sh.log and richamp_scale_and_subset_post_init.sh.log, which will be generated in the richamp-support folder. Keep in mind that the post_init code runs alongside the forecast, while the other post-processing code runs after the forecast.
    • If you get stuck or find a bug, contact Josh Port (joshua_port@uri.edu).