I have received some strange GAMS error code messages that I don't understand, see below and included file. Anyone that can support?
153868 $LOADR MILESTONYR
**** $579
**** LINE 65 INCLUDE C:\VEDA\Veda\GAMS_WrkTIMES\_dd_.dd
**** LINE 55 BATINCLUDE C:\VEDA\Veda\GAMS_SrcTIMES.v4.5.0\setglobs.gms
%1 1
**** LINE 23 BATINCLUDE C:\VEDA\Veda\GAMS_SrcTIMES.v4.5.0\maindrv.mod
%1 mod
**** LINE 94 INPUT C:\VEDA\Veda\GAMS_WrkTIMES\TempTest.RUN
**** 579 Cannot clear a set used as a domain or used in lag/ord operations
154179 $LOADR BLE
**** $579
**** LINE 376 INCLUDE C:\VEDA\Veda\GAMS_WrkTIMES\_dd_.dd
**** LINE 55 BATINCLUDE C:\VEDA\Veda\GAMS_SrcTIMES.v4.5.0\setglobs.gms
%1 1
**** LINE 23 BATINCLUDE C:\VEDA\Veda\GAMS_SrcTIMES.v4.5.0\maindrv.mod
%1 mod
**** LINE 94 INPUT C:\VEDA\Veda\GAMS_WrkTIMES\TempTest.RUN
**** 579 Cannot clear a set used as a domain or used in lag/ord operations
08-02-2021, 06:38 PM (This post was last modified: 08-02-2021, 06:44 PM by Antti-L.)
Good question, Anna!
The partial answer is that you have a GAMS domain violation, which triggers filtering all parameters via a GDX file. But for some reason that does not seem to work correctly under your GAMS 34.2.0 (I guess this is brand new GAMS).
Therefore, the best solution for you now is to fix the domain violation in your model. It seems the commodity 'BFUKER' has not been defined as a commodity. I hope you can find that error in your model.
But as for TIMES, the problem with the latest GAMS, causing the unexpected error, should also be fixed. I will try to see if I can find out why this error arises... I have not seen such with earlier GAMS versions.
08-02-2021, 08:17 PM (This post was last modified: 09-02-2021, 03:20 AM by Antti-L.)
Ok, I tested a bit with GAMS v34.2, and the cause of the problem is that they have changed the output from the GDXDUMP utility. And that happens to be crucial for filtering out any domain violations.
This means that under GAMS v34.2 TIMES will not work with models having domain violations. At least until I can figure out how to fix this issue.
Therefore, if you can use an older GAMS system, I would suggest to use that instead, or make sure that you have no domain violations in your model (albeit often harmless, they may be considered modeling errors anyway).