A module that formerly worked has stopped working

A module that formerly worked but now crashes can often be fixed by removing the section for the module in imatest-v2.ini, (or in imatest.ini, multicharts.ini or rescharts.ini prior to Imatest 4.2), as appropriate. Imatest 4.1+ may open an error reporting window when a crash occurs. We recommend sending us the error report before applying the fix.

Note 1:  Reinstalling the same build of Imatest rarely solves this type of problem, but downloading and installing the current build of the most recent version your license allows often helps. Go to www.imatest.com/support/download/, select the appropriate release and operating system, then click Download Upgrade.

Note 2:  rescharts.ini and multicharts.ini were eliminated in Imatest 4.2+. All settings are stored in imatest-v2.ini, which can be opened for editing from the Imatest, Rescharts, or Multicharts windows. imatest-v2.ini is compatible with non-Latin characters (Asian languages). Changes are described in INI file format changes in 4.2.

Note 3:  To help us prevent similar errors in the future, please send the error report. In most cases an Error reporting window will appear. Follow the instructions, making sure to include your correct email and a brief description of what you were doing. If the Error reporting window fails to appear you can click File, Copy current session, then paste the session into an email to support@imatest.com. If you’ve closed and restarted Imatest since encountering the error, you can click File, Copy last session.

 

  • Record or remember your settings for the broken module (so you can manually restore them later). This can often be done conveniently using a screen capture utility.
  • Click INI File Settings in the Imatest, Rescharts, or Multicharts window. (In Imatest 4.2+ It makes no difference because all settings are stored in imatest-v2.ini.)
  • Select INI File Editor. This opens the INI File Editor, shown below.

The INI File Editor is a powerful tool for editing ini (settings) files.
You can often fix a broken (but formerly working) module by selecting the section
corresponding to the module, then clicking Delete section. followed by Save.

  • Select a section to view, edit, or delete from the Section dropdown menu (near the top). Section names usually correspond to module names. Errors can often be fixed by (A) removing an entire section (this restores the default values) or (B) by editing a single line (if you know what you’re doing).

Some section names don’t fit the pattern. We are leaving section names unchanged (for now) for backwards compatibility. We apologize for the confusion.

    • Stepchart module:
      [q13] is used for the Stepchart module, which originally supported only linear grayscale stepcharts, such as the Kodak Q-13 and Q-14. Note that [stepchart] is used for grayscale stepcharts in Multitestnot for Stepchart.
    • Multicharts and Multitest modules
      [gamut] is used for settings common to all (or most) Multicharts/Multitest charts. There are also sections for individual test chart analyses whose name corresponds to the chart name (generally abbreviated). Here are the lists of names (taken from the code).
      For (mostly) color charts:  {‘cc24’; ‘it8’; ‘special’; ‘qpcard’; ‘ccsg’; ‘stepchart’; ‘special’; ‘cdm28’; ‘sfrp20’; ‘utt’; ‘spydercheckr’; ‘hale’; ‘te226’; ‘mxn’; ‘cdm-dc48’; ‘colorgauge’; ‘rezchecker’; ‘cmp’; ‘esfriso’; ‘iso-16505’}
      For multi-row Grayscale charts:  {‘iso-14524’; ‘qa-61’; ‘qa-62’; ‘iso-15739’; ‘ite’; ‘oecf-20’; ‘sqcirc’; ‘eia’; ‘qa-79’; ‘mxn’; ‘sdr-36’; ‘sq-20’; ‘contrast-res’; ‘te269’}
       
  • (A) To fix a problem by resetting a section, Select the section, then press Delete section. You will need to manually set the desired settings to the your preferred values. This method is recommended for most users.
     
  • (B) To fix a problem by editing a line, Select the section that contains the line, select the line in the large window, make the change in the line edit window just above the large window, then press Enter. This method requires more knowledge than (A).
     
  • To save your changes press Save, which is grayed out until changes are made. If you with to cancel your changes, press either Reload ini file or Close.
Example: Checkerboard stops working. Press the INI File dropdown menu, then select INI File Editor. Select the [colorcheck] section, then press Delete section, Save, Close. You’ll need to manually restore your old settings in the next run.

Other solutions

Sometimes the problem is in the image file itself. Matlab has difficulty reading files with bad header data. Look at the command window to see if there are warnings about problems reading the file. You can often fix such problems by “laundering” the file by reading it into an image viewer/editor such as Irfanview (an excellent free program), then saving it with a similar name.

Read More

Problem Starting Imatest after Installation

Symptoms of the problem:

After installation, upon attempting to start Imatest, nothing happens.  

Running using diagnostic mode, or from a command window may show an error similar to this:

Previously accessible file “C:\Program Files\Imatest\Master\imatest_mcr\imatest\
startup.m” is now inaccessible.
Error:Error in mclFreeStackTrace.

Sources of the problem:

  • Inability for Imatest to write to the program files folder, such as: C:\Program Files (x86)\Imatest\v4.0\Master\imatest_mcr\
  • Anti virus can block Imatest and it’s installer from writing files to the above location.  ESET is a particular brand of anti-virus that has been known to cause this.
  • Systems that have Java disabled by their administrative group policies

Potential Solutions:

  • Disabling Anti-virus during Installation or during the first run
  • Running Imatest as Administrator
  • Correcting the administrative policy blocking Java, or moving to a system without that policy

Solution for Imatest IT:

  • Delete the C:\Users\%USERNAME%\AppData\Local\Temp\%USERNAME%\mcrCache8.1 folder then re-run the test
Read More