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'd like to investigate the cause of the long run times in some/many/all of the HELICS examples and see if there's something simple we can do to reduce the runtimes.
The text was updated successfully, but these errors were encountered:
I've done some initial testing showing that changing the logging level to "INFO" cuts the runtime in half and dramatically reduces the size of the log files. I would be in favor of making this change across the board with a few caveats:
We will need to be consistent across the examples about which messages get logged at which levels so that user's have a consistent experience.
It would be good to be able to change the logging level on the command line.
Right now, when I change the log level, the examples don't always run to completions (see this Github issue).
I'd like to investigate the cause of the long run times in some/many/all of the HELICS examples and see if there's something simple we can do to reduce the runtimes.
The text was updated successfully, but these errors were encountered: