Links below are to the most recent development snapshots for the OOMMF upcoming 1.2 alpha 4 release. Be advised that the API for the 1.2a4 release is in rapid development, and substantial changes may occur between snapshots. Third party (contributed) software designed for the 1.2a3 release of OOMMF may not function with some or all of these snapshots. Compatibility patches for some of the contributed software may be found in the snapshot under the oommf/app/oxs/contrib/ directory.
This code requires Tcl/Tk. We recommend the latest stable (i.e., not alpha or beta) release of Tcl and Tk concurrent with the snapshot. OOMMF software does not support any alpha or beta releases of Tcl/Tk, and each snapshot of OOMMF may not work with later releases of Tcl/Tk. Check the release dates of both OOMMF and Tcl/Tk to ensure compatibility.
Important note 1: If you are using one of the pre-compiled binary snapshots, then the version of Tcl/Tk on your system must match the Tcl/Tk version and "bitness" against which the OOMMF binaries were built. For example, if you have 32-bit (x86) Tcl/Tk 8.4.19 installed, then you should download the build of OOMMF for Tcl/Tk 8.4.x/32-bit. If you have 64-bit (x64) Tcl/Tk 220.127.116.11 installed, then you should download the build of OOMMF for Tcl/Tk 8.5.x/64-bit. The 32-bit versions of Tcl/Tk + OOMMF run fine on 64-bit Windows, although, being 32-bit applications, they will not be able to run simulations requiring more than 2 GB of memory.
Important note 2: Do not try to unpack snapshots on top of and into an existing OOMMF installation. The pimake "upgrade" target is non-operative in the snapshots. Instead, snapshots should be unpacked into a fresh directory tree. Be sure to retain the directory structure when unpacking.
Important note 3: Each snapshot contains a version of the OOMMF User's Guide (OUG) current at the time of the snapshot:
Threaded Tcl/Tk note: The OOMMF snapshots all support thread enabled Tcl/Tk. If you are running Tcl/Tk 8.3.0 or later, you can check if your Tcl/Tk is thread enabled by starting a tclsh shell, and issuing the command "parray tcl_platform" at the prompt. If you get a "tcl_platform(threaded) = 1" line, then your build is thread enabled. The snapshots with pre-compiled Windows binaries assume a thread-enabled Tcl/Tk. If you build OOMMF from source, the build scripts will check to see if Tcl/Tk is thread enabled, and build accordingly.
OOMMF is an experimental system. NIST assumes no responsibility whatsoever for its use by other parties, and makes no guarantees, expressed or implied, about its quality, reliability, or any other characteristic.
We would appreciate acknowledgment if the software is used.
Back to OOMMF 1.2 software page, or
The National Institute of Standards and Technology (NIST) is an agency of the U.S. Commerce Department.
Freedom of Information Act (FOIA) /
No Fear Act Policy / ExpectMore.gov (performance of federal programs) / NIST Information Quality Standards /
Environmental Policy Statement
Date created: April 26, 2011 | Last updated: October 16, 2011 Contact: Webmaster