thladnik / vxpy-app Goto Github PK

Y mirror signal does not match the number of frames recorded by MScan. The signal seems to be recorded correctly (no gaps or jumps in the signal) but the number of peaks in the Y mirror signal does not match the number of frames recorded in MScan. The difference is usually around 20/50 frames for a recording of 5000-8000 frames total. The peakfinding algorithm was checked multiple times and the error does not lie there. Somehow vxpy records a y mirror signal with more peaks than frames recorded by MScan. This frightens me.

If there are parameters that use a dictionary to map keys with a value (i.e. motion_axis, motion_type), currently the actual values (transformation matrix for motion_axis or assigned integer for motion_type) are being saved to the display file. It would be much more user friendly if instead the keys ("vertical","rotation", etc.) were saved.

Y mirror signal does not match the number of frames recorded by MScan. The signal seems to be recorded correctly (no gaps or jumps in the signal) but the number of peaks in the Y mirror signal does not match the number of frames recorded in MScan. The difference is usually around 20/50 frames for a recording of 5000-8000 frames total. The peakfinding algorithm was checked multiple times and the error does not lie there. Somehow vxpy records a y mirror signal with more peaks than frames recorded by MScan. This frightens me.

ERROR 15:27:56,159 vxpy...ces.camera.basler_pylon Unable to grab frame from <vxpy.devices.camera.basler_pylon.BaslerCamera object at 0x7f93648b5070> // 3791651083, The image stream is out of sync.

Camera can crash during recording. Problem detecting camera. Can be fixed by unplugging and replugging camera USB.

Add feature to eye detection routine GUI (maybe just a box to check or a drop down window) to select if eyes are being recorded from above or below so that direction can be determined correctly.

The GUI for image scaling (contrast, range) is still very buggy and can't be fixed to the same values for both streamed images.

It should be possible to read in frames that are not 512x512. To be able to scan in MScan a t 8Hz, the frame size needs to be reduced to 256x256. It would be convenient if the expected frame size can be easily adjusted.