-
Notifications
You must be signed in to change notification settings - Fork 11
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
DOC : add how to read fmriprep visual report #21
base: mkdocs
Are you sure you want to change the base?
DOC : add how to read fmriprep visual report #21
Conversation
…nfo from my paper
…ion with the info from my paper
…info from my paper
…mentary material of my paper
visualisation as the latter has been removed in the version 22.0.0 of fMRIPrep doc : Add SDC information under alignement of functional and anatomical data doc : add arrows to point at the apparent artifact caused by the interpolation used for visualisation
…into quality check the three preprocessing step evaluated here
fix : replace gray matter and white matter by their abbreviations fix : Add precision about the fact that the brain mask extracted from T1w and BOLD are different and they obey different exclusion criteria
23f4af9
to
119bb98
Compare
Hi @sarenseeley, Additionally, I'm missing a few elements listed below. I would gladly welcome your help if you have more insights on the following :
|
Responded to questions in issue nipreps#21
@celprov hopefully I did this correctly, but let me know if not! Also, I'm wondering if instead of "good"/"bad" we should use "better"/"worse" (or similar terms) to avoid the document being read as prescriptive? |
…_report updated HOWTO visual reports document
fix : fix markdown layout problem
@effigies Thank you it worked. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just some initial thoughts. I haven't done a thorough read-through of the content. My impression is that if I were reading this document, I would want a gross structure like:
- Introduction
- Structure of a report
- Description of sections, probably mention the top bar for quick navigation
- Suggested order of operations (check errors and summaries first, then walk through the reportlets)
- Reportlet walkthrough
- For each reportlet:
- A good example
- A description of what is being shown in the reportlet (could be taken directly from the captions in the reports)
- A good/bad example for each thing presented in the reportlet
- For each reportlet:
I think the current document focuses mostly on that last bullet. I feel like I would want my hand held a bit more if I were reading this for the first time.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This file looks like arrows on a white background. I don't know if it's missing layers or the brain images are in the wrong layer...
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
+1
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just got through line 28. Will continue at some other time
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
+1
What's the status of this? @celprov please look at my review whenever you are back :) |
|
Co-authored-by: Oscar Esteban <[email protected]>
fix: remove ICA-AROMA section as it does not exist anymore
…riprep_visual_report
Add a document to the Nipreps documentation explaining how to read fMRIprep visual report.
For each visualisation, the document answers the following questions :