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

Community practices documentation first version #3

Merged
merged 58 commits into from
May 28, 2024
Merged

Community practices documentation first version #3

merged 58 commits into from
May 28, 2024

Conversation

beccaclements99
Copy link
Collaborator

@beccaclements99 beccaclements99 commented Feb 12, 2024

Version 1 of best practices documentation

Change Type

  • bugfix (+0.0.1)
  • minor (+0.1.0)
  • major (+1.0.0)
  • refactoring (no version update)
  • test (no version update)
  • infrastructure (no version update)
  • documentation (no version update)
  • other

Checklist before review

  • I added everything I wanted to add to this PR.
  • [Code or tests only] I wrote/updated the necessary docstrings.
  • [Code or tests only] I ran and passed tests locally.
  • [Documentation only] I built the docs locally.
  • My contribution is harmonious with the rest of the code: I'm not introducing repetitions.
  • My code respects the adopted style, especially linting conventions.
  • The title of this PR is explanatory on its own, enough to be understood as part of a changelog.
  • I added or indicated the right labels.
  • I added information regarding the timeline of completion for this PR.
  • Please, comment on my PR while it's a draft and give me feedback on the development!

Upload version 1 best practices documentation
@smoia smoia added the Minormod This PR generally closes an "Enhancement" issue. It increments the minor version (0.+1.0) label Feb 13, 2024
@RayStick
Copy link
Member

Great work 👏 🤩

Copy link
Contributor

@likeajumprope likeajumprope left a comment

Choose a reason for hiding this comment

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

Fantastic effort, and very well written!

@@ -0,0 +1,11 @@
# 2. What type of physiological data does the Physiopy community work with?

The most common types of physiological data acquired in fMRI analysis within members of our community are cardiac (photoplethysmographypulse, ECG/EKG) and respiration, either ventilation (respiratory belt) and/or gas concentration (particularly expired CO2). Links are provided to their lab websites if you wish to reach out about questions or look through any methods/analyses in their publications.
Copy link
Contributor

Choose a reason for hiding this comment

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

The first and second sentence somehow do not flow - what does the "their" in "their lab websites" refer to? Data? Maybe change "their" to "some common examples by labs of members in the community" or something

docs/source/physiopy_community.md Outdated Show resolved Hide resolved
smoia and others added 4 commits February 28, 2024 18:15
Co-authored-by: Rachael Stickland <50215726+RayStick@users.noreply.github.com>
Co-authored-by: Johanna Bayer <hannabayer.89@gmail.com>
Co-authored-by: Rachael Stickland <50215726+RayStick@users.noreply.github.com>
Co-authored-by: Rachael Stickland <50215726+RayStick@users.noreply.github.com>
Copy link

@rgbayrak rgbayrak left a comment

Choose a reason for hiding this comment

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

Some references are incomplete, not added to the References list as a full citation and have different formatting.

Citations under data collection section that do not appear in References:

  • (Liu et al., 2019)
  • Bulte and Wartolowska (2017)
  • Zvolanek et al., NeuroImage, 2023
  • Liu et al., 2017
  • Pinto et al. 2021

Also some in Data Processing section as well (disclaimer: I did not check every tab)
(Bhattacharyya and Lowe, 2004).

References Section/Tab:
Not alphabetically ordered, making it hard to read, i.e. Bottenhorn comes last.

Choose a reason for hiding this comment

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

ex. full date, milliseconds since 12 AM, other formats… > such as full date, milliseconds since 12 AM, other formats

[SETUP_170322] Is this purposefully left in the text?

BNC > abbreviation not explained in this specific page.

Will the link be clickable of just appear next to the title for the link?

Copy link
Member

Choose a reason for hiding this comment

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

+1 for the citation of the community practice meeting [SETUP_170322] being confusing.

Copy link
Collaborator

Choose a reason for hiding this comment

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

Thank you for spotting that @rgbayrak, I added those and more references that were missing (here 5083560). The Community Practices Meetings list was also added to the references. Maybe we can cite them like "(CPM1, March 2022)", @rgbayrak and @m-miedema?

Copy link
Collaborator

Choose a reason for hiding this comment

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

The other comments have been addressed here 6383ff6 (except for the references to the Community Practices meetings, which will be fixed when we have a consensus on the nomenclature).

Copy link
Collaborator

Choose a reason for hiding this comment

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

Regarding the Community Practices meetings references (e.g. [SETUP_170322]), we decided to remove them (kept them as a comment only, so they can still be tracked internally).

Copy link
Collaborator

@me-pic me-pic left a comment

Choose a reason for hiding this comment

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

Great work !

I just added really minor comments, please feel free to ignore them if not relevant.


When establishing a physiological monitoring setup, it is essential to follow a systematic approach. Once you have identified the signals you intend to capture, and prior to initiating data collection from a subject, it is imperative to ensure that all necessary checks from the essentials’ list have been completed.

You will require **peripheral devices**, typically attached to the subject, and **recording devices** (often connected to a computer/laptop) for data acquisition and storage. Post-recording, it is crucial to accurately track events corresponding to both physiological and neuroimaging recordings at equivalent time points. To achieve this, beforehand, additional **synchronization** is necessary, unless it is already integrated into the software you are utilizing.
Copy link
Collaborator

Choose a reason for hiding this comment

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

Really great work 🎉 🎉

This a just a minor detail, but I would maybe just rephrase this paragraph to respect the chronogical order of proceeding, i.e. talking about the necessity to synchronize physio and neuroimaging recordings to accurately track events.

Copy link
Collaborator

Choose a reason for hiding this comment

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

Thanks Marie-Eve! I tried to reorder the sentence according to your suggestion (here 19f0024)

Copy link
Collaborator

Choose a reason for hiding this comment

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

LGTM ! Thank you Inês !


## ECG
ECG is based on electrical activity and allows a reliable monitoring of cardiac cycle features.
ECG traces the potential change over the heart generated by the sinoatrial (SA) and atrioventricular (AV) nodes. It provides very precise beat-by-beat HR information. Depending on the system you are using and whether it is connected to another device (e.g., EEG cap), the electrodes can be placed on the chest or on the back of the subject. The ECG allows us to clearly monitor the entire QRS complex and cardiac cycle of the patient.
Copy link
Collaborator

@me-pic me-pic Feb 28, 2024

Choose a reason for hiding this comment

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

Since the abbreviation was not define previously on this page, I would be tempted to explicitly write heart rate (HR) instead of just HR

Copy link
Collaborator

Choose a reason for hiding this comment

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

Fixed here 6289ff6 to always use "heart rate".

ECG is based on electrical activity and allows a reliable monitoring of cardiac cycle features.
ECG traces the potential change over the heart generated by the sinoatrial (SA) and atrioventricular (AV) nodes. It provides very precise beat-by-beat HR information. Depending on the system you are using and whether it is connected to another device (e.g., EEG cap), the electrodes can be placed on the chest or on the back of the subject. The ECG allows us to clearly monitor the entire QRS complex and cardiac cycle of the patient.

Inside the MRI environment, the ECG will be distorted by magnetic induction and RF pulses.
Copy link
Collaborator

Choose a reason for hiding this comment

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

I don't know if it's relevant, but I would maybe explicitly mention radiofrequency (RF) instead of just RF

Copy link
Collaborator

Choose a reason for hiding this comment

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

Fixed here 6289ff6 to always use "radiofrequency".

ECG traces the potential change over the heart generated by the sinoatrial (SA) and atrioventricular (AV) nodes. It provides very precise beat-by-beat HR information. Depending on the system you are using and whether it is connected to another device (e.g., EEG cap), the electrodes can be placed on the chest or on the back of the subject. The ECG allows us to clearly monitor the entire QRS complex and cardiac cycle of the patient.

Inside the MRI environment, the ECG will be distorted by magnetic induction and RF pulses.
It is important to note that like most signals, the ECG is susceptible to artifacts introduced by magnetic induction and RF pulses and to cardio-ballistic effects from the mechanical movement of the heart and flow of blood in the magnetic field that need to be cleaned appropriately after the scan (Kugel et al., 2003). Certain commercial devices have built in filters to suppress MRI-related artifacts; however, understanding what is real and noise in your signal is essential prior to using it for any kind of analysis (Abacherli, et al., 2005; Gray et al., 2009; Odille et al., 2007).
Copy link
Collaborator

Choose a reason for hiding this comment

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

what is real and what is noise

Copy link
Collaborator

Choose a reason for hiding this comment

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

Fixed here 6289ff6.

Copy link
Member

Choose a reason for hiding this comment

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

Typo: For particularly thin subjects, adding a pad between the belt and the chest might be necessary to avoid saturation due to loosen belts.

Copy link
Collaborator

Choose a reason for hiding this comment

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

Fixed here 6289ff6.

@m-miedema
Copy link
Member

m-miedema commented Feb 29, 2024

It's exciting the way this is coming together! My main comments are that

  1. The in-text references to community meetings, while helpful internally, are not helpful in this context. Perhaps there could be a list of topics that have been discussed and in-text references that make it more clear that we're referencing a conversation? E.g. (Community Practice Meeting: Respiration, date).
  2. The comment regarding eddy currents should be moved out of the gas section and into a more general practice for collecting data.
  3. I'm not sure if this is in the scope of this PR, but section 6 seems to currently imply that e.g. HRV or other physiological derivatives should be directly input into a GLM. It seems unhelpful to include this section without at least mentioning PRFs.

@goodalse2019
Copy link
Collaborator

This all looks amazing! Awesome job everyone. Super excited for this to go public.

@joanacspinto
Copy link

Hi all, I've taken a brief look at this - amazing work! Well done :)
Just some minor points:

  • the references to the community meetings look a bit odd
  • the order. I would recommend moving "2. Community" to a later stage. I like the flow of 1. motivation, 2. setting up the system, 3. acquiring data, 3. analysing data etc

@afni-dglen
Copy link

afni-dglen commented Mar 20, 2024

This is really nice work on this documentation, and I learned a lot reading this. I will note a few nit-picky details - please see the attached md files.

collect_phys.md
process_phys.md
physio_importance.md
phys_set_up.md

isesteves and others added 10 commits March 21, 2024 15:03
- Added a small summary about the references
- Added the list of Community Practices Meetings and short descriptions
- Updated the references with missing items and ordered them
- Minor formatting changes
- Minor text changes in the "Syncing with the neuroimaging acquisition" subsection
- Added two missing references
- Removed one reference that was not being used
Updated based on feedback from Daniel Glen
Updated based on feedback from Daniel Glen
More updates based on feedback from Daniel Glen
- Removed CMP in-text references 
- Minor text changes (reordered one paragraph according to the comments)
Updated based on feedback from Daniel Glen
Updated based on feedback from Daniel Glen
Make this section appear first instead of second (here I am just changing the numbering)
- Added list of contributors (orcid, affiliations, name)
@github-actions github-actions bot added the Internal Changes affect the internal API. It doesn't increase the version, but produces a changelog label May 27, 2024
@github-actions github-actions bot added the Documentation This issue or PR is about the documentation label May 28, 2024
@smoia
Copy link
Member

smoia commented May 28, 2024

Are we pushing the button?

Yes, we are.

🎉 🎉 🎉

@smoia smoia merged commit f2267c1 into master May 28, 2024
2 checks passed
@smoia
Copy link
Member

smoia commented May 28, 2024

🚀 PR was released in 2024.0.0 🚀

@smoia smoia added the released This issue/pull request has been released label May 28, 2024
@smoia smoia deleted the 1.0 branch July 15, 2024 17:27
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 Internal Changes affect the internal API. It doesn't increase the version, but produces a changelog Majormod This PR breaks compatibility, and increments the major version (+1.0.0) released This issue/pull request has been released
Projects
Status: Done
Development

Successfully merging this pull request may close these issues.