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.