-
Notifications
You must be signed in to change notification settings - Fork 27
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
Format of Region, Scenario names, Variable names and Descriptions #138
Comments
Thanks for these suggestions - we have started to compile such guidelines at https://docs.ece.iiasa.ac.at/standards.html (rendered from a GitHub repo at https://github.com/iiasa/ece-docs) for lack of a better place. Feel free to open a PR there! |
Follow-up (because I tried to implement this): Agree to make
|
If we remove it from the descriptions, variables, scenario names and units, that would be a good step forward (or actually sufficient for the code I have in mind). |
I wonder whether it would make sense to define some standards for the naming of variables, model regions, scenario names and also descriptions.
;
and"
in descriptions, as they mess with the usual format PIK uses for exchange this data. It doesn't seem to be a big deal, but useful for us (there are a few uses of"
which might be just removed 1, 2, 3),
in region names (not like REMIND dies it) such that the quoting of region names can be avoided, same for scenario names. I also would prefer not to have special characters in scenario names.Might be worth thinking about it
The text was updated successfully, but these errors were encountered: