Open nyama8 opened 5 days ago
After reviewing the qt3scan code a bit I think there's a fair amount of improvements that could be made. For example, we can likely decouple from the qt3uw/nipiezojenapy
repo and keep the hardware level controllers within qdlutils
. In addition it will likely require some more intensive restructuring which I don't mind doing.
I would definitely like this and in my eyes, the python code is less friendly to use b/c these changes are not implemented compared to the MATLAB code.
Some points I've been griping about for a while:
qt3scan
needs to be brought to parity with the Matlab confocal scan code. This involves (but is not limited to) the following features:qt3ple
). In doing this, logic needs to be implemented to handle having multiple windows open and releasing hardware when not actively scanning or moving.np.nan
values during the scan to enable right-click-based movement to positions not yet scanned.qt3ple
application added a DAQ digitial reader in which the user can instead specify a time for readout and the back end computes the number of cycles automatically (clock rate is part of the hardware configuration still, but does not affect the results).Please add more suggestions for improvements/features below. Remember that the goal is for this code to be as lightweight as possible while maintaining easy functionality.