Skip to content
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

Weird behavior - automatic sets generation #326

Closed
DIUANA opened this issue May 25, 2020 · 1 comment
Closed

Weird behavior - automatic sets generation #326

DIUANA opened this issue May 25, 2020 · 1 comment

Comments

@DIUANA
Copy link

DIUANA commented May 25, 2020

Code sample or context

Expected result

map_tec_time and map_tec_act set as:
X, node, year time=[SUMMER, SPRING, WINTER, FALL]

Problem description

Dear I hope you are fine and safe.

Let me try to explain this issue properly.

I have 4 sub time periods: [SUMMER, SPRING, WINTER, FALL]
and a parent time which is YEAR

I have a technology X that works on the sub-annual time, however, if I set a relation XR associated to this technology X when IXMP generates the gdx file it creates a map_tec_time and a map_tec_act sets (that are generated automatically) with time year also associated to the technology X.

Therefore, instead of get the result for map_tec_time as I was expecting, such as:
X, node, year time=[SUMMER, SPRING, WINTER, FALL]
I got
X, node, year time=[SUMMER, SPRING, WINTER, FALL, YEAR]

If I try to pass those sets to the model manually I get the following error message:
com.gams.api.GAMSException: Symbol map_tec_time exists already

Also if I do not set a relation associated to the technology it generates the result as expect, withou the year in the aforementioned sets.

How can I deal with this issue?

All the Best and thanks in advance.

Versions

'2.0.0'

Output of ixmp show-versions
<!--
  Run one of the following and paste the results here:
  - 'ixmp show-versions' in a terminal, or
  - 'import ixmp; ixmp.show_versions()' in a Python interpreter.
-->
@khaeru
Copy link
Member

khaeru commented Apr 28, 2022

This appears to be the same situation/error reported at iiasa/message_ix#348, so closing as a duplicate.

@khaeru khaeru closed this as completed Apr 28, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants