‘year’ set on scenario != ‘year’ set in GAMS
Open
Nobody has claimed this yet.
- Dominant language
- Jupyter Notebook
- Stars
- 150
- Forks
- 178
- Avg merge
- 17h 32m
- Merged PRs (30d)
- 2
Description
Perhaps this is impossible to fix at the moment, but I ran into many many headaches before realizing that there is not a one-to-one mapping between s.set('year') and the set year in a GAMS gdx file. Moreover, the set year in a MESSAGE GDX file is not consistent with the set year in a MACRO GDX file. It would be nice to harmonize these..
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Compare how s.set('year') maps to the year set in GAMS GDX files, including the differences between MESSAGE and MACRO GDX files. Clarify the intended harmonized behavior and define what consistency across these sets would mean before assessing implementation options.
Written by the indexing model from the issue text.
Assessment
- Domain
- data
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100