Experiments¶
This section contains ready-to-run experiments for Spikeling. Each page is designed to work both in:
- Hardware mode (real device connected over USB/serial)
- Emulator mode (no hardware required)
The experiments follow an electrophysiology-inspired workflow:
- apply a defined input (DC injection, stimulus waveform, light, synapses)
- observe Vm and spikes
- record/export (CSV)
- measure one or two simple metrics
- interpret the result
If you are still installing or connecting the system, start with: - Quickstart → First experiment
If you need conceptual background first, see: - User guide → Concepts
Start here (recommended path)¶
-
Patch-clamp-style labs
A set of classroom-friendly labs that teach current clamp logic, excitability, adaptation, and synapses. -
Excitability and threshold
Find threshold, quantify the silent→spiking transition, and show how noise makes threshold probabilistic. -
Adaptation and firing patterns
Measure spike-frequency adaptation and compare firing regimes across neuron modes. -
Synapses and inputs
Build synapses (axon → synapse), demonstrate excitation vs inhibition, and observe temporal summation. -
Network with two units
Create minimal network motifs and map presynaptic activity to postsynaptic output. -
Stimulus recipes
A cookbook of stimuli (steps, sine/triangle, chirps, noise, light flicker) with “what it teaches” guidance.
Choosing an experiment¶
If you only have one unit: - do Excitability and threshold - then Adaptation and firing patterns - use Stimulus recipes to extend
If you have two units: - add Synapses and inputs - then Network with two units
If you are teaching a large class: - use Emulator mode for the first run of each experiment to standardise expectations, then transition to hardware.
Recording and analysis (recommended)¶
Most experiments become more valuable if students record and analyse at least one dataset.
- Export workflow: User guide → Recording and export
- Starter analysis: Data analysis → Python quickstart
Troubleshooting¶
If something does not behave as expected: - start with Quickstart → Troubleshooting - confirm cables and ports using Controls and I/O