Distributed CellProfiler

Distributed CellProfiler is a tool that runs the CellProfiler image-analysis platform across a cluster of computers, letting researchers process large…

  • AI
  • Automation
  • Tools & Utilities
Distributed CellProfiler is a tool that runs the CellProfiler image-analysis platform across a cluster of computers, letting researchers process large cell-image datasets in parallel instead of on a single machine.

Platform availability

Available on 0 of 10 platforms

  • Unraid (not listed)
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm (not listed)
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)
  • Any server (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

57/100 Fair

Maintained
74last commit 37 days ago
Popular
3345 GitHub stars
Easy to install
250 install platforms, install notes, Docker image
Light to run
No data
Security check
85no serious findings, CI

Based on 4 of 5 factors.

GitHub stars
45
Open issues
15
Last commit
2026-10-15
Latest release
v2.2.2
Activity
stale

Checked 3 days ago - source: GitHub (DistributedScience/Distributed-CellProfiler)

Resources & Compatibility

ARM (e.g. Raspberry Pi) is not supported.

Checked 54 days ago - source: Docker Hub image tags and published docs

First-install notes

  • Install the Dask packages first Run the pip install command to get dask and distributed. Without them, the app can't connect to a cluster or run tasks on Dask workers. source
  • Start a local cluster for testing Create a Dask client without giving it an address to start a scheduler and worker on your own machine. This is the easiest first run and avoids connection errors from a missing cluster address. source
  • Point the app at the scheduler When using a real cluster, initialize the client with the scheduler address, like Client('host:port'). If you omit or mistype this, the app won't know where to send work. source
  • Set up the AWS infrastructure first Prepare the four AWS resources the app needs — an SQS queue, an ECS cluster, an S3 bucket, and a spot fleet of EC2 instances — using boto3 and the AWS CLI (or the AWS Management Console) before running the worker container. source

Fetched 43 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

Does Distributed CellProfiler run CellProfiler inside Docker on AWS?

Yes. It runs encapsulated Docker containers with CellProfiler in Amazon Web Services infrastructure.

What cloud costs should I expect when using Distributed CellProfiler?

The DCP code is open source and completely free to use, but cloud compute power and storage in AWS or another cloud provider may cost money.

Where should I store DCP files to avoid file-loading problems?

Keep the pipeline, images, CSV list, and metadata on S3, since that worked in the reported Amazon network file-loading issue.

Answers sourced from forum.image.sc, forum.image.sc, github.com

Community

Collected 48 days ago - public community threads