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
Add a version of timing_step_37 using MGTransferMF #15842
Conversation
1513eb7
to
b66c288
Compare
I have rebased this PR. |
"solve", | ||
"matvec_double", | ||
"matvec_float", | ||
"matvec_float_coarser"}}; |
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.
This test has a significant overlap with the already existing timing_step_37
. Would you mind to condense the measurements down to the values we are actually interested in?
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 agree, we should only measure the setup of the transfer and the solver time. Everything else should be equivalent I believe.
std::tuple<Metric, unsigned int, std::vector<std::string>> | ||
describe_measurements() | ||
{ | ||
return {Metric::timing, 4, {"setup_transfer", "solve"}}; |
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.
Done!
@tamiko any last opinions on this PR? If not, I will merge tomorrow. |
depends on #15794