# Output¶

### Output Times¶

The times for user-defined intermediate outputs can be specified in this section. For convenience, the user should include an early output time in order to check whether the simulation has started correctly. Series of outputs with a constant interval or factor between the times can be easily defined with linear_step or logarithmic_step (for geometric series). In the example shown here, the user requests outputs for $t = 0.25 s$ and $1.0 s$, every $0.5 s$ until $10.0 s$, and every $1.0 s$ until $25.0 s$.

All these input elements can be combined and repeated in arbitrary way. This input section has to be finished using the keyword end_of_simulation.

There are some further options which can be used in this input block for the output times at an arbitrary position:

• first: Requests an extra output after the first internal time step.
• end_at_temperature: This keyword is followed by a termperature value. It requests an additional output and terminates the execution when the given temperature is reached.

Example: Time input data: linear_step

...
# Time input data
# ============
# Finish input of output times (in seconds) with 'end_of_simulation'
# 'regularly-spaced' outputs can be set with 'linear_step'
# or 'logarithmic_step' and then specifying the increment
# and end value
# ('automatic_outputs' optionally followed by the number
#  of outputs can be used in conjuction with 'linear_from_file')
#  'first'                  : additional output for first time-step
#  'end_at_temperature'    : additional output and end of simula-tion
#                             at given temperature
first
0.1
linear_step 0.5 10.00
linear_step 1.0 25.00
end_at_temperature 1200.
end_of_simulation
...


### Output files¶

In this section, the types of output files which shall be written by MICRESS® must be specified. These outputs are either binary files which can be viewed with DP_MICRESS (unless another format is specified explicitly in the Name of output files section), or text files which can be opened with standard text editors.

Traditionally, each output type has to be activated or deactivated in an extra line in the driving file and in the requested order by using the corresponding positive or negative keyword, e.g. out_restart or no_out_restart for writing or not writing a restart file (see above). Alternatively, terse, verbose or legacy modes can be used. These options will be detailed in the next edition of this manual. In the meantime please consult the MICRESS® forum (www.micress.de).

The meaning and the contents of the individual output files in alphabetic order of their extension is documented in chapter 3.3.

Example: Enable output of different type (legacy mode)

# Output files
# ------------
# Selection of the outputs
# [legacy|verbose|terse]
# Restart data output?                                 ('rest')
# Options:     out_restart      no_out_restart         [wallclock time, h.]
out_restart
# Grain number output?                                 ('korn')
# Options:     out_grains       no_out_grains
out_grains
# Phase number output?                                 ('phas')
# Options:     out_phases       no_out_phases          [no_interfaces]
out_phases
# Fraction output?                                     ('frac')
# Options:     out_fraction     no_out_fraction        [phase number]
out_fraction 0 1
# Average fraction table?                              ('TabF')
# Options:     tab_fractions    no_tab_fractions       [front_temp] [TabL_steps]
tab_fractions
...