BUG: <Please write a comprehensive title after the 'BUG: ' prefix> Significantly higher fluorescence values in Suite2p in images collected thru Scanimage and saved in imageJ #1139
We noticed that the baseline fluorescence (F) values are very different when we use images collected with Scanimage directly with Suite2p versus the same image opened and saved again with ImageJ. For example, the F value changes from 4000 (Scanimage file) to 18000 (same file saved in imageJ with no modification). Can you please tell me why this is the case and how we can use ImageJ saved files with Suite2p so that the baseline fluorescence is not elevated?
Reproduce the code example:
no any codes, just running suite2p to identify ROIs, the fluorescence values are different.
Error message:
no error messages.
Version information:
suite2p v0.14.4
Context for the issue:
We are getting significantly two different values in Suite2p which definitely affects our results. So, I believe that this issue should be prioritized.
Describe the issue:
We noticed that the baseline fluorescence (F) values are very different when we use images collected with Scanimage directly with Suite2p versus the same image opened and saved again with ImageJ. For example, the F value changes from 4000 (Scanimage file) to 18000 (same file saved in imageJ with no modification). Can you please tell me why this is the case and how we can use ImageJ saved files with Suite2p so that the baseline fluorescence is not elevated?
Reproduce the code example:
Error message:
Version information:
suite2p v0.14.4
Context for the issue:
We are getting significantly two different values in Suite2p which definitely affects our results. So, I believe that this issue should be prioritized.