DumpFiles

[rwendner]

In order to export data for external post-processing (e.g. Matlab) there are a number of dump file options available:
WriteStateVariableDumpEvery 0.010 ms
WriteCellDataDump 'fileName'
WriteFacetDataDump 'fileName'

Recently extended by the new modules
FacetDataDump { }
ParticleDataDump { }

Comment 1:
WriteFacetDataDump and the new module FacetDataDump sound very similar but do very different things.
I suggest renaming the WriteFacetDataDump to FacetGeometryDump
Furthermore I would rename WriteCellDataDump to CellGeometryDump

Comment 2:
Please add the volumes that are associated with a facet into the FacetGeometryDump.

Comment 3:
The existing WriteStateVariableDumpEvery should be rename, e.g. to SVDataDump.
At the moment only a fixed interval in computational time is allowed and all SVs are dumped.
This is extremely storage intensive. Please implement the same functionality you have for the FacetDataDump module, i.e. specifying realtimeinterval or realtimeloadcurve as well as the option to select the statevariables you want to dump by label; and also the filename.

Comment 4:
The data structure of the FacetDataDump module and the old WriteStateVariableDumpEvery is inconsistent.

Comment 5:
We have the option to define a ScalarField based on a tetlist or hexlist with the command
ScalarField TetList 'listname' StateVariable "Temperature"
However, we have no way to actually dump the results of the diffusion problem (tetbased) in a consistent format.
For postprocessing as well as prescribing the results of a previous run of the diffusion problem it would be great to add a TetDataDump module.
This TetDataDump module then can also be used to dump statevariables of a FE based mechanical problem, see Comment 6.
I guess then we should also have HexDataDump module.

Comment 6:
In the manual the
WriteStateVariableDataDumpEvery 0.01 ms
is used in combination with a BeamParticlesConstraintList. This does not seem to work at the moment.
It would be perfect if this functionality is available for LDPM, tets, hex, beams, and constraintlists.
In that case we also would need to have a further function, something like IntegrationPointGeometryDump or IPGeometryDump

[giacusatis]

Was any of these suggestions considered/implemented?

[zhouxinwei]

The accepted changes have been implemented in version 2016.3.00, please refer manual for details.

1-3. accepted.

4. WriteStateVariableDumpEvery is marked as obsolete and will be discontinued. Refer manual for better replacement.

5. ScalarField in this context was used before M-LDPM framework. It will be discontinued, use LDPM modules instead.

6. StateVariableDataDump is updated for tet lists (LDPM, Flex) and hex lists (FBSingleIP, 8IP), rest will come later. Can you give an example where IPGeometryDump is needed and what type of geometric information are you looking for?

[rwendner]

Thanks for the implementation.

I found one more inconsistency: In LDPM we have (had)

WriteStateVariableDumpEvery 0.010 ms

while in the BeamParticleConstraintList the corresponding command is

WriteStateVariableDataDumpEvery 0.01 ms

What is the current way of dumping the constraint list SVs?
Was this also updated ?

[zhouxinwei]

SV dump for LDPM was updated in previous reply.

SV dump for BeamParticleConstraintList is updated in version 2016.7.39.

StateVariableDataDump is the keyword we should use.

Please refer manual for details.