Veda2.0 Released!


Time Series Ignored
#1
TimeSeriesIgnored_Debugging.Log is created whenever I try to run a case where I change efficiency of a particular process.
I use the following file to change the efficiency: Scen__DEBUGGINGERRORS.zip. It contains changes to two processes EZPCOA110 and EZCCGT110. Although the same approach is used to both of them, the change of efficiency is ignored only in case of EZCCGT110. Can anybody explain why?

The only significant difference I could find between the two processes is that year2 has a value of "1" for the initial efficiency value in case of EZCCGT110; year2 is "null" in case of EZPCOA110.

Grateful for any help...
Olexandr



Attached Files
.txt   TimeSeriesIgnored_Debugging.Log.txt (Size: 4.21 KB / Downloads: 1)
.txt   Errors_Olexandr_BalykRisoe_DTU.txt (Size: 5.19 KB / Downloads: 0)
.zip   Scen__DEBUGGINGERRORS.zip (Size: 7.8 KB / Downloads: 1)
Reply
#2
I am afraid that you have bumped into an undocumented feature of VEDA: If Year2 is set to "1" for a parameter in some scenario, the corresponding times series cannot be overriden by any scenario, unless you set the "1" flag into the Year2 field also in the scenario, which is supposed to change the values.

You can set the Year2 field to "1" by putting into the Year column e.g. "2010-1" instead of just "2010". Note also that in this case you cannot change individual data points of the time series, but you must specify the entire time series.

I hope this helps.
Antti
Reply
#3
Thanks a lot Annti! It works. Clap

I also noticed that one has to use ~TFM_INS and that it is not possible to use ~TFM_UPD. A log file with the ignored time series is created anyway, but this time I could see that the ignored time series were the ones that I wanted to substitute.

Many, many thanks!
Olexandr
Reply
#4
Most probable reason is that UPD has access to only those values that come from alphabetically inferior scenarios.
For example, values that come from Scen_B can be UPDated in Scen_C but they will not be seen in Scen_A. However, inserts are available for update in the same scenario.
Reply


Possibly Related Threads…
Thread Author Replies Views Last Post
  time variant emission coefficient dgchoi 5 12,398 26-06-2023, 04:09 PM
Last Post: Antti-L
  SHARE-I/O for all process and all time horizon ejin 7 3,462 08-03-2023, 10:55 AM
Last Post: AKanudia
  Problems to sync a small model with 8736 time-slices Pernille.S 21 36,400 28-05-2020, 12:01 AM
Last Post: AKanudia
  Time stepped algorithm -demand projection canismajoris 7 8,205 18-05-2020, 08:39 PM
Last Post: Antti-L
  Tips for reducing syncing time of SysSettings? Pernille.S 2 5,139 14-11-2019, 02:19 PM
Last Post: Pernille.S
  Very long sync time kogexo 10 15,398 30-10-2019, 07:57 PM
Last Post: kogexo
  auxiliary input of time commodity ignored Anita Prajapati 5 8,411 25-10-2019, 07:42 PM
Last Post: Anita Prajapati
  Synchronising takes too long time MohammedAbiAfthab 4 8,058 10-06-2019, 02:35 PM
Last Post: MohammedAbiAfthab
  Defining Time-Slice AF in a scenario files Anna (AKR) 1 4,118 10-05-2019, 04:17 PM
Last Post: AKanudia
  Solve Time Under SO2,NOX,PM2.5 Taxes mbr1818 4 7,873 23-03-2019, 10:24 PM
Last Post: Antti-L

Forum Jump:


Users browsing this thread: 1 Guest(s)