The story of how software is created in a lab
How a side project by a PhD student becomes the lab's software, and what happens when one person is left maintaining it.
Notes from the labBlog
What I've learned building and repairing research software, one lab at a time.
How to create a good documentation for your lab?
Who reads your lab's documentation, how to organise it (how-to, tutorials, API), and how to keep it up to date automatically.
Setup a closed-loop experiment
Open Ephys, Falcon or custom software: how to choose a platform for real-time, closed-loop neuroscience experiments.
Task-based behavior control experiment
BeHive, the maze automation software built for the Kloosterman lab: a plugin system, a state-transition task model and three researchers running experiments in parallel.