Veda2.0 Released!


A question about UC_RHSRT~0
#1
I want to ask a question about "UC_RHSRT~0" in Regular Scenario. What's the meaning of "UC_RHSRT~0" here? And based on what should I set the value of "UC_RHSRT~0"? I couldn't find a exact explanation from the official learning materials of ETSAP. What's more, in the official learning materials of ETSAP, the words "UC_RHSRTS~0" appear, and there is also a place where "UC_RHSTS~0" appears. What do these two represent respectively?



           
Reply
#2
It is UC_RHSRTS~0 in the first documentation example (not UC_RHSRT~0), and so I refer to that below.

I would say the meaning of UC_RHSRTS~0 is already explained in the second screenshot from the documentation: "owing to interpolation rule (5) specified in the UC_RHSRTS~0 column" So, the value(s) under the column having the header UC_RHSRTS~0 define interpolation rules for the corresponding time-series instances of the attribute UC_RHSRTS, which are being defined.

The use of the tilde ~ is only a VEDA feature, so such does not exist in the TIMES syntax. The VEDA developers may help you with that syntax, if it has not been explained in the VEDA documentation. But the UC_RHSRTS attribute and the IE (interpolation/extrapolation) options are TIMES features, and their meanings are explained in the documentation, Part II. Likewise, the UC_RHSTS and UC_RHSRT attributes are fully explained there.
Reply
#3
(07-07-2023, 09:22 PM)Antti-L Wrote: It is UC_RHSRTS~0 in the first documentation example (not UC_RHSRT~0), and so I refer to that below.

I would say the meaning of UC_RHSRTS~0 is already explained in the second screenshot from the documentation: "owing to interpolation rule (5) specified in the UC_RHSRTS~0 column" So, the value(s) under the column having the header UC_RHSRTS~0 define interpolation rules for the corresponding time-series instances of the attribute UC_RHSRTS, which are being defined.

The use of the tilde ~ is only a VEDA feature, so such does not exist in the TIMES syntax. The VEDA developers may help you with that syntax, if it has not been explained in the VEDA documentation. But the UC_RHSRTS attribute and the IE (interpolation/extrapolation) options are TIMES features, and their meanings are explained in the documentation, Part II.  Likewise, the UC_RHSTS and UC_RHSRT attributes are fully explained there.
Thanks for your reply! I have found the default value of UC_RHSRTS is 10 in the documentation, Part II. [font="PingFang SC", Arial, "Hiragino Sans GB", STHeiti, "Microsoft YaHei", "WenQuanYi Micro Hei", sans-serif]Does this mean that I have no problem filling in 10?[/font]
Reply
#4
> I have found the default value of UC_RHSRTS is 10 in the documentation, Part II.

No, it is not the default value of UC_RHSRTS in general, it is only the default value of UC_RHSRTS~0 (i.e. the interpolation/extrapolation option for UC_RHSRTS).

> Does this mean that I have no problem filling in 10?

Filling in 10 is fine, if that is indeed the interpolation/extrapolation rule what you want.  But as it is already the default, it does not make much sense practically: In that case you would, in my view, be slightly better off without filling in any value, because the only impact of filling in 10 would be a small increase in the database size (as compared to not filling it in).
Reply
#5
(09-07-2023, 04:27 AM)Antti-L Wrote: > I have found the default value of UC_RHSRTS is 10 in the documentation, Part II.

No, it is not the default value of UC_RHSRTS in general, it is only the default value of UC_RHSRTS~0 (i.e. the interpolation/extrapolation option for UC_RHSRTS).

> Does this mean that I have no problem filling in 10?

Filling in 10 is fine, if that is indeed the interpolation/extrapolation rule what you want.  But as it is already the default, it does not make much sense practically: In that case you would, in my view, be slightly better off without filling in any value, because the only impact of filling in 10 would be a small increase in the database size (as compared to not filling it in).
Thanks for your reply! You explained it very clearly. What's more, if I fill in 5 or 15, what will be the impact on my model?
Reply
#6
> What's more, if I fill in 5 or 15, what will be the impact on my model?

The options are all explained in the doumentation, Part II, Section 3.1.1 Inter- and extrapolation of user input parameters.

  Option 5: Interpolation and forward extrapolation; Applies to: All
  Option 15: Interpolation migrated at start, forward extrapolation; Applies to: Bounds, RHS

The direct impact is as described above, the difference between 5 and 15 being that with the option 15 migration is additionally applied to the first model period having a data point. "Migration" is explained in the documentation as follows: "Migration means that data points are interpolated and extrapolated within each period but not across periods." So, for example, with both options UC_RHSRTS will be fully interpolated between the data points and then extrapolated forwards from the last data point. But with option 15 the first data point is additionally migrated to the Milestone year of the period where it is located (if that Milestone year does not fall inside the range of data points). The difference is thus subtle, but may be quite important in some cases: Compared to option 5, the option 15 may cause an additional constraint to be generated for the first model period having a UC_RHSRTS data point. Any UCRTS user constraints are generated only for those Milestone years that have a UC_RHSRTS value defined (after interpolation/extrapolation).
Reply
#7
(09-07-2023, 08:24 PM)Antti-L Wrote: > What's more, if I fill in 5 or 15, what will be the impact on my model?

The options are all explained in the doumentation, Part II, Section 3.1.1 Inter- and extrapolation of user input parameters.

  Option 5: Interpolation and forward extrapolation; Applies to: All
  Option 15: Interpolation migrated at start, forward extrapolation; Applies to: Bounds, RHS

The direct impact is as described above, the difference between 5 and 15 being that with the option 15 migration is additionally applied to the first model period having a data point. "Migration" is explained in the documentation as follows: "Migration means that data points are interpolated and extrapolated within each period but not across periods." So, for example, with both options UC_RHSRTS will be fully interpolated between the data points and then extrapolated forwards from the last data point. But with option 15 the first data point is additionally migrated to the Milestone year of the period where it is located (if that Milestone year does not fall inside the range of data points). The difference is thus subtle, but may be quite important in some cases: Compared to option 5, the option 15 may cause an additional constraint to be generated for the first model period having a UC_RHSRTS data point. Any UCRTS user constraints are generated only for those Milestone years that have a UC_RHSRTS value defined (after interpolation/extrapolation).
Thanks for your reply! I already understand the interpolation problem. [font="PingFang SC", Arial, "Hiragino Sans GB", STHeiti, "Microsoft YaHei", "WenQuanYi Micro Hei", sans-serif]I have another question about NewTechs, which has been posted on the forum. So far, no one has replied to me. Please answer my question when you have time. The link is as follows:[/font]https://forum.kanors-emr.org/showthread.php?tid=1282
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)