Make PVDReader initialize VTKReaders lazily
What does this MR do?
PVDReader now only stores the paths to VTK files and initializes
VTKReader instances when they are explicitly accessed. This passes effective memory management to the user. Users can choose if missing VTK files should result in exceptions or warnings.
Additionally, the associated time can now be passed to
VTKReader in its constructor.
Why was this MR needed?
PVDReader loads VTKReaders for all referenced files immediately. For large VTK files, and especially for many of them, this can be very costly and even max out the RAM.
Is there something that needs to be double checked?
Can this MR be accepted?
Implemented lazy initialization in
- Initialization of
- Added/Updated documentation
- Pipeline passing
- Squash option set
- Delete branch option set
Added entry to
Assignee: If the Squash option is set, check/update the commit message right before merging!