Patrick Sadil

> * The order appears to be AP(reverse)-PA(forward)-AP(reverse)-PA(forward) (see below). @psadil Could you please confirm your data? @mr-jaemin thanks for this information. Yes, I can confirm that this order matches...

Still just trying to understand how this code goes together. Does the following sound about right: [`group_dicoms_info_seqinfos`](https://github.com/nipy/heudiconv/blob/8fca121ae204e33b008f3b4e9dac57310eef266d/heudiconv/dicoms.py#L15) is around where some modifications would be needed. The PAR files are getting...

sounds good, I'll go with the --parrec argument. Just as a heads up, I won't be fast at this (end of semester season + slow python coder), but so long...

Finally have a bit of time to sit and work on this. Looks like the simplest workaround would be to create a temporary .nii file with nibabel's `parrec2nii` load that...

Handling this ended up being fairly far above my head. Sorry to have snagged it and then silently threw up my hands! I'm not aware of anyone else working on...

> ... It is lower on the priority list of bugs to fix because I'm not convinced that there is a real benefit to forcing the dedicated fmaps into topup,...

FWIW, I'm encountering the same issue with the similar set of symptoms (supposedly "No errors to report!", and those warnings in the error file). Following an implication of [this suggestion](https://github.com/PennLINC/qsiprep/issues/262#issuecomment-878054267),...

@mslw , thanks for following up! > I am wondering, what was your intended use case for "metadata"? I didn't have one; I discovered the issue while exploring the python...

What else is needed to get that pull request finished?

Tests added! Do these seem like they're on the right track?