16-10-2019, 02:32 PM
Thank you for the good news.
My investigation has revealed some additional information: The issue was apparently being triggered by the domain violations in your model. Although there were only a few domain violations (related to the undefined process UE-ETH1100-BIO), and these were basically unrelated to the serious problems that were then manifested, the bug in those GAMS versions mentioned above caused incorrect processing of the model topology, when the model had the domain violations. But I tested also by removing the 10 FLO_EMIS parameters defined for UE-ETH1100-BIO, and the problems then no longer occurred!
It would be good modelling practice to check for any domain violations and eliminate them from the model (you can see the GAMS warnings in the listing file). But I know that many TIMES models (perhaps even the majority I have had the chance to have a look at) do have some domain violations, at least during model and/or scenario development and testing phases. Therefore, I would think that this GAMS bug may actually have been affecting many users.
My investigation has revealed some additional information: The issue was apparently being triggered by the domain violations in your model. Although there were only a few domain violations (related to the undefined process UE-ETH1100-BIO), and these were basically unrelated to the serious problems that were then manifested, the bug in those GAMS versions mentioned above caused incorrect processing of the model topology, when the model had the domain violations. But I tested also by removing the 10 FLO_EMIS parameters defined for UE-ETH1100-BIO, and the problems then no longer occurred!
It would be good modelling practice to check for any domain violations and eliminate them from the model (you can see the GAMS warnings in the listing file). But I know that many TIMES models (perhaps even the majority I have had the chance to have a look at) do have some domain violations, at least during model and/or scenario development and testing phases. Therefore, I would think that this GAMS bug may actually have been affecting many users.