Open the teaching deck, worksheet, and editable slide source.
Interactive Lab
Practice in short loops: checkpoint quiz, microtask decision, and competency progress tracking.
Why Map the Brain Checkpoint
Question Framing Microtask
Pick the best study question for a first connectomics project.
Progress Tracker
State is saved locally in your browser for this module.
0% complete
Motivation-to-Question Annotation
Click the region that most strongly supports the case for high-resolution connectomics.
Selected hotspot: none
Capability target
Write one connectomics study question with measurable structural outputs and one explicit non-claim. Articulate a personal motivation statement linking daily annotation work to a larger scientific mission.
Why this module matters
Motivation drives persistence, but technical progress requires disciplined question framing. Connectomics demands sustained effort: proofreading thousands of neurons, tracing axons through noisy volumes, and reconciling ambiguous merges. Without a clear sense of purpose, even talented annotators burn out. This module anchors learners’ curiosity in concrete, testable questions so that motivation survives the transition from excitement to routine.
Concept set
1) Question before method
Technical: define target measurement before tool choice. A well-formed connectomics question specifies the circuit, the organism, the resolution, and the expected structural readout (e.g., synapse count, path length, motif frequency).
Plain language: know what you are asking first.
Misconception: tools generate good questions automatically. In reality, tools like FlyWire or CAVE are powerful but directionless without a hypothesis.
2) Structure informs, not fully explains
Technical: structural data constrains hypotheses but does not alone prove dynamic function. A synapse between neuron A and neuron B tells you connection exists; it does not tell you whether the synapse is active under a given stimulus.
Plain language: maps guide, they do not finish the story.
Misconception: connectome equals full explanation. The C. elegans connectome was completed decades ago, yet behavior prediction from wiring alone remains an open problem.
3) Motivation should be bounded
Technical: ambitious goals need near-term measurable milestones. Break “map the whole brain” into “proofread 50 neurons in optic lobe region X by Friday.”
Plain language: big vision, small testable steps.
Misconception: broad vision statements are sufficient project plans.
4) Why curiosity matters in connectomics
Technical: the field requires sustained motivation through tedious annotation work. Large-scale connectomics projects (FlyWire, MICrONS, MouseConnects HI-MC) depend on thousands of hours of manual proofreading. Curiosity about the underlying biology is the fuel that keeps annotators engaged through repetitive tasks.
Plain language: you need a reason to keep going when the work gets boring.
Misconception: excitement at the start is enough to carry you through a multi-month project.
5) The “motivation gap”
Technical: early excitement diverges from the reality of proofreading thousands of neurons. The gap between “I want to understand the brain” and “I am fixing merge errors in segment 47,832” is real and predictable. Recognizing this gap in advance helps learners build coping strategies (milestone celebrations, rotation between tasks, connecting daily work to publications).
Plain language: the honeymoon phase ends; plan for it.
Misconception: if the work feels tedious, you chose the wrong field.
6) Growth mindset in technical training
Technical: errors are learning opportunities, not failures. In proofreading, every false merge you catch teaches you about the segmentation algorithm’s failure modes. Every split error reveals tissue preparation artifacts. Tracking your error patterns builds expertise faster than avoiding mistakes.
Plain language: mistakes teach you what the computer got wrong and why.
Misconception: good annotators never make errors. In practice, even expert proofreaders disagree on 5-10% of decisions.
7) The connectomics “why”
Technical: linking daily annotation work to the larger scientific mission of understanding brain circuits. Each proofread neuron contributes to a wiring diagram that enables circuit-level hypotheses about sensory processing, motor control, learning, and disease. The FlyWire project demonstrated that distributed annotation by 287 contributors could produce a whole-brain connectome.
Plain language: every neuron you trace is a sentence in the story of how brains work.
Misconception: my individual contribution is too small to matter.
Core workflow
Identify curiosity question.
Convert to measurable structural hypothesis.
Define one metric and one limitation.
Plan first dataset/tool touchpoint.
Write a personal motivation statement connecting your question to a long-term scientific goal.
Detailed run-of-show (90 minutes)
Block 1: Opening hook (00:00-12:00)
Instructor script: “Welcome. Today we answer one question: why would anyone spend years mapping brain wires? Let me show you.” Play 3-minute clip from Sebastian Seung’s TED talk. Then show a before/after of a raw EM image vs. a fully reconstructed neuron. Ask: “What questions could you answer with this reconstruction that you could not answer with the raw image?”
Collect 3-4 responses on whiteboard. Highlight that each response implies a different measurement.
Block 2: Connectomics landscape (12:00-28:00)
Instructor script: “Let’s ground this in real projects.” Walk through three case studies in 5 minutes each:
C. elegans (White et al., 1986): the first complete connectome. 302 neurons. What it enabled, what it could not explain.
FlyWire whole-brain (Dorkenwald et al., 2024): 130,000+ neurons, 287 proofreaders, first whole-brain connectome of an adult animal with complex behavior.
MouseConnects HI-MC (ongoing): scaling to mammalian cortex, the challenge of petascale data.
After each case study, ask: “What question drove this project?” Write answers on board.
Block 3: Question framing workshop (28:00-48:00)
Instructor script: “Now it is your turn. Take 5 minutes to write down the broadest brain question you care about. Do not filter.” (5 min silent writing)
“Now narrow: what specific circuit or region relates to your question? What structural measurement would you need?” (5 min revision)
Pair-share: partners critique each other’s questions using the checklist: Does it specify organism? Region? Measurement? Limitation? (10 min)
Block 4: Evidence-boundary critique (48:00-65:00)
Instructor script: “Every good connectomics question has a twin: the non-claim. What can your structural data NOT tell you?” Present three example hypotheses and their non-claims. Learners practice writing non-claims for their own questions.
Class discussion: collect 3 examples of well-formed question + non-claim pairs.
Instructor script: “Before we close, I want you to write something personal. Why are you here? Not the resume version — the real version. What about brains or circuits or data makes you want to do this work? And how will you remind yourself of that reason when the work gets tedious?”
Silent writing: 10 minutes. Prompt: “Write 3-5 sentences explaining why you want to work in connectomics and what you will do when motivation dips.”
Voluntary sharing: 2-3 learners read their statements aloud.
Block 6: Exit ticket (80:00-90:00)
Submit: (1) your testable question with metric, dataset, and non-claim; (2) your motivation statement.
Instructor script: “These two documents are your compass for the rest of the program. We will revisit them in Module 06.”
Studio activity: “Write your connectomics motivation statement”
Overview
Learners produce two artifacts: a question-to-hypothesis sheet and a personal motivation statement.
Part A: Question-to-hypothesis sheet (30 minutes)
State your broad curiosity question (1 sentence).
Narrow to a specific circuit, region, or organism (1 sentence).
Define the structural measurement you would need (e.g., synapse count between cell types X and Y).
Specify the dataset you would use (e.g., FlyWire, MICrONS, FAFB).
State one non-claim: what your structural data cannot tell you.
Define a falsification condition: what result would disprove your hypothesis?
Part B: Motivation statement (20 minutes)
Write 150-300 words addressing:
Why connectomics? What drew you to this field?
What specific aspect of brain circuitry fascinates you?
How does your daily work (annotation, proofreading, coding) connect to the larger mission?
What is your plan for sustaining motivation through tedious stretches? (Be specific: milestones, rewards, accountability partners, rotation between tasks.)
Peer review (10 minutes)
Exchange motivation statements with a partner. Provide feedback on: (1) specificity — does the statement name concrete goals? (2) sustainability — does the plan for maintaining motivation seem realistic?
Assessment rubric
Minimum: question, metric, limitation all present; motivation statement addresses why and how.
Strong: clear falsification condition, realistic scope, motivation statement includes specific sustainability strategies.
Failure: motivational text without measurable outputs; motivation statement is generic (“I like brains”).
White, J. G., Southgate, E., Thomson, J. N., & Brenner, S. (1986). The structure of the nervous system of the nematode Caenorhabditis elegans. Philosophical Transactions of the Royal Society B, 314(1165), 1-340.
Dorkenwald, S., et al. (2024). Neuronal wiring diagram of an adult brain. Nature, 634, 124-138.
Seung, H. S. (2012). Connectome: How the Brain’s Wiring Makes Us Who We Are. Houghton Mifflin Harcourt.
Dweck, C. S. (2006). Mindset: The New Psychology of Success. Random House.
Lichtman, J. W., & Denk, W. (2011). The big and the small: challenges of imaging the brain’s circuits. Science, 334(6056), 618-623.
Quick practice prompt
Write a 3-sentence hypothesis with one metric and one caveat. Then write 2 sentences explaining why this question matters to you personally.
Teaching Materials
Slide Deck
Classroom-ready deck links for teaching and delivery.