Francesc Verdugo

From the user perspective when visualizing a FEFunction: ```julia # Default options (like now) writevtk(trian,"trian",cellfields=["uh"=>uh]) # Custom options options = VtkOptions(compress=false,ascii=true) writevtk(options,trian,"trian",cellfields=["uh"=>uh]) ```

Idem for `createvtk`

Hi @urbainvaes ! The FE functions in Gridap can be evaluated at any point you want. However, only a set of practical cases are exposed via the high-level API, but...

>it seems that I should first figure out the cell in which my physical point [1, 1] is? Yes, this is the part that is not implemented now in gridap....

> `valuetype` is a mandatory keyword argument in the `PLagrangian` FE space constructor > > ``` > FESpace( reffe=:PLagrangian, conformity=:L2, valuetype = Float64, order = 1, model = model) >...

In any case, I will not use `valuetype` for referring to the type of the components. I would use something like `componenttype`. That is either define `componenttype=Float64` + `fieldtype=:vector`, or...

> 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. `scalartype`...

Perhaps `comptype` (for component type)?. In any case, I would not expose this to the users for the moment. So we are not in a hurry for deciding this now

In Julia parlance, this is specifically called `eltype`. But, perhaps it is a bit confusing since we have the concept of "reference finite ELement"

I have just realized that the constructor for `RaviartThomasRefFE(p:: Polytope, order::Int)` has not any argument for the value type (or the component type depending on the criterion we chose). The...