Files
Claude ed1797eb8c Document the megapixel presets, warnings, bounds and upgrade path
The README had been patched incrementally from 5 model families to 30 and
had accumulated gaps where behaviour was only discoverable by reading the
source or the changelog.

- Document the mp_size preset table. The labels are approximations of
  common standard resolution areas, and two are notably off: "0.5" is
  really 0.56 MP (768x768) and "2.5" is 2.25 MP (1536x1536). That mapping
  had never been written down anywhere.

- Add a warnings reference. The node emits four distinct warnings, each
  meaning the result differs from what was asked for, and none of them
  were documented. Message text is quoted from the source.

- Replace the inputs list with a table carrying the actual widget ranges,
  which were previously undocumented (mp_size_float is 0.01-16.0, not the
  0.01-4.0 it started as; max_tile_size is 256-8192; length is 1-4096).

- Document the 16384 resolution ceiling and the alignment floor in
  Features, not just in the 1.5.1 changelog entry.

- Add an "Upgrading from 1.2.x" section. The four user-visible behaviour
  changes were scattered across three changelog entries; anyone upgrading
  had to reconstruct them.

- Rework the workflow example: the old one predated video support and the
  width/height outputs. Adds a video variant showing length, and states
  the concrete numbers each example produces.

- Document how to add a model family and how releases work, including the
  align-must-divide-vae_scale invariant and the reference-vs-override
  split in the test suite.

- Update the allocation bullet, which still claimed only device matching
  after 1.5.1 added the dtype split.

- Give __init__.py a docstring explaining why the mappings are
  re-exported rather than redefined - a second copy of the dicts is
  exactly how the display names silently broke before 1.3.0.

Every number in the new examples is verified against the code rather than
asserted: FLUX 16:9 at 1MP is 1344x768 with 1344x768 tiles in a 2x2 grid,
and WAN at length 81 gives 21 latent frames.

Docs only - no code behaviour change, and pyproject.toml is untouched so
this does not trigger a publish. The registry page will keep showing the
1.5.1 README until the next version bump.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01KbDZTWCvSqbXEX3GHJkSXw
2026-07-30 11:35:31 +00:00

13 lines
538 B
Python

"""Bobs Latent Optimizer - ComfyUI custom node package entry point.
ComfyUI imports this package and reads NODE_CLASS_MAPPINGS and
NODE_DISPLAY_NAME_MAPPINGS from it. Both are re-exported from the
implementation module rather than redefined here: the two dicts are matched by
key, so keeping a second copy in this file is how the display names silently
stopped applying before 1.3.0.
"""
from .Bobs_Latent_Optimizer import NODE_CLASS_MAPPINGS, NODE_DISPLAY_NAME_MAPPINGS
__all__ = ["NODE_CLASS_MAPPINGS", "NODE_DISPLAY_NAME_MAPPINGS"]