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 #196

Open
Rombur opened this issue Jul 8, 2016 · 3 comments
Open

Postprocessor #196

Rombur opened this issue Jul 8, 2016 · 3 comments
Labels

Comments

@Rombur
Copy link
Collaborator

Rombur commented Jul 8, 2016

Clean up post-processor to output solution.

@Rombur Rombur added the ready label Jul 8, 2016
@dalg24
Copy link
Collaborator

dalg24 commented Dec 8, 2016

@Rombur Would you comment that issue? #242 added an inspector that can trigger the post processor to write the solution to a file. What is the next action?

@Rombur
Copy link
Collaborator Author

Rombur commented Dec 8, 2016

The post-processor is not tested and I have no clue if it actually works. The inspector just output the mesh because it's what I needed. It also calls the post-processor but that is legacy code that you didn't want to lose and it has never been tested.

@Rombur
Copy link
Collaborator Author

Rombur commented Dec 8, 2016

Just to be clear on what the clean up is about. We decided to break the Postprocessor class in multiple classes. The problem with the current class is that Postprocessor needs to compute some quantities before we can start a simulation, i.e., it is not only a postprocessor.

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

No branches or pull requests

2 participants