I was wondering if FE::reinit() in fe_boundary.C for sides and edges
should/could force reinitialization when qrule->shapes_need_reinit() is
true, as is done in FE::reinit() in fe.C. I'm attaching a simple patch
to this email that makes this change.
Thanks,
-- Boyce
Index: src/fe/fe_boundary.C
===================================================================
--- src/fe/fe_boundary.C (revision 4857)
+++ src/fe/fe_boundary.C (working copy)
@@ -159,6 +159,9 @@
// initialize quadrature rule
qrule->init(side->type(), side_p_level);
+ if(qrule->shapes_need_reinit())
+ shapes_on_quadrature = false;
+
// FIXME - could this break if the same FE object was used
// for both volume and face integrals? - RHS
// We might not need to reinitialize the shape functions
@@ -254,6 +257,9 @@
// initialize quadrature rule
qrule->init(edge->type(), elem->p_level());
+ if(qrule->shapes_need_reinit())
+ shapes_on_quadrature = false;
+
// We might not need to reinitialize the shape functions
if ((this->get_type() != elem->type()) ||
(edge->type() != static_cast<int>(last_edge)) || //
Comparison between enum and unsigned, cast the unsigned to int
------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense.
http://p.sf.net/sfu/splunk-d2dcopy1
_______________________________________________
Libmesh-devel mailing list
Libmesh-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/libmesh-devel
