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

Understanding bad_frames.npy usage #1158

Open
darioringach opened this issue Jan 28, 2025 · 0 comments
Open

Understanding bad_frames.npy usage #1158

darioringach opened this issue Jan 28, 2025 · 0 comments

Comments

@darioringach
Copy link

Discussed in #1157

Originally posted by darioringach January 28, 2025
Using:
Name: suite2p
Version: 0.14.4

I am crating an int64 np array shaped as (#nframes,) in bad_frames.npy
Suite2p seems to read and report the number of bad frames correctly after registration.
So it seems all is working Ok...

However, the data in Fall.mat shows very similar data (fluorescence and spikes) to what I obtain without the bad_frames (which comprise about 20% of the frames). Morever, ops.meanImg is exactly the same in both cases.

What am I missing?

Thank you!

Dario

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

No branches or pull requests

1 participant