wormscore
Blind scoring of fluorescent neurons in C. elegans, with measurement and genetics statistics.
Built for scoring reporter neurons (normal / dim / missing) in confocal z-stacks. Nothing is tied
to one neuron, marker or microscope: those are settings in each project's config.json, so other
organisms work the same way.
- Blind: every image gets a random code. Genotypes and file names stay in a sealed key until you finish scoring.
- Fixed display: every image from the same microscope is shown with the same brightness range. You can page through z-planes and overlay brightfield.
- Measured, not decided: suggested cell bodies and your drawn regions are measured (peak, mean, local background, sharpest plane, saturation). The numbers are written to files and never shown while you score. The software never labels a cell normal, dim or missing.
- Traceable: every number links to the exact file, path, series and SHA-256 checksum it came from.
- Reproducible: every parameter and software version is appended to
log.mdon each run. - Local: runs on your computer only. Nothing is uploaded.
Supported raw formats: Leica .lif, Zeiss .czi, OME-TIFF (including Micro-Manager style files with
a .companion.ome). Channel identity (marker vs brightfield) is read from metadata, never guessed.
Install
Windows, no Python needed: download wormscore-windows.zip from the Releases page, unzip it,
and double-click wormscore.exe. It opens the wormscore app window: your projects on the left and the
four steps (Scan data, Build blind set, Score, Unblind) as a guided list with progress and time left.
The older launcher window is still there for one version: wormscore.exe --classic.
With Python 3.12 or newer:
pip install wormscore
The newest code from GitHub: pip install git+https://github.com/arjunkai/wormscore.git
This installs a wormscore command and wormscore-launcher, which opens the same app window (in your
default browser on macOS and Linux).
Try it in two minutes (simulated data)
wormscore demo my_demo
wormscore inventory my_demo
wormscore prepare my_demo
wormscore app my_demo
demo writes 20 simulated worm heads (controls with two normal cells; mutants with cells that are
normal, dim or missing at random) and a demo_truth.csv you can check your calls against later.
In the app window, use Try a demo..., then the steps in order: Scan data > Build blind set > Score.
Real worms: wormscore demo my_demo --real (or Real worm images in the app's demo dialog) downloads four
L1 heads with an endogenous GFP reporter, about 150 MB, from
Sun and Hobert 2021
(Zenodo 5602160, CC BY 4.0). Each file is checked against its
MD5 from the Zenodo record and cached in %LOCALAPPDATA%\wormscore\demo_cache (~/.cache elsewhere).
The two reporters stand in for two genotypes; both are normal animals, so this is for practice.
The images are not part of this repository.
Using it on your own images
- Copy your data to a local folder (not a synced cloud folder if the data is not yours to share):
wormscore copy D:\from\drive C:\data\my_copycopies every file, checks each one by SHA-256 and makes the copies read-only. - Make a project:
wormscore init C:\projects\my_project, then editconfig.json: pointsourcesat your images, write genotype rules, and name your neurons. Seeexamples/config_example.json. - Scan:
wormscore inventory my_projectlists every file (outputs/manifest.csv: raw image, duplicate, derived projection, reference, hidden system file) and every image with its metadata and channel identity (outputs/inventory.csv). Check the flags column. - Build the blind set:
wormscore prepare my_projectapplies the inclusion rules, assigns codes, finds and measures suggested cells, and writes the sealed key. Excluded images and the reasons are inoutputs/excluded.csv. To leave out images by name (for example a plate with the wrong reporter), add"exclude": [{"match": "*pattern*", "reason": "why"}]to that source. Images taken after scoring started can be added withwormscore prepare my_project --add-new-images(scan first): existing codes stay the same and new images get codes after the last one. - Score:
wormscore app my_project. For each image: answer any yellow questions, score each neuron, save, then outline each cell body (or accept a suggestion) and save regions. - Unblind after scoring:
wormscore unblind my_project --i-have-finished-scoring. Writesoutputs/unblinded/merged.csv(scores + numbers + key, one row per image), a summary, and results tables:per_neuron.csv(one row per animal and neuron, for plotting),penetrance.csv(animals with 0, 1, 2 ... affected neurons) andfisher_tests.csv(Fisher's exact within each microscope, Bonferroni-corrected). Setunblinding.reference_genotypeinconfig.jsonto test against a control. Optional, off unless set inunblinding:question_outcomesturns the per-neuron questions into the same penetrance and Fisher tables (for example "process defect" when a dendrite question is answered "no"), andinteractiontests a double mutant against the value two single mutants predict (Product model by default) with a binomial test. Also optional: a secondary definition of "affected" (descriptive, within one microscope), planned comparisons, one-sided tests, labelled sources, and comparisons across microscopes for chosen measures (with warnings). All of these are recorded as an analysis plan before scoring and locked once scoring starts. See docs/METHODS.md.methods_text.mdis a draft Methods paragraph on blinding, measurement and statistics; fill in theblindingsection ofconfig.json(who coded, who scored) or edit the [brackets] it leaves.
Project folder
| Path | Contents | Open while scoring? |
|---|---|---|
config.json |
every parameter | yes |
log.md |
every run: parameters, software versions, counts | yes |
outputs/manifest.csv, inventory.csv, excluded.csv |
what was found and what was left out | yes |
outputs/auto_measurements.csv |
numbers for suggested spots | avoid until done |
blind/ |
images for scoring, named by code | used by the app |
scoring/ |
your scores, regions and their measurements | scores yes; avoid roi_measurements.csv |
key/ |
code to file, genotype, settings | no, not until scoring is finished |
How it works
See docs/METHODS.md for every step in plain language, suitable for adapting into a Methods section, including the measurement definitions and their limits.
Development
pip install -e .[dev]
pytest
The tests build a simulated project and check the measurements, the blinding (no genotype or file name reaches the scoring page), code stability, the unblinding locks and traceability. Leica and Zeiss readers are checked against real files locally; real images are never committed.
Build the Windows app: packaging\build_windows.bat.
Privacy
This repository contains code only. .gitignore excludes image formats, keys, scores and outputs.
Do not commit or upload data that belongs to someone else.
License and citation
MIT License (see LICENSE). If you use wormscore in research, please cite the version you used.
Each release has its own DOI on Zenodo; doi:10.5281/zenodo.23520610
lists all versions and resolves to the latest. GitHub's "Cite this repository" button (from
CITATION.cff) gives the reference, and log.md
in your project records which version ran each step.
wormscore reads Leica files with liffile and Zeiss files with
czifile (both BSD-3). The Windows app bundles these and other
libraries; their licenses are in THIRD_PARTY_LICENSES.txt next to wormscore.exe.
Metadata
Release files for wormscore 0.7.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| wormscore-0.7.1.tar.gz | 130.0 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| wormscore-0.7.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 248.6 kB
Release files / wormscore-0.7.1.tar.gz
| Download URL | wormscore-0.7.1.tar.gz |
|---|---|
| Size | 130.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
ec311dbf584000326289f605a652ab9776158b9eff4e6ba893a49eabbe60ca4c
|
|
BLAKE2b-256 checksum How to use checksums |
16cc7b139d290f155fc7e8baf1d7dafd9bc315a25a0543d0dda8bebb9c4119c5
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 21, 2026.
Transparency logRelease files / wormscore-0.7.1-py3-none-any.whl
| Download URL | wormscore-0.7.1-py3-none-any.whl |
|---|---|
| Size | 118.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
597b2d71059b8c5c0e3600d96fcea3a8791652abba80b97a0d91512ea8cf92d3
|
|
BLAKE2b-256 checksum How to use checksums |
84364277b1b8a1f528ccae6f989df566eb5a5dce7d67f3e3e33d6896958c4a64
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 21, 2026.
Transparency logSecurity for wormscore 0.7.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for wormscore-0.7.1.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 21, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.