I have recently started modelling in UKTM for our analysis this year, and I found that the modelling seems not respond to the constraints I put in.
It seems they’re picked up properly, however it’s not working in the model run itself. To give you an example, I’ve put in the constraints I tried in the attachment, and neither of these constraints worked. There were no conflicting constraints anywhere else in the model, no error message or anything, and both constraints were picked up as I could see them in the Browse section, so I’m not sure why they don’t work at all.
I’m wondering if I could get some help from you on that.
I could not spot any issues in the screenshot (apart from the superfluous Cset_CN indexes). Are these constraints defined in a new scenario, such that you could post the DD file (zipped) for that scenario, to see if that reveals something?
If defined properly, you should nonetheless get the User_con values reported for these constraints, and if you see them reported, can you show the reported values?
20-08-2023, 04:37 PM (This post was last modified: 20-08-2023, 09:57 PM by UKTM User.)
Hi Antti,
Thank you for your reply. I've got the DD file (zipped) but it seems too big to upload as an attachment. I've uploaded to OneDrive, and please see the link below.
The reported values for these constraints: HYGL (PHYGEY*) = 0 in all years, HYGL (PHYGNGALQ*) = 919.16 in year 2050, these values remained unchanged from before these constraints were put in.
>I've got the DD file (zipped) but it seems too big to upload as an attachment. I've uploaded to OneDrive, and please see the link below.
Hmm... I asked for the DD file (a single file), where those constraints are defined. But ok, I downloaded all your files from the OneDrive share. However, none of the DD files there contained any trace of those constraints!
The constraints were: UC_H2MRwithCCUS_UP and UC_Electrolysis_LO (I see you have deleted the picture; luckily I had it still in my cache). These constraint names do not appear in any of your model input files (*.DD), or in your results files (*.VD*). So, I conclude that you have chosen not to include those constraints in your model run, which of course explains your issue ("neither of these constraints worked").
I also asked you to show the reportedUser_con values for these constraints.
>The reported values for these constraints: HYGL (PHYGEY*) = 0 in all years, HYGL (PHYGNGALQ*) = 919.16 in year 2050
But you were not defining any constraints named HYGL (PHYGEY*) or HYGL (PHYGNGALQ*); I asked you to show the reported User_con values for UC_H2MRwithCCUS_UP and UC_Electrolysis_LO. However, it is clear that the values you stated cannot be the reportedUser_con values for these constraints, because nothing was actually reported for those constraints. So, I wonder where you have taken e.g. the value 919.16 in year 2050?
(20-08-2023, 10:44 PM)Antti-L Wrote: >I've got the DD file (zipped) but it seems too big to upload as an attachment. I've uploaded to OneDrive, and please see the link below.
Hmm... I asked for the DD file (a single file), where those constraints are defined. But ok, I downloaded all your files from the OneDrive share. However, none of the DD files there contained any trace of those constraints!
The constraints were: UC_H2MRwithCCUS_UP and UC_Electrolysis_LO (I see you have deleted the picture; luckily I had it still in my cache). These constraint names do not appear in any of your model input files (*.DD), or in your results files (*.VD*). So, I conclude that you have chosen not to include those constraints in your model run, which of course explains your issue ("neither of these constraints worked").
I also asked you to show the reportedUser_con values for these constraints.
>The reported values for these constraints: HYGL (PHYGEY*) = 0 in all years, HYGL (PHYGNGALQ*) = 919.16 in year 2050
But you were not defining any constraints named HYGL (PHYGEY*) or HYGL (PHYGNGALQ*); I asked you to show the reported User_con values for UC_H2MRwithCCUS_UP and UC_Electrolysis_LO. However, it is clear that the values you stated cannot be the reportedUser_con values for these constraints, because nothing was actually reported for those constraints. So, I wonder where you have taken e.g. the value 919.16 in year 2050?
Thank you for your reply, it makes sense to me. I have selected this constraint file when running the model, but maybe it was not included in the model run for some reason.
Please see the screenshot in the attachment. The constraint file name containing these two constraints is FES23ST_Hydrogen (the one highlighted).
Sorry that I misunderstood you for the User_con values. I'm wondering where can I find them?
>Please see the screenshot in the attachment. The constraint file name containing these two constraints is FES23ST_Hydrogen (the one highlighted).
Could not see any attachment, where is it? User_con is a reporting attribute. I assume you are familiar with the TIMES reporting attributes, such as Var_Act, Var_FIN, VAR_Fout, etc.?
(20-08-2023, 11:52 PM)Antti-L Wrote: >Please see the screenshot in the attachment. The constraint file name containing these two constraints is FES23ST_Hydrogen (the one highlighted).
Could not see any attachment, where is it? User_con is a reporting attribute. I assume you are familiar with the TIMES reporting attributes, such as Var_Act, Var_FIN, VAR_Fout, etc.?
(20-08-2023, 11:52 PM)Antti-L Wrote: >Please see the screenshot in the attachment. The constraint file name containing these two constraints is FES23ST_Hydrogen (the one highlighted).
Could not see any attachment, where is it? User_con is a reporting attribute. I assume you are familiar with the TIMES reporting attributes, such as Var_Act, Var_FIN, VAR_Fout, etc.?
Sorry I didn't realise that it didn't upload successfully, I've attached it again. Hope you can see it now.
I'll have a look at User_con in attribute section under the Results area.
(21-08-2023, 12:08 AM)Antti-L Wrote: You need to click the icon with green curved arrows at the top part of the Scenario Groups pane, to get the group updated.
I have clicked the icon with green curved arrows at the top, and it worked. I have also found the User_con for these constraints in the attribute section.
