Xander
Previously each vtk input would be read/parsed multiple times if it contained multiple needed fields. Now it will read each vtk only once. (per processor)
# Description # Checklist Miscellaneous items that may need to be done when making a PR: - [ ] Documentation related to this PR is up to date (Doxygen format)...
I think it would be overkill to add another field type for adaptive mesh criteria. So I think allowing the postprocess loop to run if it contains a field needed...
Currently, the only way to do this is by increasing the refinement in one direction, but it doesn't work well with AMR. Might need to also be an integer-only type...
Both vtk and raw data
This would save a lot of overhead that would otherwise be needed on the backend like specialized dependencies and avoid trouble with dofhandlers. Similarly to how we have an is_postprocess...