27-05-2020, 09:11 PM (This post was last modified: 27-05-2020, 09:12 PM by NeilGrant.)
Hi there,
I have been trying to apply a policy which reduces final energy consumption in industry by different amounts across my 15 regions in TIAM.
I'm attaching the scenario file which I am using to do this, which attempts to use UC_COMCON to do this.
This file syncs correctly in the model, and when looking at the constraint in VEDA_FE all seems to be OK. But the model terminates the run without solving. I'm attaching the LST file - which reports an error code 172 - Element Redefined.
Does anyone know what the issue is here? It appears I am defining something (a coefficient? the UC_RHSRT?) multiple times and this is causing errors. But it's not clear to me where this is, and how I might go about fixing it.
I'm using
VEDA_FE: 4.5.828
TIMES Source Code: V4.27
Microsoft Office 365
(27-05-2020, 09:11 PM)NeilGrant Wrote: Hi there,
I have been trying to apply a policy which reduces final energy consumption in industry by different amounts across my 15 regions in TIAM.
I'm attaching the scenario file which I am using to do this, which attempts to use UC_COMCON to do this.
This file syncs correctly in the model, and when looking at the constraint in VEDA_FE all seems to be OK. But the model terminates the run without solving. I'm attaching the LST file - which reports an error code 172 - Element Redefined.
Does anyone know what the issue is here? It appears I am defining something (a coefficient? the UC_RHSRT?) multiple times and this is causing errors. But it's not clear to me where this is, and how I might go about fixing it.
I'm using
VEDA_FE: 4.5.828
TIMES Source Code: V4.27
Microsoft Office 365
All the best,
Neil
See here for LST file - apologies it did not attach in previous post
27-05-2020, 09:39 PM (This post was last modified: 27-05-2020, 09:40 PM by Antti-L.)
Yes, the reason seems to be that you appear to be using too long UC names.
The "element redefined" error is caused by the dummy commodities VEDA has created, appending the UC constraint names with "_" or "-" , but the total length appears to get truncated at 32 characters. I guess your version of VEDA may have a 32 character limit for commodity names. Try making the UC names shorter (at most 30 chars).
Neil, you could also reimport this scenario after turning off dummy imports for UCs under user options - import settings.
I see that your UC names happen to be exactly 32 char.
Curious, that you chose to embed the region in UC names... any particular reason why you did not did not use the region index of UC_RHSRT for this? And your interpolation options may not be working because the values have been specified for UC_RHSRTS and the interpolation options are for UC_RHSRT.
Note that a more robust and simpler specification for this UC would be CSET_SET=NRG and CSET_CN=IND*. You don't need any PSET cols as UC_COMCON only has a commodity index.
Hi Amit and Antti,
Thanks for your comments. Either reducing the length of the UC_Name, or turning off dummy imports for UC's fixed this issue, and the file is now syncing and running correctly.