-
Notifications
You must be signed in to change notification settings - Fork 90
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
participants.tsv files are erroneously expected to always have more than one column #891
Comments
Hello! 👋 Thanks for opening your first issue here! ❤️ We will try to get back to you soon. 🚴🏽♂️ |
Hi @SebastianSpeer , it seems your error message is due to the |
@adam2392 , This is what it looks like: github does not support tsv files so I can't upload it as such. I can upload it as csv if needed? |
Thanks @SebastianSpeer, I think this is a bug on our side. We somehow always expected
The fast fix for us would be to use something like |
@SebastianSpeer do you perhaps want to prepare a fix and make a pull request? |
Oups, I forgot that this was already fixed in #886 |
@SebastianSpeer This will be fixed in the next version bump. Until then, visit the file
to:
Voilà. |
I'm working (presumably) on the same dataset (EEGManyPipelines study), and there is a further error with this .tsv file that is not fixed with simply loading the data with File "<decorator-gen-584>", line 24, in make_report
File "c:\users\user\anaconda3\lib\site-packages\mne_bids\report.py", line 500, in make_report
participant_summary = _summarize_participants_tsv(root)
File "c:\users\user\anaconda3\lib\site-packages\mne_bids\report.py", line 232, in _summarize_participants_tsv
n_age_unknown = len(p_ages)
TypeError: object of type 'NoneType' has no len() However, fixing this did not fix the problem with loading the dataset, as the participants contain
|
Dear MNE BIDS team,
I'm trying to read in data via mne-bids. Everything works fine until the channel locations are read in.
This is what my channels tsv file looks like:
This is the error message I'm receiving:
Could this issue be due to an incorrectly formatted tsv file?
The text was updated successfully, but these errors were encountered: