-
Notifications
You must be signed in to change notification settings - Fork 15
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
Allow cfg
files to be more machine-independent
#425
Comments
Shouldn't the |
yes, but there are a variety of derived paths. E.g.,
|
I see. I think those should just be hard-coded at this point, and the |
I think some users may want to use completely different dataset paths though.
I think we're officially supporting the same machines -- the ones on Unified. |
I see, in that case carry on. It doesn't sound like you need any input from me, but ping me if so. |
@forsyth2 : in most cases (99%+), a user will want to use the standard observational datasets for The paths should be set transparently, either in zppy or E3SM Diags with the |
@forsyth2 : here is an example of an e3sm_diags section from a zppy configuration file on chrysalis:
We want this to work properly without having to specify For other tasks, the main offending parameter is
which should support specifying directly a filename
with |
Another parameter would be
which a user should have the option of omitting completely with There are other machine dependent parameters such as |
Re: diags observations paths -- I'm working on automating those parameters. Re: mapping files -- this was completed in #381. Re:
|
Observation paths are automated in #426. |
https://github.com/E3SM-Project/zppy/blob/main/tests/integration/utils.py#L125 -- can we reduce the number of parameters that are machine-specific?
For example, the diags paths could be consolidated into a single parameter.
The text was updated successfully, but these errors were encountered: