Uwe 31677a3e25 [FEM] use unique result mesh name ...

- it is a long-standing bug that the name of the result mesh object is not unique. For example for a frequency analysis you get for every result the same object "ResultMesh". When now a "ResultMesh" object is deleted because one result mode object should be deleted, all result modes loose their mesh.
To fix this, use a unique name for the mesh object.

2023-03-16 06:19:10 +01:00

..

__init__.py

…

convert2TetGen.py

FEM: python code formatting

2022-07-12 15:04:26 +02:00

exportNastranMesh.py

Fix trivial typos

2021-10-06 07:54:05 +02:00

importCcxDatResults.py

remove Python2 code

2023-03-04 17:51:43 -06:00

importCcxFrdResults.py

[FEM] use unique result mesh name

2023-03-16 06:19:10 +01:00

importFenicsMesh.py

remove Python2 code

2023-03-04 17:51:43 -06:00

importInpMesh.py

remove Python2 code

2023-03-04 17:51:43 -06:00

importPyMesh.py

fix commit

2023-03-04 17:51:43 -06:00

importToolsFem.py

FEM: Fix typo

2022-06-02 10:49:55 -05:00

importVTKResults.py

remove Python2 code

2023-03-04 17:51:43 -06:00

importYamlJsonMesh.py

remove Python2 code

2023-03-04 17:51:43 -06:00

importZ88Mesh.py

remove Python2 code

2023-03-04 17:51:43 -06:00

importZ88O2Results.py

remove Python2 code

2023-03-04 17:51:43 -06:00

readFenicsXDMF.py

…

readFenicsXML.py

…

writeFenicsXDMF.py

…

writeFenicsXML.py

…