-
Notifications
You must be signed in to change notification settings - Fork 157
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
Mistakes in documentation of the parameters #51
Comments
I came across this while looking for documentation-related issues. The docstring seems to correctly match the definition: message_ix/message_ix/model/MESSAGE/parameter_def.gms Lines 483 to 487 in 154c581
The parameter is used here: message_ix/message_ix/model/MESSAGE/model_core.gms Lines 1701 to 1708 in 154c581
As far as I can tell:
So the definition and description here seem to be correct. Can @OFR-IIASA, @danielhuppmann or someone else confirm this is the right interpretation? |
Hi @ClaraLuisa , have you found other innaccuracies like the one you presented here? |
@khaeru sorry for this edit, but I just tried to change my code to the parameter convention of node | emission | type_tec | year and now the parameter does not make it through to the database instead gives me the error message: KeyError: 'type_emission' |
I'm closing this issue since @khaeru's understanding seems to be correct. As far as I can tell, @francescolovat tried adapting the parameter definition as suggested here, which didn't work. He then reverted the change because it "ha[d] no sense and [was] wrong", so if it is an actual error or if you find any new errors, please create a new issue for them :) |
Some parameters are described inaccurately on http://messageix.iiasa.ac.at/. eg "historical_emission" should be something like:
instead it reads:
The text was updated successfully, but these errors were encountered: