INTEGRATION_ReopenTimestpFilesAfterHowManyCycles

*.timestep-Files close and reopen again after how many cycles (debug reasons)

On the cluster, the permanently opened file units of the *.timestep-files get sometimes in conflict with the frequent reopening of these files if FPM_CurveMonitor is used. Try to check, if re-opening can avoid this trouble. On the other hand, keeping the file units open in MESHFREE leads to better performance, especially on slow file systems (like the ITWM-one)
This item is referenced in: