From 46963968921b8a2b36ce70edd3306f2009a1aad2 Mon Sep 17 00:00:00 2001 From: ritchie <4462072+repentsinner@users.noreply.github.com> Date: Wed, 12 Aug 2026 06:31:35 -0700 Subject: [PATCH] docs: state what the package does, not where it came from MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The README claimed bmd-signal-gen "consumes it back over SDI". The dependency runs the other way: bmd-signal-gen declares display-patterns[charts,io]>=0.2.0 and imports it. SDI is what bmd-signal-gen emits to a display, not how it consumes this library. Drops the extraction provenance from the README and describes the consumer relationship plainly. REQUIREMENTS and SPEC keep theirs — the split is a recorded design decision there, not a history lesson. --- README.md | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/README.md b/README.md index e39321f..71aed60 100644 --- a/README.md +++ b/README.md @@ -15,9 +15,10 @@ array namespace (numpy or torch), so it serves CLI signal generators and GPU-resident render graphs alike. Chart authoring and TIFF export install as extras. -Extracted from +Used by [bmd-signal-gen](https://github.com/OpenDisplayEval/bmd-signal-gen), -which consumes it back over SDI. Sibling consumers and context: +which sends the rendered patterns to a display over SDI or HDMI. +Related: [color-wrangler](https://github.com/Fuse-Technical-Group/color-wrangler) (LED-surface characterization umbrella) and its component repos. @@ -81,7 +82,7 @@ write_chart_tiff("my_chart.tiff", image, layout) `render_counter_panel`, `decode_counter`). The root is the canonical import surface; no dependency beyond numpy — torch renders through the `xp` parameter without ever being required. -- `display_patterns.image_generators` — extraction-era class surface +- `display_patterns.image_generators` — legacy class surface (`PatternGenerator`), kept for existing consumers; delegates to the catalog. - `display_patterns.charts` — chart types, colorimetric conversion, and