Apply concepts in practical workflows, quality control, tools, and reproducible research operations.
This track focuses on applying connectomics knowledge to real research workflows: running analyses on petascale datasets, applying machine learning and computer vision to EM data, maintaining reproducibility, and producing publication-ready outputs. Resources connect directly to the MouseConnects dataset, the Connectome Quality tool, and the workflow pipeline from acquisition through circuit interpretation. Learners should have completed the Core Concepts & Methods foundation before focusing here.
Fadel alignment: Skills, Meta-learning
Who this is for. Readers like Maya, who has the fundamentals and now needs a defensible result, and Amir, an AI scientist who can build the model but not yet judge whether the data supports the claim.
How to work through this track
Time: 70-80 hours, typically over 14-18 weeks, alongside a real project.
Starting point: Core Concepts & Methods, or equivalent working familiarity with EM data and reconstruction.
Get reproducible access to real data (~5 h) Dataset access guide, then Technical Unit 04's query lab. You finish with: A version-pinned notebook with a reproducibility header.
Learn how a segmentation fails before you try to repair one (~8 h) Modules 06 and 07, the segmentation and quality-control pair that Technical Unit 08 builds on. You finish with: An error taxonomy you can apply to a real volume, and one documented correction pass with its quality impact stated.
Learn proofreading as an allocation problem (~8 h) Technical Unit 08 and its planning lab. You finish with: A proofreading plan with a triage rule, defined levels, and a stopping rule someone else could evaluate.
Measure quality against your own endpoint (~8 h) The connectome quality notebook path, steps 1-4. You finish with: A measured statement of how proofreading changes your headline number.
Analyze without fooling yourself (~10 h) Technical Unit 09, including the three-null worked example and the error simulation. You finish with: A motif analysis with a defended null, corrected multiple comparisons, and an error band.
Build the operational habits (~36 h) Modules 12-16, 18, 20, 21. You finish with: Working practice in pipelines, big data, visualization, and reproducibility.
What "done" looks like
Completion here is a capability, not a set of pages visited. You are through this track when:
Every figure you produce records its dataset version, query code, and date.
You can state your proofreading level and stopping rule, and defend both.
You report an effect size under more than one null model, and you say which you pre-specified.
You have run an error-sensitivity simulation on your own result and know whether it survives.
Common detours
The predictable ways learners lose time on this track:
Analyzing against an unpinned segmentation. The code runs; the answer drifts.
Optimizing an aggregate quality metric instead of the endpoint the project actually reports.
Treating Erdos-Renyi as an acceptable null for a spatially embedded, degree-heterogeneous graph.
Mode axis
This track in each mode
The topic is the same in all three. What changes is the sequencing, who supplies feedback, and what counts as done — see modes for the full description of each.
đź§
Self-study
Available
Workable alone, but only if you have a real dataset in front of you. Without one the proofreading and analysis labs become thought experiments, which is exactly the failure mode this track exists to prevent.
Worth knowing: Do the version-pinning habit from the first query, not after your first result drifts.
Modules 06, 07, 12-16, 18, 20 and 21 have session kits. Best run alongside a live project rather than as a standalone course.
Worth knowing: Bring your own group's data if you have it. The generic scenarios work, but the arguments about triage priority get real when the volume is theirs.
This is the track the intensive would be built on. The proofreading and QC work here is the closest the site comes to contributory tasks, but nothing downstream currently consumes the output.
Computer vision methods—from classical filters to deep learning—applied to EM imagery for segmentation support, morphology extraction, and quality diagnostics.
LLM-assisted patch triage and annotation support with human-in-the-loop verification gates to prevent hallucination and unsupported scientific inference.
Reproducible preprocessing workflows from raw connectomics data through analysis-ready releases with integrity checks, QC metrics, and full provenance.
Defensible statistical inference for connectomics: choosing null models, controlling multiplicity in high-dimensional tests, and reporting with explicit assumptions.