Collection of currently unsupported 4C-Input File features

[c-p-schmidt]

This issue is meant to collect all features that are currently not supported by the 4C-Webviewer to obtain an overview of what is still missing and what could be the next steps to improve it further.

[c-p-schmidt]

• Reading input files that use the rather new feature of directly reading the EXODUS file is not yet supported

[gilrrei]

• Displaying BEAM elements (@davidrudlstorfer @isteinbrecher, since the webviewer is built upon pyvista and FourCIPP, I think meshpy could be interfaced quite well)
• Displaying NURBS

[davidrudlstorfer]

@gilrrei thanks for the ping

We've already discussed this shortly with someone from the webviewer team - MeshPy already supports a pyvista visualization of the beam geometry. Therefore, this should be rather straightforward.

[isteinbrecher]

As @davidrudlstorfer said, converting an existing MeshPy Mesh to vtk/pyvista is not an issue. However, MeshPy currently does not support reading of input files containing beam elements and then converting them to an internal Mesh object. This is not 100% straightforward for certain types of beam elements, but if it is a desired feature to have the pipeline "yaml file -> MeshPy Mesh -> vtk structure for webviewer" this can surely be done.

For NURBS, we use the splinepy library in MeshPy and I think the interal visualisation there is based on vedo which also uses vtk (if I am not mistaken). So displaying NURBS should also be possible.

[dragos-ana]

• Currently, the only functions that can be visualized are of type SYMBOLIC_FUNCTION_OF_SPACE_TIME.
• Input validation in EDIT mode is not available. The input is only validated once the user tries to export the file.