The MIF 1.1 format is an older micromagnetic problem specification format used by the mmSolve 2D solvers. It is not compatible with the MIF 2.1 format used by the Oxs 3D solvers. However, the command line tool mifconvert may be used as a conversion aid; mifconvert is also called automatically by Oxs solvers when a MIF 1.x file is input to them.
A sample MIF 1.1 file is included below. The first line of a MIF file must be of the
form “# MIF x.y”, where x.y represents the format revision
number. (The predecessor MIF 1.0 format was not included in any
released version of OOMMF.)
After the format identifier line, any line ending in a backslash,
‘\’, is joined to the succeeding line before any other processing
is performed. Lines beginning with a ‘#’ character are comments
and are ignored. Blank lines are also ignored.
All other lines must consist of a Record Identifier followed by a parameter list. The Record Identifier is separated from the parameter list by one or more ‘:’ and/or ‘=’ characters. Whitespace and case is ignored in the Record Identifier field.
The parameter list must be a proper Tcl list. The parameters are parsed (broken into separate elements) following normal Tcl rules; in short, items are separated by whitespace, except as grouped by double quotes and curly braces. Opening braces and quotes must be whitespace separated from the preceding text. The grouping characters are removed during parsing. Any ‘#’ character that is found outside of any grouping mechanism is interpreted as a comment start character. The ‘#’ and all following characters on that line are interpreted as a comment.
Order of the records in a MIF 1.1 file is unimportant, except as explicitly stated below. If two or more lines contain the same Record Identifier, then the last one takes precedence, with the exception of Field Range records, of which there may be several active. All records are required unless listed as optional. Some of these record types are not supported by mmProbEd, however you may modify a MIF 1.1 file using any plain text editor and supply it to mmSolve2D using FileSource.
For convenience, the Record Identifier tags are organized into several groups; these groups correspond to the top-level buttons presented by mmProbEd. We follow this convention below.