Closed olejandro closed 9 months ago
Alternatively, one could use the scenario order to overwrite one definition with another and attempt to solve the model anyway...
I won't be comfortable making all the assumptions needed to have a successful run in this case, but we can certainly issue a clear message. Thanks for testing this case.
@deepakgupta256
We attempted to solve a case with Scenario group having TimeSlice definition in two Regular Scenarios and got the following detailed error message popup.
Did you not receive the messages outlined below? Or is your case different from what we are currently testing?
Thanks for taking a look at it @deepakgupta256. I do not get the error message; also in my case it says "Completed" instead of "Completed with error". I use localhost version 3.0.2.
I am able to reproduce the behaviour (i.e. no error message and "Completed" instead of "Completed with error") on this model by adding A_SYS_SAD_1TS
to NoMitigation group and solving No_Mitigation case.
The message was inadvertently suppressed in some cases. The non-fatal error thrown due to missing TS def in SysSettings has also been addressed in version 3.0.3.
When a attempting to solve a case with multiple timeslice definitions selected (by accident), I've observed the following behaviour from Veda:
I think it is reasonable, that the no attempt is made to solve the model when multiple timeslice definitions are selected in a scenario group. It would be very helpful to warn the user about it though.