I have two signals in my movies: ch1 = green non-functional signal, ch2 = red calcium signal (jRGECO1a). When I assign Ch2 to the functional signal in the ops file, it fails to extract meaningful ROIs from the second functional channel. Assigning Ch1 vs Ch2 fails to extract relevant ROIs from the jRGECO channel. Splitting the data and running the jRGECO data separately works as expected and extracts calcium signals from clearly defined cells.
This error only occurs if the data comes from a .raw file (ThorImage), but not if I use .sbx data (neurolabware). Is there something about the .raw files that is preventing the channel assignment? For .raw files, note that the average intensity outputs will always show the non-functional channel as the channel 1, no matter which one I choose as the functional channel. Whereas when I load in an .sbx file, the first channel in the gui is the jRGECO channel when I select it as the functional channel.
Describe the issue:
I have two signals in my movies: ch1 = green non-functional signal, ch2 = red calcium signal (jRGECO1a). When I assign Ch2 to the functional signal in the ops file, it fails to extract meaningful ROIs from the second functional channel. Assigning Ch1 vs Ch2 fails to extract relevant ROIs from the jRGECO channel. Splitting the data and running the jRGECO data separately works as expected and extracts calcium signals from clearly defined cells.
This error only occurs if the data comes from a .raw file (ThorImage), but not if I use .sbx data (neurolabware). Is there something about the .raw files that is preventing the channel assignment? For .raw files, note that the average intensity outputs will always show the non-functional channel as the channel 1, no matter which one I choose as the functional channel. Whereas when I load in an .sbx file, the first channel in the gui is the jRGECO channel when I select it as the functional channel.
Thanks in advance for taking a look!
Reproduce the code example:
Error message:
Version information:
v0.14.4
Context for the issue:
No response