-
Notifications
You must be signed in to change notification settings - Fork 113
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
Add Scenario.to_csv() method #300
Labels
Comments
khaeru
changed the title
add to_csv() method to message_ix.Scenario class to overcome limitations of to_excel()
Add to_csv() method to Scenario class to overcome limitations of to_excel()
Apr 1, 2020
Related to #292. |
Here is more complete code that in principle does all that is needed from my perspective, but as I am not fluent in Python there are probably better ways of doing this.
|
3 tasks
khaeru
changed the title
Add to_csv() method to Scenario class to overcome limitations of to_excel()
Add Scenario.to_csv() method
Sep 14, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The to_excel method of the message_ix.Scenario class suffers from size limitations of individual sheets in the xlsx format (maximum of 1048576 rows) when used with large models such as the global MESSAGEix-GLOBIOM model instance. To overcome this limitation…(this limitation, #292, was removed by #309 and #345)It is proposed to add a to.csv() method that exports all sets and parameters to csv files and combines them in a zip archive. Below is a code snippet that exports all parameters of a model instance to csv files and can thus serve as a starting point for such a method.
The text was updated successfully, but these errors were encountered: