Skip to content
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

Question about data structuring prior to running BIDSKIT #119

Open
ChristineFarrugia opened this issue Apr 4, 2023 · 0 comments
Open

Question about data structuring prior to running BIDSKIT #119

ChristineFarrugia opened this issue Apr 4, 2023 · 0 comments

Comments

@ChristineFarrugia
Copy link

Hi,

We are currently trying to process some data with BIDSKIT but are unsure on how best to structure it. The data consists of the following series:

  • An anatomical scan (T1)
  • Three separate fMRI scans. Participants were watching a different video during each scan. Additionally, the fMRI scans do not have identical acquisition parameters (it's mainly the number of volumes that changes).
  • A gradient field map set (2 magnitude images + 1 phase difference) for EACH fMRI scan (so 3 sets in total).

Up till now we have tried:

  • Not separating the data into different sessions. In this case the protocol translator file correctly identifies the different fMRI series, but only creates one gradient field map entry, which is a problem, since we want to associate each set of gradient field maps with the corresponding fMRI data.
  • Putting the fMRI data sets (together with the respective field maps) into different session folders. However, when we do this BIDSKIT only generates ONE fMRI entry and ONE gradient field map entry. Which is not what we were expecting, since each fMRI data set has a different series description (due to the variations in the number of volumes).

Any advice would be greatly appreciated :-)
Christine

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant