Missing required argument: fileand refuses to operate when using the -ipat option unless a non "-ipat" file is also given.
Processing input from stdineven though the image is of a type (e.g., BMP) that any2ppm can otherwise interpret.
ERROR: couldn't recognize image data
ERROR: Input error during read of Microsoft .bmp file sample.bmp bitmap: Illegal palette indexSolution: As with item 2, the most comprehensive solution is to install the tkimg Tcl/Tk extension. Alternatively, you can replace oommf/ext/if/if.cc with this file, or else apply this patch. This bug affects the C++ code, so rebuilding OOMMF is required. (2004-Mar-20)
Notes on patch files:
A number of patch files are provided above for fixing problems. After downloading a patch, exit all OOMMF applications and cd to the top-level OOMMF directory (i.e., the directory named "oommf"). Then run the command
patch -p1 < patchfilewhere patchfile is the name of patch file. If there are any patch "rejects", then some hand-editing may be necessary, but this shouldn't happen if you are patching against an unmodified OOMMF distribution.
The command `patch' is a Unix text processing utility. A version for Windows can be downloaded from the GnuWin32 project.
If the patch only affects Tcl code (files ending in the .tcl extension), then after applying the patch you can restart OOMMF and be good to go. If the patch affects the C++ source (.cc or .h files), then follow the rebuilding instructions in the next section.
Any file replacement or patch involving OOMMF C++ source (files with the .cc or .h extension) will necessitate a recompile and relink of OOMMF. Of course, this requires a suitable compiler. To rebuild, cd to the top-level OOMMF directory (i.e., the directory named "oommf"), and issue the commands:
tclsh oommf.tcl pimake distcleanThe first command ("distclean") deletes all binary object files and executables, so the second command can rebuild from scratch. This is necessary if you were using an OOMMF binary release, because it is unlikely that the release binaries are compatible with your compiler/linker. If you built from source, then you should be able to bypass the "distclean" step. Additional instructions can be found in the installation section of the OOMMF User's Guide.
tclsh oommf.tcl pimake
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.
Commercial equipment and software referred to on these pages are identified for informational purposes only, and does not imply recommendation of or endorsement by the National Institute of Standards and Technology, nor does it imply that the products so identified are necessarily the best available for the purpose.
Back to the OOMMF 1.1 software page, or