Veda2.0 Released!

ACT_EFF in TIMES and VEDA Attributes

Antti has just made me realise that Veda interprets commodities as CGs for ACT_EFF in case no input in other_indexes is specified. I can see that this is not reflected in TIMES and VEDA Attributes where Other_Indexes appears to be a mandatory input for ACT_EFF and there is no indication that Commodity can be used instead.

Amit, are there any other TIMES attributes that are treated similarly and could TIMES and VEDA Attributes facility in Veda be updated to reflect this?

All commodities are in fact CGs, and the current behaviour is in my view logical and user-friendly. The CG index is mandatory, but it can be specified in several ways (which is in fact true already for strict commodity indexes). However, I admit having had some influence on the design, which apparently now causes some confusion to you.  On the other hand I am glad that until now, you have nonetheless had no problems with this design, have you?  Blush 

Other similar attributes include all those that do not have a commodity index, but only a single CommGrp index, such as PRC_ACTFLO and FLO_BND. I think it would become unnecessarily cumbersome if the user would always have to add the CommGrp (or Other_Indexes) column for using these parameters (or to play with the value column headers, which may not be a good option), even though the CG would be well specified by the commodity specified on the table row.
Thanks for sharing the details Antti! I personally have 2 issues with the current behaviour:
1) Lack of transparancy: i.e. behaviour is different from what one would expect by looking at TIMES and VEDA Attributes facility.
2) Error handling: no way to tell whether a user really meant to specify single commodity CG or forgot to specify ACT in Other_Indexes.

Before this I had an impression that TIMES attribute inputs had to be explicit (except for clearly specified defaults in TIMES and VEDA Attributes facility), while many of the Veda attributes were focusing on reducing the burden for the user (e.g. IRE_PRICE vs COST). It seems the distinction is not that clear.
I agree that this behavior is not evident in the Attribute master, but the rule is quite clear - as Antti has pointed out: for attributes that have a single CommGrp index and do *not* have a Commodity index, Commodity will be used as CommGrp *IF* CommGrp is not specified.

Possibly Related Threads…
Thread Author Replies Views Last Post
  The potential mistake exists in the EU-TIMES 11 447 09-05-2024, 03:42 PM
Last Post: wnijs
  GDX diff fails to find GAMS in VEDA vincedh 2 237 19-04-2024, 06:41 PM
Last Post: vincedh
  Veda online not solving. Getting veda 2.0? frangb99 0 138 17-03-2024, 11:52 PM
Last Post: frangb99
  VEDA Run Manager Module UgurHalden 1 288 21-02-2024, 05:14 PM
Last Post: Ravinder
  Optimization problem: TIMES code caicedoeng 1 279 12-02-2024, 11:32 AM
Last Post: Ravinder
Photo Installing VEDA in a server without internet acess sergio.vargas.cbba 1 219 06-02-2024, 04:24 PM
Last Post: Ravinder
  Capacity units in gdx/dd files vs veda iris 14 4,194 03-01-2024, 08:04 PM
Last Post: Antti-L
Question VBA code in Veda input files AKanudia 11 1,890 29-12-2023, 09:50 AM
Last Post: AKanudia
  Submit TIMES models to GAMS Engine NicoKoenig 5 1,102 02-10-2023, 04:54 PM
Last Post: Antti-L
  Is there a way to adjust to the VTrun.cmd file generated when pressing solve in Veda? kristofferand 22 7,149 22-08-2023, 07:32 PM
Last Post: VictorG

Forum Jump:

Users browsing this thread: 1 Guest(s)