Stress Result in Shells

About the development of the FEM module/workbench.

Moderator: bernd

User avatar
HarryvL
Posts: 941
Joined: Sat Jan 06, 2018 7:38 pm

Re: Stress Result in Shells

Postby HarryvL » Sat Mar 24, 2018 10:00 am

Thanks Bernd.

On the topic of changing material parameters: I take CalculixSteel as a basis. If I then type 0.0 in the dialog box for Poisson's Ratio and exit the material object dialog, the value will be reset to 0.3 upon return to the dialog. If I reduce it to 0.0 with the dial then it will get set to 0.1 upon return. That's why I manually change it - just to be sure. PS: A Poisson's ratio of 0.0 is perfectly acceptable from a physical point of view.
User avatar
bernd
Posts: 7301
Joined: Sun Sep 08, 2013 8:07 pm
Location: Zürich, Switzerland

Re: Stress Result in Shells

Postby bernd » Sat Mar 24, 2018 11:20 am

strange ... setting poissons ratio to 0.0 should surely be possible. I will have a look at this one too.
User avatar
bernd
Posts: 7301
Joined: Sun Sep 08, 2013 8:07 pm
Location: Zürich, Switzerland

Re: Stress Result in Shells

Postby bernd » Sat Mar 24, 2018 9:41 pm

HarryvL wrote:
Sat Mar 24, 2018 10:00 am
Thanks Bernd.

On the topic of changing material parameters: I take CalculixSteel as a basis. If I then type 0.0 in the dialog box for Poisson's Ratio and exit the material object dialog, the value will be reset to 0.3 upon return to the dialog. If I reduce it to 0.0 with the dial then it will get set to 0.1 upon return. That's why I manually change it - just to be sure. PS: A Poisson's ratio of 0.0 is perfectly acceptable from a physical point of view.
next PR will have a workaround. https://github.com/berndhahnebach/FreeC ... diff=split

The material task panel really needs to be recoded but that's another story ...
User avatar
HarryvL
Posts: 941
Joined: Sat Jan 06, 2018 7:38 pm

Re: Stress Result in Shells

Postby HarryvL » Sun Mar 25, 2018 8:16 am

Thanks Bernd.

The VTK pipeline and export work well for solid elements and "Beam Shell Result Output 3D" set to FALSE. It looks like an isolated problem for 3D Shells (and beams?) now.

RHS_Plastic_14kN_Mises_PV_1.png
RHS_Plastic_14kN_Mises_PV_1.png (53.07 KiB) Viewed 291 times
RHS_Plastic_14kN_Mises_PV_2.png
RHS_Plastic_14kN_Mises_PV_2.png (72.74 KiB) Viewed 291 times
RHS_Plastic_14kN_Peeq_PV_1.png
RHS_Plastic_14kN_Peeq_PV_1.png (35.84 KiB) Viewed 291 times
Strip_PV_displacements.png
Strip_PV_displacements.png (34.21 KiB) Viewed 291 times
UR_
Posts: 737
Joined: Tue Jan 03, 2017 8:42 pm

Re: Stress Result in Shells

Postby UR_ » Sun Mar 25, 2018 9:51 am

Using HarryvL's file (test56.fcstd), i got a crash :(

https://forum.freecadweb.org/download/file.php?id=55290

tested with:
OS: Windows 10
Word size of OS: 64-bit
Word size of FreeCAD: 64-bit
Version: 0.17.13452 (Git)
Build type: Release
Branch: master
Hash: 34633c144de9133c1f9aeb7da783f369cae9bfaf
Python version: 2.7.14
Qt version: 4.8.7
Coin version: 4.0.0a
OCC version: 7.1.0
Locale: German/Germany (de_DE)



backtrace:

Code: Select all

warning: Critical error detected c0000374

Thread 1 received signal SIGTRAP, Trace/breakpoint trap.
0x00007ff823df877b in ntdll!RtlIsNonEmptyDirectoryReparsePointAllowed () from /c/WINDOWS/SYSTEM32/ntdll.dll
(gdb) bt
#0  0x00007ff823df877b in ntdll!RtlIsNonEmptyDirectoryReparsePointAllowed () from /c/WINDOWS/SYSTEM32/ntdll.dll
#1  0x00007ff823dffcfa in ntdll!RtlpNtMakeTemporaryKey () from /c/WINDOWS/SYSTEM32/ntdll.dll
#2  0x00007ff823d9fa02 in ntdll!RtlSetProxiedProcessId () from /c/WINDOWS/SYSTEM32/ntdll.dll
#3  0x00007ff823d2cbcb in ntdll!RtlAllocateHeap () from /c/WINDOWS/SYSTEM32/ntdll.dll
#4  0x00007ff823d28e0b in ntdll!RtlAllocateHeap () from /c/WINDOWS/SYSTEM32/ntdll.dll
#5  0x00007ff823e034fe in ntdll!RtlpNtMakeTemporaryKey () from /c/WINDOWS/SYSTEM32/ntdll.dll
#6  0x00007ff823db50d4 in ntdll!memset () from /c/WINDOWS/SYSTEM32/ntdll.dll
#7  0x00007ff823d28e0b in ntdll!RtlAllocateHeap () from /c/WINDOWS/SYSTEM32/ntdll.dll
#8  0x00007ff823d247f6 in ntdll!RtlReAllocateHeap () from /c/WINDOWS/SYSTEM32/ntdll.dll
#9  0x00007ff823d2421f in ntdll!RtlReAllocateHeap () from /c/WINDOWS/SYSTEM32/ntdll.dll
#10 0x00007ff823d2411a in ntdll!RtlReAllocateHeap () from /c/WINDOWS/SYSTEM32/ntdll.dll
#11 0x00007ff823e04658 in ntdll!RtlpNtMakeTemporaryKey () from /c/WINDOWS/SYSTEM32/ntdll.dll
#12 0x00007ff823db3095 in ntdll!memset () from /c/WINDOWS/SYSTEM32/ntdll.dll
#13 0x00007ff823d2421f in ntdll!RtlReAllocateHeap () from /c/WINDOWS/SYSTEM32/ntdll.dll
#14 0x00007ff823d2411a in ntdll!RtlReAllocateHeap () from /c/WINDOWS/SYSTEM32/ntdll.dll
#15 0x00007ffff83776bb in realloc () from /c/WINDOWS/SYSTEM32/MSVCR120.dll
#16 0x00007fffdd1beb6b in vtkCommonCore-7.0!?ResizeAndExtend@?$vtkDataArrayTemplate@_J@@IEAAPEA_J_J@Z ()
   from /c/Program Files/FreeCAD/bin/vtkCommonCore-7.0.dll
#17 0x00007fffdd1bf417 in vtkCommonCore-7.0!?WritePointer@?$vtkDataArrayTemplate@_J@@QEAAPEA_J_J0@Z ()
   from /c/Program Files/FreeCAD/bin/vtkCommonCore-7.0.dll
#18 0x00007fffdce4378d in vtkCommonDataModel-7.0!?InsertNextCell@vtkCellArray@@QEAA_J_JPEB_J@Z ()
   from /c/Program Files/FreeCAD/bin/vtkCommonDataModel-7.0.dll
#19 0x00007fffe2831adc in Fem!??4Tools@Fem@@QEAAAEAV01@AEBV01@@Z () from /c/Program Files/FreeCAD/Mod/Fem/Fem.pyd
#20 0x00007fffe2833f03 in Fem!?exportVTKMesh@FemVTKTools@Fem@@SAXPEBVFemMesh@2@V?$vtkSmartPointer@VvtkUnstructuredGrid@@@@M@Z ()
   from /c/Program Files/FreeCAD/Mod/Fem/Fem.pyd
#21 0x00007fffe2825168 in Fem!?load@FemPostPipeline@Fem@@QEAAXPEAVFemResultObject@2@@Z ()
   from /c/Program Files/FreeCAD/Mod/Fem/Fem.pyd
#22 0x00007fffe28b53b7 in Fem!?load@FemPostPipelinePy@Fem@@QEAAPEAU_object@@PEAU3@@Z ()
   from /c/Program Files/FreeCAD/Mod/Fem/Fem.pyd
#23 0x00007fffe28b4d82 in Fem!?staticCallback_load@FemPostPipelinePy@Fem@@SAPEAU_object@@PEAU3@0@Z ()
   from /c/Program Files/FreeCAD/Mod/Fem/Fem.pyd
#24 0x00000000657d26c9 in python27!PyCFunction_Call () from /c/Program Files/FreeCAD/bin/python27.dll
#25 0x0000000065835541 in python27!PyEval_GetFuncDesc () from /c/Program Files/FreeCAD/bin/python27.dll
#26 0x0000000065832ddc in python27!PyEval_EvalFrameEx () from /c/Program Files/FreeCAD/bin/python27.dll
#27 0x0000000065834154 in python27!PyEval_EvalCodeEx () from /c/Program Files/FreeCAD/bin/python27.dll
#28 0x000000006586e590 in python27!PyRun_FileExFlags () from /c/Program Files/FreeCAD/bin/python27.dll
#29 0x000000006586e3e0 in python27!PyRun_StringFlags () from /c/Program Files/FreeCAD/bin/python27.dll
#30 0x00007ffff4767d5e in FreeCADBase!?runString@InterpreterSingleton@Base@@QEAA?AV?$basic_string@DU?$char_traits@D@std@@V?$allocator@D@2@@std@@PEBD@Z () from /c/Program Files/FreeCAD/bin/FreeCADBase.dll
#31 0x00007fffef60f3c0 in FreeCADGui!?doCommand@Command@Gui@@SAXW4DoCmd_Type@12@PEBDZZ ()
   from /c/Program Files/FreeCAD/bin/FreeCADGui.dll
#32 0x00007fffdbb00f91 in initFemGui () from /c/Program Files/FreeCAD/Mod/Fem/FemGui.pyd
#33 0x00007fffef610616 in FreeCADGui!?invoke@Command@Gui@@QEAAXH@Z () from /c/Program Files/FreeCAD/bin/FreeCADGui.dll
#34 0x0000000064b8992c in QtCore4!?activate@QMetaObject@@SAXPEAVQObject@@PEBU1@HPEAPEAX@Z ()
   from /c/Program Files/FreeCAD/bin/QtCore4.dll
#35 0x0000000064d50f68 in QtGui4!?activate@QAction@@QEAAXW4ActionEvent@1@@Z () from /c/Program Files/FreeCAD/bin/QtGui4.dll
#36 0x00000000650afb5b in QtGui4!?checkedId@QButtonGroup@@QEBAHXZ () from /c/Program Files/FreeCAD/bin/QtGui4.dll
#37 0x00000000650b0b7e in QtGui4!?mouseReleaseEvent@QAbstractButton@@MEAAXPEAVQMouseEvent@@@Z ()
   from /c/Program Files/FreeCAD/bin/QtGui4.dll
#38 0x00000000651653cf in QtGui4!?mouseReleaseEvent@QToolButton@@MEAAXPEAVQMouseEvent@@@Z ()
   from /c/Program Files/FreeCAD/bin/QtGui4.dll
#39 0x0000000064dab70b in QtGui4!?event@QWidget@@MEAA_NPEAVQEvent@@@Z () from /c/Program Files/FreeCAD/bin/QtGui4.dll
#40 0x0000000064d6119a in QtGui4!?notify_helper@QApplicationPrivate@@QEAA_NPEAVQObject@@PEAVQEvent@@@Z ()
   from /c/Program Files/FreeCAD/bin/QtGui4.dll
#41 0x0000000064d5f94e in QtGui4!?notify@QApplication@@UEAA_NPEAVQObject@@PEAVQEvent@@@Z ()
   from /c/Program Files/FreeCAD/bin/QtGui4.dll
#42 0x00007fffef5ec000 in FreeCADGui!?trUtf8@ExpressionLineEdit@Gui@@SA?AVQString@@PEBD0H@Z ()
   from /c/Program Files/FreeCAD/bin/FreeCADGui.dll
#43 0x0000000064b72d3c in QtCore4!?notifyInternal@QCoreApplication@@AEAA_NPEAVQObject@@PEAVQEvent@@@Z ()
   from /c/Program Files/FreeCAD/bin/QtCore4.dll
#44 0x0000000064d5ea0f in QtGui4!?sendMouseEvent@QApplicationPrivate@@SA_NPEAVQWidget@@PEAVQMouseEvent@@00PEAPEAV2@AEAV?$QPointer@VQWidget@@@@_N@Z () from /c/Program Files/FreeCAD/bin/QtGui4.dll
#45 0x0000000064dc7612 in QtGui4!?winMouseButtonUp@QApplication@@SAXXZ () from /c/Program Files/FreeCAD/bin/QtGui4.dll
#46 0x0000000064dc5ab6 in QtGui4!?winFocus@QApplication@@QEAAXPEAVQWidget@@_N@Z () from /c/Program Files/FreeCAD/bin/QtGui4.dll
#47 0x00007ff82149b85d in USER32!CallWindowProcW () from /c/WINDOWS/System32/USER32.dll
#48 0x00007ff82149b1ef in USER32!DispatchMessageW () from /c/WINDOWS/System32/USER32.dll
#49 0x0000000064b9bb9d in QtCore4!?processEvents@QEventDispatcherWin32@@UEAA_NV?$QFlags@W4ProcessEventsFlag@QEventLoop@@@@@Z ()
   from /c/Program Files/FreeCAD/bin/QtCore4.dll
#50 0x0000000064dc26c5 in QtGui4!?qt_getRegisteredWndClass@@YA?BVQString@@XZ () from /c/Program Files/FreeCAD/bin/QtGui4.dll
---Type <return> to continue, or q <return> to quit---
#51 0x0000000064b711df in QtCore4!?exec@QEventLoop@@QEAAHV?$QFlags@W4ProcessEventsFlag@QEventLoop@@@@@Z ()
   from /c/Program Files/FreeCAD/bin/QtCore4.dll
#52 0x0000000064b732b0 in QtCore4!?exec@QCoreApplication@@SAHXZ () from /c/Program Files/FreeCAD/bin/QtCore4.dll
#53 0x00007fffef5b7a4b in FreeCADGui!?runApplication@Application@Gui@@SAXXZ () from /c/Program Files/FreeCAD/bin/FreeCADGui.dll
#54 0x00007ff61ef24c50 in ?? ()
Backtrace stopped: previous frame inner to this frame (corrupt stack?)
(gdb)

workflow:
- loading test file from HarryvL
- activating analysis
- delete existing solver object
- recreate solver object (nonexperimental)
- set output to 3D
- write INP
- run ccx
- result object is ok :)
- mark result object in tree view and try to create vtk pipeline
- bang :shock:
thschrader
Posts: 1383
Joined: Sat May 20, 2017 12:06 pm
Location: Germany

Re: Stress Result in Shells

Postby thschrader » Sun Mar 25, 2018 4:38 pm

UR_ wrote:
Sun Mar 25, 2018 9:51 am
Using HarryvL's file (test56.fcstd), i got a crash :(
Confirmed. Mesh-results ok, after clicking pipeline-button, FC crashes.
System:
OS: Windows 10
Word size of OS: 64-bit
Word size of FreeCAD: 64-bit
Version: 0.17.13433 (Git)
Build type: Release
Branch: master
Hash: b45bc4889d390eb50022a49a58c6af80f4a328f5
Python version: 2.7.14
Qt version: 4.8.7
Coin version: 4.0.0a
OCC version: 7.1.0
Locale: German/Germany (de_DE)
test_harrys_file.JPG
test_harrys_file.JPG (214.04 KiB) Viewed 247 times
crashed.JPG
crashed.JPG (75.4 KiB) Viewed 247 times
User avatar
bernd
Posts: 7301
Joined: Sun Sep 08, 2013 8:07 pm
Location: Zürich, Switzerland

Re: Stress Result in Shells

Postby bernd » Sun Mar 25, 2018 8:28 pm

it chrashes here too.

BUT there is a workaround. Export the result to vtk file and import the vtk file as vtk pipline (or use the exported vtk file in paraview) will work :D

Neverless I will have a look at the crash.

bernd
User avatar
bernd
Posts: 7301
Joined: Sun Sep 08, 2013 8:07 pm
Location: Zürich, Switzerland

Re: Stress Result in Shells

Postby bernd » 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 :o :shock: at least it does for me :mrgreen:
UR_
Posts: 737
Joined: Tue Jan 03, 2017 8:42 pm

Re: Stress Result in Shells

Postby UR_ » Sun Mar 25, 2018 8:56 pm

bernd wrote:
Sun Mar 25, 2018 8:37 pm
at least it does for me
Here too. :?
User avatar
bernd
Posts: 7301
Joined: Sun Sep 08, 2013 8:07 pm
Location: Zürich, Switzerland

Re: Stress Result in Shells

Postby bernd » Sun Mar 25, 2018 9:13 pm

saving and reloading the file normalizes the element and node numbering of the result mesh. They start with one after reload. Seams our vtk mesh builder or vkt itself has problems with node and or element numbers not starting with 1 or with the gaps ...