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

Questions about LEDs and hemodynamics correction #4

Closed
oraby opened this issue Jul 7, 2021 · 2 comments
Closed

Questions about LEDs and hemodynamics correction #4

oraby opened this issue Jul 7, 2021 · 2 comments

Comments

@oraby
Copy link

oraby commented Jul 7, 2021

Hello,

It was recommended in the paper to set the LED power between 10–25 mW for both LEDs. My question is:

  • should the LEDs be calibrated in continuous mode, or in camera-synced pulse on/off mode?

We are still adapting the pipeline to our data, and currently we are having the following reconstructed output of the averaged SVT signal of the reward epoch:
Reward_avgVideo
The reward is delivered around frame no. ~3-4 , and it's bit unexpected to see the brain gets inhibited as such. We were wondering whether one of the LEDs power is less than what's needed. We currently calibrate our LEDs in continuous mode.
Have you experienced such case before?

@oraby
Copy link
Author

oraby commented Jul 7, 2021

This was the hemodynamics correction results that we got for this session:
image

In this session, I was using the baseline as the 20th percentile of each channel.
Does the violet scaling here looks like in order or is it too much?

@jcouto
Copy link
Owner

jcouto commented Jul 8, 2021

Hi Hatem,

that is correct. We are successful with 10-25mW measured in continuous mode (e.g. with a S425C sensor that is large enough to capture all light at the focal plane). This will be an over-estimate of the actual value that reaches the brain but it simplifies the calibration since it does not depend on the imaging rate.

When imaging we first saturate the camera sensor, and then reduce the power so that there are no pixels in cortex with values over 75% of the dynamic range of the sensor (we do this separately for the 470 and 405nm channels).

I don't often see negative regression coefficients, could you run the pipeline with wfield preprocess <foldername> please? I wonder if the baseline could be causing this of if it is something else. Please make sure you do not have a 'frames_average' file in foldername.

Thanks in advance, Joao

@jcouto jcouto closed this as completed Jun 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

2 participants