-
Notifications
You must be signed in to change notification settings - Fork 114
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
Export scenario to gdx #259
Comments
Is it possible to get an older version of ixmp? Because if the possibility to export a scenario to gdx is deprecated I would prefer to have an older version to be able to do that. |
@DIUANA , thanks for raising this issue. We'll check this. Meanwhile, you can use the |
@khaeru, Previously, there were two methods of |
Sorry about this! We didn't have any indication (e.g. a test, or documentation) that they were used for that purpose, so didn't hesitate to change them. @DIUANA #243 is in progress and will be merged shortly, probably today. After that, the correct way to use the internal methods to write to file will be:
This is what is done in We need to have a more general discussion about the I/O user interface for 3.0, since there are many possibilities. So I will target this issue there.
Always possible. Read the documentation for |
Many thanks guys. I will check by tomorrow or next week if I ll be able to apply the function. |
This topic was mentioned in the MESSAGEix weekly meeting on 03 Nov 2022. At the moment, there is a possibility to read the solution from GDX using
|
Hi. I would like to know how to export the scenario to a gdx file in order to debug a scenario?
In the previous version the function to_gdx was available but it is not working in the latest release.
I tried to take advantage from the backend functions but they are demanding about some dependencies I guess
it returns: 'Scenario' object has no attribute 'jindex'
Does ixmp still have a simple function to generate gdx file withou solve the scenario?
The text was updated successfully, but these errors were encountered: