How hiteshkumar18/orchestration-mea works
Orchestration-MEA is a lab control and analysis layer for MEA recordings. A user configures projects and analysis options in the web UI, starts the watcher, and receives independently tracked Network and ActivityScan results. The watcher waits for recording folders to settle, then runs the external MEA-Analysis driver locally or submits Network work to Slurm. Checkpoint and history views expose progress; reporting and NWB conversion support downstream use. Edges reflect README statements and the supplied source index/excerpts; several domain modules are present in the tree but their internal wiring was not sampled.
Main entry points: api.py Control API · watcher.py Recording watcher · activity_scan.py ActivityScan analysis · app.js Control UI
Components 25
Lab control
- Control UI
orchestration/static/app.js - Control API
orchestration/api.py - User attribution
orchestration/accounts.py - Folder picker
orchestration/native_picker.py
Run orchestration
- Recording watcher
orchestration/watcher.py - Driver options
orchestration/driver_schema.py - MEA checkout validation
orchestration/mea_repo.py - Slurm backend
orchestration/slurm_backend.py - Job memory guard
orchestration/memguard.py
Analysis outputs
- ActivityScan analysis
orchestration/activity_scan.py - Activity trends
orchestration/activity_trends.py - Data exploration
orchestration/explore.py - NWB conversion
orchestration/nwb - MaxWell summary
orchestration/maxwell_summary.py
Status and reports
- Checkpoint status
orchestration/checkpoints.py - Run history
orchestration/history.py - Run monitoring
orchestration/monitor.py - Run details
orchestration/rundetail.py - Tabular exports
orchestration/tabular.py - AI report handoff
orchestration/handoff.py - Report generation
orchestration/report
External systems
- MEA pipeline driver
- Recording folders
- Analysis outputs
Other components
- Lab user
Connections 28
- Lab user → Control UI: configures
README.md - Control UI → Control API: calls API
orchestration/api.py - Control API → Recording watcher: controls
orchestration/api.py - Control API → Driver options: loads options
orchestration/api.py - Control API → User attribution: attributes actions
orchestration/api.py - Control API → Folder picker: offers selection
orchestration/api.py - Recording watcher → Recording folders: polls for completion
README.md - Recording watcher → MEA checkout validation: validates checkout
orchestration/watcher.py - Recording watcher → Driver options: builds arguments
orchestration/watcher.py - Recording watcher → MEA pipeline driver: launches subprocess
README.md - Recording watcher → ActivityScan analysis: dispatches scan
README.md - Recording watcher → Slurm backend: submits Network jobs
README.md - Recording watcher → Job memory guard: limits job memory
orchestration/watcher.py - MEA pipeline driver → Recording folders: reads recordings
README.md - MEA pipeline driver → Analysis outputs: writes results
README.md - ActivityScan analysis → Recording folders: reads scan data
README.md - ActivityScan analysis → Analysis outputs: writes scan outputs
README.md - Slurm backend → Analysis outputs: copies results
README.md - Control API → Checkpoint status: queries status
orchestration/api.py - Recording watcher → Run history: records run changes
orchestration/watcher.py - Recording watcher → Checkpoint status: reads checkpoint state
orchestration/watcher.py - Control API → Run monitoring: exposes monitoring
orchestration/api.py - Control API → Run details: serves run details
orchestration/api.py - Control API → Run history: serves run history
orchestration/api.py - Control API → AI report handoff: prepares handoff
orchestration/api.py - AI report handoff → Report generation: builds report package
orchestration/handoff.py - MaxWell summary → Recording folders: reads recordings
orchestration/maxwell_summary.py - Data exploration → Tabular exports: uses tabular helpers
orchestration/explore.py