the difference between UC_RHSRTS and UC_RHSRTS~0

[Lee]

Hello,can someone help me to understand the  difference between UC_RHSRTS and UC_RHSRTS~0. I see both of them means to give a absolute value to enable the capacity buildup to start. But in one model I see it have different value.

[Antti-L]

I am not a VEDA expert, but as there seem to be no responses from the VEDA support team, please find below my layperson attempt to help a bit with that VEDA syntax.

I think it is well explained in the documentation, Part IV, and some more detailed information about the underlying TIMES details can be found in Part II.

UC_RHSRTS defines right hand side values (for the default year, unless a Year column is filled in) for user constraints (for those by region, by period and by timeslice), and UC_RHSRTS~0 defines interpolation/extrapolation (IE) options for those values.  The tilde "~" can be used under VEDA as a separator for specifying index labels for attributes in value column headers of FI_T and UC_T tables. The label '0' is a special label referring to the year index in TS (time series) attributes. But as you know, in reality there is no year 0 in the Anno Domini (AD) calendar year system. Therefore, the '0' label has been reserved for a special purpose, which is to act as a placeholder for the IE options.

[VictorG]

I have a question related to ~ character.

I want to add a row in my runfile with a string containing a ~. Veda stops reading at the ~ and skip everything after. Is there a way to deactivate ~ and keep it just as text ?

[Antti-L]

It would be possible by using a trick with a system environment variable, but I am sure the VEDA support or @KanORS-AssistGPT can point out a VEDA solution. However, please note that the gdx file name in LPOINT should not include the extension (.gdx).

[AKanudia]

I am glad you are using parameteric scenarios

Veda splits the contents of Other_Indexes field on "~". We can make it do that only for the attributes that actually carry multiple indexes in that field. For immediate relief, you can do a dedicated Ref run that is named without a "~". Of course, my suggestion will not work if you are trying to do this in a dynamic way where multiple parameteric scenarios are being used as LPOINT.

[VictorG]

Thank you for the replies. I changed manually the name of the input files for this time but I would like to use a dynamic way in the future where parametric scenarios are used as reference.

I was thinking of using a placeholder and a script to change to a tilde in all run files but this manual change of reference name is simpler.

[AKanudia]

I confirm that this issue will be fixed in the upcoming release. Next week, hopefully.