SaveImages (to a sub-folder) Error

There may be a bug in the SaveImages module. If selecting a subfolder option e.g. Output File Location: Default Output Folder sub-folder, this generates this error message:

Traceback (most recent call last):
File “cellprofiler\pipeline.pyc”, line 305, in run
File “cellprofiler\modules\colortogray.pyc”, line 139, in run
File “cellprofiler\cpimage.pyc”, line 497, in get_image
ValueError: Image must be color, but it was grayscale
Wed Jul 14 12:05:38 2010: Image # 2, module ColorToGray # 2: 0.02 sec (bg)
Pipeline saved with CellProfiler SVN revision 9978
Traceback (most recent call last):
File “cellprofiler\gui\moduleview.pyc”, line 867, in on_browse_pressed
TypeError: get_absolute_path() takes exactly 3 arguments (1 given)
Traceback (most recent call last):
File “cellprofiler\gui\moduleview.pyc”, line 867, in on_browse_pressed
TypeError: get_absolute_path() takes exactly 3 arguments (1 given)
Traceback (most recent call last):
File “cellprofiler\gui\moduleview.pyc”, line 867, in on_browse_pressed
TypeError: get_absolute_path() takes exactly 3 arguments (1 given)
Traceback (most recent call last):
File “cellprofiler\gui\moduleview.pyc”, line 867, in on_browse_pressed
TypeError: get_absolute_path() takes exactly 3 arguments (1 given)

Hi Amos,

Hmmm, what are setting the sub-folder to when you select “Default Output Folder sub-folder”? (i.e, the box under the “Output File Location” setting when you select this option)
-Mark

Hi Mark,
All the settings are shown in the attached image. The initially the box below “Output File Location” has the text “None” in it, this can be deleted (or indeed I can type into this box). The error is generated when I click on the folder icon on the RHS of the box.

I noticed as well that the module LoadImages as a similar box, “input image file location” this can be set to “Default Image Folder sub-folder” and the folder icon to the RHS of this does launch a file browser without error (perhaps the functionally is correctly implemented here?).

thanks,
Amos


Hi Amos,

Thanks for the screenshot! I’ve reproduced this error and it definitely is a bug, but fortunately, it has been solved already in our development code. Our upcoming release will not have this problem.

Cheers,
-Mark

Cheers Mark,
I’ll await your next release.

Rgds,
Amos

Hi Amos,

I believe that our current release (r10415) has fixed this problem.
-Mark