Talon Chandler

@ziw-liu and I just met to discuss our plan for `imread`, especially wrt #90. Should `imread` provide a universal entry point that returns different objects depending on the underlying file?...

My understanding of the consensus we reached today is that multi-position datasets are fundamentally different from single-position datasets (at least in the eyes of the ome-zarr spec), so these two...

> read_collection returns a 6 dimensional array, even if you pass it a path to a single fov. I think "6-dimensional array" was the wrong word choice...what I had in...

I really like the signature you're proposing @ziw-liu: ``` BaseFOV.frame_camera_timestamp(T: int, C: int, Z: int) -> datetime.datetime: ``` Building on this, maybe the **per-frame metadata** can be accessible via: ```...

@mattersoflight, @edyoshikun, and I just discussed this issue offline, and we agreed that scale information for the P, T, Z, Y, and X dimensions would be extremely valuable for iohub....

I think encoding in a coordinate translation would be excellent.

I agree that modifying scale, channel names, and contrast limits are good candidates for CLI shortcuts in `iohub`.

Thanks @ziw-liu! I'll suggest a uniform affiliation to `CZ Biohub SF` instead of the current non-uniform `Chan Zuckerberg Biohub San Francisco` and `CZ Biohub`. Otherwise, LGTM!

@ieivanov @ziw-liu this is ready for review and testing. The latest version renames wells in place without copying, updating the metadata appropriately. It adds new rows/columns and deletes empty rows/columns...

Nice bug find and fix! I like it in its own file, but do you want it in `iohub/cli/rename_wells.py` instead of `iohub/rename_wells.py`? I'm flexible. Ready to merge from my perspective.