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

Add dataset-level description option #61

Open
tsalo opened this issue Jan 23, 2024 · 1 comment
Open

Add dataset-level description option #61

tsalo opened this issue Jan 23, 2024 · 1 comment
Labels
enhancement New feature or request

Comments

@tsalo
Copy link
Member

tsalo commented Jan 23, 2024

I'm starting to work on CuBIDS, which is useful for annotating variant acquisitions in a BIDS dataset (e.g., adding an acq entity if some runs of a task have X volumes and some have Y volumes in the dataset). It would be great to have an option in pybids-reports that generates a description that accounts for variants by specifically looking at the acq field and reporting across subjects.

For example, let's say we have a dataset like this:

sub-01/
    func/
        sub-01_task-rest_acq-100volumes_bold.nii.gz
sub-02/
    func/
        sub-02_task-rest_acq-100volumes_bold.nii.gz
sub-03/
    func/
        sub-03_task-rest_acq-90volumes_bold.nii.gz

In the current version of pybids-reports, we would end up with two patterns in the BIDSReport report Counter: one that describes subjects 01 and 02, and a second one that describes subject 03. My proposal is a parameter in BIDSReport that would describe the whole dataset, treating the different acq values as different variants on the same task (assuming all other entities are the same).

Something like:

For session 01:
MR data were acquired using a 3-Tesla Siemens Prisma MRI scanner.
In two subjects, one run of resting-state fMRI data were collected (). Each run was XX minutes in length, during
which 100 functional volumes were acquired.
In one subject, one run of resting-state fMRI data were collected (). Each run was XX minutes in length, during
which 90 functional volumes were acquired.

@tsalo tsalo added the enhancement New feature or request label Jan 23, 2024
@Remi-Gau
Copy link
Contributor

treating the different acq values as different variants on the same task (assuming all other entities are the same)

yeah that was my thought when I started reading the beginning of your issue.

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

No branches or pull requests

2 participants