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 was quite surprised when running a case that out like this on standard out stop after some time:
Restart file written for report step XXX/YYY, date = DD-MMM-20XX 00:00:00
Newton its= 6, linearizations= 7 (1.1sec), linear its= 18 (1.8sec)
...
Starting time step 8, stepsize 0.634895 days, at day xxxx.x/yyyyyy, date = 11-XXX-20XX
Starting time step 9, stepsize 0.634895 days, at day xxxx.x/yyyyyy, date = 11-XXX-20XX
This is the last output (even the summary at the end is misssing) for a case that is running much longer. I know that this because of the limit for INFO messages,.
I think this quite unfortunate, because there is no way to tell whether the simulation is still running unless one looks and monitors the PRT file. At least on clusters this might not always be possible.
I was actually about to kill the run but thankfully got the idea to look at the PRT file before.
Is this behavior really what we intended?
The text was updated successfully, but these errors were encountered:
The limit was set somewhat arbitrary, maybe influenced by similar limits in other simulators, but I would not be opposed to setting no limit for info(), or just increasing it 10x.
bska
changed the title
No output tostandard out of long running cases because of message limit for informational messages
No output to standard out of long running cases because of message limit for informational messages
Feb 23, 2024
I was quite surprised when running a case that out like this on standard out stop after some time:
This is the last output (even the summary at the end is misssing) for a case that is running much longer. I know that this because of the limit for INFO messages,.
I think this quite unfortunate, because there is no way to tell whether the simulation is still running unless one looks and monitors the PRT file. At least on clusters this might not always be possible.
I was actually about to kill the run but thankfully got the idea to look at the PRT file before.
Is this behavior really what we intended?
The text was updated successfully, but these errors were encountered: