Veda2.0 Released!


TFM_UPD could not be input
#1
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
Reply
#2
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
Reply
#3
(29-04-2024, 07:11 PM)xiao.li8@mcgill.ca 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
Reply
#4
(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
Reply
#5
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].
[+] 1 user Likes AKanudia's post
Reply
#6
(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!
Reply


Possibly Related Threads…
Thread Author Replies Views Last Post
  Batteries input capacity constraint juan.correalaguna@vito.be 5 722 05-04-2024, 06:00 PM
Last Post: Antti-L
  Constraining input shares LucasD 3 776 04-01-2024, 09:33 PM
Last Post: LucasD
  Rounding all input data MikkelBosack 4 1,637 04-01-2024, 01:40 PM
Last Post: VictorG
Question VBA code in Veda input files AKanudia 11 2,287 29-12-2023, 09:50 AM
Last Post: AKanudia
  INPUT OUTPUT attributes Lukas 1 825 03-11-2022, 04:58 AM
Last Post: AKanudia
  Defining dynamic endogenous emission factor for output commodity based on input Simon Andersen 4 2,546 17-02-2022, 01:05 AM
Last Post: Simon Andersen
  migration to VEDA2.0- TFM_UPD Lukas 3 3,323 04-02-2021, 02:09 PM
Last Post: Antti-L
Question ERRORS IN INPUT DATA/COMPILE JozefO 13 11,523 23-12-2020, 08:49 PM
Last Post: AKanudia

Forum Jump:


Users browsing this thread: 1 Guest(s)