Computational toolbox for large scale Calcium Imaging Analysis, including movie handling, motion correction, source extraction, spike deconvolution and result visualization.
This would be the most up-to-date version of CaImAn. This may or may not be an issue, but it pertains to calling register_multisession with more than 2 sessions.
I noticed in the register_multisession code, you run a for loop over sessions, calling register_ROIs. When calling register_ROIs, you define A1 as A[sess] and A2 as A_union, which A_union=A[0].copy(). What is confusing is why we would then call template1 as templates[sess] and template2 as templates[sess-1] (see screenshot). Why wouldn't we define template2 as templates[0] given that A1 is indirectly defined as A[0].copy()?
This would be the most up-to-date version of CaImAn. This may or may not be an issue, but it pertains to calling
register_multisession
with more than 2 sessions. I noticed in theregister_multisession
code, you run a for loop over sessions, callingregister_ROIs
. When callingregister_ROIs
, you defineA1
asA[sess]
andA2
asA_union
, whichA_union=A[0].copy()
. What is confusing is why we would then calltemplate1
astemplates[sess]
andtemplate2
astemplates[sess-1]
(see screenshot). Why wouldn't we definetemplate2
astemplates[0]
given thatA1
is indirectly defined asA[0].copy()
?