4
4
5
5
[ ![ Binder] ( https://mybinder.org/badge_logo.svg )] ( https://mybinder.org/v2/gh/cpp-lln-lab/CPP_BIDS/master?filepath=notebooks%2Fbasic_usage.ipynb )
6
6
7
+ ** Documentation**
8
+
9
+ [ ![ Documentation Status: stable] ( https://readthedocs.org/projects/cpp-bids/badge/?version=stable )] ( https://cpp-bids.readthedocs.io/en/stable/?badge=stable )
10
+
11
+ ** Cite it**
12
+
13
+ [ ![ DOI] ( https://zenodo.org/badge/DOI/10.5281/zenodo.4007674.svg )] ( https://doi.org/10.5281/zenodo.4007674 )
14
+
7
15
** Unit tests and coverage**
8
16
9
17
[ ![ ] ( https://img.shields.io/badge/Octave-CI-blue?logo=Octave&logoColor=white )] ( https://github.com/cpp-lln-lab/CPP_BIDS/actions )
19
27
20
28
[ ![ All Contributors] ( https://img.shields.io/badge/all_contributors-3-orange.svg?style=flat-square )] ( #contributors- )
21
29
22
- * * *
30
+ ---
23
31
24
32
# CPP_BIDS
25
33
@@ -44,42 +52,24 @@ A set of function for matlab and octave to create
44
52
structure and filenames for the output of behavioral, EEG, fMRI, eyetracking
45
53
studies.
46
54
47
- ## Output format
48
-
49
- ### Modality agnostic aspect
50
-
51
- Subjects, session and run number labels will be numbers with zero padding up to
52
- 3 values (e.g subject 1 will become ` sub-001 ` ).
53
-
54
- A session folder will ALWAYS be created even if not requested (default will be
55
- ` ses-001 ` ).
56
-
57
- Task labels will be printed in camelCase in the filenames.
58
-
59
- Time stamps are added directly in the filename by adding a suffix
60
- ` _date-YYYYMMDDHHMM ` which makes the file name non-BIDS compliant. This was
61
- added to prevent overwriting files in case a certain run needs to be done a
62
- second time because of a crash (Some of us are paranoid about keeping even
63
- cancelled runs during my experiments). This suffix should be removed to make the
64
- data set BIDS compliant. See ` convertSourceToRaw.m ` for more details.
65
-
66
- For example:
67
-
68
- ``` bash
69
- sub-090/ses-003/sub-090_ses-003_task-auditoryTask_run-023_events_date-202007291536.tsv
70
- ```
71
-
72
55
## Documentation
73
56
74
57
- [ Installation] ( ./docs/installation.md )
75
58
- [ How to use it: jupyter notebooks] ( ./notebooks )
76
- - [ Functions description ] ( ./docs/functions-description.md )
59
+ - [ General documentation ] ( https://cpp-bids.readthedocs.io/en/dev/index.html )
77
60
78
61
## Contributing
79
62
80
63
Feel free to open issues to report a bug and ask for improvements.
81
64
82
- ### Guidestyle
65
+ If you want to contribute, have a look at our
66
+ [ contributing guidelines] ( https://github.com/cpp-lln-lab/.github/blob/main/CONTRIBUTING.md )
67
+ that are meant to guide you and help you get started. If something is not clear
68
+ or you get stuck: it is more likely we did not do good enough a job at
69
+ explaining things. So do not hesitate to open an issue, just to ask for
70
+ clarification.
71
+
72
+ ### Style guide
83
73
84
74
- We use camelCase.
85
75
@@ -97,23 +87,31 @@ Here are the naming templates used.
97
87
98
88
- Behavior
99
89
100
- ` sub-<label>[_ses-<label>]_task-<label>[_acq-<label>][_run-<index>]_events.tsv `
101
- ` sub-<label>[_ses-<label>]_task-<label>[_acq-<label>][_run-<index>]_events.json `
102
- ` sub-<label>[_ses-<label>]_task-<label>[_acq-<label>][_run-<index>]_beh.tsv `
103
- ` sub-<label>[_ses-<label>]_task-<label>[_acq-<label>][_run-<index>]_beh.json `
90
+ ``` bash
91
+ sub-< label> [_ses-< label> ]_task-< label> [_acq-< label> ][_run-< index> ]_events.tsv
92
+ sub-< label> [_ses-< label> ]_task-< label> [_acq-< label> ][_run-< index> ]_events.json
93
+ sub-< label> [_ses-< label> ]_task-< label> [_acq-< label> ][_run-< index> ]_beh.tsv
94
+ sub-< label> [_ses-< label> ]_task-< label> [_acq-< label> ][_run-< index> ]_beh.json
95
+ ```
104
96
105
97
- BOLD
106
98
107
- ` sub-<label>[_ses-<label>]_task-<label>[_acq-<label>][_ce-<label>][_dir-<label>][_rec-<label>][_run-<index>][_echo-<index>]_<contrast_label>.nii[.gz] `
99
+ ``` bash
100
+ sub-< label> [_ses-< label> ]_task-< label> [_acq-< label> ][_ce-< label> ][_dir-< label> ][_rec-< label> ][_run-< index> ][_echo-< index> ]_< contrast_label> .nii[.gz]
101
+ ```
108
102
109
103
- iEEG
110
104
111
- ` sub-<label>[_ses-<label>]_task-<task_label>[_run-<index>]_ieeg.json `
105
+ ``` bash
106
+ sub-< label> [_ses-< label> ]_task-< task_label> [_run-< index> ]_ieeg.json
107
+ ```
112
108
113
109
- EEG
114
110
115
- ` sub-<label>[_ses-<label>]_task-<label>[_run-<index>]_eeg.<manufacturer_specific_extension> `
116
- ` sub-<label>[_ses-<label>]_task-<label>[_run-<index>]_eeg.json `
111
+ ``` bash
112
+ sub-< label> [_ses-< label> ]_task-< label> [_run-< index> ]_eeg.< manufacturer_specific_extension>
113
+ sub-< label> [_ses-< label> ]_task-< label> [_run-< index> ]_eeg.json
114
+ ```
117
115
118
116
<!-- European data format (Each recording consisting of a .edf file)
119
117
@@ -132,14 +130,19 @@ Biosemi data format (Each recording consisting of a .bdf file) -->
132
130
current format ` <matches>_recording-eyetracking_physio.tsv.gz `
133
131
134
132
future BEP format in a dedicated eyetracker folder
135
- ` sub-<participant_label>[_ses-<label>][_acq-<label>]_task-<task_label>_eyetrack.<manufacturer_specific_extension> `
133
+
134
+ ``` bash
135
+ sub-< participant_label> [_ses-< label> ][_acq-< label> ]_task-< task_label> _eyetrack.< manufacturer_specific_extension>
136
+ ```
136
137
137
138
- Stim and physio
138
139
139
- ` <matches>[_recording-<label>]_physio.tsv.gz `
140
- ` <matches>[_recording-<label>]_physio.json `
141
- ` <matches>[_recording-<label>]_stim.tsv.gz `
142
- ` <matches>[_recording-<label>]_stim.json `
140
+ ``` bash
141
+ < matches> [_recording-< label> ]_physio.tsv.gz
142
+ < matches> [_recording-< label> ]_physio.json
143
+ < matches> [_recording-< label> ]_stim.tsv.gz
144
+ < matches> [_recording-< label> ]_stim.json
145
+ ```
143
146
144
147
### Change log
145
148
@@ -164,6 +167,7 @@ Thanks goes to these wonderful people
164
167
165
168
<!-- markdownlint-enable -->
166
169
<!-- prettier-ignore-end -->
170
+
167
171
<!-- ALL-CONTRIBUTORS-LIST:END -->
168
172
169
173
This project follows the
0 commit comments