BIDs & Validation Error Explanation # 2

[ayshahamkari]

Screenshot above explains the error that we are having with Subject_0329.
This subjects has been manually checked and gone through the new validation pipeline on xnat. I reached out to both Haidee and Amal and to
they are assuming that this may be due to either an incomplete acquisition, or naming structure error, it's very difficult to tell right now given limited access to info and scanner.

I just wanted to reach out and check in with you to see if perhaps there is an issue with the BIDs structure for not taking the scans? For example, is it because of a misspelling that did not include the number '5' after Multidelay for the ASL?

Thanks !

[soumen02]

we might need @putiw on this, have to wait till she's back.

[ayshahamkari]

Sounds good!

[putiw]

This one has data from two separate sessions mixed together (2022-10-14, 2024-03-06). The 2024 session has two asl_m0 scans (series 48 and 50), but no MultiDelay. The scan 49 from 2024 is missing, which is where I expect the ASL to be. The only ASL MultiDelay is from the 2022 session (scan 55), and it's a completely different protocol (40 slices instead of 48, 12 volumes instead of 10 or 25, different TR, and different naming). This doesn't match either version 1 or version 2 of our protocol. This is a bit confusing, I am also not too sure, please double triple check on the timing and parameters of each scan and confirm.

Also the GE fieldmaps from 2022 (scans 46–49) are getting matched as EPI fieldmaps but we don't need these as we have the 2024 SE fieldmaps (scans 21–22) which are the correct ones for the func data.

Could you check with Haidee/Amal about what happened during the 2024 scan session? Specifically whether an ASL MultiDelay was actually acquired and didn't get uploaded to XNAT, or if the scan was skipped/aborted for this subject.
Since the 2022 ASL is neither version 1 nor version 2 and has different acquisition parameters from the rest of the dataset, I don't think we should use it as it would be too different from all the other subjects' data. You can discuss with Bas or Kartik to make the final call on that after hearing back from Haidee/Amal about what happened.

For the BIDS conversion itself, I can update the config to convert the 2022 old ASL data if you want, but again, it is REALLY different, I don't know enough about ASL to tell you if this is a big problem.