#Imagej piv macro how to#

Launch ImageJ again, this time from the console as described above.

If the first method does not work, and you can reproduce the hang: Press ⌃ Ctrl + A to select it, then ⌃ Ctrl + C to copy it to the clipboard.If successful, it will open a new window with the stack trace. There are two ways to create such a snapshot, known as a “thread dump” or “stack trace”.

#Imagej piv macro how to#

This information can give the developers valuable hints about how to fix the problem. If ImageJ appears to hang-i.e., it stops responding to inputs-it is often helpful to take a “snapshot” of where the program is at after the hang occurs. For maximum debugitude, turn on both! If ImageJ freezes or hangs This might reveal different information than using the techniques described above. There is another debug mode, which can be enabled in the Edit › Options › Misc… menu, by checking Debug mode. See the Logging page for more about SciJava logging. Valid levels include: none, error, warn, info, debug and trace. You can control the log level more precisely by setting the system property.

Make a copy of ImageJ-win64.exe called debug.exe.

To diagnose problems with ImageJ, it is often helpful to launch it in debug mode:ĭEBUG=1 /Applications/ImageJ2.app/Contents/MacOS/ImageJ-macosx See also How do I launch ImageJ with a different version of Java?. On macOS, you can use this script to diagnose which versions of Java are installed on your system. “Java 1.8.0_45” or similar indicates Java 8, while “Java 1.7.0_79” or similar indicates Java 7.

The relevant number is the one after “Java 1.”-so e.g. You can tell which Java version ImageJ is using by clicking the ImageJ status bar and looking for the part that says e.g. How to troubleshoot problems Checking the Java version