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
I think the message about starting the simulation "#===Simulation Start===" is too short. The simulation trace is often long lines, so I think it's better for this log to be longer. For example, "=====================Simulation Start=====================".
This will allow for a clearer separation of the snippy output at generation time from the model output at run time. Now it is difficult to find the moment when the simulation begins, since it merges with the trace.
This can be reproduced with my model which can be downloaded from here.
Here, the size of the message "#===Simulation Start===" is much smaller than the size of the trace and the snippy output. I think they should be separated better.
The text was updated successfully, but these errors were encountered:
Hello!
I think the message about starting the simulation "#===Simulation Start===" is too short. The simulation trace is often long lines, so I think it's better for this log to be longer. For example, "=====================Simulation Start=====================".
This will allow for a clearer separation of the snippy output at generation time from the model output at run time. Now it is difficult to find the moment when the simulation begins, since it merges with the trace.
This can be reproduced with my model which can be downloaded from here.
Snippy command line:
Where
layout.yaml
looks like:Library
libSnippyRVdash.so
must be located in the directory with the snippy, or you must specify the absolute path to it in thelayout.yaml
.The output of the program is as follows:
Here, the size of the message "#===Simulation Start===" is much smaller than the size of the trace and the snippy output. I think they should be separated better.
The text was updated successfully, but these errors were encountered: