-
Notifications
You must be signed in to change notification settings - Fork 14
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
Remove dimensions
implicit default from DataStructureDefinition
#422
Remove dimensions
implicit default from DataStructureDefinition
#422
Conversation
dimensions
implicit defaultdimensions
implicit default from DataStructureDefinition
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.
A few more minor comments, then good to be merged from my side!
* Each "dimension" to be used for validation (default: *variable* and *region*) must | ||
have its own sub-directory in the *definitions* folder. The dimension names usually | ||
follow the column names of the IAMC data format. | ||
* Each "dimension" to be used for validation must have its own sub-directory in |
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.
Is this still true? So if we only import variables from an external repo, do we need a definitions/variable
folder?
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.
I was wondering how to rewrite this clearly and succinctly. With this PR, if dimensions are imported from external repos, it's only necessary to specify the subfolders if no dimensions are specified in nomenclature.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.
Good to merge from my side.
Removes implicit default dimensions
["region", "variable"]
fromDataStructureDefinition
, instead defaulting todefinitions
subdirectories.Running workflows without
definitions
subdirectories is also possible as long asnomenclature.yaml
sets the dimensions and respective external repos (seetest_mapping_from_external_repository
's configuration file).For project validation,
dimensions
defaults to either those innomenclature.yaml
or todefinitions
subdirectories (without either, it fails).