Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Postprocessor: unify component selection for MeshAdaptor/VTUOutput/Quantities into the `Postprocessor #159

Open
tamiko opened this issue Jul 30, 2024 · 0 comments

Comments

@tamiko
Copy link
Member

tamiko commented Jul 30, 2024

This is long overdue: Currently, we are selecting and extracting components by hand separately in each of these classes. We should avoid this wasted effort and code duplication and simply handle everything in the Postprocessor class.

This probably needs to be done with some sort of "subscription" design from the consumer classes so that the postprocessor only computes and extracts values when needed. Another tricky part will be the speed requirements for the Quantities::accumulate() call because it gets called after every time step...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant