Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

motion energy as roi type #9

Closed
imgross opened this issue Jul 29, 2019 · 2 comments
Closed

motion energy as roi type #9

imgross opened this issue Jul 29, 2019 · 2 comments

Comments

@imgross
Copy link

imgross commented Jul 29, 2019

Hi Carsen,

thanks for setting up this cool GUI ! As we talked in the Data Science course it would be great to also have an ROI type that is able to read out absolute motion energy. In my case it would be for extracting time points when my arm moves into the FOV of the camera.

Cheers,
Isa-Maria

@carsen-stringer
Copy link
Member

This has now been added as field "motion" to the _proc.npy output file :)

@phanhuynh
Copy link

Hi Carsen, sometimes my _proc.npy output file does not contain the field 'motion'. Do you know what could be causing this: dict_keys(['filenames', 'save_path', 'Ly', 'Lx', 'sbin', 'fullSVD', 'save_mat', 'Lybin', 'Lxbin', 'sybin', 'sxbin', 'LYbin', 'LXbin', 'avgframe', 'avgmotion', 'avgframe_reshape', 'avgmotion_reshape', 'motion', 'motSv', 'movSv', 'motMask', 'movMask', 'motMask_reshape', 'movMask_reshape', 'motSVD', 'movSVD', 'pupil', 'running', 'blink', 'rois', 'sy', 'sx'])

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants