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

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

Open
niraulasuraj9 opened this issue Aug 12, 2024 · 0 comments

Comments

@niraulasuraj9
Copy link

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:

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.

@niraulasuraj9 niraulasuraj9 changed the title BUG: <Please write a comprehensive title after the 'BUG: ' prefix> The fluorescence values in Suite2p increases significantly when images collected thru Scanimage are saved in imageJ and processed in Suite2p 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 Aug 13, 2024
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