ome_tiff_write — FILEIO `ome_tiff` op

• Data kinds: any → any

• Call: import fullseye as fs; fs.ledger.ome_tiff_write(stack, *, meta) (to call the implementation directly, import fileio; fileio.ome_tiff_write(stack, *, meta); from the registry, opsfileio.get("ome_tiff_write"))

• GPU: none (CPU reference implementation only)

Usage

Write a TCZYX multidimensional array with physical sizes and channel names as OME-TIFF bytes.

> The detailed description below is the original text — the summary and the headings are translated.

meta['axes'] は TCZYX の部分列で YX 終端。X/Y(および Z 軸があれば Z)の physical_size_* と *_unit、C 軸があれば channel_names を必須とする。書いた axes は名前空間つきの MapAnnotation に残し、長さ 1 の軸も ome_tiff_read で戻る。

呼び出し例: ome_tiff_write(stack, meta={"axes": "CZYX", ...})。

References (sample data, literature)

• Sample-data catalog (download URLs / licences) — 2-D uses skimage.data (BSD/public domain) plus synthetic images; 3-D lists download URLs for real data sources (Stanford, PDS, …).

• Operator provenance and references — the sources of the research/methods this op family came from.

• The canonical algorithm (author, year) and its uses are named in the family usage guide above.

Runnable examples (verified samples that actually call this op)

• fileio_scientific_roundtrip — py -3.11 examples/fileio_scientific_roundtrip.py

Ops the type connects to (they accept `any` as input)

table_write_csv · table_read_csv · mesh_write_ply · mesh_read_ply · mesh_write_stl · mesh_read_stl · mesh_write_obj · mesh_read_obj

Same category (`ome_tiff`)

ome_tiff_read

*Provenance: fileio.py — FILEIO operator registry. This per-op note is generated by tools/opdocs.py md (do not hand-edit).*

ome_tiff_write — FILEIO ome_tiff op