Error when grouping images




I have been setting up various tracking pipelines and always run in the problem that the grouping does not work when using the LoadImages module. It works like a charm when using the newer integrated modules, but the same logic does not work in the old LoadImages module. The reason why I use the old module is that I want to run it headless on a cluster and that with very long movies or fast movies, the loading takes an insane amount of time. This issue is several years old, would be nice to fix it.


Can you explain more about this issue a bit- is it this problem? Can you take advantage of batch files perhaps instead?
Can you use LoadData to load your movies?

I’d have to check with our software team to be sure, but given everything on their plate I have my doubts whether they’ll have time to add new functionality to a legacy module anytime soon. My guess is that LoadImages may not even be available in CP 3.0, though again I’m not sure about that.


I hope LoadImages is not dumped, that would make cell profiler to compatible with cluster compute and essentially make it useless for HCS. It’s not a legacy module if the software itself suggests using it for large amount of images.
It seems that the error was fixed and it was my specifications of the image sets that was wrong. I apologise for this. I assumed because in the past it didn’t group images correctly that the error was the same. Here it seems to work. I have only one channel though, so I’ll try with multiple channels and let you know.



I hope LoadImages is not dumped, that would make cell profiler to compatible with cluster compute and essentially make it useless for HCS.

It’ll certainly still be possible to run CP in a cluster environment even if LoadImages goes away; you can use

  • LoadData + a file CSV (that CP itself will generate for you using the first four image modules if you like)
  • The first four image modules with CreateBatchFiles
  • The first four image modules plus --file-list
  • The first four image modules plus simply passing CP the name of the folder where all the images are (new in 3.0, and one of the big advantages LoadImages had)

I’m not sure of any guidance specifically to use LoadImages in case of large image sets, and I can’t find it easily, but I’d definitely be interested in learning more about your particular use case and why you think it’s important the module be kept. I don’t think it’s been decided yet whether or not LoadImages will stay in 3.0, but the more compelling use cases we have for any given functionality in the software the more likely it’ll survive the upgrade.


Hi Beth,

not sure that anything you mention will work in our cluster environment. The head nodes handles the dispatching to the nodes and there is no reach through from the work directory where the images are stored. This is a pretty standard way to set up a cluster. The CreateBatch Files is meant for Windows, which is not an environment for clusters. I’ll discuss with our HPC guys to see what will work and what not.
Thank you in any case for looking into this. It’s never easy, I know of a few places who are struggling to put CP on their clusters.

Marc Bickle, PhD
Head HT-Technology Development Studio
Max Planck Institute of Molecular Cell Biology and Genetics
Pfotenhauerstr. 108
D-01307 Dresden

phone +49 351 210 2595
fax +49 351 210 1689

DRESDEN-concept Technology Platform: