dumpfiles for BeamXXXConstraint lists

[rwendner]

At the moment we have the ability to dump the statevariables of BeamParticleConstraintList and BeamTetConstraintList.

The result may look like:

BeamTetConstraint: 1
1 1 -2.94073e+06 -2.67562e-05
1 2 -4.2337e+06 7.74625e-06
2 1 -2.97432e+06 1.80069e-05
2 2 -4.29856e+06 -2.74455e-05
3 1 -3.77931e+06 5.81403e-05
3 2 -3.99328e+06 9.3048e-06
BeamTetConstraint: 2
1 1 -1.69304e+06 -1.3309e-05
1 2 -1.73789e+06 -4.33715e-05
2 1 -1.33668e+06 -1.0452e-05
2 2 -2.41584e+06 6.42155e-05
3 1 -1.51054e+06 -3.68892e-05
3 2 -2.25248e+06 -5.15224e-05
EOF

for the following code

Code: Select all

BeamTetConstraintList TIES RebarConcreteInteraction {
  BeamList PRESTR
  TetList PRTC
  RebarConcreteInteraction RCIM
  NumberOfCircumferentialConstraintsPerBeamElement 3
  NumberOfAxialConstraintsPerBeamElement 2
  RebarRadius 10 mm
  StateVariableDataDump { // [1]
    TimeInterval 0.1 ms
    // TimeIntervalCurve LC // or
    // RealTimeInterval 1 hours // or
    // RealTimeIntervalCurve LCR
    FileName ./Dump/RCISVDump
    DeleteAllFiles
    SVLabels { // use All or specify by label
      "Axial stress"
      "Circumf. slippage"
    }
  }
}


Can you please add an explanation of the dump file structure to the manual?

For postprocessing it is important to know the corresponding coordinates of the exported values, i.e. we need also something like the IPGeometryDataDump.

Similar to my other posts on dumpfiles, I suggest to add a header with the number of beam elements that follow, the computational time, the realtime, the number of exported SVs, and their labels.

[rwendner]

I just noted that also a RCISVDump.000.geo file is generated which contains the following information

1 0.000471239 3 2
0 0 0 -1 0 0.01125 -0.01 0.06
0 1 0 -1 0 0.03375 -0.01 0.06
1 0 0 0.5 -0.866025 0.01125 0.005 0.0513397
1 1 0 0.5 -0.866025 0.03375 0.005 0.0513397
2 0 -0 0.5 0.866025 0.01125 0.005 0.0686603
2 1 -0 0.5 0.866025 0.03375 0.005 0.0686603
2 0.000471239 3 2
0 0 0 -1 0 0.05625 -0.01 0.06
0 1 0 -1 0 0.07875 -0.01 0.06
1 0 0 0.5 -0.866025 0.05625 0.005 0.0513397
1 1 0 0.5 -0.866025 0.07875 0.005 0.0513397
2 0 -0 0.5 0.866025 0.05625 0.005 0.0686603
2 1 -0 0.5 0.866025 0.07875 0.005 0.0686603

Can you please provide an explanation and add it to the manual ?

Automatically dumping the required geometry as *.geo is a nice feature. We could consider doing the same thing for the other dump files.
Alternatively, we should remove the automatic generation of this file and add something like the IPGeomDataDump.
In any case, the logic, syntax and file structures should be consistent between all the dump files

[zhouxinwei]

Suggestions will be considered.

[zhouxinwei]

Features are updated in version 2016.9.05.

[rwendner]

I suggest to rename the GeometryDataDump to IPGeometryDataDump to be consistent with the dump file command of the tet and hex lists.
Alternatively, remove the "IP" from the commands of hxL, ttL

I also noticed that automatically .geo is added to the filename of the geometry dump file. This is not a big deal but inconsistent with the other geometry dumps of LDMP,tet and hex lists.