Lesson Flow

Learn

Goals and Concepts

Start with the capability target and concept set for this module.

Practice

Studio Activity

Apply the ideas in a guided activity tied to realistic outputs.

Check

Assessment Rubric

Use the rubric to verify competency and identify improvement targets.

Teach

Slides and Worksheets

Open the teaching deck, worksheet, and editable slide source.

Interactive Lab

Practice in short loops: checkpoint quiz, microtask decision, and competency progress tracking.

Checkpoint Quiz

Q1. Which output most clearly demonstrates module competency?

A measurable artifact linked to an explicit method A general reflection about interest in neuroscience A list of future goals without evidence

Competency is shown through measurable, method-linked evidence.

Q2. What should always accompany a technical claim in this curriculum?

A limitation or uncertainty statement A motivational quote A citation count

Every claim should include boundaries and uncertainty.

Q3. What is the best next step after identifying a gap in understanding?

Define a concrete practice task and verification criterion Skip to a harder module Ignore the gap if progress is slow

Progress improves when gaps become explicit practice targets.

Submit Quiz

Microtask Decision

Choose the action that best improves scientific reliability.

Record method, version, and decision rationale before sharing results Share results quickly and document details later Rely on memory for why decisions were made

Check Decision

Progress Tracker

State is saved locally in your browser for this module.

• Read capability target
• Complete studio activity
• Review assessment rubric
• Pass checkpoint quiz
• Complete microtask
• Complete annotation challenge

0% complete

Reset Progress

Annotation Challenge

Click the hotspot with the strongest evidence for the requested feature.

A B C

Selected hotspot: none

Check Annotation

Capability target

Publish a reproducibility-ready connectomics package (data + methods + metadata + limitations) that an external group can audit and reuse.

Why this module matters

Connectomics studies are technically dense and often impossible to interpret without exact workflow context. FAIR and reproducibility are not paperwork; they are scientific validity infrastructure.

Concept set

1) FAIR as implementation checklist

• Technical: findable identifiers, accessible storage, interoperable formats, and reusable metadata each require concrete engineering choices.
• Plain language: “FAIR” only counts if someone else can actually find, open, and use your work.
• Misconception guardrail: posting files online is not enough.

2) Reproducibility is layered

• Technical: computational reproducibility (same code/data => same result) differs from inferential reproducibility (same conclusion under reasonable variation).
• Plain language: rerunning code and trusting conclusions are related but not identical.
• Misconception guardrail: a notebook that runs once does not guarantee robust science.

3) Hidden curriculum in reproducibility

• Technical: unwritten norms include naming conventions, release etiquette, assumption disclosure, and reviewer-ready method transparency.
• Plain language: many expectations are “known by insiders” unless we teach them directly.
• Misconception guardrail: learners should not be penalized for norms that were never made explicit.

4) FAIR applied to connectomics

Each FAIR principle maps to concrete connectomics infrastructure. Findable means assigning DOIs for datasets and providing stable CAVE endpoints that resolve to specific data versions. Accessible means offering open APIs and tools like CloudVolume that allow programmatic data retrieval without manual download. Interoperable means using standard formats such as SWC for neuron morphologies, Zarr for volumetric data, and NWB for neurophysiology so that tools across labs can ingest each other’s outputs. Reusable means materialization versioning in CAVE, which lets any researcher retrieve the exact state of the segmentation and annotations at a given point in time.

A practical reproducibility checklist for any connectomics analysis release should include: the dataset version or release identifier, the CAVE materialization number (if applicable), the code commit hash for all analysis scripts, the environment specification (e.g., conda environment file or Docker image), and the full parameter configuration used. Without all five elements, a third party cannot reliably reproduce the analysis, even with access to the same underlying data.

Hidden curriculum scaffold

• What senior reviewers expect but rarely state:
  • Dataset and code version IDs in figure legends/methods.
  • Explicit handling of failed runs and excluded samples.
  • A short “known limitations” section with concrete failure modes.
• How to make these norms visible to trainees:
  • Provide reproducibility checklists before assignments.
  • Share annotated examples of strong/weak method reporting.
  • Require mentorship feedback on documentation, not only results.

Core workflow: FAIR/reproducibility release

1. Define release scope (dataset slice, code commit, parameter set).
2. Add machine-readable metadata and provenance fields.
3. Validate rerun path in a clean environment.
4. Write methods/limitations notes for external users.
5. Publish with changelog and deprecation policy.

Studio activity: reproducibility hardening sprint

Scenario: Your lab plans to release a connectomics analysis package to collaborators.

Tasks

1. Build a FAIR metadata sheet for one analysis output.
2. Create a reproducibility checklist with pass/fail criteria.
3. Draft a “known limitations” section and one deprecation note.
4. Peer-test another team’s package for reuse friction.

Expected outputs

• FAIR metadata form.
• Reproducibility checklist + validation log.
• Reuse friction report with remediation recommendations.

Assessment rubric

• Minimum pass
  • Core provenance fields are present and clear.
  • Re-run instructions are testable by peers.
  • Limitations and assumptions are explicit.
• Strong performance
  • Identifies hidden reproducibility norms and makes them explicit.
  • Anticipates downstream reuse failure points.
  • Produces concise, audit-friendly documentation.
• Common failure modes
  • Missing version identifiers for data/code.
  • Methods descriptions that omit key parameters.
  • “Reproducible in principle” claims without validation evidence.

Content library references

• Provenance and versioning — CAVE materialization and pipeline lineage
• Data formats and representations — Standard formats for interoperability
• Proofreading tools — CAVE as a model for versioned science

Teaching resources

• Workflow context: Connectomics workflow
• Reference context: Atlas Connectomics Reference
• Quality context: Connectome Quality tool
• Mentorship support: Ask-an-Expert

Evidence anchors from connectomics practice

Key papers/resources to use

• FAIR Guiding Principles (2016)
• Peng (2011) - Reproducible Research in Computational Science
• H01 dataset landing + paper

Key datasets/platforms

• MICrONS Explorer
• FlyWire
• Workflow overview

Competency checks

• Can an external learner rerun your result with your documentation alone?
• Are dataset and code versions explicit in every core artifact?
• Are your known limitations concrete enough to guide interpretation?

Quick practice prompt

Take one prior analysis output and add:

1. provenance metadata,
2. reproducibility instructions,
3. a 5-line limitations section.

Teaching Materials

Slide Deck

Classroom-ready deck links for teaching and delivery.

Open slide deck page

Open rendered HTML deck

Download PowerPoint (.pptx)

Activity Worksheet

Learner worksheet aligned to the studio activity and rubric.

Open worksheet

Slide Source

Marp source file for editing and rendering.

course/decks/marp/modules/module21.marp.md

Related Content

Datasets

• /datasets/workflow
• /datasets/mouseconnects

Personas

• /avatars/gradstudent
• /avatars/mentor

Tools

• /tools/connectome-quality/

Frameworks

• research-incubator-model
• education-models

Next Modules

• module22