Basile

Results 78 comments of Basile

As a side note, exporting phase data (more as an exploratory choice) and trying to put it in BIDS has been triggering a lot of problems in different parts of...

@tsalo is that something that is fixed by https://github.com/nipreps/niworkflows/pull/594 ? Should this be backported to the LTS, or it's too complex (depends on niworkflows/pybids changes) ? Thanks!

Thanks for reporting that issue. So if I understand the bids contains multiple fieldmaps for the same acquisition (ie. multiple IntendedFor), this is uncommon but I see nothing against that...

From what I understand, it can only extract information from a single dicom tag. Would it be possible to make it generalize to extract from multiple tags. The most flexible...

I am looking into a way to fix that. One option would be to store both the absolute path and the path relative to layout root in the `BIDS*File` objects,...

So if I understand, the database would store root-relative path, and when layout is loaded, the given root would be prepend to the path of the query results. As a...

The json one is correct. ``` layout=bids.BIDSLayout('./generic/',validate=False) json=layout.get(subject='01',session='vid001',suffix="sbref",datatype='func',extension='json',task='bournesupremacy',run=1)[0] nii=layout.get(subject='01',session='vid001',suffix="sbref",datatype='func',extension='nii.gz',task='bournesupremacy',run=1)[0] nii.filename 'sub-01_ses-vid001_task-bournesupremacy_run-01_sbref.nii.gz' json.filename 'sub-01_ses-vid001_task-bournesupremacy_run-01_sbref.json' nii.get_metadata()['PhaseEncodingDirection'] 'j' json.get_dict()['PhaseEncodingDirection'] 'j-' ``` Here is a clipped version of the json file: ``` ... 'PartialFourier':...

``` nii.get_associations() [, , ] ``` The only json is the one that matches the filename. The output flip is because I ran it on another subdataset, sorry about that....

It does have the opposite phase direction, so this could be the cause. What is weird is that only the nii.gz is listed in the associations and not the json....

Ok thanks a lot for the detailed explanation! If I understood correctly by level you mean entity, so if a json doesn't have a task defined it applies to all...