It should look like this so it works in hp case.
// This is available only after call to reinit.
unsigned int
FEInterfaceValues::get_component(const unsigned int interface_dof_index) const
{
const auto dof_pair = dofmap[interface_dof_index];
if(dof_pair[0] != numbers::invalid_unsigned_int)
The simplest solution seems to be to add a function like this.
// This is available only after call to reinit.
unsigned int
FEInterfaceValues::get_component(const unsigned int interface_dof_index) const
{
const auto dof_pair = dofmap[interface_dof_index];
if(dof_pair[0] != numbers::invalid_u
On 9/14/24 08:04, Praveen C wrote:
unsigned int ii = (i < n_cell_dofs) ? i : i - n_cell_dofs;
const auto c =
fe_face_values.get_fe().system_to_component_index(ii).first;
Praveen:
this makes the assumption that you first have the DoFs from one side, and then
the ones from t
Najwa:
I ran step-22 with Q2^d-Q1 and Q3^d-Q2, and I observed the same behavior.
Additionally, I found that in my code, even when using Q2, these jumps also
appear, though on a smaller scale and in fewer locations.
This brings me to an updated question:
* Is this behavior not significant
Dear all,
I have an important update on the situation.
I ran step-22 with Q2^d-Q1 and Q3^d-Q2, and I observed the same behavior.
Additionally, I found that in my code, even when using Q2, these jumps also
appear, though on a smaller scale and in fewer locations.
This brings me to an updated
