-
Notifications
You must be signed in to change notification settings - Fork 154
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
Disentangle message_ix and ixmp_source #254
Comments
I'm not sure why you think that item 3 depends on item 2? |
I see the relationships as follows:
As the latter point shows, this is somewhat implementation-dependent. |
I would not describe There are a number of additional mapping sets used as flags for GAMS, generally named |
This is good news, then—if the logic is simple and there's no special treatment of any of the categorizations, then it's easy to port.
Okay, thanks for pointing these out. Searching led me to MsgScenario.writeParametersToGDX() where these are defined; this should be the reference for whoever tackles these tasks. |
@francescolovat's question on #275 revealed some additional issues to address/code to be consulted. |
One goal of iiasa/ixmp#182 / #249 was to clarify what core functionality of the message_ix modeling framework currently resides in the Java code of ixmp_source (i.e. behind ixmp's JDBCBackend).
As the name suggests, it is not the task of a storage backend to provide core model/framework logic; this logic should instead live in this repo. (In the current situation, new, non-Java backends would each be forced to re-implement that logic, which would be duplicative and increase points of failure.)
This issue is for:
Pieces
(@khaeru to flesh these out/keep them updated based on discussion below; others feel free to edit)
message_ix.Scenario(..., version='new')
returns a Scenario pre-populated with certain sets and parameters.message_ix.Scenario.cat_list(...)
,.cat(...)
and.add_cat(...)
operate by creating and manipulating related sets namedtype_*
andmap_*
.type_*
andcat_*
mappings #21 could be addressed at the same time.Scenario.toGDX()
writes Scenario data to a GDX file.Scenario.readSolutionFromGDX()
reads the solution (levels of specific variables and marginals of specific equations) from a GDX file. It does not read any structure (i.e., sets) or input data (i.e., parameters).Notes
The text was updated successfully, but these errors were encountered: