Improve FieldSaver and CheckPointer code
The current code for implementing FieldSavers and CheckPointers is difficult to maintain and extend. The issue of data output in general and how to better implement FieldSavers etc. should be discussed and implemented, coincident with a major version release (e.g. v3.0).
Blueprint information
- Status:
- Not started
- Approver:
- Dion Weatherley
- Priority:
- Medium
- Drafter:
- None
- Direction:
- Needs approval
- Assignee:
- None
- Definition:
- Discussion
- Series goal:
- None
- Implementation:
-
Not started
- Milestone target:
- None
- Started by
- Completed by
Related branches
Related bugs
Sprints
Whiteboard
This blueprint links with the following Answers threads:
https:/
https:/
Feature requests related to FieldSaver and/or CheckPointer improvements:
(1) ability to specify output precision via python API (including scientific and no. of decimal places)
(2) greater support for wall-particle interaction FieldSavers
(3) support for TriMesh and LinMesh related FieldSavers
- TriMesh is partially supported
(4) a more consistent way of specifying the output format for field savers, i.e. get away from the current "RAW", "RAW_WITH_ID" and so on and specify the saved data directly, choosing from ID, pos, rad, "field"
(5) enable multiple checkpointers. Can be useful for taking snapshots with different frequency during different parts of a simulation
