One option would be to create a single cell triangulation that matches the reference cell's geometry. Then you can get all of this information easily without having to dig into the inner working of the FEValues and Mapping classes.
J-P On Friday, December 23, 2016 at 11:29:41 AM UTC+1, [email protected] wrote: > > Thanks. I see things clearer now, hopefully. If everything is defined on a > unit cell [0,1]^d, how can I output FEValues quantities in the unit cell > first. From what I understand now, we receive the quantities directly on > the real cell (reference cell). Hence, using fe_values.reinit(cell) we > compute only necessary things depending on the similarity of the current > cell to the unit cell. Am I still able to check the quantities on the unit > cell somehow and than map them to the real cell, or at least output both to > understand more clearly how things work? > > I checked the unit cell coordinates by means of > GeometryInfo<dim>::unit_cell_vertex() and receive the following: > > UNIT CELL COORDINATES > > 0 0 > 1 0 > 0 1 > 1 1 > > But as already mentioned I still have unmapped quantities such as: > > > GAUSS POINT COORDINATES > > -0.57735 -0.57735 > 0.57735 -0.57735 > -0.57735 0.57735 > 0.57735 0.57735 > > From what I understood the shape functions will not change for a standard > FE_Q element, if it is not a Raviart-Thomas element. But shape function > gradients, jacobians, GAUSS points, etc. will change. > > Is it possible now to output unit cell shape function gradients or > quadrature points before they are mapped? > > Kind regards, > Seyed Ali Mohseni > > -- The deal.II project is located at http://www.dealii.org/ For mailing list/forum options, see https://groups.google.com/d/forum/dealii?hl=en --- You received this message because you are subscribed to the Google Groups "deal.II User Group" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
