GitLab

#1668 Now there is an exception in case a CoordsMatching interpolator input data aren't valid. The exception class has been moved in FEltSpace library, as it's from there the exception needs to be thrown and OperatorInstances is not yet defined when FiniteElementSpace is dealt with.

#1668 Set up the tests which triggers asserts in FromCoordsMatching when there are invalid data in the Lua file. Now these case must be addressed and return the newly minted dedicated exception.

#1668 Set up a new test which illustrate the issue (when an invalid component configuration is chosen an assert is met whereas it should clearly be handled by an exception).

#1669 - #1673 Now there might be several CoordsMatchingFile in a same InputData and they may be interpreted in oth directions. I need however to write the tests to ensure all is working as expected.

#1673 InputData: extend InterpolationFile so that there may be several in the Lua file. Not completely done up till the end: InterpolationFile::mesh_pair is not yet used as some hardcoded stuff is still there.å

#1672 Modify the interpolation file input data so that it is now a section rather than a leaf, which a template parameter. We did only half the way here: in the call the index is currently harcoded.

#1672 Keep moving initialization steps from GodOfDof in the helper facility which does it layer by layer for each GodOfDof.

#1672 Start splitting GodOfDof::Init(): steps to initialize the output directories and the finite element spaces are now addressed in the InitAllGodOfDof facility which does so for all the GodOfDof at once.

#1671 Add a function which returns the parallelism strategy from a Lua input file. It handles gracefully the case no Parallelism block are in the associated input_data.

#1669 FromCoordsMatching interpolator: modify its prototype to avoid using the interpolation file input data.

#1670 Introduce a new utility to find a \a FEltSpace given only its unique id, without knowing its GodOfDof. It is only for internal use...