Replies: 2 comments 3 replies
-
Indeed that output fell through the cracks, the info is still computed though... Maybe we can make it one of the history outputs. WALL_TIME is the average time per iteration, so multiply the final value by the number of iterations +1 to get the total. |
Beta Was this translation helpful? Give feedback.
-
I think it would be great to output it to the history. I guess an alternative I can see at the moment is to add the Regarding WALL_TIME, this changes every iteration. Would summing it be sufficient? Or would this be less than the actual run time? Thanks and regards, |
Beta Was this translation helpful? Give feedback.
-
Dear Team,
Firstly, thanks for the latest SU2 update! I noticed on migrating from v6 to v7 that the maximum residual location is no longer displayed in the screen output. Is there any way to get this information back or exported to the history file? I tied looking through the
SU2_CFD -d
options but it didn't look like there was an output for this. I found it to be quite useful for debugging mesh issues.Secondly, is there an equivalent to the v6 wall clock Time(min) output for the history file? I tried
WALL_TIME
but this gave the individual iteration times instead. I assume that cumulatively adding these output might give an approximation of the runtime but may be less than the actual time due to I/O and overhead?Thanks and kind regards,
Tim
Beta Was this translation helpful? Give feedback.
All reactions