Add some HiP-CT docs

[dstansby]

This adds some docs on the HiP-CT data, including registrations, as requested by @kabilar. cc @ucbpclw

[kabilar]

Perhaps we should use the acq entity for the resolution. The chunk entity could be used for different fields of view in the same sample. If the same field of view is acquired multiple times then perhaps the ses entity should be used.

[dstansby]

That sounds good - we could do acq-overview and acq-zoom for the low/high resolution scans. I don't think we have the same field of view multiple times, and if we do it won't be exactly the same scan/field of view so I don't think we need to use ses.

I'll take a look into renaming our datasets to use acq.

[kabilar]

Thanks @dstansby. Sounds great.

So for example the file sub-I58_sample-blockIC2_chunk-201_PC.ome.zarr would be renamed to sub-I58_sample-blockIC2_acq-zoom_chunk-01_PC.ome.zarr and sub-I58_sample-blockIC2_chunk-401_PC.ome.zarr would be renamed to sub-I58_sample-blockIC2_acq-zoom_chunk-02_PC.ome.zarr?

Since you are renaming files should we change the modality suffix? If I am not mistaken, I believe that PC is now going to be XPCT.

[dstansby]

I think the new datasets would be called:

sub-I58_sample-blockIC2_acq-zoom_chunk-01_PC.ome.zarr
sub-I58_sample-blockIC2_acq-overview_PC.ome.zarr

For the overviews, we only have one per sample, so I think we don't want to use chunk for these datasets? If we end up more than one overview per sample (e.g., taken at different times or with different resolutions) we could then make the acq label more specific for each dataset (e.g., acq-overview2025 in the hypothetical instance that we do another one next year)

[kabilar]

Thank you @dstansby. This is great. I have a few suggestions above.