1 Topic by djd (edited by djd 14-05-2010 03:54:08)

  • djd
  • Member
  • Offline
  • Registered: 01-08-2009
  • Posts: 21

Topic: Nodes numbering,L4axisymm element, coupling, etc

Hi, bp
I have several quetions to consult with you.
1) In the DofManager Records in the oofemInput.pdf, I saw "The numbering of individual dof managers is arbitrary, it could be even non-continuous."  But, in domain.c I saw
if ( ( num < 1 ) || ( num > nnode ) ) {
            _error2("instanciateYourself: Invalid dofManager number (num=%d)", num);
        }
which means that the node numbers should ranges from 1 to nnode. This indicates that the node numbering should be continuous.  Am I wrong?
2) Recently, I did an axisymmetric analysis.  I applied an constant surface (line) load (in global coordinate) on the L4axisymm elements. But when assemling the global load vector, the L4axisymm elements seems to fail to take into account of the oriention of the loading surface. Can you check it?
3) If I want to couple the u,v,w displacements of  three nodes, for example 1 2 3 (node 1 is master dofmanager),  how should I document it in the data file? Using the masterMask key word?
Sincerely Yours.

2 Reply by bp

  • bp
  • Administrator
  • Offline
  • From: Prague, Czech Rep.
  • Registered: 02-03-2007
  • Posts: 1,047

Re: Nodes numbering,L4axisymm element, coupling, etc

Hi djd,

1) the numbering is arbitrary, however,  oofem uses internally local continuous numbering of nodes and other components for efficiency reasons. Perhaps, the lines you are mentioning refer to local internal numbering, rather to user numbering used on input.

2) Could you provide a simple example, I will check
3) By coupling you mean enforcing these displacements to be the same for all nodes? if yes, you can achieve this using masterMask. For example, on the node 2 use following

node 2 coords 3 0. 0. 0. dofType 3 1 1 1 masterMask 3 1 1 1

where dofType declares all dofs as simple slaves, masterMask then links all dofs to corresponding dofs on node 1.

Borek

bp's Website

3 Reply by djd (edited by djd 26-05-2010 05:16:47)

  • djd
  • Member
  • Offline
  • Registered: 01-08-2009
  • Posts: 21

Re: Nodes numbering,L4axisymm element, coupling, etc

Hi,bp
You have said that the node numbering is arbitrary. I tested the following example  with mixed elements you provided before. But the following error poped up.
"
____________________________________________________
           OOFEM - Finite Element Solver
        Copyright (C) 1994-2008 Borek Patzak
____________________________________________________
Total number of solution steps 1
Instanciating domain                1
_______________________________________________________
Error: (.\src\oofemlib\domain.C:495)
Class: Domain, number: 1
instanciateYourself: Invalid dofManager number (num=41)
_______________________________________________________
Total 1 error(s) and 0 warning(s) reported
oofem exit code 1
"

Here is the content of the data file.(It is also attached.)
"
shell.out
Test illustrating a shell elements combined with 3d elements - clamped beam
# left part made of shell elements
# right part made of space elements
# requires oofem 1.9 and later
LinearStatic nsteps 1
domain 3d
OutputManager tstep_all dofman_all element_all
ndofman 40 nelem 15 ncrosssect  2 nmat 2 nbc 2 nic 0 nltf 1
# nodes
# shell part
node 1 coords 3 0.0 0.0 0.0 ndofs 6 DofIDMask 6 1 2 3 4 5 6 bc 6 1 1 1 1 1 1
node 2 coords 3 0.0 1.0 0.0 ndofs 6 DofIDMask 6 1 2 3 4 5 6 bc 6 1 1 1 1 1 1
node 3 coords 3 1.0 0.0 0.0 ndofs 6 DofIDMask 6 1 2 3 4 5 6 bc 6 0 0 0 0 0 1
node 4 coords 3 1.0 1.0 0.0 ndofs 6 DofIDMask 6 1 2 3 4 5 6 bc 6 0 0 0 0 0 1
node 5 coords 3 2.0 0.0 0.0 ndofs 6 DofIDMask 6 1 2 3 4 5 6 bc 6 0 0 0 0 0 1
node 6 coords 3 2.0 1.0 0.0 ndofs 6 DofIDMask 6 1 2 3 4 5 6 bc 6 0 0 0 0 0 1
node 7 coords 3 3.0 0.0 0.0 ndofs 6 DofIDMask 6 1 2 3 4 5 6 bc 6 0 0 0 0 0 1 load 1 2
node 8 coords 3 3.0 1.0 0.0 ndofs 6 DofIDMask 6 1 2 3 4 5 6 bc 6 0 0 0 0 0 1 load 1 2
#3d part
RigidArmNode 10 coords 3 3.0 0.0 -0.3 master 7 mastermask 3 1 1 1 dofType 3 2 2 2
RigidArmNode 11 coords 3 3.0 0.0 -0.1 master 7 mastermask 3 1 1 1 dofType 3 2 2 2
RigidArmNode 12 coords 3 3.0 0.0  0.1 master 7 mastermask 3 1 1 1 dofType 3 2 2 2
RigidArmNode 13 coords 3 3.0 0.0  0.3 master 7 mastermask 3 1 1 1 dofType 3 2 2 2
RigidArmNode 20 coords 3 3.0 1.0 -0.3 master 8 mastermask 3 1 1 1 dofType 3 2 2 2
RigidArmNode 21 coords 3 3.0 1.0 -0.1 master 8 mastermask 3 1 1 1 dofType 3 2 2 2
RigidArmNode 22 coords 3 3.0 1.0  0.1 master 8 mastermask 3 1 1 1 dofType 3 2 2 2
RigidArmNode 23 coords 3 3.0 1.0  0.3 master 8 mastermask 3 1 1 1 dofType 3 2 2 2
node 30 coords 3 4.0 0.0 -0.3
node 31 coords 3 4.0 0.0 -0.1
node 32 coords 3 4.0 0.0  0.1
node 33 coords 3 4.0 0.0  0.3
node 40 coords 3 4.0 1.0 -0.3
node 41 coords 3 4.0 1.0 -0.1
node 42 coords 3 4.0 1.0  0.1
node 43 coords 3 4.0 1.0  0.3
node 50 coords 3 5.0 0.0 -0.3
node 51 coords 3 5.0 0.0 -0.1
node 52 coords 3 5.0 0.0  0.1
node 53 coords 3 5.0 0.0  0.3
node 60 coords 3 5.0 1.0 -0.3
node 61 coords 3 5.0 1.0 -0.1
node 62 coords 3 5.0 1.0  0.1
node 63 coords 3 5.0 1.0  0.3
node 70 coords 3 6.0 0.0 -0.3 bc 3 1 1 1
node 71 coords 3 6.0 0.0 -0.1 bc 3 1 1 1
node 72 coords 3 6.0 0.0  0.1 bc 3 1 1 1
node 73 coords 3 6.0 0.0  0.3 bc 3 1 1 1
node 80 coords 3 6.0 1.0 -0.3 bc 3 1 1 1
node 81 coords 3 6.0 1.0 -0.1 bc 3 1 1 1
node 82 coords 3 6.0 1.0  0.1 bc 3 1 1 1
node 83 coords 3 6.0 1.0  0.3 bc 3 1 1 1
#elements
#shell elements
rershell 1 nodes 3 1 3 2 crosssect 1 mat 1
rershell 2 nodes 3 2 3 4 crosssect 1 mat 1
rershell 3 nodes 3 3 5 4 crosssect 1 mat 1
rershell 4 nodes 3 4 5 6 crosssect 1 mat 1
rershell 5 nodes 3 5 7 6 crosssect 1 mat 1
rershell 6 nodes 3 6 7 8 crosssect 1 mat 1
#3d elements
lspace 10 nodes 8 10 30 40 20 11 31 41 21 crosssect 2 mat 2
lspace 11 nodes 8 11 31 41 21 12 32 42 22 crosssect 2 mat 2
lspace 12 nodes 8 12 32 42 22 13 33 43 23 crosssect 2 mat 2
lspace 20 nodes 8 30 50 60 40 31 51 61 41 crosssect 2 mat 2
lspace 21 nodes 8 31 51 61 41 32 52 62 42 crosssect 2 mat 2
lspace 22 nodes 8 32 52 62 42 33 53 63 43 crosssect 2 mat 2
lspace 30 nodes 8 50 70 80 60 51 71 81 61 crosssect 2 mat 2
lspace 31 nodes 8 51 71 81 61 52 72 82 62 crosssect 2 mat 2
lspace 32 nodes 8 52 72 82 62 53 73 83 63 crosssect 2 mat 2
# cross sections
SimpleCS 1 thick 0.6 width 1.0
Simplecs 2
#materials
isole 1 E 10.0 n 0.15 talpha 0.0 d 0.0
isole 2 E 10.0 n 0.15 talpha 0.0 d 0.0
#boundary conditions
BoundaryCondition  1 loadTimeFunction 1 prescribedvalue 0.0     
NodalLoad 2 loadTimeFunction 1 Components 6 0.0 0.0 -1.0 0.0 0.0 0.0
ConstantFunction 1 f(t) 1.
"
What is the problem?
Sincerely yours.
djd

4 Reply by bp

  • bp
  • Administrator
  • Offline
  • From: Prague, Czech Rep.
  • Registered: 02-03-2007
  • Posts: 1,047

Re: Nodes numbering,L4axisymm element, coupling, etc

Hi djd,

I tried the example you have provided and it works (at least for me). Please note, that support for arbitrary numbering was introduced in version 1.9. So, you should use the latest 1.9 version (or updated repository version).
You can check oofem version easily, by running oofem with -v option:

$ ~/oofem/rel-1.9/targets/oofem-debug/bin/oofem -v
____________________________________________________
           OOFEM - Finite Element Solver            
        Copyright (C) 1994-2009 Borek Patzak        
____________________________________________________

OOFEM version 1.9 (x86_64-unknown-linux-gnu, oofemlib sm tm fm iml dss)
of May 26 2010 on cml

Copyright (C) 1994-2009 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.

bp's Website

  • djd
  • Member
  • Offline
  • Registered: 01-08-2009
  • Posts: 21

Re: Nodes numbering,L4axisymm element, coupling, etc

Hi,bp
Thanks for your quick reply.  I have found the problem.  I didn't predefine __ENABLE_COMPONENT_LABELS.