The pipeline does not currently support batch parallelization, processing images sequentially. For large screening datasets this may be a practical limitation, though the per-image processing time (seconds to minutes depending on image size and analysis modules) is acceptable for most experimental workflows.
Nice work! This seems like a useful tool for making image analysis more accessible.
I was curious whether there was a specific reason for the limitation you mention here: "The pipeline does not currently support batch parallelization, processing images sequentially."
My first thought was that segmentation might be the main constraint (especially when using Cellpose). But it seems like one possible architecture would be to run segmentation first and save masks, then parallelize the downstream steps (puncta detection, colocalization, morphology measurements, etc.) across images or cells.
That part of the pipeline seems like it could be relatively straightforward for Claude to parallelize with something like multiprocessing or joblib and might significantly improve throughput for larger datasets, since downstream analysis would no longer be tied to per-image segmentation.
Was something like this considered, or are there constraints (e.g., Cellpose behavior, I/O, memory usage) that make parallelization less practical?