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
extend distributed_compute_point_locations #15101
extend distributed_compute_point_locations #15101
Conversation
053a158
to
9b767ed
Compare
const double tolerance = 1e-10, | ||
const std::vector<bool> & marked_vertices = {}, | ||
const bool enforce_unique_mapping = true); |
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 guess the different ordering of the parameters in comparison to the one of the internal function is a bit annoying but we cannot change that.
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 was thinking about the same thing. I think even if we could change it without problems within deal.II
(what I am not sure about), it might break user code. Thus, I refrained from this.
/rebuild |
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.
Looks good to me, apart from documentation issues.
…ocations Co-authored-by: Martin Kronbichler <martin.kronbichler@uni-a.de>
c845900
to
886935d
Compare
/rebuild |
I want to use
distributed_compute_point_locations
in combination withenforce_unique_mapping=false
. Since this function just calls the internal one, the needed changes are just to forward the arguments. I also addedmarked_vfertices
to the function signature to be able to specify it as well.@peterrum