-
Notifications
You must be signed in to change notification settings - Fork 3
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
Add support for global aerosol DA in JCB #33
Conversation
mass_fraction_of_dust005_in_air, mass_fraction_of_sea_salt001_in_air, | ||
mass_fraction_of_sea_salt002_in_air, mass_fraction_of_sea_salt003_in_air, | ||
mass_fraction_of_sea_salt004_in_air] | ||
datapath: ./bkg |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Since the idea (in general) is to have absolute flexibility on the JCB side I wonder if this (there are other examples elsewhere too) could be replaced with a variable? Say {{aero_bkg_datapath}} for example, then have aero_bkg_datapath: ./bkg on your GDASapp side? Then there is no evidence of global workflow assumptions about path structure in JCB. Someone could pull this YAML into another environment without having to modify the YAML.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yep, I can do that.
What the title says. Depends on: NOAA-EMC/jcb-gdas#33 NOAA-EMC/jcb-algorithms#5
Add in templates so that global aerosol DA can use JCB to generate YAML configuration for the variational application + B matrix supporting executables.