Madison Swain-Bowden

I've verified that I encounter this issue as well. It doesn't occur within the first few images of a sequence though. I tried running through the images in test mode...

After further investigation, it looks like two things: 1. I only get this issue when I run multiple workers (e.g. if I run `Sequence1` and `Sequence2` of the sample data...

Error Traceback: ``` Worker 0: Error detected during run of module TrackObjects#9 Worker 0: Traceback (most recent call last): Worker 0: File "/home/aether/git/CellProfiler/cellprofiler/pipeline.py", line 1912, in run_image_set Worker 0: self.run_module(module,...

It looks like this might be an issue with `cpmorphology.faster_minimum_distance2`

Thanks for checking that! I know less about centrosome than I do CellProfiler, we'll wait for @0x00b1 or @mcquin to comment before moving forward.

Hello @dschetel! Unfortunately, I don't believe that is possible with the current implementation. One way you could potentially speed up the reading of the file is by splitting the processing...

Hi @ge2sasag! Are you using the compiled version of CellProfiler by chance? What settings are you using for active contours? And if possible, can you provide a minimal image set/pipeline...

It appears that environment variables that are created for an environment using `conda env config vars set ` also attempt to get unset every time an environment is deactivated once...

This issue still persists using the instructions I described above.

It definitely is, we will give that a shot and report back!