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

FEPointEvaluation: Remove unit_points member, access them through MappingInfo instead #14926

Merged
merged 2 commits into from Mar 25, 2023

Conversation

bergbauer
Copy link
Contributor

As suggested in #14809 (comment)

@kronbichler
Copy link
Member

/rebuild

@kronbichler kronbichler merged commit f36b3bc into dealii:master Mar 25, 2023
11 checks passed
Comment on lines -956 to +973
const bool precomputed_mapping = mapping_info_on_the_fly.get() == nullptr;
if (precomputed_mapping)
{
unit_points =
mapping_info->get_unit_points(current_cell_index, current_face_number);

if (update_flags & update_values)
values.resize(unit_points.size(), numbers::signaling_nan<value_type>());
if (update_flags & update_gradients)
gradients.resize(unit_points.size(),
numbers::signaling_nan<gradient_type>());
}
if (!is_reinitialized)
reinit(numbers::invalid_unsigned_int);
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@gassmoeller Could this be the problematic change which leads to #14984 ? Could you try to call FEPointEvaluation::reinit(numbers::invalid_unsigned_int) manually after NonMatching::MappingInfo::reinit()?

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

Successfully merging this pull request may close these issues.

None yet

2 participants