-
Notifications
You must be signed in to change notification settings - Fork 3
/
Copy pathvalidate.txt
212 lines (184 loc) · 40.4 KB
/
validate.txt
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
1: [ERR] Files with such naming scheme are not part of BIDS specification. This error is most commonly caused by typos in file names that make them not BIDS compatible. Please consult the specification and make sure your files are named correctly. If this is not a file naming issue (for example when including files not yet covered by the BIDS specification) you should include a ".bidsignore" file in your dataset (see https://github.com/bids-standard/bids-validator#bidsignore for details). Please note that derived (processed) data should be placed in /derivatives folder and source data (such as DICOMS or behavioural logs in proprietary formats) should be placed in the /sourcedata folder. (code: 1 - NOT_INCLUDED)
./sub-20231103lunapilotspa2/anat/sub-20231103lunapilotspa2_acq-b0recon_magnitude_heudiconv744_e1.nii.gz
Files with such naming scheme are not part of BIDS specification. This error is most commonly caused by typos in file names that make them not BIDS compatible. Please consult the specification and make sure your files are named correctly. If this is not a file naming issue (for example when including files not yet covered by the BIDS specification) you should include a ".bidsignore" file in your dataset (see https://github.com/bids-standard/bids-validator#bidsignore for details). Please note that derived (processed) data should be placed in /derivatives folder and source data (such as DICOMS or behavioural logs in proprietary formats) should be placed in the /sourcedata folder.
Evidence: sub-20231103lunapilotspa2_acq-b0recon_magnitude_heudiconv744_e1.nii.gz
./sub-20231103lunapilotspa2/anat/sub-20231103lunapilotspa2_acq-b0recon_magnitude_heudiconv744_e2.nii.gz
Files with such naming scheme are not part of BIDS specification. This error is most commonly caused by typos in file names that make them not BIDS compatible. Please consult the specification and make sure your files are named correctly. If this is not a file naming issue (for example when including files not yet covered by the BIDS specification) you should include a ".bidsignore" file in your dataset (see https://github.com/bids-standard/bids-validator#bidsignore for details). Please note that derived (processed) data should be placed in /derivatives folder and source data (such as DICOMS or behavioural logs in proprietary formats) should be placed in the /sourcedata folder.
Evidence: sub-20231103lunapilotspa2_acq-b0recon_magnitude_heudiconv744_e2.nii.gz
./sub-20231103lunapilotspa2/anat/sub-20231103lunapilotspa2_acq-b0recon_phase.nii.gz
Files with such naming scheme are not part of BIDS specification. This error is most commonly caused by typos in file names that make them not BIDS compatible. Please consult the specification and make sure your files are named correctly. If this is not a file naming issue (for example when including files not yet covered by the BIDS specification) you should include a ".bidsignore" file in your dataset (see https://github.com/bids-standard/bids-validator#bidsignore for details). Please note that derived (processed) data should be placed in /derivatives folder and source data (such as DICOMS or behavioural logs in proprietary formats) should be placed in the /sourcedata folder.
Evidence: sub-20231103lunapilotspa2_acq-b0recon_phase.nii.gz
./sub-20231103lunapilotspa2/anat/sub-20231103lunapilotspa2_acq-b1.nii.gz
Files with such naming scheme are not part of BIDS specification. This error is most commonly caused by typos in file names that make them not BIDS compatible. Please consult the specification and make sure your files are named correctly. If this is not a file naming issue (for example when including files not yet covered by the BIDS specification) you should include a ".bidsignore" file in your dataset (see https://github.com/bids-standard/bids-validator#bidsignore for details). Please note that derived (processed) data should be placed in /derivatives folder and source data (such as DICOMS or behavioural logs in proprietary formats) should be placed in the /sourcedata folder.
Evidence: sub-20231103lunapilotspa2_acq-b1.nii.gz
./sub-20231103lunapilotspa2/anat/sub-20231103lunapilotspa2_acq-noMT_MTR.nii.gz
Files with such naming scheme are not part of BIDS specification. This error is most commonly caused by typos in file names that make them not BIDS compatible. Please consult the specification and make sure your files are named correctly. If this is not a file naming issue (for example when including files not yet covered by the BIDS specification) you should include a ".bidsignore" file in your dataset (see https://github.com/bids-standard/bids-validator#bidsignore for details). Please note that derived (processed) data should be placed in /derivatives folder and source data (such as DICOMS or behavioural logs in proprietary formats) should be placed in the /sourcedata folder.
Evidence: sub-20231103lunapilotspa2_acq-noMT_MTR.nii.gz
./sub-20231103lunapilotspa2/anat/sub-20231103lunapilotspa2_acq-yesMT_MTR.nii.gz
Files with such naming scheme are not part of BIDS specification. This error is most commonly caused by typos in file names that make them not BIDS compatible. Please consult the specification and make sure your files are named correctly. If this is not a file naming issue (for example when including files not yet covered by the BIDS specification) you should include a ".bidsignore" file in your dataset (see https://github.com/bids-standard/bids-validator#bidsignore for details). Please note that derived (processed) data should be placed in /derivatives folder and source data (such as DICOMS or behavioural logs in proprietary formats) should be placed in the /sourcedata folder.
Evidence: sub-20231103lunapilotspa2_acq-yesMT_MTR.nii.gz
./sub-20231103lunapilotspa2/anat/sub-20231103lunapilotspa2_desc-div_MP2RAGE.nii.gz
Files with such naming scheme are not part of BIDS specification. This error is most commonly caused by typos in file names that make them not BIDS compatible. Please consult the specification and make sure your files are named correctly. If this is not a file naming issue (for example when including files not yet covered by the BIDS specification) you should include a ".bidsignore" file in your dataset (see https://github.com/bids-standard/bids-validator#bidsignore for details). Please note that derived (processed) data should be placed in /derivatives folder and source data (such as DICOMS or behavioural logs in proprietary formats) should be placed in the /sourcedata folder.
Evidence: sub-20231103lunapilotspa2_desc-div_MP2RAGE.nii.gz
./sub-20231103lunapilotspa2/anat/sub-20231103lunapilotspa2_desc-mask_MP2RAGE.nii.gz
Files with such naming scheme are not part of BIDS specification. This error is most commonly caused by typos in file names that make them not BIDS compatible. Please consult the specification and make sure your files are named correctly. If this is not a file naming issue (for example when including files not yet covered by the BIDS specification) you should include a ".bidsignore" file in your dataset (see https://github.com/bids-standard/bids-validator#bidsignore for details). Please note that derived (processed) data should be placed in /derivatives folder and source data (such as DICOMS or behavioural logs in proprietary formats) should be placed in the /sourcedata folder.
Evidence: sub-20231103lunapilotspa2_desc-mask_MP2RAGE.nii.gz
./sub-20231103lunapilotspa2/anat/sub-20231103lunapilotspa2_desc-nomask_UNIT1.nii.gz
Files with such naming scheme are not part of BIDS specification. This error is most commonly caused by typos in file names that make them not BIDS compatible. Please consult the specification and make sure your files are named correctly. If this is not a file naming issue (for example when including files not yet covered by the BIDS specification) you should include a ".bidsignore" file in your dataset (see https://github.com/bids-standard/bids-validator#bidsignore for details). Please note that derived (processed) data should be placed in /derivatives folder and source data (such as DICOMS or behavioural logs in proprietary formats) should be placed in the /sourcedata folder.
Evidence: sub-20231103lunapilotspa2_desc-nomask_UNIT1.nii.gz
./sub-20231103lunapilotspa2/fmap/sub-20231103lunapilotspa2_acq-b0_phase.nii.gz
Files with such naming scheme are not part of BIDS specification. This error is most commonly caused by typos in file names that make them not BIDS compatible. Please consult the specification and make sure your files are named correctly. If this is not a file naming issue (for example when including files not yet covered by the BIDS specification) you should include a ".bidsignore" file in your dataset (see https://github.com/bids-standard/bids-validator#bidsignore for details). Please note that derived (processed) data should be placed in /derivatives folder and source data (such as DICOMS or behavioural logs in proprietary formats) should be placed in the /sourcedata folder.
Evidence: sub-20231103lunapilotspa2_acq-b0_phase.nii.gz
./sub-20231103lunapilotspa2/fmap/sub-20231103lunapilotspa2_acq-b0echo5_magnitude_heudiconv270_e1.nii.gz
Files with such naming scheme are not part of BIDS specification. This error is most commonly caused by typos in file names that make them not BIDS compatible. Please consult the specification and make sure your files are named correctly. If this is not a file naming issue (for example when including files not yet covered by the BIDS specification) you should include a ".bidsignore" file in your dataset (see https://github.com/bids-standard/bids-validator#bidsignore for details). Please note that derived (processed) data should be placed in /derivatives folder and source data (such as DICOMS or behavioural logs in proprietary formats) should be placed in the /sourcedata folder.
Evidence: sub-20231103lunapilotspa2_acq-b0echo5_magnitude_heudiconv270_e1.nii.gz
./sub-20231103lunapilotspa2/fmap/sub-20231103lunapilotspa2_acq-b0echo5_magnitude_heudiconv270_e2.nii.gz
Files with such naming scheme are not part of BIDS specification. This error is most commonly caused by typos in file names that make them not BIDS compatible. Please consult the specification and make sure your files are named correctly. If this is not a file naming issue (for example when including files not yet covered by the BIDS specification) you should include a ".bidsignore" file in your dataset (see https://github.com/bids-standard/bids-validator#bidsignore for details). Please note that derived (processed) data should be placed in /derivatives folder and source data (such as DICOMS or behavioural logs in proprietary formats) should be placed in the /sourcedata folder.
Evidence: sub-20231103lunapilotspa2_acq-b0echo5_magnitude_heudiconv270_e2.nii.gz
./sub-20231103lunapilotspa2/fmap/sub-20231103lunapilotspa2_acq-b0echo5_magnitude_heudiconv270_e3.nii.gz
Files with such naming scheme are not part of BIDS specification. This error is most commonly caused by typos in file names that make them not BIDS compatible. Please consult the specification and make sure your files are named correctly. If this is not a file naming issue (for example when including files not yet covered by the BIDS specification) you should include a ".bidsignore" file in your dataset (see https://github.com/bids-standard/bids-validator#bidsignore for details). Please note that derived (processed) data should be placed in /derivatives folder and source data (such as DICOMS or behavioural logs in proprietary formats) should be placed in the /sourcedata folder.
Evidence: sub-20231103lunapilotspa2_acq-b0echo5_magnitude_heudiconv270_e3.nii.gz
./sub-20231103lunapilotspa2/fmap/sub-20231103lunapilotspa2_acq-b0echo5_magnitude_heudiconv270_e4.nii.gz
Files with such naming scheme are not part of BIDS specification. This error is most commonly caused by typos in file names that make them not BIDS compatible. Please consult the specification and make sure your files are named correctly. If this is not a file naming issue (for example when including files not yet covered by the BIDS specification) you should include a ".bidsignore" file in your dataset (see https://github.com/bids-standard/bids-validator#bidsignore for details). Please note that derived (processed) data should be placed in /derivatives folder and source data (such as DICOMS or behavioural logs in proprietary formats) should be placed in the /sourcedata folder.
Evidence: sub-20231103lunapilotspa2_acq-b0echo5_magnitude_heudiconv270_e4.nii.gz
./sub-20231103lunapilotspa2/fmap/sub-20231103lunapilotspa2_acq-b0echo5_magnitude_heudiconv270_e5.nii.gz
Files with such naming scheme are not part of BIDS specification. This error is most commonly caused by typos in file names that make them not BIDS compatible. Please consult the specification and make sure your files are named correctly. If this is not a file naming issue (for example when including files not yet covered by the BIDS specification) you should include a ".bidsignore" file in your dataset (see https://github.com/bids-standard/bids-validator#bidsignore for details). Please note that derived (processed) data should be placed in /derivatives folder and source data (such as DICOMS or behavioural logs in proprietary formats) should be placed in the /sourcedata folder.
Evidence: sub-20231103lunapilotspa2_acq-b0echo5_magnitude_heudiconv270_e5.nii.gz
./sub-20231103lunapilotspa2/fmap/sub-20231103lunapilotspa2_acq-b0high_magnitude_heudiconv245_e1.nii.gz
Files with such naming scheme are not part of BIDS specification. This error is most commonly caused by typos in file names that make them not BIDS compatible. Please consult the specification and make sure your files are named correctly. If this is not a file naming issue (for example when including files not yet covered by the BIDS specification) you should include a ".bidsignore" file in your dataset (see https://github.com/bids-standard/bids-validator#bidsignore for details). Please note that derived (processed) data should be placed in /derivatives folder and source data (such as DICOMS or behavioural logs in proprietary formats) should be placed in the /sourcedata folder.
Evidence: sub-20231103lunapilotspa2_acq-b0high_magnitude_heudiconv245_e1.nii.gz
./sub-20231103lunapilotspa2/fmap/sub-20231103lunapilotspa2_acq-b0high_magnitude_heudiconv245_e2.nii.gz
Files with such naming scheme are not part of BIDS specification. This error is most commonly caused by typos in file names that make them not BIDS compatible. Please consult the specification and make sure your files are named correctly. If this is not a file naming issue (for example when including files not yet covered by the BIDS specification) you should include a ".bidsignore" file in your dataset (see https://github.com/bids-standard/bids-validator#bidsignore for details). Please note that derived (processed) data should be placed in /derivatives folder and source data (such as DICOMS or behavioural logs in proprietary formats) should be placed in the /sourcedata folder.
Evidence: sub-20231103lunapilotspa2_acq-b0high_magnitude_heudiconv245_e2.nii.gz
./sub-20231103lunapilotspa2/fmap/sub-20231103lunapilotspa2_acq-b0high_magnitude_heudiconv245_e3.nii.gz
Files with such naming scheme are not part of BIDS specification. This error is most commonly caused by typos in file names that make them not BIDS compatible. Please consult the specification and make sure your files are named correctly. If this is not a file naming issue (for example when including files not yet covered by the BIDS specification) you should include a ".bidsignore" file in your dataset (see https://github.com/bids-standard/bids-validator#bidsignore for details). Please note that derived (processed) data should be placed in /derivatives folder and source data (such as DICOMS or behavioural logs in proprietary formats) should be placed in the /sourcedata folder.
Evidence: sub-20231103lunapilotspa2_acq-b0high_magnitude_heudiconv245_e3.nii.gz
./sub-20231103lunapilotspa2/fmap/sub-20231103lunapilotspa2_acq-b0high_magnitude_heudiconv245_e4.nii.gz
Files with such naming scheme are not part of BIDS specification. This error is most commonly caused by typos in file names that make them not BIDS compatible. Please consult the specification and make sure your files are named correctly. If this is not a file naming issue (for example when including files not yet covered by the BIDS specification) you should include a ".bidsignore" file in your dataset (see https://github.com/bids-standard/bids-validator#bidsignore for details). Please note that derived (processed) data should be placed in /derivatives folder and source data (such as DICOMS or behavioural logs in proprietary formats) should be placed in the /sourcedata folder.
Evidence: sub-20231103lunapilotspa2_acq-b0high_magnitude_heudiconv245_e4.nii.gz
./sub-20231103lunapilotspa2/fmap/sub-20231103lunapilotspa2_acq-b0high_magnitude_heudiconv245_e5.nii.gz
Files with such naming scheme are not part of BIDS specification. This error is most commonly caused by typos in file names that make them not BIDS compatible. Please consult the specification and make sure your files are named correctly. If this is not a file naming issue (for example when including files not yet covered by the BIDS specification) you should include a ".bidsignore" file in your dataset (see https://github.com/bids-standard/bids-validator#bidsignore for details). Please note that derived (processed) data should be placed in /derivatives folder and source data (such as DICOMS or behavioural logs in proprietary formats) should be placed in the /sourcedata folder.
Evidence: sub-20231103lunapilotspa2_acq-b0high_magnitude_heudiconv245_e5.nii.gz
./sub-20231103lunapilotspa2/fmap/sub-20231103lunapilotspa2_acq-b0high_phase.nii.gz
Files with such naming scheme are not part of BIDS specification. This error is most commonly caused by typos in file names that make them not BIDS compatible. Please consult the specification and make sure your files are named correctly. If this is not a file naming issue (for example when including files not yet covered by the BIDS specification) you should include a ".bidsignore" file in your dataset (see https://github.com/bids-standard/bids-validator#bidsignore for details). Please note that derived (processed) data should be placed in /derivatives folder and source data (such as DICOMS or behavioural logs in proprietary formats) should be placed in the /sourcedata folder.
Evidence: sub-20231103lunapilotspa2_acq-b0high_phase.nii.gz
./sub-20231103lunapilotspa2/fmap/sub-20231103lunapilotspa2_acq-b0pfc_magnitude_heudiconv470_e1.nii.gz
Files with such naming scheme are not part of BIDS specification. This error is most commonly caused by typos in file names that make them not BIDS compatible. Please consult the specification and make sure your files are named correctly. If this is not a file naming issue (for example when including files not yet covered by the BIDS specification) you should include a ".bidsignore" file in your dataset (see https://github.com/bids-standard/bids-validator#bidsignore for details). Please note that derived (processed) data should be placed in /derivatives folder and source data (such as DICOMS or behavioural logs in proprietary formats) should be placed in the /sourcedata folder.
Evidence: sub-20231103lunapilotspa2_acq-b0pfc_magnitude_heudiconv470_e1.nii.gz
./sub-20231103lunapilotspa2/fmap/sub-20231103lunapilotspa2_acq-b0pfc_magnitude_heudiconv470_e2.nii.gz
Files with such naming scheme are not part of BIDS specification. This error is most commonly caused by typos in file names that make them not BIDS compatible. Please consult the specification and make sure your files are named correctly. If this is not a file naming issue (for example when including files not yet covered by the BIDS specification) you should include a ".bidsignore" file in your dataset (see https://github.com/bids-standard/bids-validator#bidsignore for details). Please note that derived (processed) data should be placed in /derivatives folder and source data (such as DICOMS or behavioural logs in proprietary formats) should be placed in the /sourcedata folder.
Evidence: sub-20231103lunapilotspa2_acq-b0pfc_magnitude_heudiconv470_e2.nii.gz
./sub-20231103lunapilotspa2/fmap/sub-20231103lunapilotspa2_acq-b0pfc_magnitude_heudiconv470_e3.nii.gz
Files with such naming scheme are not part of BIDS specification. This error is most commonly caused by typos in file names that make them not BIDS compatible. Please consult the specification and make sure your files are named correctly. If this is not a file naming issue (for example when including files not yet covered by the BIDS specification) you should include a ".bidsignore" file in your dataset (see https://github.com/bids-standard/bids-validator#bidsignore for details). Please note that derived (processed) data should be placed in /derivatives folder and source data (such as DICOMS or behavioural logs in proprietary formats) should be placed in the /sourcedata folder.
Evidence: sub-20231103lunapilotspa2_acq-b0pfc_magnitude_heudiconv470_e3.nii.gz
./sub-20231103lunapilotspa2/fmap/sub-20231103lunapilotspa2_acq-b0pfc_magnitude_heudiconv470_e4.nii.gz
Files with such naming scheme are not part of BIDS specification. This error is most commonly caused by typos in file names that make them not BIDS compatible. Please consult the specification and make sure your files are named correctly. If this is not a file naming issue (for example when including files not yet covered by the BIDS specification) you should include a ".bidsignore" file in your dataset (see https://github.com/bids-standard/bids-validator#bidsignore for details). Please note that derived (processed) data should be placed in /derivatives folder and source data (such as DICOMS or behavioural logs in proprietary formats) should be placed in the /sourcedata folder.
Evidence: sub-20231103lunapilotspa2_acq-b0pfc_magnitude_heudiconv470_e4.nii.gz
./sub-20231103lunapilotspa2/fmap/sub-20231103lunapilotspa2_acq-b0pfc_magnitude_heudiconv470_e5.nii.gz
Files with such naming scheme are not part of BIDS specification. This error is most commonly caused by typos in file names that make them not BIDS compatible. Please consult the specification and make sure your files are named correctly. If this is not a file naming issue (for example when including files not yet covered by the BIDS specification) you should include a ".bidsignore" file in your dataset (see https://github.com/bids-standard/bids-validator#bidsignore for details). Please note that derived (processed) data should be placed in /derivatives folder and source data (such as DICOMS or behavioural logs in proprietary formats) should be placed in the /sourcedata folder.
Evidence: sub-20231103lunapilotspa2_acq-b0pfc_magnitude_heudiconv470_e5.nii.gz
./sub-20231103lunapilotspa2/fmap/sub-20231103lunapilotspa2_acq-b0pfc_phase.nii.gz
Files with such naming scheme are not part of BIDS specification. This error is most commonly caused by typos in file names that make them not BIDS compatible. Please consult the specification and make sure your files are named correctly. If this is not a file naming issue (for example when including files not yet covered by the BIDS specification) you should include a ".bidsignore" file in your dataset (see https://github.com/bids-standard/bids-validator#bidsignore for details). Please note that derived (processed) data should be placed in /derivatives folder and source data (such as DICOMS or behavioural logs in proprietary formats) should be placed in the /sourcedata folder.
Evidence: sub-20231103lunapilotspa2_acq-b0pfc_phase.nii.gz
./sub-20231103lunapilotspa2/fmap/sub-20231103lunapilotspa2_acq-b1_magnitude_heudiconv143_e1.nii.gz
Files with such naming scheme are not part of BIDS specification. This error is most commonly caused by typos in file names that make them not BIDS compatible. Please consult the specification and make sure your files are named correctly. If this is not a file naming issue (for example when including files not yet covered by the BIDS specification) you should include a ".bidsignore" file in your dataset (see https://github.com/bids-standard/bids-validator#bidsignore for details). Please note that derived (processed) data should be placed in /derivatives folder and source data (such as DICOMS or behavioural logs in proprietary formats) should be placed in the /sourcedata folder.
Evidence: sub-20231103lunapilotspa2_acq-b1_magnitude_heudiconv143_e1.nii.gz
./sub-20231103lunapilotspa2/fmap/sub-20231103lunapilotspa2_acq-b1_magnitude_heudiconv143_e2.nii.gz
Files with such naming scheme are not part of BIDS specification. This error is most commonly caused by typos in file names that make them not BIDS compatible. Please consult the specification and make sure your files are named correctly. If this is not a file naming issue (for example when including files not yet covered by the BIDS specification) you should include a ".bidsignore" file in your dataset (see https://github.com/bids-standard/bids-validator#bidsignore for details). Please note that derived (processed) data should be placed in /derivatives folder and source data (such as DICOMS or behavioural logs in proprietary formats) should be placed in the /sourcedata folder.
Evidence: sub-20231103lunapilotspa2_acq-b1_magnitude_heudiconv143_e2.nii.gz
./sub-20231103lunapilotspa2/fmap/sub-20231103lunapilotspa2_acq-b1_phase.nii.gz
Files with such naming scheme are not part of BIDS specification. This error is most commonly caused by typos in file names that make them not BIDS compatible. Please consult the specification and make sure your files are named correctly. If this is not a file naming issue (for example when including files not yet covered by the BIDS specification) you should include a ".bidsignore" file in your dataset (see https://github.com/bids-standard/bids-validator#bidsignore for details). Please note that derived (processed) data should be placed in /derivatives folder and source data (such as DICOMS or behavioural logs in proprietary formats) should be placed in the /sourcedata folder.
Evidence: sub-20231103lunapilotspa2_acq-b1_phase.nii.gz
Please visit https://neurostars.org/search?q=NOT_INCLUDED for existing conversations about this issue.
2: [ERR] You have to define 'RepetitionTime' for this file. (code: 10 - REPETITION_TIME_MUST_DEFINE)
./sub-20231103lunapilotspa2/func/sub-20231103lunapilotspa2_task-rest_bold.nii.gz
You have to define 'RepetitionTime' or 'VolumeTiming' for this file. It can be included one of the following locations: /task-rest_bold.json, /sub-20231103lunapilotspa2/sub-20231103lunapilotspa2_task-rest_bold.json, /sub-20231103lunapilotspa2/func/sub-20231103lunapilotspa2_task-rest_bold.json
Please visit https://neurostars.org/search?q=REPETITION_TIME_MUST_DEFINE for existing conversations about this issue.
3: [ERR] You have to define 'Units' for this file. (code: 17 - UNITS_MUST_DEFINE)
./sub-20231103lunapilotspa2/fmap/sub-20231103lunapilotspa2_acq-b1Brain_fieldmap.nii.gz
You have to define 'Units' for this file. It can be included one of the following locations: /fieldmap.json, /acq-b1Brain_fieldmap.json, /sub-20231103lunapilotspa2/sub-20231103lunapilotspa2_fieldmap.json, /sub-20231103lunapilotspa2/sub-20231103lunapilotspa2_acq-b1Brain_fieldmap.json, /sub-20231103lunapilotspa2/fmap/sub-20231103lunapilotspa2_fieldmap.json, /sub-20231103lunapilotspa2/fmap/sub-20231103lunapilotspa2_acq-b1Brain_fieldmap.json
./sub-20231103lunapilotspa2/fmap/sub-20231103lunapilotspa2_acq-b1SkullIGNORE_fieldmap.nii.gz
You have to define 'Units' for this file. It can be included one of the following locations: /fieldmap.json, /acq-b1SkullIGNORE_fieldmap.json, /sub-20231103lunapilotspa2/sub-20231103lunapilotspa2_fieldmap.json, /sub-20231103lunapilotspa2/sub-20231103lunapilotspa2_acq-b1SkullIGNORE_fieldmap.json, /sub-20231103lunapilotspa2/fmap/sub-20231103lunapilotspa2_fieldmap.json, /sub-20231103lunapilotspa2/fmap/sub-20231103lunapilotspa2_acq-b1SkullIGNORE_fieldmap.json
./sub-20231103lunapilotspa2/fmap/sub-20231103lunapilotspa2_acq-combinedXb1_fieldmap.nii.gz
You have to define 'Units' for this file. It can be included one of the following locations: /fieldmap.json, /acq-combinedXb1_fieldmap.json, /sub-20231103lunapilotspa2/sub-20231103lunapilotspa2_fieldmap.json, /sub-20231103lunapilotspa2/sub-20231103lunapilotspa2_acq-combinedXb1_fieldmap.json, /sub-20231103lunapilotspa2/fmap/sub-20231103lunapilotspa2_fieldmap.json, /sub-20231103lunapilotspa2/fmap/sub-20231103lunapilotspa2_acq-combinedXb1_fieldmap.json
Please visit https://neurostars.org/search?q=UNITS_MUST_DEFINE for existing conversations about this issue.
4: [ERR] You have to define 'PhaseEncodingDirection' for this file. (code: 18 - PHASE_ENCODING_DIRECTION_MUST_DEFINE)
./sub-20231103lunapilotspa2/fmap/sub-20231103lunapilotspa2_acq-rest_dir-AP_epi.nii.gz
You have to define 'PhaseEncodingDirection' for this file. It can be included one of the following locations: /epi.json, /acq-rest_epi.json, /dir-AP_epi.json, /acq-rest_dir-AP_epi.json, /sub-20231103lunapilotspa2/sub-20231103lunapilotspa2_epi.json, /sub-20231103lunapilotspa2/sub-20231103lunapilotspa2_acq-rest_epi.json, /sub-20231103lunapilotspa2/sub-20231103lunapilotspa2_dir-AP_epi.json, /sub-20231103lunapilotspa2/sub-20231103lunapilotspa2_acq-rest_dir-AP_epi.json, /sub-20231103lunapilotspa2/fmap/sub-20231103lunapilotspa2_epi.json, /sub-20231103lunapilotspa2/fmap/sub-20231103lunapilotspa2_acq-rest_epi.json, /sub-20231103lunapilotspa2/fmap/sub-20231103lunapilotspa2_dir-AP_epi.json, /sub-20231103lunapilotspa2/fmap/sub-20231103lunapilotspa2_acq-rest_dir-AP_epi.json
./sub-20231103lunapilotspa2/fmap/sub-20231103lunapilotspa2_acq-rest_dir-PA_epi.nii.gz
You have to define 'PhaseEncodingDirection' for this file. It can be included one of the following locations: /epi.json, /acq-rest_epi.json, /dir-PA_epi.json, /acq-rest_dir-PA_epi.json, /sub-20231103lunapilotspa2/sub-20231103lunapilotspa2_epi.json, /sub-20231103lunapilotspa2/sub-20231103lunapilotspa2_acq-rest_epi.json, /sub-20231103lunapilotspa2/sub-20231103lunapilotspa2_dir-PA_epi.json, /sub-20231103lunapilotspa2/sub-20231103lunapilotspa2_acq-rest_dir-PA_epi.json, /sub-20231103lunapilotspa2/fmap/sub-20231103lunapilotspa2_epi.json, /sub-20231103lunapilotspa2/fmap/sub-20231103lunapilotspa2_acq-rest_epi.json, /sub-20231103lunapilotspa2/fmap/sub-20231103lunapilotspa2_dir-PA_epi.json, /sub-20231103lunapilotspa2/fmap/sub-20231103lunapilotspa2_acq-rest_dir-PA_epi.json
Please visit https://neurostars.org/search?q=PHASE_ENCODING_DIRECTION_MUST_DEFINE for existing conversations about this issue.
5: [ERR] You have to define 'TotalReadoutTime' for this file. (code: 19 - TOTAL_READOUT_TIME_MUST_DEFINE)
./sub-20231103lunapilotspa2/fmap/sub-20231103lunapilotspa2_acq-rest_dir-AP_epi.nii.gz
You have to define 'TotalReadoutTime' for this file. It can be included one of the following locations: /epi.json, /acq-rest_epi.json, /dir-AP_epi.json, /acq-rest_dir-AP_epi.json, /sub-20231103lunapilotspa2/sub-20231103lunapilotspa2_epi.json, /sub-20231103lunapilotspa2/sub-20231103lunapilotspa2_acq-rest_epi.json, /sub-20231103lunapilotspa2/sub-20231103lunapilotspa2_dir-AP_epi.json, /sub-20231103lunapilotspa2/sub-20231103lunapilotspa2_acq-rest_dir-AP_epi.json, /sub-20231103lunapilotspa2/fmap/sub-20231103lunapilotspa2_epi.json, /sub-20231103lunapilotspa2/fmap/sub-20231103lunapilotspa2_acq-rest_epi.json, /sub-20231103lunapilotspa2/fmap/sub-20231103lunapilotspa2_dir-AP_epi.json, /sub-20231103lunapilotspa2/fmap/sub-20231103lunapilotspa2_acq-rest_dir-AP_epi.json
./sub-20231103lunapilotspa2/fmap/sub-20231103lunapilotspa2_acq-rest_dir-PA_epi.nii.gz
You have to define 'TotalReadoutTime' for this file. It can be included one of the following locations: /epi.json, /acq-rest_epi.json, /dir-PA_epi.json, /acq-rest_dir-PA_epi.json, /sub-20231103lunapilotspa2/sub-20231103lunapilotspa2_epi.json, /sub-20231103lunapilotspa2/sub-20231103lunapilotspa2_acq-rest_epi.json, /sub-20231103lunapilotspa2/sub-20231103lunapilotspa2_dir-PA_epi.json, /sub-20231103lunapilotspa2/sub-20231103lunapilotspa2_acq-rest_dir-PA_epi.json, /sub-20231103lunapilotspa2/fmap/sub-20231103lunapilotspa2_epi.json, /sub-20231103lunapilotspa2/fmap/sub-20231103lunapilotspa2_acq-rest_epi.json, /sub-20231103lunapilotspa2/fmap/sub-20231103lunapilotspa2_dir-PA_epi.json, /sub-20231103lunapilotspa2/fmap/sub-20231103lunapilotspa2_acq-rest_dir-PA_epi.json
Please visit https://neurostars.org/search?q=TOTAL_READOUT_TIME_MUST_DEFINE for existing conversations about this issue.
6: [ERR] The number of volumes in this scan does not match the number of volumes in the corresponding .bvec and .bval files. (code: 29 - VOLUME_COUNT_MISMATCH)
./sub-20231103lunapilotspa2/dwi/sub-20231103lunapilotspa2_dir-PA_dwi.nii.gz
The number of volumes in this scan does not match the number of volumes in the corresponding .bvec and .bval files.
Please visit https://neurostars.org/search?q=VOLUME_COUNT_MISMATCH for existing conversations about this issue.
7: [ERR] .bval and .bvec files must be single space delimited and contain only numerical values. (code: 47 - B_FILE)
./sub-20231103lunapilotspa2/dwi/sub-20231103lunapilotspa2_dir-PA_dwi.bval
.bval and .bvec files must be single space delimited and contain only numerical values.
./sub-20231103lunapilotspa2/dwi/sub-20231103lunapilotspa2_dir-PA_dwi.bvec
.bval and .bvec files must be single space delimited and contain only numerical values.
Please visit https://neurostars.org/search?q=B_FILE for existing conversations about this issue.
8: [ERR] You have to define 'TaskName' for this file. (code: 50 - TASK_NAME_MUST_DEFINE)
./sub-20231103lunapilotspa2/func/sub-20231103lunapilotspa2_task-rest_bold.nii.gz
You have to define 'TaskName' for this file. It can be included one of the following locations: /task-rest_bold.json, /sub-20231103lunapilotspa2/sub-20231103lunapilotspa2_task-rest_bold.json, /sub-20231103lunapilotspa2/func/sub-20231103lunapilotspa2_task-rest_bold.json
Please visit https://neurostars.org/search?q=TASK_NAME_MUST_DEFINE for existing conversations about this issue.
9: [ERR] The compulsory file /dataset_description.json is missing. See Section 03 (Modality agnostic files) of the BIDS specification. (code: 57 - DATASET_DESCRIPTION_JSON_MISSING)
Please visit https://neurostars.org/search?q=DATASET_DESCRIPTION_JSON_MISSING for existing conversations about this issue.
10: [ERR] acq Name contain an Illegal Character hyphen or underscore. Please edit the filename as per BIDS spec. (code: 59 - ACQ_NAME_CONTAIN_ILLEGAL_CHARACTER)
./sub-20231103lunapilotspa2/anat/sub-20231103lunapilotspa2_acq-b0recon_magnitude_heudiconv744_e1.nii.gz
acq Name contain an Illegal Character hyphen or underscore. Please edit the filename as per BIDS spec.
Evidence: acq name contains illegal character:/sub-20231103lunapilotspa2/anat/sub-20231103lunapilotspa2_acq-b0recon_magnitude_heudiconv744_e1.nii.gz
./sub-20231103lunapilotspa2/fmap/sub-20231103lunapilotspa2_acq-b0echo5_magnitude_heudiconv270_e1.nii.gz
acq Name contain an Illegal Character hyphen or underscore. Please edit the filename as per BIDS spec.
Evidence: acq name contains illegal character:/sub-20231103lunapilotspa2/fmap/sub-20231103lunapilotspa2_acq-b0echo5_magnitude_heudiconv270_e1.nii.gz
./sub-20231103lunapilotspa2/fmap/sub-20231103lunapilotspa2_acq-b0echo5_magnitude_heudiconv270_e3.nii.gz
acq Name contain an Illegal Character hyphen or underscore. Please edit the filename as per BIDS spec.
Evidence: acq name contains illegal character:/sub-20231103lunapilotspa2/fmap/sub-20231103lunapilotspa2_acq-b0echo5_magnitude_heudiconv270_e3.nii.gz
./sub-20231103lunapilotspa2/fmap/sub-20231103lunapilotspa2_acq-b0echo5_magnitude_heudiconv270_e5.nii.gz
acq Name contain an Illegal Character hyphen or underscore. Please edit the filename as per BIDS spec.
Evidence: acq name contains illegal character:/sub-20231103lunapilotspa2/fmap/sub-20231103lunapilotspa2_acq-b0echo5_magnitude_heudiconv270_e5.nii.gz
./sub-20231103lunapilotspa2/fmap/sub-20231103lunapilotspa2_acq-b0high_magnitude_heudiconv245_e2.nii.gz
acq Name contain an Illegal Character hyphen or underscore. Please edit the filename as per BIDS spec.
Evidence: acq name contains illegal character:/sub-20231103lunapilotspa2/fmap/sub-20231103lunapilotspa2_acq-b0high_magnitude_heudiconv245_e2.nii.gz
./sub-20231103lunapilotspa2/fmap/sub-20231103lunapilotspa2_acq-b0high_magnitude_heudiconv245_e4.nii.gz
acq Name contain an Illegal Character hyphen or underscore. Please edit the filename as per BIDS spec.
Evidence: acq name contains illegal character:/sub-20231103lunapilotspa2/fmap/sub-20231103lunapilotspa2_acq-b0high_magnitude_heudiconv245_e4.nii.gz
./sub-20231103lunapilotspa2/fmap/sub-20231103lunapilotspa2_acq-b0pfc_magnitude_heudiconv470_e1.nii.gz
acq Name contain an Illegal Character hyphen or underscore. Please edit the filename as per BIDS spec.
Evidence: acq name contains illegal character:/sub-20231103lunapilotspa2/fmap/sub-20231103lunapilotspa2_acq-b0pfc_magnitude_heudiconv470_e1.nii.gz
./sub-20231103lunapilotspa2/fmap/sub-20231103lunapilotspa2_acq-b0pfc_magnitude_heudiconv470_e3.nii.gz
acq Name contain an Illegal Character hyphen or underscore. Please edit the filename as per BIDS spec.
Evidence: acq name contains illegal character:/sub-20231103lunapilotspa2/fmap/sub-20231103lunapilotspa2_acq-b0pfc_magnitude_heudiconv470_e3.nii.gz
./sub-20231103lunapilotspa2/fmap/sub-20231103lunapilotspa2_acq-b0pfc_magnitude_heudiconv470_e5.nii.gz
acq Name contain an Illegal Character hyphen or underscore. Please edit the filename as per BIDS spec.
Evidence: acq name contains illegal character:/sub-20231103lunapilotspa2/fmap/sub-20231103lunapilotspa2_acq-b0pfc_magnitude_heudiconv470_e5.nii.gz
./sub-20231103lunapilotspa2/fmap/sub-20231103lunapilotspa2_acq-b1_magnitude_heudiconv143_e1.nii.gz
acq Name contain an Illegal Character hyphen or underscore. Please edit the filename as per BIDS spec.
Evidence: acq name contains illegal character:/sub-20231103lunapilotspa2/fmap/sub-20231103lunapilotspa2_acq-b1_magnitude_heudiconv143_e1.nii.gz
Please visit https://neurostars.org/search?q=ACQ_NAME_CONTAIN_ILLEGAL_CHARACTER for existing conversations about this issue.
11: [ERR] _fieldmap.nii[.gz] file does not have accompanying _magnitude.nii[.gz] file. (code: 91 - _FIELDMAP_WITHOUT_MAGNITUDE_FILE)
./sub-20231103lunapilotspa2/fmap/sub-20231103lunapilotspa2_acq-b1Brain_fieldmap.nii.gz
_fieldmap.nii[.gz] file does not have accompanying _magnitude.nii[.gz] file.
./sub-20231103lunapilotspa2/fmap/sub-20231103lunapilotspa2_acq-b1SkullIGNORE_fieldmap.nii.gz
_fieldmap.nii[.gz] file does not have accompanying _magnitude.nii[.gz] file.
./sub-20231103lunapilotspa2/fmap/sub-20231103lunapilotspa2_acq-combinedXb1_fieldmap.nii.gz
_fieldmap.nii[.gz] file does not have accompanying _magnitude.nii[.gz] file.
Please visit https://neurostars.org/search?q=_FIELDMAP_WITHOUT_MAGNITUDE_FILE for existing conversations about this issue.
1: [WARN] You should define 'SliceTiming' for this file. If you don't provide this information slice time correction will not be possible. 'Slice Timing' is the time at which each slice was acquired within each volume (frame) of the acquisition. Slice timing is not slice order -- rather, it is a list of times containing the time (in seconds) of each slice acquisition in relation to the beginning of volume acquisition. (code: 13 - SLICE_TIMING_NOT_DEFINED)
./sub-20231103lunapilotspa2/func/sub-20231103lunapilotspa2_task-rest_bold.nii.gz
You should define 'SliceTiming' for this file. If you don't provide this information slice time correction will not be possible. It can be included one of the following locations: /task-rest_bold.json, /sub-20231103lunapilotspa2/sub-20231103lunapilotspa2_task-rest_bold.json, /sub-20231103lunapilotspa2/func/sub-20231103lunapilotspa2_task-rest_bold.json
Please visit https://neurostars.org/search?q=SLICE_TIMING_NOT_DEFINED for existing conversations about this issue.
2: [WARN] The recommended file /README is missing. See Section 03 (Modality agnostic files) of the BIDS specification. (code: 101 - README_FILE_MISSING)
Please visit https://neurostars.org/search?q=README_FILE_MISSING for existing conversations about this issue.
Summary: Available Tasks: Available Modalities:
48 Files, 630.62MB MRI
1 - Subject
1 - Session
If you have any questions, please post on https://neurostars.org/tags/bids.