Veda2.0 Released!


Definition of multiple timeslice trees in a single model
#1
Dear Amit, 

VEDA 2.0 is a great tool. 

Would it make sense to have also a possibility to flexibly select different timeslice tree definitions before the run, in a way similar with the flexibility we have to select different definitions of the periods?  

For instance, the TAG ~TimeSlices which is currently supported only in the system settings file could also be available in scenario files? Then the user can flexibly select the active timeslice tree for the run by selecting the appropriate scenario file. Or, perhaps this functionality can be implemented in a different and more efficient way.  

This could reduce the maintenance effort for users needing to maintain the same model with different timeslice trees for different purposes.  

Thanks a lot, 
Vangelis
<font color=BLUE><em>The best way to predict the future is to create it. </em></font> <img src='smileys/smiley24.gif' border='0' align='middle' />
Reply
#2
Thanks for the confirmation Smile

Yes, what you suggest is possible, and we plan to implement it soon. User will be responsible to ensure that all parameters defined at the timeslice level are consistent with the active timeslice definition. One way to ensure this is to have all such parameters in a single file, along with the timeslice definition.
Reply
#3
(20-04-2021, 12:54 PM)AKanudia Wrote: Thanks for the confirmation Smile

Yes, what you suggest is possible, and we plan to implement it soon. User will be responsible to ensure that all parameters defined at the timeslice level are consistent with the active timeslice definition. One way to ensure this is to have all such parameters in a single file, along with the timeslice definition.

Hi Amit, 

Thank you for considering this option too.  

Yes, the user should be responsible in organising the scenario files in such a way that this feature will work without conflicts, e.g. like as you suggested in your email before. 

Best wishes, 
Vangelis
<font color=BLUE><em>The best way to predict the future is to create it. </em></font> <img src='smileys/smiley24.gif' border='0' align='middle' />
Reply
#4
Hi Amit & Evangelos

Just wondering, if it would also be possible to work with this in combination with the fix investment idea Lisa suggested in https://forum.kanors-emr.org/showthread.php?tid=850. So it would be possible to run the model at e.g. 30 time slices with investment decisions, but then change the time slice setup to hourly resolution but with fixed investments (possible just for one year)?

Best
Mikkel
Reply
#5
Maybe you did not notice from that thread that the "fix investment idea" was never considered.

Instead, the facility for fixing new capacities to a previous solution was implemented already in TIMES v4.4.2, over a year ago. So, that can indeed be used, and I don't see why it couldn't be used regardless of the timeslice configuration.  But it is only related to capacities and not investment costs, which may thus be different.
Reply
#6
(28-09-2021, 07:11 PM)Antti-L Wrote: Maybe you did not notice from that thread that the "fix investment idea" was never considered.

Instead, the facility for fixing new capacities to a previous solution was implemented already in TIMES v4.4.2, over a year ago. So, that can indeed be used, and I don't see why it couldn't be used regardless of the timeslice configuration.  But it is only related to capacities and not investment costs, which may thus be different.

Thanks Antti.
Reply


Forum Jump:


Users browsing this thread: 2 Guest(s)