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

Namelist parameters and many physical constants don't really belong in NDSL #32

Open
oelbert opened this issue Mar 18, 2024 · 0 comments
Labels
enhancement New feature or request

Comments

@oelbert
Copy link
Collaborator

oelbert commented Mar 18, 2024

Is your feature request related to a problem? Please describe.
Namelist elements and default values are specified in ndsl/namelist.py which means that model developers have to esid ndsl code when implementing a scheme with new runtime parameters in pyFV3 or pySHiELD. Similarly if a scheme needs a new physical constant (like a heat capacity at a new temperature) it gets implemented in ndsl/constants.py. Moreover it is very unclear how to set up experiments with different values, such as simulating Earth with a smaller radius.

Describe the solution you'd like
namelist.py should specify a minimal, extensible namelist class that can be inherited in Pace, pyFV3, and pySHiELD namelists.
For constants.py ¯\(ツ)

@oelbert oelbert added the enhancement New feature or request label Mar 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant