Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Solving a case with multiple timeslice definitions selected #29

Closed
olejandro opened this issue Jan 22, 2024 · 5 comments
Closed

Solving a case with multiple timeslice definitions selected #29

olejandro opened this issue Jan 22, 2024 · 5 comments
Assignees

Comments

@olejandro
Copy link

When a attempting to solve a case with multiple timeslice definitions selected (by accident), I've observed the following behaviour from Veda:

  • no error is thrown;
  • only "> Start" and "> Completed" lines are output to the log window;
  • no dd files are written.

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.

@olejandro
Copy link
Author

Alternatively, one could use the scenario order to overwrite one definition with another and attempt to solve the model anyway...

@akanudia
Copy link
Contributor

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

@deepakgupta256 deepakgupta256 self-assigned this Jan 23, 2024
@deepakgupta256
Copy link
Contributor

deepakgupta256 commented Jan 23, 2024

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?

MultiTimeSlice1
MultiTimeSlice2

@olejandro
Copy link
Author

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.

@akanudia
Copy link
Contributor

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants