I ended up adding the boundary conditions in the file instead of inside the
program. More handy I guess.
On Fri, Aug 29, 2014 at 9:19 PM, Miguel Angel Salazar de Troya <
[email protected]> wrote:
> I've realized that the error comes from here
>
> dof_id_type last_elem = mesh.n_active_elem
I've realized that the error comes from here
dof_id_type last_elem = mesh.n_active_elem()-1;
mesh.boundary_info->add_side(last_elem,2,0);
Basically I want to add a boundary condition to the top of the last
element. Can I only do it calling it from its processor?
On Fri, Aug 29, 2014 at 8:45 PM,
I have this simple mesh in .xda format:
DEAL 003:003
4 # Num. Elements
10 # Num. Nodes
16 # Length of connectivity vector (Num elements * Num Nodes)
0 # Num. Boundary Conds.
65536 # String Size (ignore)
1 # Num. Element Types. We just have quads, no triangles
5 # Element types in each block.
4 #
