Jonny Saunders

I did something like this here https://github.com/CohenLabPrinceton/pvp/blob/master/pvp/common/values.py

Got started on this https://github.com/wehr-lab/autopilot/blob/7a8c561d2a94c1ce5f69f621dd1c40be3e7e1ef7/autopilot/core/subject.py#L40-L217

I see two things here: first, the `HARDWARE` parameterization in `prefs.json` needs to match the structure of the `HARDWARE` dictionary that is the class attribute. (note that `pin_numbers` is just...

"board-numbering" is the canonical way of referring to, well, the board number (the position of the pin on the board). this is currently documented here: https://docs.auto-pi-lot.com/en/dev/autopilot.hardware.html ...

Document behavior of triggers re: advancing stage when not desired. https://github.com/wehr-lab/autopilot/issues/148#issuecomment-1033255537

all the various config files and the structure of the user directory should get its own page since it's a central concept that a lot of people (justifiably) miss, eg....

add security notice -- this software is intended to be used on a local area network not exposed to the public internet and has not been hardened in any way,...

> installation instructions (here: https://docs.auto-pi-lot.com/en/latest/guide/installation.html) do not clarify the best practices for having a separate git folder with the autopilot code, and a user autopilot folder with prefs, protocols, data,...

use and configuration of the systemd daemon

use this to document the structure of the wiki ... on the wiki https://github.com/wehr-lab/autopilot/issues/127#issuecomment-906794608