-
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
MetaCode brainstorming #241
Comments
I think that this is a good model to follow, but I suggest to implement it step by step. The first PR should be the |
The second PR should be a |
@danielhuppmann sounds like a sensible approach to me |
@GretchenSchowalter, can you take a first stab at this? Please look at this tutorial to better understand the "meta" indicators: https://pyam-iamc.readthedocs.io/en/stable/tutorials/pyam_first_steps.html |
@danielhuppmann, I'd say we can close this, right? |
Closing, with a follow-up at #270 |
Following our discussion earlier, I'm sketching out some ideas for a
MetaCodeList
.I think it's easiest to start at what the yaml file is supposed to look like:
the three above examples illustrate some of the use cases that I can see, listing them in order:
true
andfalse
, defaulting tofalse
Downscaling*
, in which case, however, it is required.Looking at this again @danielhuppmann I'll retract my previous suggestion of making the entries in
allowed_values
MetaCodes
as that seems too complicated and not every entry in the sampleMetaCodeList
even featuresallowed_values
.It's probably better to translate the above structure into something like:
then we'd have a
MetaCodeList
to hold a list ofMetaCodes
.The text was updated successfully, but these errors were encountered: