Debugging input¶

The normal view of MICpad does show the standard output of a MICRESS simulation next to the input file, resp. driving file, containing the simulation setup. If the driving file contains the standard comments and they do fit the parameters, the output can easily be compared with the input. Possible input errors can easily be located if not highlighted anyway.

Errornous driving file and standard output

However, this match between input and output might be lost during major modifications. For example, inserting an additional phase makes it necessary to modify the list of phase interactions. As the comments with the input questions are not updated automatically, orientation might get lost and the reason of an input error might be not obvious anymore.

In this case, setting a break point helps. It can be set by clicking on a line number of the driving file. MICRESS will stop reading input at this point and appropriate input question for the next parameter will be displayed in the standard output.

Input break point after first phase interaction