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

Streamlining #5

Open
3 tasks
pernak18 opened this issue Mar 16, 2021 · 2 comments
Open
3 tasks

Streamlining #5

pernak18 opened this issue Mar 16, 2021 · 2 comments
Assignees

Comments

@pernak18
Copy link
Owner

pernak18 commented Mar 16, 2021

We need to make the process easier for end users after I'm done developing. Action items:

  • single template for by-band and broadband (band dimension, flux_* vs. band_flux_*)
  • SW and LW templates need to be available -- maybe the code to generate them?
  • diffuse flux (and net diffuse) inclusion would be nice (right now we do it in the g-point reduction code)
@pernak18 pernak18 self-assigned this Mar 16, 2021
@pernak18
Copy link
Owner Author

regarding the template used as input into the driver, here is an abridged version of my current protocol:

  1. grab separate single-band and broadband templates in /project/projectdirs/e3sm/pernak18/reference_netCDF/g-point-reduce/
  2. input single-band file from item 1 in the Garand RRTMGP driver in this repository (working version from Dec 2020, not the most recent commit in garand_atmos)
  3. run with broadband file from 1 in the same executable as 2
  4. generate a shortwave template, which has other input parameters in the netCDF
  5. repeat steps 2 and 3 for the SW

this is a bit tedious somewhat difficult to remember, plus it hinders our examination with the profz and statz plotz, because our output flux netCDFs from steps 3 and 5 are only correct in the broadband (by-band fluxes could conceivably be correct as well, but then broadband fluxes would be wrong).

i'm working on a workaround that will stitch together correct by-band results from 2 with correct broadband results from 3 (and will probably do the same thing for the SW) so we have a central reference file with both, which we do not have right now.

@pernak18
Copy link
Owner Author

more commentary on the template in another issue:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant