thanks for the reply. I will give it a try and report back ...


BTW:
NIP 1 was taken from official examples ... http://www.oofem.org/resources/doc/oofe … ss-example

noone around who has some idea in this regard?

thanks for confirming this.

cheers bernd

just realized and had to write some corner case code in FreeCAD just for oofem because it seams to need a density and thermal expansion coefficient to run a analysis even if they are not needed for a mechanical linear analysis.

Is this really true or can they be omitted somehow?

cheers bernd

BTW: Mystran and Calculix give for these both quad4 meshes around 86 mm, means near the real max deflection already.

Is there something special with the oofem quad4 or did I do something wrong in the input file?

the rough mesh file ...

attached two simple quad4 analysises. Same geometry as in http://www.oofem.org/forum/viewtopic.php?id=1886 so real max deformation is around 87 mm.

For a quad4 mesh I would expect for a rough mesh a deformation which is to stiff and as finer the mesh gets as weaker it is but nearer to the real result. But it is not the case. The rought mest very much to weak. Even the fine mesh is still 10 % above the real deformation.

rough mesh max deflection 118 mm
fine mesh deflection 93 mm

Any explanations around ... ?

I can confirm with "stype 1" it works with 2.5 too.

great !

Has this problem been fixed in recent versions of oofem? Is there a newer version for debian available or is self compiling advised?

cheers bernd from FreeCAD FEM project.

oofem debian package from oofem download is used ...

$ oofem -v

OOFEM version 2.5 (x86_64-Linux, fm;tm;sm;dss;IML++)
of Dec 30 2017 on jaja

Copyright (C) 1994-2017 Borek Patzak
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

$

BTW: For the mesh OOFEM fails to analyse (first post) CalculiX, Z88 and Mystran do analyse the same maximum deflection of 61.21 mm

ahh forgot the file, here it is ...

attached the file which gives reasonable results  OOFEM gives as well as CalculiX, Mystran and Z88 the exact same result for this tet4 mesh. They all give 53.87 mm.

A tet10 mesh with similar size gives 87.4 mm in all programme which is perfectly fine.

cheers bernd

Hi there,

Attached two oofem input files. One gives reasonable results (a bit to stiff but this might because it is first order tet element). The other has a slightly finer mesh and this does return a error:





$
$ oofem -f  Mesh_not_ok.in 
____________________________________________________
           OOFEM - Finite Element Solver
        Copyright (C) 1994-2017 Borek Patzak
____________________________________________________


Solving ...

_______________________________________________________
Error: (/home/bp/devel/oofem.git/src/oofemlib/floatmatrix.C:1259)
In solveForRhs:
pivot too small, cannot solve 4 by 4 matrix
_______________________________________________________
stack trace:
  /lib/liboofem.so : oofem::SPRNodalRecoveryModel::computePatch(oofem::FloatMatrix&, oofem::IntArray&, int&, oofem::SPRPatchType, oofem::InternalStateType, oofem::TimeStep*)+0x49b
  /lib/liboofem.so : oofem::SPRNodalRecoveryModel::recoverValues(oofem::Set, oofem::InternalStateType, oofem::TimeStep*)+0x41a
  /lib/liboofem.so : oofem::VTKXMLExportModule::getNodalVariableFromIS(oofem::FloatArray&, oofem::Node*, oofem::TimeStep*, oofem::InternalStateType, int)+0x8d
  /lib/liboofem.so : oofem::VTKXMLExportModule::exportIntVars(oofem::VTKPiece&, oofem::IntArray&, oofem::IntArray&, int, oofem::TimeStep*)+0x199
  /lib/liboofem.so : oofem::VTKXMLExportModule::setupVTKPiece(oofem::VTKPiece&, oofem::TimeStep*, int)+0x1e7
  /lib/liboofem.so : oofem::VTKXMLExportModule::doOutput(oofem::TimeStep*, bool)+0xecd
  /lib/liboofem.so : oofem::ExportModuleManager::doOutput(oofem::TimeStep*, bool)+0x62
  /lib/liboofem.so : oofem::EngngModel::terminate(oofem::TimeStep*)+0x7c
  /lib/liboofem.so : oofem::EngngModel::solveYourself()+0x9c9
Total 1 error(s) and 0 warning(s) reported
oofem exit code 1
$

15

(2 replies, posted in General Help)

Hi nitramkaroh,

smile, this worked out very well. Got the points and understood how it works.

cheers bernd

16

(2 replies, posted in General Help)

Hi oofem folks,

attached a simple cube with 4 node loades. Two things I do not understand ...

- line 97:
BoundaryCondition 1  loadTimeFunction 1  dofs 3 1 2 3  values 1 0.0  set 2

What does the "values 1 0.0" stands for?


- instead of the 4 node loads I would like to use a surface load by "ConstantSurfaceLoad" I could not find an example and thus I failed to add such an surface load.

Thanks in advance for any help, Bernd

17

(0 replies, posted in General Help)

just wanted to say hello. My name is bernd. I am structural engineer based in Winterthur (near Zürich). I started to play with oofem on debian buster. I used the deb from download page. Installation worked like charm.

I encountered my first problem I am not able to solve with QTRSpace (10 node tetrahedron) elements. But this will be a separate topic.

cheers bernd