You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am not sure how this horror (27-Aug-2020 11:33:5.3325) got into my header (I am suspecting the SPM DICOM import is trying to be TOO smart) but is that something that would be flagged by BIDSonym ?
The text was updated successfully, but these errors were encountered:
Indeed, SPM is a bit more "hands-on" concerning image file headers than most other software. IIRC, @miykael even had names or so in there. However, this is definitely also an interaction with whatever folks at the scanner put in (e.g. sequence name). Hm, I think as it is right now, BIDSonym would not capture that. You would get a tsv file for each image you have containing all key-value pairs present, but the date would not be indicated as "potentially problematic". This is actually something that should be noted and I'll try to add a date format finder so that whenever something like that is present BIDSonym will flag it as "potentially problematic" in the respective tsv file.
NB: it definitely won't delete/change such things as I don't want to open up the possibility of image header modification (looking at you SPM, hehe).
Hey.
Quickly realized this is in my dataset.
I am not sure how this horror (
27-Aug-2020 11:33:5.3325
) got into my header (I am suspecting the SPM DICOM import is trying to be TOO smart) but is that something that would be flagged by BIDSonym ?The text was updated successfully, but these errors were encountered: