Chris Markiewicz
Chris Markiewicz
@DimitriPapadopoulos There are several unaddressed comments above. They're hidden by default.
Ah, missed this. No, it's totally fine to drop 32-bit. I sincerely doubt nitime will be the only problem if fmriprep tries to run on 32-bit.
We need to add file rules to the schema and text to the spec. This could go on derivatives/imaging_data or derivatives/pet, or similar Are there required metadata for these files?
To expand on the file rules, here is the current rule for derivative PET data (`rules.files.deriv.imaging.pet_pet_volumetric` in https://bids-specification.readthedocs.io/en/latest/schema.json): ```yaml "pet_pet_volumetric": { "entities": { "task": "optional", "tracer": "optional", "reconstruction": "optional", "run":...
@mnoergaard If the BEP23 consensus is that there will be no more required metadata for MImap files, then that's fine. I would just be sure you're not rushing to put...
In fits and starts. @adelavega says actually not terrible, limited mostly by bandwidth. We're thinking a bit about a new API that will make layout more a manipulable object than...
@adelavega Correct me if I'm wrong, but the plan moving forward would be to integrate `bids2table` instead?
I think this is a duplicate of https://github.com/nipreps/fmriprep/issues/3195. Would you mind having a look to confirm?
PRs are welcome. I would suggest starting by getting a type checker running and passing in CI, and only after that start adding more than the bare minimum necessary annotations....