Calculating H Fields from Magnetization: mag2hfield

The mag2hfield utility takes a MIF 1.1 micromagnetic problem specification file (.mif) and a magnetization file (.omf) and uses the mmSolve2D computation engine to calculate the resulting component (self-magnetostatic, exchange, crystalline anisotropy, Zeeman) and total energy and/or H fields. The main use of this utility to study the fields in a simulation using magnetization files generated by an earlier mmSolve2D run.

Launching
The mag2hfield launch command is:

tclsh oommf.tcl mag2hfield [standard options]
   [-component [all,][anisotropy,][demag,][exchange,][total,][zeeman] \
   [-data [energy,][field]] [-energyfmt fmt] [-fieldstep #] \
   mif_file omf_file [omf_file2 ...]

where

-component [all,][anisotropy,][demag,][exchange,][total,][zeeman]

Specify all energy/field components that are desired. Optional; default is total, which is the sum of the crystalline anisotropy, demagnetization (self-magnetostatic), exchange, and Zeeman (applied field) terms.

-data [energy,][field]

Calculate energies, H fields, or both. Energy values are printed to stdout, H fields are written to files as described below. Optional; the default is energy,field.

-energyfmt fmt

Output C printf-style format string for energy data. Optional. The default format string is "%s".

-fieldstep #

Applied field step index, following the schedule specified in the input MIF file (0 denotes the initial field). Optional; default is 0.

mif_file

MIF micromagnetic problem specification file (.mif). Required.

omf_file

Magnetization state file. This can be in any of the formats accepted by the avfFile record of the input MIF file. Required.

omf_file2 ...

Optional additional magnetization state files.

The H field output file format is determined by the Total Field Output Format record of the input MIF 1.1 file. The output file names are constructed using the form basename-hanisotropy.ohf, basename-hzeeman.ohf, etc., where basename is the input .omf magnetization file name, stripped of any trailing .omf or .ovf extension.

OOMMF Documentation Team
September 28, 2017