With the addition of python routines in Imatest 5.0, several components require a working python installation. When some installation problems occur, the user may encounter the error message:
Undefined variable “py” or class “py.model.Message”.
With the addition of python routines in Imatest 5.0, several components require a working python installation. When some installation problems occur, the user may encounter the error message:
Undefined variable “py” or class “py.model.Message”.
Error Message: Error in extracting CTF file to ‘C:\ProgramData\Imatest\mcr_cache\4.5\Master\mcrCache9.0.1\imates0’. Details: ‘Could not set last modified time: C:/ProgramData/Imatest/mcr_cache/4.5/Master/mcrCache9.0.1/imates0/toolbox/imaq/imaqextern/drivers/win64/genicam/genICam_v2_4/redist/Microsoft_VC80_CRT_x86_x64.msi: Broken pipe
Solution:
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). We show how to do this conveniently using the INI File Editor.
An error reporting window normally opens when a crash occurs. We recommend sending us the error report before applying the fix. Click on Send Error Report, Note that a screen capture of the window |
|
We encourage you to send us the image (in a separate email to support@imatest.com). Having the image can make it easier for us to replicate and fix the error. |
Note 1: Please check to be sure the problem isn’t caused by a badly framed or badly photographed image. In such cases, Note 2: Reinstalling the same build of Imatest rarely solves this type of problem, although 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 3: All settings are stored in imatest-v2.ini, which can be opened for editing from the INI File Settings dropdown menu in the Imatest, Rescharts, Color/Tone Interactive, or Uniformity Interactive windows. imatest-v2.ini is compatible with non-Latin characters (Asian languages). Changes after Imatest 4.2 are described in INI file format changes in 4.2. Note 4: To help us prevent similar errors in the future, please send the error report. In most cases an Error reporting window (shown above) will appear. Follow the instructions, making sure to enter 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. |
Quick summary: the key to fixing this type of error is to remove the section (or critical lines in the section) of the INI file (usually imatest-v2.ini) that corresponds to the broken module. This restores the default values. Section names are enclosed in brackets ([…]) in the INI file. |
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 . followed by .
Some section names don’t fit the pattern. We are leaving section names unchanged (for now) for backwards compatibility. We apologize for the confusion.
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. |
This can also be accomplished in a text editor by pressing INI File, View/Edit INI file.
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.
Affects: Version 3.5.1 and below.
The following message appears several times in the DOS window when you try to save data:
Function ‘get_param’ is not implemented in standalone mode.
This is an issue with the MATLAB runtime library. This has no effect on the saved images, and it’s rarely visible since the DOS window remains in the background.
This is fixed