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.
This migration concerns the following keys:
These keys stem from a time when the fertilizer sector was not explicitly modelled for every dataset. This was the case in datasets where
has_aggregated_chemical_industry = true
.When these aggregate inputs are set in combination with the individual inputs of the fertilizer and other chemical sector however, the demand from the fertilizer sector goes to 0. This is not intentional and can present problems for scenarios where these inputs have been set.
Since all datasets currently have an explicit fertilizer sector and the aggregate inputs are not accessible in the frontend, we want to remove the aggregate inputs from all recent scenarios (>2021). We can then remove the inputs from ETSource altogether.
@noracato when I check the presence of each slider in migratable scenarios I get 682, 1564 and 1564 cases. However, when I run the migration I get 7663 migrated scenarios. Could you look into this to see where this difference comes from?
Merging is on hold until cleared by ENTSO.