Santiago Badia

It would be nice to implement Nedelec elements on tetrahedra/triangles. But due to time restrictions, it is not in my shortlist. If @WenjieYao wants to develop it, it would be...

@WenjieYao I have updated the link. Now it should work. We are working on the Piola transformations from the reference to the physical space, so the last part (not discussed...

It is needed here, when we want to exploit symmetry https://github.com/gridap/Gridap.jl/blob/28dd80b2ad2c099a85c030f4d6670552f8a2fdb5/src/Algebra/SymSparseMatrixCSR.jl#L33

By the way, if you think that docstrings can be added/improved in the process, more than welcomed! I know that there are parts that are poorly documented.

What you are asking is possible, but not standard in finite element methods. Usually, in finite element methods, you evaluate the solution in the mesh nodes, and you would do...

Yes, we can do it and add, e.g., one case in which the user defines the array of points. @fverdugo In order to provide a more general evaluation of FE...

It is already implemented. If you use it in your example, you should get the values on the nodes of each cell.

Hi @urbainvaes , Thanks for the interest in Gridap. In the comment you point out, I was saying that the standard way to evaluate FE functions was cellwise, since FE...

Ok, in this case, I would probably think about using `fieldtype` with values `:scalar`, `:vector`, `:tensor`, or a number such that the field will be a 0-tensor. Mandatory keyword arg...

As soon as we distinguish the two concepts, it is OK to me. What about `numbertype` with `:Float64` , `:ComplexF64` or whatever number type in Julia you like.