-
Notifications
You must be signed in to change notification settings - Fork 713
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
testing of step-40 to step-49 #17165
Conversation
tests/examples/step-49.diff
Outdated
88,91c88,92 | ||
< std::ofstream out(filename); | ||
< GridOut grid_out; | ||
< grid_out.write_vtu(triangulation, out); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
only remove this single line
c4dcabd
to
33152d6
Compare
33152d6
to
8f32603
Compare
tests/examples/step-40.diff
Outdated
< const unsigned int n_cycles = 8; | ||
--- | ||
> const unsigned int n_cycles = 3; | ||
662c664 | ||
659c661 | ||
< output_results(cycle); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I thought about this some more and I think we should keep all calls to graphical output.
tests/examples/step-43.diff
Outdated
> // std::cout << " ..." << solver_control.last_step() | ||
> // << " CG iterations." << std::endl; | ||
2161,2162c2170,2171 | ||
< if (timestep_number % 200 == 0) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
keep these
tests/examples/step-44.diff
Outdated
1126c1126 | ||
< output_results(); | ||
--- | ||
> // output_results(); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
and these
tests/examples/step-44.diff
Outdated
--- | ||
> // output_results(); | ||
1543c1543 | ||
< std::cout << " Setting up quadrature point data..." << std::endl; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
why do you remove this?
tests/examples/step-45.diff
Outdated
@@ -0,0 +1,4 @@ | |||
768c768 | |||
< output_results(refinement_cycle); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
keep this
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think you did not address this point
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Got it, thanks! Instead of changing tests/examples/step-45.cc and propagating it via update_diffs, I corrected the step-45.diff directly. Needless to say I called update_diffs later for other reason which reversed step-45.cc to the original state...
tests/examples/step-46.diff
Outdated
< std::cout << " Writing output..." << std::endl; | ||
< output_results(refinement_cycle); | ||
--- | ||
> std::cout << " Writing output..." << std::endl; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
keep these
tests/examples/step-47.diff
Outdated
@@ -0,0 +1,4 @@ | |||
905c905 | |||
< output_results(cycle); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
keep these
tests/examples/step-49.diff
Outdated
91,91c91,92 | ||
< std::cout << " written to " << filename << std::endl << std::endl; | ||
--- | ||
> // std::cout << " written to " << filename << std::endl << std::endl; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
keep this
605d121
to
18d14b4
Compare
Proceeding after #17100, #17084, #17130.
CTests should not write any vtk and, if they output any iteration counts, they should do it with with a range of acceptable answers.