MICpad is a driving (input) file editor specialized on MICRESS.

## One comprehensive view of a MICRESS simulation¶

Driving file, standard text output and tabular data, list of result types in one graphical user interface.

Overview

The headlines of the driving file sections are listed in a tree view to ease navigation.

Bookmarks

## Start, pause and stop simulations directly on your desktop¶

Control simulation

The Run Configuration dialog allows to choose a MICRESS or HOMAT application, resp. converters like Mesh2HOMAT, for each individual input file. The kind of input will be detected automatically and the appropriate application will be used.

Note

Try to use standard file extensions (.dri, .hin, *.min) to ensure a correct input detection.

The main menu Simulation or the toolbar allows to control your running simulation. Each application will be running in a separate process, not as a MICpad subprocess. If you exit MICpad, you will be asked whether you want to kill your running simulation processes or not.

Automatic refresh does monitor simulations results files from applications started outside of MICpad, e.g. on a compute cluster.

## Monitoring of results¶

Text output, e.g. tabular fractions

A list of available results allows easy monitoring of generated tabular data which can also be plotted in separate windows. Use the context menu in the tabular view to access these plotting, resp. exporting, options of selected columns.
Field data can be visualized by the 2D viewer Display MICRESS using the Display button.

## Converting to MICRESS 7.1 input syntax¶

Syntax conversion

Successful conversion to MICRESS 7.1

The syntax conversion Convert 6.4 to 7.1 will convert a current 6.4 driving file to an intermediate representation of a 7.1 driving file, i.e. in principle only keywords.
This file can be run by MICRESS 7.0 and the resulting mirrored input file '*.in' will contain a pretty printed 7.0 file. Use the IN->DRI button to copy it back to your driving file.

Note

Check the conversion log for errors and warnings. If a conversion was not successful, a not well understood/parsed 6.4 file is the reason. Use Check 6.4 to see where the problem is and eventually choose an alternative input setting to make parsing (and conversion) successful. Afterwards, the original settings can be enabled in the new file, again.

The conversion from 6.4 is offered because of the major input changes in 7.0, i.e. reordering of blocks, input shifts. There are only minor changes from 7.0 to 7.1.