<!-- source-page: 451 -->

```txt
VariableName='variable' />
<Filter StepName='full step name'
FrameIndex='individual frame number'
VariableName='variable' />
</DefaultFilters> 
```

<MasterOdb Name='path to master output database'>

Filtering elements for the master output database are optional. If you want to filter the data from this output database, include a <Filter> element within this section for each filtering option you want to define.

```txt
</Master0db> 
```

<Odb Name='path to output database'>

Filtering elements for the output database are optional. If you want to filter the data from this output database, include a <Filter> element within this section for each filtering option you want to define.

```txt
</0db>
```

Append an <Odb> element for each additional output database you want to include.

```asp
</OdbInput> 
```

# Data not included in combined output databases

The following types of output data are not included when you combine output database files:

• History output.   
• Surface data.   
• Data from analytical rigid part instances.   
• Local coordinate systems associated with field output data.

# Command summary

abaqus odbcombine

$\scriptstyle \mathbf { j o b } = j o b - n a m e$ [input=configuration-file-name] [verbose=level]

# Command line options

job

This option specifies the name of the resulting combined output database and the name of the log file. Abaqus also searches for a configuration file by this name.

If you omit this option from the command line, Abaqus will prompt you for its value.

<!-- source-page: 452 -->

# input

This option specifies the name of the configuration file that specifies the output databases you want to combine and the steps, frames, and output variables to be included in the combination. The configuration file must be in .xml format.

# verbose

This option specifies the level of detail for the messages that Abaqus writes to the log file. Possible values are 1 or 2. If you specify 1, Abaqus writes only errors and warnings to the log file; if you specify 2, Abaqus also records the filtering options you select and lists the model data and field output data that were successfully copied to the combined output database.

<!-- source-page: 453 -->

# 3.2.26 NETWORK OUTPUT DATABASE FILE CONNECTOR

Products: Abaqus/CAE Abaqus/Viewer

# References

• “Execution procedure for Abaqus: overview,” Section 3.1.1   
• “Accessing an output database on a remote computer,” Section 9.3 of the Abaqus/CAE User’s Guide

# Overview

A network ODB connector creates a connection to a network ODB server that can be used to access a remote output database. The abaqus networkDBConnector command is used to start the network ODB server. A network ODB connector can be created from any platform—Windows or Linux; however, the network ODB server must reside on a Linux platform.

Abaqus uses password files to authenticate the connection between the client and the server. The password on the network ODB server must be stored in a file called .abaqus\_net\_passwd in your home directory on the remote system. You must update this file after 30 days, and the password must be at least 8 characters long.

In addition, your home directory on the local client machine can contain either of the following:

• A file called .abaqus\_hostname\_passwd. This file allows you to connect to the remote server on the machine called hostname.   
• A file called .abaqus\_net\_passwd. This file allows you to connect to the network ODB server on any machine.

The contents of the password file on both the server and the client must be identical. In addition, Abaqus checks that you are the only user with permission to read from or to write to the password files. If neither file exists, Abaqus tries to use remote and secure shell commands to read the password from the network ODB server. However, the security configuration at your site may prevent Abaqus from reading the password.

# Command summary

```ini
abaqus networkDBConnector port={serverPortNumber | auto_assigned}
[timeout=time out value in seconds]
[host=hostname]
[stop]
[ping] 
```

<!-- source-page: 454 -->

# Command line options

# port

This option specifies the port number on the network ODB server. If port=auto\_assigned, Abaqus automatically assigns the port number.

# timeout

This option specifies the timeout period in seconds for the network ODB server. The server exits if it does not receive any communication from the client during the time specified. A timeout value of zero indicates that the server will run until it is terminated explicitly using the stop option.

# host

This option specifies the name of the machine that is hosting the network ODB server. This option is used with the stop and ping options. If this option is not provided, Abaqus uses the name of the machine from which the execution procedure was issued.

#

This option specifies that Abaqus should stop the network ODB server that was established using the specified host name and port number.

# ping

This option queries the network ODB file server that was established using the specified host name and port number. Use this option to confirm that the network ODB server exists and that communications have been established.

<!-- source-page: 455 -->

# 3.2.27 MAPPING THERMAL AND MAGNETIC LOADS

Product: Abaqus/Standard

# References

• “Execution procedure for Abaqus: overview,” Section 3.1.1   
• “Eddy current analysis,” Section 6.7.5   
• “Predefined loads for sequential coupling,” Section 16.1.3   
• \*CFLUX   
• \*CLOAD

# Overview

The abaqus emloads utility converts results output from a time-harmonic eddy current analysis for use as loads in a subsequent heat transfer, coupled temperature-displacement, or stress/displacement analysis. For example, magnetic body force intensity output is converted to point loads. You specify the names of the time-harmonic eddy current analysis results output database (.odb) file and the input file for the subsequent analysis on the command line. The utility creates an output database file containing a mesh that matches the mesh in your subsequent analysis and steady-state concentrated nodal fields consistent with the time-harmonic eddy current analysis results. Your time-harmonic eddy current and subsequent analysis meshes can be dissimilar, and results transfer ensures global conservation of the flux quantities when your model domains match; i.e., the model boundaries are the same. You can then use this new output database file to apply concentrated loads and concentrated heat fluxes in the subsequent analysis.

# Results conversion

The utility converts whole element output quantities from a time-harmonic eddy current analysis to nodal results. You use the options listed in Table 3.2.27–1 in the subsequent analysis to specify the output database file (and optionally the step and increment) from which the data are to be read.

# Utility execution

The utility executes in two phases. Abaqus writes progress information and, if appropriate, error messages to the screen during each phase.

In the first phase a datacheck analysis is performed on your subsequent analysis input file to create an output database representation of a “target” mesh. This phase requires that your input file be sufficiently complete to successfully run abaqus datacheck, with the exception that you can have \*CFLUX and \*CLOAD options that include the FILE parameter to refer to files that are not available. If this phase is successful, the utility proceeds to the second phase; otherwise, an error message is issued.

In the second phase time-harmonic eddy current analysis load data are mapped from the source to the target output database. In this phase all steps and increments found in the original analysis are defined

<!-- source-page: 456 -->

Table 3.2.27–1 Supported results conversion. 

<table><tr><td>Electromagnetic analysis output variable</td><td>Converted output variable</td><td>Input file option</td></tr><tr><td>Rate of Joule heat dissipation EMJH</td><td>Concentrated heat flux CFL11</td><td>*CFLUX, FILE=odb-name, STEP=step-number, INC=inc</td></tr><tr><td>Magnetic body force intensity EMBF</td><td>Point load components CF</td><td>*CLOAD, FILE=odb-name, STEP=step-number, INC=inc</td></tr></table>

in the target output database. This phase requires that your target model domain lie within the source model domain. If it does not, an appropriate error message is issued.

Command summary 

<table><tr><td>abaqus emloads</td><td>job=target-odb-nameinput=subsequent analysis input-file-namesourceodb=time-harmonic eddy current analysis odb-file-name</td></tr><tr><td>Command line options</td><td></td></tr></table>

# job

This option specifies the name of the resulting “target” output database file.

# input

This option specifies the name of the subsequent analysis Abaqus input file. This file must be sufficiently complete to successfully run, as described above.

# sourceodb

This option specifies the name of the time-harmonic eddy current analysis output database file.

<!-- source-page: 457 -->

# 3.2.28 ELEMENT MATRIX ASSEMBLY UTILITY

Product: Abaqus/Standard

# Reference

• “Generating matrices,” Section 10.3

# Overview

The abaqus mtxasm utility assembles element matrices contained in a SIM document and, optionally, writes the assembled matrices to text files. If assembled matrices are already available in a SIM document, you can use this utility to write them to text files.

Command summary 

<table><tr><td>abaqus mtxasm</td><td>job=name-of-assembled-mtx-sim-doc[oldjob=name-of-element-mtx-sim-doc] [text]</td></tr><tr><td colspan="2">Command line options</td></tr></table>

# job

This option is used to specify the name of the SIM document containing assembled matrices or to which assembled matrices will be written, depending on the mode of operation.

# oldjob

This option is used to specify the name of the SIM document containing element matrices to be assembled. If this option is not used, the SIM document specified using the job option must already exist and contain assembled matrices.

# text

This option is used to write assembled matrices to text files in the matrix input format. Each matrix is written to a file that follows the naming convention jobname\_matrixN.mtx, where jobname is the name specified using the job option, matrix is a four-letter identifier (STIF, MASS, DMPV, DMPS, or LOAD) indicating the matrix type relevant for structural or thermal matrices, and N is the increment number.

<!-- source-page: 458 -->

<!-- source-page: 459 -->

# 3.2.29 FIXED FORMAT CONVERSION UTILITY

Products: Abaqus/Standard Abaqus/Explicit

# Reference

• “Execution procedure for Abaqus: overview,” Section 3.1.1

# Overview

The abaqus free utility will convert the fixed format input files used with Abaqus 5.8 to the free format input files used with subsequent Abaqus releases.

# Command summary

abaqus free

$$
\mathbf {j o b} = \text { job - name }
$$

$$
\text { input } = \text { input - file }
$$

# Command line options

job

This option is used to specify the name of the free format input file to be output by the utility.

input

This option is used to specify the name of the fixed format input file to be converted.

<!-- source-page: 460 -->
