-
Notifications
You must be signed in to change notification settings - Fork 67
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
Remove daysback
option
#160
Conversation
CI fails:
I remember, there was this issue with the previous anonymization approach in old datasets… |
I first thought this was related to mne-tools/mne-python#7711 but it's probably sth else |
I guess we'll just have to re-anonymize the dataset and push it to OpenNeuro? However I don't have write access to the It says "uploaded by Julia Guiomar Niso Galán" -- anyone know how I could get in touch to ask for creation of a new revision, or for access rights to publish it myself? |
yes data needs to be fixed on openneuro |
ping @guiomar @hoechenberger can you articulate what exactly is the problem with the dataset for the benefit of @guiomar ? |
@jasmainak I just dropped her an email 😃 So my understanding of the issue is that, in essence, the dataset was anonymized with an older version of MNE, and newer versions have difficulties dealing with that. We need to re-anonymize the dataset with MNE 0.20 to fix the problem. |
I doubt it was anonymized with MNE. Maybe with brainstorm ... |
it was anonymized with brainstorm but using older convention of the bids
standard
… |
Hi! If I correctly remember we did a face mask on T1w MRI (using open tool Face Masking, http://nrg.wustl.edu/software/face-masking (Milchenko and Marcus 2013)) and anonymize the acquisition date by adding a random number of hours (different for each subject but the same for each scan within a subject) as suggested by the BIDS spec at that time (1.0.2). Happy to upload the new version. |
regarding acq_time this issue is that fif files cannot store dates that are
too old. We had to change the valid acq_time in BIDS anonymized files to
make it fif compatible.
|
Ok, I see! Thank you Alex |
By the way, do you know if this has been updated to the BIDS spec? |
@sappelhoff @jasmainak can you help me point to the right section in the bids standard? |
The "anonymization" rule details in BIDS were changed in November 2019, see: bids-standard/bids-specification#363 ... based on the discussion in this issue: bids-standard/bids-specification#360 The only change was: To distinguish real dates from shifted dates always use year
-1900
+1925
or earlier when including shifted years. So I guess @agramfort is right with what he said in #160 (comment) ... the data was probably anonymized to some date prior to 1900 ... and this now trips up the FIF file format, which can only store dates that are a bit later (not prior 1900) edit: it's important to say though, that anonymizing BEFORE 1900 is not wrong per se (see wording in the spec: "1925 or earlier") ... it's basically a FIF problem. |
what I don't understand is how brainstorm deals with dates before 1900. @guiomar must have checked that the files can be read after anonymizing. |
just to be sure @hoechenberger are you dealing with fif files or CTF files? |
they are |
Thanks a lot @sappelhoff!! |
so CTF files are not subject to the same int32 issues as fif, it might be an MNE issue ... |
the pb comes when you save any fif file starting from the CTF ds file
(new raw, epochs, evoked etc).
|
oh boy ... |
Thanks! Then if this is the case, BIDS should enforce to to use a year 1925, and remove the "or earlier" from the specs. |
The problem is that in longitudinal studies, people want to keep the relative time. So if you had recordings over 5 years, they want to keep this information. but I agree that the 1925 year limit is too stringent. It doesn't make pragmatic sense and will hinder adoption of BIDS in MEG community |
According to HHS regulations, you only need to anonymize up to a year:
|
You can always do a PR to bids-standard/bids-specification to insert a note that alerts people to the fact that "choosing a very early date (e.g., 1880) will negatively affect interoperability. --> because FIF does not support it." AFAIK this is not a problem for any other data format. |
Thanks! I think I'll do :) |
I think @alexrockhill looked into this deeply at some point. |
some date in 1901 :) it's basically 1st January 1970 - number of seconds that can be represented by int32 (=2,147,483,647) |
The datetime is stored in fif as a 32-bit integer which when converted into seconds before/after Jan 1, 1970 (time = 0) ranges from 1901 to 2040 or so (the numbers aren't exact) that's why we had to ask BIDS to move the anonymization date required up from before 1900 to before 1925. |
Thanks a lot!! |
Anonymization should happen on the BIDS level. Closes mne-toolsGH-159.
3464935
to
8df7274
Compare
Closed via #257 |
Anonymization should happen on the BIDS level.
Closes GH-159.