video_write_gif — VIDEOCUBE `export` op

• Data kinds: rgbvideo → text

• Call: import fullseye as fs; fs.ledger.video_write_gif(frames, path: 'str', fps: 'float' = 10.0) -> 'str' (to call the implementation directly, import videocube; videocube.video_write_gif(frames, path: 'str', fps: 'float' = 10.0) -> 'str'; from the registry, opsvideocube.get("video_write_gif"))

Usage

Writes a frame sequence to an animated GIF (text = the path written). A reusable exit point.

frames is a grey video (T, H, W) or a colour rgbvideo (F, H, W, 3). float maps [0, 1] to 0..255; integers go to uint8 as they are (out-of-range values are clipped). All frames are saved (Pillow folds a picture identical to the previous one into 1 frame and reduces the count, so the all-frames saving path of video.write_video is used, and after writing the frame count is read back to verify). Without Pillow, ImportError (optional dependency). path must end with .gif.

>>> video_write_gif(video_cube_orbit(clip, n_frames=24), "out/cube.gif", fps=12)

'out/cube.gif'

Detailed usage guide

• videocube family guide

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)

• poc_video_cube — py -3.11 examples/poc_video_cube.py

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

—

Same category (`export`)

—

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

video_write_gif — VIDEOCUBE export op