Replies: 2 comments 3 replies
-
Yes, it should be initialized in the constructor. It's an oversight on my part, I'll add a fix in one of our upcoming PRs. Fortunately, the only place |
Beta Was this translation helpful? Give feedback.
3 replies
-
diff --git a/src/serac/numerics/functional/functional.hpp b/src/serac/numerics/functional/functional.hpp
index d4a8222b..b6ec900f 100644
--- a/src/serac/numerics/functional/functional.hpp
+++ b/src/serac/numerics/functional/functional.hpp
@@ -202,7 +202,7 @@ public:
*/
Functional(mfem::ParFiniteElementSpace* test_fes,
std::array<mfem::ParFiniteElementSpace*, num_trial_spaces> trial_fes)
- : test_space_(test_fes), trial_space_(trial_fes)
+ : update_qdata(false), test_space_(test_fes), trial_space_(trial_fes)
{
for (uint32_t i = 0; i < num_trial_spaces; i++) {
P_trial_[i] = trial_space_[i]->GetProlongationMatrix(); |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I am looking at a LiDO run under valgrind, and valgrind is indicating that update_qdata is uninitialized. Should Functional's constructor initialize update_qdata to false? It only appears to be referenced in a handful of places. Based on what I see in the solid_functional, it looks like the default value should be false, but I am just guessing.
serac/src/serac/numerics/functional/functional.hpp
Line 516 in 6550835
Beta Was this translation helpful? Give feedback.
All reactions