From 977f60504165085a327ca42dffac4a9e2fd91b6f Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Jon=20Haitz=20Legarreta=20Gorro=C3=B1o?= Date: Sat, 17 Feb 2024 18:45:54 -0500 Subject: [PATCH] [custom] fix lesson contents --- episodes/02-exploring-fmriprep.md | 4 ---- 1 file changed, 4 deletions(-) diff --git a/episodes/02-exploring-fmriprep.md b/episodes/02-exploring-fmriprep.md index 91176821..5c801a8c 100644 --- a/episodes/02-exploring-fmriprep.md +++ b/episodes/02-exploring-fmriprep.md @@ -121,7 +121,6 @@ Specifically: This data is single-session, so a session folder is missing here - but with multiple sessions you will see anat and ses-[insert\_session\_here] folders where each session folder contain a func folder. - :::::::::::::::::::::::::::::::::::::::::::::::::: Hopefully you're now convinced that the outputs of fMRIPREP roughly follows BIDS organization principles. The filenames themselves give you a full description of what each file is (check the [slides](https://docs.google.com/presentation/d/1er6dQcERL-Yeb5-7A29tJnmqgHNaLpTLXM3e-SmpjDg/edit?usp=sharing) to get an idea of what each file means! @@ -239,7 +238,6 @@ preproc_T1 If we didn't configure pyBIDS with config=['bids','derivatives'] then the desc keyword would not work! - :::::::::::::::::::::::::::::::::::::::::::::::::: Note that we also pulled in MNI152NLin2009cAsym\_preproc.nii.gz data as well. This is data that has been transformed into MNI152NLin2009cAsym template space. We can pull this data out by further specifying our layout.get using the space argument: @@ -303,8 +301,6 @@ t1w_func_data Now that we have a handle on how fMRIPREP preprocessed data is organized and how we can pull this data. Let's start working with the actual data itself! - - :::::::::::::::::::::::::::::::::::::::: keypoints - fMRIPrep stores preprocessed data in a 'BIDS-like' fashion