-
Notifications
You must be signed in to change notification settings - Fork 111
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
[WIP] Participants data always null. Issue 49 never thrown. #1772
Conversation
…ets reassigned, declare with let not const"" This reverts commit 5ec0b3d.
Codecov ReportPatch coverage:
Additional details and impacted files@@ Coverage Diff @@
## master #1772 +/- ##
==========================================
- Coverage 85.71% 83.40% -2.32%
==========================================
Files 130 92 -38
Lines 6575 3893 -2682
Branches 1524 1270 -254
==========================================
- Hits 5636 3247 -2389
+ Misses 833 548 -285
+ Partials 106 98 -8
☔ View full report in Codecov by Sentry. |
… they do and use Object assign
…t tests in case there is no participants file
We now get code 67
|
@dorahermes could you look into this, please? |
Suggestion from maintainers meeting: for legacy validator automatically add 67 to ignored codes if --ignore-nifti-headers used, prevent us from having to edit ignored codes in bids-examples tests. |
It seems that 3 subjects are missing folders (jf, gf, jp). Data from these subjects is located in the original ECoG library. Let me know if you prefer option 1 or 2:
(I am not sure why I missed these subjects in the conversion. One thing I vaguely remember is that there was a mismatch in electrodes and channels, but the current version of the ECoG library does not have any mismatches. There was an update in 2022 though.) |
IMO if the usefulness of the dataset as an example isn't damaged by dropping the subjects, removing them from |
agreed |
Participants was being defined as a const and assigned null. Usual use case for consts is to give it an actual array or object with reference and then later on push to that array or object. For whatever reason tsv validation attempts to reassign the participants reference it gets.