Replies: 1 comment 1 reply
-
you can just exclude the border, you'll almost never get good ROIs at the border |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I've been thinking about the
motion.border_nan
setting. At first, I was happy to use the default setting of "copy," but I noticed that with either "copy" or "min," I see a band of highly-correlated pixels around the image border (which makes sense), and I sometimes get a large number of elongated ROIs within that band. Maybe not a big deal if they are all rejected, but with my current settings some are accepted. So I wondered whether different border settings could help, specifically leaving them as NaN (though maybe cropping would actually be the best?)I'm wondering about these lines in the main tutorial notebook:
If I understand correctly, this basically overrides the setting for anything other than 'copy' and forces the border to take the min value over the whole movie. (Which also fixes the behavior of 'min' which otherwise, I think, computes a border value for each chunk individually?) My question is, is there a strong reason for this? For example, mesmerize-core doesn't set
border_to_0
in its equivalent code. But when I did end up with some NaNs in the movie passed to CNMF (due to a bug in my code), I got an error. Shouldpreprocess.check_nan
be turned off ifmotion.border_nan
is True?Thanks,
Ethan
Beta Was this translation helpful? Give feedback.
All reactions