Remove save_count from NSPostProcessor
Issue #32
resolved
The save_count causes difficulties with restart-code, as currently, data is identified by save_count. I suggest to identify it with timestep instead.
The only place where save_count is used in logic (as far as I can see) is to start storing HDF5-data. This will currently also cause havoc with restart-problems, and can be handled in any number of different ways.
Any objections?
Comments (8)
-
-
reporter All (at least shelve, xml, and hdf5) saved data are identified by save_count. It would be more logic to identify it with timestep or time.
I've already replaced the logic related to save_count on first save of hdf5.
-
Go ahead.
-
timestep is better than time, avoids floating point formatting.
-
reporter Agreed.
-
- changed milestone to 1.3
-
- marked as critical
-
reporter - changed status to resolved
- Log in to comment
Which data is identified by save_count and where?