-
Notifications
You must be signed in to change notification settings - Fork 85
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
Supporting CNTs (Neuroscan) files #922
Comments
Hello! 👋 Thanks for opening your first issue here! ❤️ We will try to get back to you soon. 🚴🏽♂️ |
.cnt is not a format parf of the BIDS standard
https://bids-specification.readthedocs.io/en/bep-009/04-modality-specific-files/03-electroencephalography.html
|
Thanks @agramfort , I meant as an input format (that is, I want to convert from cnt to any of the accepted bids formats). Right now I think it is giving an error when it extracts the .cnt extesion and is not able to pass the ALLOWED_INPUT_EXTENSIONS check: Lines 1365 to 1383 in 4c0755c
Maybe I'm doing something wrong, Im just opening the file with the |
Here is a colab with the replication of the error I get: https://colab.research.google.com/drive/1cKaSnQglJwdLL-isNBlN6z5p_LixvkJN?usp=sharing |
@sappelhoff WDYT? |
Hi @yjmantilla :) I think if we are supporting Nihon Kohden and Persyst, we might as well support CNT ... as long as all of these non-supported file formats get auto-converted into a BIDS supported format. Could be an added feature in a PR? |
sounds like a plan !
… |
@sappelhoff Thanks! I could test what happens if one naively just adds the .cnt format to the MANUFACTURERS dictionary, and start from there what would be required to accept support cnt . |
Describe the problem
Hi mne-bids team. I was wondering if there was any reason for not supporting CNTs. I have run into some problems when using
write_raw_bids
and I noticed it was not on the list of eeg extensions:mne-bids/mne_bids/config.py
Lines 49 to 55 in 4c0755c
Is there a reason for not supporting it beyond not being included on this dictionary?
The text was updated successfully, but these errors were encountered: