Dear John,
thanks for your reply.
I’m attaching a simple test with 2 elements in which I define a system with a
single variable using first order elements of l2_lagrange family.
I initialize the variable so that each degree of freedom stores its own ID.
If I use write_discontinuous _exodusII(), t
On Fri, Feb 10, 2017 at 2:43 PM, Rossi, Simone wrote:
> Dear John,
> thanks for your reply.
> I’m attaching a simple test with 2 elements in which I define a system
> with a single variable using first order elements of l2_lagrange family.
> I initialize the variable so that each degree of freedo
On Fri, Feb 10, 2017 at 9:11 AM, Rossi, Simone wrote:
> Dear Roy,
> thanks for your reply.
> I was worried about the ordering because the exported solution did not
> make sense. It seemed to apply the boundary conditions to the wrong
> elements.
> I learned that the global ordering is general dif
Dear Roy,
thanks for your reply.
I was worried about the ordering because the exported solution did not make
sense. It seemed to apply the boundary conditions to the wrong elements.
I learned that the global ordering is general different for different
fefamilies, but everything is consistent.
I
On Thu, 9 Feb 2017, Rossi, Simone wrote:
> Additionally I noticed something wrong in the assembly.
> When I use LAGRANGE fefamily my global rhs vector (for a 2D elasticity
> problem) looks like this
>
> u_x_point0
> u_y_point0
>
> u_x_point1
> u_y_point1
>
> .
> .
> .
>
> u_x_pointN
> u_y_point
Dear all,
I’m trying to implement a DG formulation for solid mechanics using linear
elements.
I’m currently using the following strategy:
I define my variables as MONOMIALS but in the assembly I pretend my FEType is
LAGRANGE.
This gives me the correct values of the shape functions on the edges.
