Support keywords/language with marker name on mesh filters
In order to facilitate the access on mesh entities (as marked or topological type, i.e elements, boundaryfaces, ....),we can define special keywords that can be used with markedelements(.), markedfaces(.) ,markededges(.) and markedpoints(.) :
-
@elements@: corresponds toelements(mesh) -
@boundaryelements@: corresponds toboundaryelements(mesh) -
@markedelements("toto","titi")@: corresponds tomarkedelements(mesh,{"toto","titi"}) -
@boundaryfaces@: corresponds toboundaryfaces(mesh) -
@internalfaces@: corresponds tointernalfaces(mesh) - ...
Another feature will be support also a small language that allows applying merge, intersect and difference operation.
*@merge(internalfaces,markedfaces("toto")@ : correspond to all internal faces and marked faces called "toto"
*@intersect(boundaryfaces,markedfaces("toto")@ : correspond to boundary faces with marker called "toto"
*@diff(boundaryfaces,markedfaces("toto")@ : correspond to all boundary faces except for markedfaces called "toto"
The delimiter keyword @will be a special character, i.e. a marker will can't have more than one @ character.
This feature will be very useful in Feel++-toolboxes in the json description.
how about using |, in math it is often use to measure something ?
Will "markers":["toto","titi"] still be accepted ?
Also, will it really be elements(mesh) or will it be the elements of the support of the function space associated with the expression ?
@romainhild it's not related to toolbox json format, so you can of course write "markers":["toto","titi"] but the idea is to write also "markers":["toto","@boundaryfaces@"].
And yes, it will support also mesh support (just developers must use the mesh support when we called markedelements), but need a little reflection if make sense
@prudhomm I don't understand, why do you talk about measures?
I would prefer |boundaryfaces| rather than @boundaryfaces@
my point was that | is used in math, eg |Omega|
it's not a measure (or cardinality), it returns a set of entities. This keyword is a delimiter for a special syntax/language interpreted and I think @ is more visible than |
Stale issue message
Stale issue message