Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.


  • Fixed modules require all settings to be entered prior to running the analysis. Stored settings are read from imatest-v2.ini and can be changed by user input. Batches of images can be run. Results are displayed as figures and can be saved as image (usually PNG), CSV, XML, and JSON files. In most cases we recommend running an interactive analysis prior to running  fixed analyses. 

  • Interactive modules are run from Graphic User Interfaces (GUIs) that allow results to be queried and modified after the analysis has been run. This allows you to explore results in great depth. Results can be saved as image (usually PNG), CSV, XML, and JSON files.



Fixed vs. Interactive module summary



Usually run after settings have been made and tested in interactive mode.

It’s generally best to run in Interactive mode first — to explore results in depth and make sure calculations are properly set up.

Graphic results in Figures allow limited manipulation (zooming or rotation for 3D images).

Graphic results displayed in GUI windows allow a high degree of manipulation: You can change calculation and display settings and you can select any available display. You can analyzed results in great depth.

Batches of files can be run.

Only a single file can be analyzed (one exception: several files can be combined (signal-averaged) to improve signal-to-noise ratio (SNR)).

Most are available as Industrial Testing (IT) modules (EXE or DLL programs that can run in production/quality control environments).

Not directly available in IT.

Images must be read from files. They cannot be directly acquired.

Images can be read from files or acquired directly from devices (development boards from Aptina, Omnivision and others as well as devices supported by the Matlab Image Acquisition toolbox). Directly-acquired images can be continuously refreshed in realtime.