Enhancing dirichlet routine API

[stefanhenneking]

Currently, the only information the user can work with (input arguments) in the dirichlet routine are the element (middle node) number Mdle, the physical coordinates of the point X(3) being evaluated, and the Icase number encoding an element's support for particular physics variables.

• This setup does not let the user know which face on the boundary X is actually on. That is, the user only has the physical location available to decide which Dirichlet data to set. It may in some cases be helpful to have the actual face number available on which X is being evaluated. Note that dirichlet is also called from hpvert (H1) and hpedge (H1,Hcurl) routines which would need to specify a face accordingly if changing the API.

• For H(div) and H(curl) vector-valued Dirichlet data, the user is expected to pass the full vector-valued solution even though only the normal and tangential components are actually needed. While this is convenient for manufactured solutions, it may not be a good way to specify Dirichlet data for unknown problems when only the normal or tangential component data is known. In that case, to correctly specify a vector-valued Cartesian solution, the user may need the normal vector which could be passed as an input to the dirichlet routine.