-
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
Sanity-check the config? #373
Comments
There is also the case of having empty entries in the lists in the stratigraphy, e.g. MyFormation:
stratigraphic: True
name: My Fm. Top
alias:
- MyFormation
- OtherAlias
- # <-- PROBLEM!
stratigraphic_alias:
- Some GP. Top
- SomeOther GP. Base
- # <-- PROBLEM! ---> This will currently export with |
It could be an option/possibility to create a utility script for doing this as well. Could be useful for debugging and setup.
|
Is this reasonable to close when we have fully moved to Pydantic validation? |
Yes, that sounds right |
Closed in lieu of having completed the move to Pydantic which does such validation. |
In an asset, the _stratigraphy block from the
global_variables.yml
was written like this:...with an empty entry for
alias
. After being consumed throughfmu-config
, it ended up like this:This lead to this failure in fmu-datio:
This is a copy/paste error which we may encounter again. Should there be some sanity checks of the config which will give more informative error messages? (This could also be done in fmu-config.)
The text was updated successfully, but these errors were encountered: