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

Add section on "Best Practices for Phys Data Collection" #177

Merged
merged 14 commits into from
Apr 2, 2020

Conversation

AyyagariA
Copy link
Collaborator

@AyyagariA AyyagariA commented Mar 16, 2020

Closes #99 addresses #12

Proposed Changes

  • Merging the changes and updates for the documentation on best practices for collecting physiological data

@smoia
Copy link
Member

smoia commented Mar 22, 2020

Hello there, any update on this?

@AyyagariA AyyagariA marked this pull request as ready for review March 23, 2020 21:55
@AyyagariA
Copy link
Collaborator Author

Ready for review!

@smoia
Copy link
Member

smoia commented Mar 24, 2020

Great!

Can I ask @RayStick, @BrightMG, and/or @CesarCaballeroGaudes to review this PR?

@AyyagariA AyyagariA added the Documentation This issue or PR is about the documentation label Mar 24, 2020
@smoia smoia requested a review from BrightMG March 27, 2020 10:45
@smoia
Copy link
Member

smoia commented Mar 27, 2020

I think that @BrightMG is looking into this with a PR to @AyyagariA's branch.
@BrightMG , can you let us know here when it's ready to be reviewed?

Co-authored-by: Kristina Zvolanek <54590158+kristinazvolanek@users.noreply.github.com>
Co-authored-by: Apoorva Ayyagari <50453337+AyyagariA@users.noreply.github.com>
@BrightMG
Copy link
Contributor

@AyyagariA's PR now contains my updated version of the best practices doc. I'd appreciate another person reviewing this now

@codecov
Copy link

codecov bot commented Mar 27, 2020

Codecov Report

Merging #177 into master will not change coverage by %.
The diff coverage is n/a.

Impacted file tree graph

@@           Coverage Diff           @@
##           master     #177   +/-   ##
=======================================
  Coverage   94.42%   94.42%           
=======================================
  Files           7        7           
  Lines         574      574           
=======================================
  Hits          542      542           
  Misses         32       32           
Impacted Files Coverage Δ
phys2bids/viz.py 97.26% <0.00%> (ø)
phys2bids/phys2bids.py 90.44% <0.00%> (ø)

Copy link
Contributor

@BrightMG BrightMG left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This ended up being mostly my own rewriting of the original documentation; as such, I do approve the changes, but strongly encourage another person vet the content

@RayStick
Copy link
Member

RayStick commented Mar 30, 2020

I can have a read through soon, if that's welcome?
I can review tomorrow morning (CST)

@RayStick RayStick self-requested a review March 30, 2020 21:30
@AyyagariA
Copy link
Collaborator Author

Thanks Molly for your feedback and guidance! @kristinazvolanek and I will be adding references and making a few edits this week.

@RayStick
Copy link
Member

RayStick commented Mar 31, 2020

I can have a read through soon, if that's welcome?
I can review tomorrow morning (CST)

I don't think I'll get to it today! @AyyagariA shall I wait until you've looked over it again, or shall I read when I can (probably tomorrow)?

@AyyagariA
Copy link
Collaborator Author

I can have a read through soon, if that's welcome?
I can review tomorrow morning (CST)

I don't think I'll get to it today! @AyyagariA shall I wait until you've looked over it again, or shall read when I can (probably tomorrow)?

There aren't any major content changes for right now, so just read when you get a chance and we will let you know if there are updates! Thank you.


**Breathing** is typically monitored using a "respiratory belt" around the participant's chest/diaphragm. The belt may be rigid or elastic, using MR compatible force or pressure transducers to generate a signal proportional to the chest diameter. The optimal positioning of the belt depends on the device being used, however it is best to be fairly consistent in how the belt is worn throughout a study. In some labs, multiple belts are used to better capture different types of breathing styles (e.g., "chest breathing" versus "belly breathing"). Often a belt is incorporated into the MRI scanner infrastructure, and these data can be collected by the scanner or recorded by a separate device. The peaks and troughs of the breathing trace are identified, which can provide information about breathing rate as well as breathing depth. There are three primary ways by which breathing can influence the fMRI signals. First, breathing often leads to bulk motion of the body and head. These effects are typically modeled using volume registration and motion correction algorithms. Second, breathing changes the chest position which can influence the success of the shim, continuously changing B0 homogeneity throughout the scan and in turn affecting signal amplitude. These effects are also modeled using techniques like RETROICOR. Thirdly, changing breathing rate and depth can influence blood gases, which can drive vasodilation or vasoconstriction, and thus substantially influence the fMRI signal amplitude. RVT correction (Birn et al. 2008) estimates the change in breathing rate/depth to model these effects.

**Blood gases:** It is also possible (and recommended!) to directly record changes in blood gas levels, rather than infer them from a chest position measurement. Most commonly we measure carbon dioxide levels (CO2), which is a known vasodilator and can drive large variability in blood flow and the BOLD signal. We can also measure oxygen (O2) levels; O2 only has a mild vasoconstictive effect on the cerebrovasculature, but oxygen levels can directly influence BOLD signal contrast. These two blood gases are typically strongly anticorrelated with eachother in most scans, but can also be manipulated independently and influence the fMRI signals through distinct mechanisms. Best practice would be to record both. Although the most accurate recordings of blood gas levels would be achieved through arterial sampling, this is not recommended for most imaging experiments. Instead, the concentrations of CO2 and O2 in arterial blood can be approximated by the partial pressure of each gas at the end of an exhalation, or the end-tidal partial pressure (commonly abbreviated as PETCO2 and PETO2). The person being scanned wears a nasal cannula (soft plastic tube that rests just below the nostrils) or face mask that is connected to a gas analyzer in the control room. The resulting data shows the fluctuations in CO2 and O2 across every breath; an algorithm must extract the "end-tidal" values.
Copy link
Member

@RayStick RayStick Apr 1, 2020

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Remove ":" after blood gases

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It says 'oxygen' after introducing the abbreviation 'O2'

docs/bestpractice.rst Outdated Show resolved Hide resolved
- respiratory belt
- disposable nasal cannula (or face mask) and long sample line to connect to control room

Some peripherals can be passed through a void in the penetration panel from the control room to the scan room (e.g., gas sampling line); others must be plugged into the penetration panel for noise filtering (e.g., some pulse sensors). Devices native to the MRI scanner may communicate wirelessly with the scanner. When adding non-native peripheral devices to the scanner environment, we recommend that you check that you are not bringing any outside noise into the scan room or bringing too much scanner noise into the physiological recordings. It may be necessary to develop additional devices or mechanisms to shield these connections.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"Some peripheral devices"

@RayStick
Copy link
Member

RayStick commented Apr 1, 2020

I gave it a read - reads well and good to go in my opinion (after references have been added, and formatting checked, etc.). There will always be more to say on this topic but I think this is a good concise introductory overview!

There are a few very minor wording comments I made.

@AyyagariA
Copy link
Collaborator Author

@smoia This is ready to go! Just pushed the final touches.

@smoia smoia changed the title Best Practices for Phys Data Collection Add section on "Best Practices for Phys Data Collection" Apr 2, 2020
@smoia
Copy link
Member

smoia commented Apr 2, 2020

@RayStick , if you approve, merge it in!

@RayStick
Copy link
Member

RayStick commented Apr 2, 2020

@RayStick , if you approve, merge it in!

Sure! (Was just reading the contributor file to remind myself whether I was allowed!)

@RayStick RayStick merged commit 19251e0 into physiopy:master Apr 2, 2020
@smoia smoia added the released This issue/pull request has been released. label Oct 14, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Documentation This issue or PR is about the documentation released This issue/pull request has been released.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Phys Data Best Practices Documentation
4 participants