Posts: 86
Threads: 22
Likes Received: 1 in 1 posts
Likes Given: 8
Joined: Jan 2024
Why the following TFM_UPD doesn't work as a constraint?
~TFM_UPD
TimeSlice LimType Attribute Year AllRegions Pset_PN
INVCOST~2050 2020 *(64/90) TRA_Bus_BEV01
INVCOST~2050 2020 *(64/90) TRA_Bus_PHEV01
INVCOST~2050 2020 *(64/90) TRA_Bus_HEV01
INVCOST~2050 2020 *(64/90) TRA_Mot_ELC1
INVCOST~2050 2020 *(64/90) TRA_Rai_Pas-ELC01
INVCOST~2050 2020 *(64/90) TRA_Rai_Frt-ELC01
INVCOST~2050 2020 *(64/90) TRA_Car_BEV01
INVCOST~2050 2020 *(64/90) TRA_Car_PHEV01
INVCOST~2050 2020 *(64/90) TRA_Car_HEV01
Best,
Xiao
Posts: 1,052
Threads: 41
Likes Received:
16 in 13 posts
Likes Given: 23
Joined: May 2010
Reputation:
16
Because Veda works with a fixed (but evolving) syntax. This will work:
~TFM_MIG
Attribute Year Year2 AllRegions Pset_PN
INVCOST 2020 2050 *0.711111111111111 TRA_Bus_BEV01
Posts: 89
Threads: 17
Likes Received: 0 in 0 posts
Likes Given: 0
Joined: Jul 2010
(29-04-2024, 07:11 PM)[email protected] Wrote: Why the following TFM_UPD doesn't work as a constraint?
~TFM_UPD
TimeSlice LimType Attribute Year AllRegions Pset_PN
INVCOST~2050 2020 *(64/90) TRA_Bus_BEV01
INVCOST~2050 2020 *(64/90) TRA_Bus_PHEV01
INVCOST~2050 2020 *(64/90) TRA_Bus_HEV01
INVCOST~2050 2020 *(64/90) TRA_Mot_ELC1
INVCOST~2050 2020 *(64/90) TRA_Rai_Pas-ELC01
INVCOST~2050 2020 *(64/90) TRA_Rai_Frt-ELC01
INVCOST~2050 2020 *(64/90) TRA_Car_BEV01
INVCOST~2050 2020 *(64/90) TRA_Car_PHEV01
INVCOST~2050 2020 *(64/90) TRA_Car_HEV01
Best,
Xiao
It is because only one year dimension is supported. The best way to think of the update tables is probably as of update queries:
https://support.microsoft.com/en-us/offi...e5ee1e0514
Posts: 86
Threads: 22
Likes Received: 1 in 1 posts
Likes Given: 8
Joined: Jan 2024
(29-04-2024, 09:56 PM)AKanudia Wrote: Because Veda works with a fixed (but evolving) syntax. This will work:
~TFM_MIG
Attribute Year Year2 AllRegions Pset_PN
INVCOST 2020 2050 *0.711111111111111 TRA_Bus_BEV01
Hi!
Sorry just a quick question, could the +1 be used in TFM_UPD table? (I mean, the TFM_UPD could only do multiply calculator?)
Best,
Xiao
Posts: 1,052
Threads: 41
Likes Received:
16 in 13 posts
Likes Given: 23
Joined: May 2010
Reputation:
16
05-05-2024, 12:36 PM
(This post was last modified: 08-05-2024, 07:44 AM by AKanudia.)
TFM_UPD (and MIG) support the four basic operations: +, -, /, and *.
Note that if a value is not prefixed with an operator, then that value is used as is - without operating with the seed value. If you want to use the addition operator then you have to write '+[number] so that the field is formatted as text.
PS: To UPDate with an absolute negative value, write ~-[number].
Posts: 86
Threads: 22
Likes Received: 1 in 1 posts
Likes Given: 8
Joined: Jan 2024
07-05-2024, 11:07 PM
(This post was last modified: 08-05-2024, 07:45 AM by AKanudia.)
(05-05-2024, 12:36 PM)AKanudia Wrote: TFM_UPD (and MIG) support the four basic operations: +, -, /, and *.
Note that if a value is not prefixed with an operator, then that value is used as is - without operating with the seed value. If you want to use the addition operator then you have to write '+[number] so that the field is formatted as text.
PS: To UPDate with an absolute negative value, write ~-[number].
Thank you!