Stress Result in Shells
Moderator: bernd
Forum rules
and Helpful information for the FEM forum
and Helpful information for the FEM forum
Re: Stress Result in Shells
related issue #2873 in case of the reason of the renumbering.
Re: Stress Result in Shells
I think, vtk isn't the problem at 1st place.
Please run ccx and generate a new Calculix_static_results object.
Have a look at plot of max principal stresses. They are looking good.
But after saving and reloading, same plot looks weird.
EDIT: exporting "weird" looking result object to vtk, looks good in paraview
Maybe heap corruption is done while producing result object.
With saving and reloading bad allocs are cleaned out.
Unfortunately vtk runs into this mess if done otherwise.
Please run ccx and generate a new Calculix_static_results object.
Have a look at plot of max principal stresses. They are looking good.
But after saving and reloading, same plot looks weird.
EDIT: exporting "weird" looking result object to vtk, looks good in paraview
Maybe heap corruption is done while producing result object.
With saving and reloading bad allocs are cleaned out.
Unfortunately vtk runs into this mess if done otherwise.
Re: Stress Result in Shells
If I re-run my original file (posted earlier) and try to export the Result as VTK then FC crashes. No different from trying to create a VTK Pipeline
Re: Stress Result in Shells
This indeed doesn't crash, but the results are wrong:bernd wrote: ↑Sun Mar 25, 2018 8:37 pm would you guys do my a favor an try this ...
- load file https://forum.freecadweb.org/download/file.php?id=55290
- recalculate the analysis
- save the file
- close the file
- reopen the file
- create a vtk pipeline from the result object
- it works at least it does for me
Then closing and opening the CalculiX_static_results object again, FreeCAD started to misbehave. Part of the model was gone and zooming out to fit on screen did not work (froze for a while and came back with an empty screen). Could there be something wrong with an array index - trying to access beyond array bounds?
Re: Stress Result in Shells
Here an example of mis-behaviour:
Re: Stress Result in Shells
the resultmesh is renumbered at save and reload, but the node numbers attribute in result object has still the old not renumbered numbers ...
Re: Stress Result in Shells
Poisson ratio fix is in master. git commit 8717edb98
Re: Stress Result in Shells
To export to vtk or to create a vtk pipeline the mesh nodes should not have gaps. Attached simple mesh will crash freecad:
https://github.com/FreeCAD/FreeCAD/blob ... #L446-L455
OS: Debian GNU/Linux 9.4 (stretch)
Word size of OS: 64-bit
Word size of FreeCAD: 64-bit
Version: 0.17.13470 (Git)
Build type: Debug
Branch: master
Hash: 656a669cb0dc3d2d3becf20a5330531233b56834
Python version: 2.7.13
Qt version: 4.8.7
Coin version: 4.0.0a
OCC version: 7.0.0
Locale: German/Switzerland (de_CH)
Code: Select all
import Fem
path = '/home/hugo/Desktop/'
nodes = Fem.FemMesh()
nodes.addNode( 0, 0, 0, 1)
nodes.addNode( 6, 12, 0, 3)
nodes.write(path + 'nodes.vtk')
https://github.com/FreeCAD/FreeCAD/blob ... #L446-L455
OS: Debian GNU/Linux 9.4 (stretch)
Word size of OS: 64-bit
Word size of FreeCAD: 64-bit
Version: 0.17.13470 (Git)
Build type: Debug
Branch: master
Hash: 656a669cb0dc3d2d3becf20a5330531233b56834
Python version: 2.7.13
Qt version: 4.8.7
Coin version: 4.0.0a
OCC version: 7.0.0
Locale: German/Switzerland (de_CH)
Re: Stress Result in Shells
I can confirm the crash but I have no idea why. It happens inside exportFemMeshFaces where it tries to destroy the grid. However, the ref counter is set to three at this point and it shouldn't try to delete it.
Re: Stress Result in Shells
It somehow seams to crash here: https://github.com/FreeCAD/FreeCAD/blob ... s.cpp#L453 If all other following code in exportVTKMesh() is commented ( this one: https://github.com/FreeCAD/FreeCAD/blob ... #L455-L461 ) FreeCAD still crashes ...
https://github.com/berndhahnebach/FreeC ... fb6934c967