Document naming of pre-processed PS-OCT data

[kabilar]

Based on a discussion with @calvinchai today, we have decided to rename the pre-processed PS-OCT data:

Original name

• mosaic_003_image_0001_processed_cropped_focus.nii

BIDS compliant name

• derivatives/sub-I80/micr/sub-I80_voi-slab1_sample-slice{slice_num:03d}_chunk-{tile_id:04d}_acq-{acq}_proc-spectraltocomplex_OCT.nii
• BIDS recommends that the sample is unique throughout the dataset
• acq is either normal or tilted
• We settled on spectraltocomplex for the proc label for now.

cc @satra @ayendiki @balbasty

[balbasty]

Sounds good! I didn't know voi was a valid tag, is it a recent addition?

[ayendiki]

I don't remember seeing it before, either, so it could be. Because "sample" was already there, it's not entirely clear to me how "voi" is meant to be different. At first I thought maybe VOI is an area inside a bigger object and a sample is an area extracted from a bigger object, but that's not what the spec suggests.

Definition: The voi- entity can be used to distinguish acquisitions localized to different regions. The label SHOULD be the name of the body region or part scanned. If used, the fields "BodyPart" and "BodyPartDetails" MUST be defined in the JSON file. BodyPartDetailsOntology is OPTIONAL to also include.

[kabilar]

The current definition of VOI doesn't exactly describe what we are representing. Perhaps I need to submit a pull request adding our use case to the definition.

[kabilar]

Looks like VOI was added in August 2024, so relatively recently.