B0FieldSource as a list about bidscoin HOT 12 CLOSED

B0FieldIdentifier | RECOMMENDED | string or array of strings

Aha, I didn't know this, I'll see what I can do

from bidscoin.

Please reopen if things are not working for you

from bidscoin.

I'm not sure if I understand the problem, as the BIDS specification defines just a single tag, not a list, right? So

B0FieldSource: 
  - tag1
  - tag2
  - tag3

should be converted to

B0FieldSource: tag1tag2tag3

???

from bidscoin.

BIDS specification says that it's a string or an array of strings. I don't really know how tools should use it, but with IntendedFor we can say that we use three fieldmaps for one functional image.

from bidscoin.

I guess you can pass a list like this?

B0FieldSource: [magnetude1, magnetude2, phasediff]

from bidscoin.

Should be fine but it shouldn't matter both forms are correct syntax.

from bidscoin.

Yes I know, but I mean that's how you can pass it in the bidseditor?

from bidscoin.

Ah, I'm not using the BIDS editor 🙈 But if I did, I'd be fine with the compact syntax.

from bidscoin.

I just tested it and, except for the <<session>> value, it worked just fine? In the template I did:

    meta: &fmap_meta
      B0FieldIdentifier: [tag1, <<session>>tag2]

And then I got this in the json sidecar file:

    "B0FieldIdentifier": [
        "tag1",
        "<<session>>tag2"
    ]

from bidscoin.

Looks fine to me. I can try to test more next week (with the <<session>> tag) as we're planning to upgrade to BIDScoin 4.3.0 and test some mappings.

from bidscoin.

Actually, entering [tag1, <<session>>tag2] in the bidseditor is interpreted as a string, so that doesn't work (but then <<session>> does), giving for sub-001_ses-01_acq-fieldmap2p4iso_magnitude1.json:

    "B0FieldIdentifier": "[tag1, 01tag2]"

from bidscoin.

NB: passing ["tag1", '<<session>>tag2'] in the bidseditor correctly (besides <<session>>) gives:

    "B0FieldIdentifier": [
        "tag1",
        "<<session>>tag2"
    ]

from bidscoin.