5.6 Example

Example 1

The following example defines a restart input file. No parameters are redefined. Only the mandatory Archive element is defined. In this case the analysis will simply continue where it left off:

<?xml version="1.0" encoding="ISO-8859-1"?>
<febio_restart version="1.0">
  <Archive>out.dmp</Archive>
</febio_restart>

Example 2

In the following example an additional step is defined, which defines a new boundary condition and a new loadcurve.

<?xml version="1.0" encoding="utf-8"?>
<febio_restart version="2.0">
  <Archive>out.dmp</Archive>
  <Step type="solid">
    <Control>
      <time_steps>10</time_steps>
      <step_size>0.1</step_size>
    </Control>
    <Boundary>
      <prescribe bc="x" node_set="set1">
         <scale lc="2">1.0</scale>
      </prescribe>
    </Boundary>
  </Step>
  <LoadData>
    <loadcurve id="2" type="linear">
      <point>1, 0</point>
      <point>2, 1</point>
    </loadcurve>
  </LoadData>
</febio_restart>

Notice the “type” attribute in the Step section. This serves a similar purpose as the Module section in the FEBio input file and defines the solver that FEBio will use to solve this step. This attribute is required when defining steps in the restart file. (The Module section is not supported in the restart input file.)

The prescribed boundary condition references a node set named “set1”. This node set must be defined in the parent input file. No new node sets (or surfaces, etc.) can be defined in the restart input file.