pyphotometry/code

pyPhotometry code, GUI and micropython firmware

code's Issues

Record from multiple boards

It would be useful to be able to record from multiple pyPhotometry boards using a single instance of the GUI. This functionallity could be modelled on pyControl's Experiments Tab, allowing users to configure, save, and run multi-setup experiments.

Automatic calibration of acqusition cycle timings

When using pyPhotometry with different photodetectors from the ones it was originally tested with it may be necessary/desirable to modify the timing of the time division acqusition cycle to match the rise and decay times of the transient response of the photodetectors. It would be useful to have functionallity to measure this using the pyPhotometry hardware/software itself and automatically work out suitable timings.

[bug] Integer overflow when the photometry data is too long

Hello,

Recently I ran into a bug importing data from pyPhotometry. The default data type of np.arange is np.int32, which will lead to an integer overflow when the recoded length is longer than 35 min at 1000Hz from the following line:

code/tools/data_import.py

Line 48 in 2e95ee7

time = np.arange(analog_1.shape[0])*1000/sampling_rate # Time relative to start of recording (ms).

Record session end time

Currently the session start date + time is recorded (using the computers clock) in the session file but the end time is not. It would be useful to record the end time so that if users want to sync pyphotometry data with event times recorded using the computer clock they can linearly interpolate between start and end times based on sample number, which should be more accurate than just using the start time.

Output sync pulses from Digital signal BNC connectors

It would be useful to be able to output sync pulses from the pyPhotometry board. This could be done using one of the Digital signal BNC connectors as these are directly connected to pins on the pyboard.