Rem mag nash #2204
Merged
Rem mag nash #2204
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add new realization 'magpie' to module '30_biomass' copying 'magpie_40' and renaming everything. Any changes needed for the new coupling that are module-related (i.e. not in the core) will be done in the new module.
- updating biomass prices and biomass demand - calculating shift factors for supply curves
Introduce new preliminary switch 'cm_MAgPIE_Nash' to activate biomass coupling while still using the old emissions
…les using CSVRead
… it from a csv file (CSVread), since CSVread filled up the memory when it was called in the solve loop, leading to out of memory errors. Added R script that writes the MAgPIE data into a gdx. Add mapping from MAgPIE variables to REMIND parameters.
- core/preloop.gms -> core/presolve.gms - 47_regipol/regiCarbonPrice/datainput.gms -> 47_regipol/regiCarbonPrice/presolve.gms
…oupling with this switch.
…e to core because values are needed earlier
…f MAgPIE iterations sm_magpieIter to trigger the import of magpieData.gdx. Use coupling switch cm_MAgPIE_Nash only to activate the MAgPIE run itself.
Introduce decision and switch when to run MAgPIE Load MAgPIE data only after MAgPIE has run at least once, otherwise use input data. Set some switches only after MAgPIE has run at least one (macSwitch, n2obio).
… across Nash iterations
At the end of the run add content of runtime.log to runstatistics.rda. Remove 'marker' column from GAMS output to runtime.log
…y in first Nash iteration if available
… that is to be continued as input.gdx
Enable processing of multiple gdx files: either to create an individual pdf per run or to plot iterations of mutliple runs into one pdf if runs have been continured
…e same script in script/single
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Purpose of this PR
Please explain your PR here.
Type of change
Indicate the items relevant for your PR by replacing ◻️ with ☑️.
Do not delete any lines. This makes it easier to understand which areas are affected by your changes and which are not.
Parts concerned
Impact
Checklist
Do not delete any line. Leave unfinished elements unchecked so others know how far along you are.
In the end all checkboxes must be ticked before you can merge.
make test) after my final commit and all tests pass (FAIL 0)remind2if and where it was neededforbiddenColumnNamesin readCheckScenarioConfig.R in case the PR leads to deprecated switchesCHANGELOG.mdcorrectly (added, changed, fixed, removed, input data/calibration)Further information (optional)