You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If I run Makita and the simulations end with an error without finalizing the pipeline, I would like to see a log with the error(s) printed in the parent folder. Currently, the CLI simply stops and closes, and you have to re-run the simulation to find out what error caused the interruption.
The text was updated successfully, but these errors were encountered:
I'm not in favor of that. It doesn't sound like a good practice for CLI interfaces.
This happens when users run the BAT file directly, isn't it? There is no problem when running the bat file from the command line. I think we should encourage users to run from the cli (documentation).
I agree that running from the CLI would be best. Another option would be to add a pause after the batch files, that could be added very easily during the batch script conversion step.
If I run Makita and the simulations end with an error without finalizing the pipeline, I would like to see a log with the error(s) printed in the parent folder. Currently, the CLI simply stops and closes, and you have to re-run the simulation to find out what error caused the interruption.
The text was updated successfully, but these errors were encountered: