Trouble Shooting

Nothing is perfect, and JPIV even less.

What do those cryptic java exceptions in the Cmd-frame mean?

The programming work is focused on convenient editing of PIV parameters and easy control over the evaluation chain. It is mostly left to the user, to check whether the combination of parameters is meaningful. Only a few common mistakes are catched by error handlers. For example, if you start a PIV evaluation without selecting input files, you get the message "No files selected.". In most cases, however, there is no special treatment of the error, you just get the exception stack trace dumped into the Cmd-frame. For example, if you use a region of interest in your PIV evaluation that extends the image, you get the message:
Exception in thread "Thread-18" java.lang.IllegalArgumentException: Crop The rectangular crop area must not be outside the image.
   at javax.media.jai.JAI.createNS(JAI.java:1087)
   at javax.media.jai.JAI.create(JAI.java:973)
   at javax.media.jai.JAI.create(JAI.java:1395)
   at jpiv2.PivImg.getSubImage(PivImg.java:286)
   at jpiv2.PivEvaluation.addCorrelation(PivEvaluation.java:237)
   at jpiv2.PivEvaluation.doPivEvaluation(PivEvaluation.java:139)
   at jpiv2.PivEvaluation.run(PivEvaluation.java:81)
For debugging purposes these messages are anyway more useful, because the code lines are given in brackets. Also the propagation of errors is documented. If you encounter a problem that can not be ascribed to the non-logic combination of parameters, and if you can reproduce it, please send the stack trace and your settings file to me. The code is certainly not free of bugs! You find the settings file "jpiv_settings.ser" in your home directory.

Why are my settings reset to default values?

This happens, when the user settings class was modified. This is sometimes the case after an update. New settings classes are generally not compatible with old objects, so that a new settings file is generated and initialized with default values.