***data_output

Description

This procedure is used to add a destination output of the post processing data of the following commands. The selection should normally come at the start of the ***-level commands, except for a ***data_source command which should always be first.

Syntax

***data_output type \(~\,~\,\) *problem_name name \(~\,~\,\) *elset eset-name \(~\,~\,\) type-specific-options

problem_name

is used to specify the root-name of the problem which would have been run in the native code. Usually the output file will be this name appended with a dot suffix of the file type.

elset

specifies that the output problem is to be a sub-mesh made up of the given element set elements. This can be used as a general results file reduction capability with

The following data source types are currently available.

Data source	Description
odb	ABAQUS odb database format (for launching use command switch Zodb -pp instead of Zrun -pp)
rst	ANSYS rst database format
fg3	FORGE fg3 database format
med	MED med database format

Currently there are no additional type-specific options.

Example

A typical example follows. The data output capability has test cases in the test/Z-mat/zebu_interface with a full assortment of stacked input and output runs are done.

****post_processing
  ***data_source Z7
    **open zpost_matsim.utp

  ***data_output odb
     *problem_name lifetime
     *elset MANIFOLD

  ***local_post_processing
     **output_number 1-9999
     **file node
     **nset manifold_nodes
     **material_file post_coefs.mat

   **process neu_sehitoglu_evi
    *total_strain_for_range

   **process copy        % for validation between input/output
    *list_var evcum
    *out_var  evcum
    *last_only
****return