#1568 Improve the way Ensight files are written handled
The choice currently in WriteFile for Ensight format is for the Coords to use the index_from_mesh_file explicitly (node id given
in Ensight format).
However, currently this index may be ill-suited for efficiency; for instance when the mesh is written after a partition this index isn't changed and the values are far from being in interval [0, Ncoords[.
Therefore, TGeometricElt::SetCoordsList()
is far less efficient, as it first looks in a small range to find the Coords when building the mesh, and if it fails consider the whole one. The small range looked at is based on the assumption the index from mesh file is very close to the actual position of the Coords object within the Mesh - which is obviously not the case for Ensight.
This ticket is clearly not on top of my todo list currently, but if the construction of the mesh takes too much time in some Models (CardiacMechanics uses up Ensight format for its mesh for instance) improving the above behaviour would provide tremendous gain (at a relatively limited cost in development time).