Trivial change in probe.py with the geometry of NN Poly3 with 25um pitch (A1x32-Poly3-xx-25s-yy).
In maps.py, I added the port-site mapping of burung with 32 channels through amps 2 and 3. This port-site mapping actually describes the mapping of the ports in the recording system to the channels in the headstage (typycally sites).
If an adapter is added, it is described by an array (col0=headstage end, col1=probe end).
Function apply_adapter takes in a port-site mapping and an adapter, and remaps the site that corresponds to each port.
This should add a bit of modularity, if in some future we will have other systems, headstages and adapters.
todo/todiscuss: allow probe files and adapters to be entered as files? (systems should be stable over time and we don't want anyone to change the mappings without going through a pull request, but probes and adapters can be more volatile, specially in debugging phases).
Trivial change in probe.py with the geometry of NN Poly3 with 25um pitch (A1x32-Poly3-xx-25s-yy).
In maps.py, I added the port-site mapping of burung with 32 channels through amps 2 and 3. This port-site mapping actually describes the mapping of the ports in the recording system to the channels in the headstage (typycally sites).
If an adapter is added, it is described by an array (col0=headstage end, col1=probe end).
Function apply_adapter takes in a port-site mapping and an adapter, and remaps the site that corresponds to each port.
This should add a bit of modularity, if in some future we will have other systems, headstages and adapters.
todo/todiscuss: allow probe files and adapters to be entered as files? (systems should be stable over time and we don't want anyone to change the mappings without going through a pull request, but probes and adapters can be more volatile, specially in debugging phases).