You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
-[Example for submodule usage](#example-for-submodule-usage)
21
38
-[Direct download](#direct-download)
22
39
-[Contributing](#contributing)
23
40
-[Guidestyle](#guidestyle)
@@ -36,7 +53,7 @@ Subjects, session and run number labels will be numbers with zero padding up to
36
53
37
54
A session folder will ALWAYS be created even if not requested (default will be `ses-001`).
38
55
39
-
Task labels will be printed in camelCase in the filenames.
56
+
Task labels will be printed in camelCase in the filenames.
40
57
41
58
Time stamps are added directly in the filename by adding a suffix `_date-YYYYMMDDHHMM` which makes the file name non-BIDS compliant. This was added to prevent overwriting files in case a certain run needs to be done a second time because of a crash (Some of us are paranoid about keeping even cancelled runs during my experiments). This suffix should be removed to make the data set BIDS compliant. See `convertSourceToRaw.m` for more details.
This function creates a very light-weight version of the side-car JSON file for a BOLD functional run.
308
+
309
+
This will only contain the minimum BIDS requirement and will likely be less complete than the info you could from DICOM conversion.
310
+
311
+
If you put the following line at the end of your experiment script, it will dump the content of the `extraInfo` structure in the json file.
312
+
313
+
```
314
+
createBoldJson(cfg, extraInfo)
315
+
```
316
+
317
+
This allows to add all the parameters that you used to run your experiment in a human readable format: so that when you write your methods sections 2 years later ("the reviewer asked me for the size of my fixation cross... FML"), the info you used WHEN you ran the experiment is saved in an easily accessible text format. For the love of the flying spaghetti monster do not save all your parameters in a `.mat` file: think of the case when you won't have matlab or octave installed on a computer (plus not everyone uses those).
318
+
319
+
Also to reading your experiment parameters, you won't have to read it from the `setParameters.m` file and wonder if those might have been modified when running the experiment and you did not commit and tagged that change with git.
320
+
284
321
## How to install
285
322
286
323
### Download with git
@@ -290,7 +327,7 @@ cd fullpath_to_directory_where_to_install
To get the latest commit you then need to update the submodule with the information
361
+
To get the latest commit you then need to update the submodule with the information
325
362
on its remote repository and then merge those locally.
326
363
```bash
327
364
git submodule update --remote --merge
328
365
```
329
366
330
-
Remember that updates to submodules need to be commited as well.
367
+
Remember that updates to submodules need to be committed as well.
368
+
369
+
#### Example for submodule usage
370
+
371
+
So say you want to clone a repo that has some nested submodules, then you would type this to get the content of all the submodules at once (here with assumption that you want to clone my experiment repo):
0 commit comments