QVAC-23811 doc: add VisionPsy Nano and image_no_upscale to multimodal page - #3959
Merged
Conversation
- Add VisionPsy Nano (base and Flash) as a recommended VLM pair in the
Models section of ai-capabilities/multimodal.mdx, alongside the
existing Qwen2.5-Omni / Qwen3-VL and SmolVLM2 entries. SmolVLM2 stays
listed to remain consistent with the embedded example, which still
uses it.
- Add a "VisionPsy Nano: base vs. Flash" subsection documenting that
the two variants share the same mmproj and are selected at load time
via modelConfig.image_no_upscale ('off' = base, 'on' = Flash).
- Keep the same level of detail as the rest of the page: no per-field
reference for other modelConfig options, no sizing or usage guidance
beyond what is strictly needed to distinguish the two variants.
Contributor
Review StatusCurrent Status: ✅ APPROVED |
Contributor
License compliance — cleanNo new dependency license findings in this PR. Warn-only (shadow) mode — this check does not block merges yet. Updated automatically by the canonical license compliance workflow. NOTICE presence (advisory)Missing NOTICE (advisory, does not block):
|
iancris
reviewed
Aug 20, 2026
Address PR #3959 review feedback (@yingying0906, @iancris): - Name the exact weights + mmproj constants for each VisionPsy variant under "Recommended pairs", and flag the counterintuitive naming (un-suffixed constants are Flash; `_1`-suffixed constants are base). - Correct the "base vs. Flash" subsection: base and Flash are separate weights + `mmproj` pairs (not a shared mmproj); the variant is chosen by loading the matching pair, and `image_no_upscale` is the preprocessing-rule flag that must match the loaded pair — the two mmprojs' identical metadata cannot express this on its own. - Drop the misleading `'off' (default)` / `'on'` list. The field is optional; unset defers to the mmproj's own value. New guidance: leave unset for base, set `image_no_upscale: 'on'` for Flash. - Add an explicit warning that a mismatch between the loaded pair and the flag passes load validation (both mmprojs declare the same `preproc_image_size`) but silently uses the wrong preprocessing rule and degrades quality. - Scope `image_no_upscale` to the idefics3-style preprocessor and to a `mmproj` that declares `clip.vision.preproc_image_size`. Note that on the other recommended pairs the flag either warns and is ignored (Qwen2.5-Omni / Qwen3-VL) or is accepted but inert (SmolVLM2) — so in practice a VisionPsy-only key.
iancris
previously approved these changes
Aug 20, 2026
Co-authored-by: Law Po Ying <30721578+yingying0906@users.noreply.github.com>
iancris
approved these changes
Aug 20, 2026
iancris
approved these changes
Aug 20, 2026
yingying0906
approved these changes
Aug 20, 2026
gianni-cor
approved these changes
Aug 20, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What problem does this PR solve?
ai-capabilities/multimodalpage recommends SmolVLM2 and Qwen as the multimodal LLM pair but does not mention the new VisionPsy Nano VLM or itsimage_no_upscaleload option, which is required to distinguish the base variant from Flash (both share the samemmprojhparams).How does it solve it?
VisionPsy Nano (base or Flash) + mmproj-*as a recommended pair alongsideQwen2.5-Omni / Qwen3-VLandSmolVLM2. SmolVLM2 stays listed so the recommended pairs remain consistent with the embedded example, which still uses it.mmprojand are selected atloadModel()time viamodelConfig.image_no_upscale('off'= base,'on'= Flash).modelConfigoptions; only what is needed to distinguish the two variants. A broader "load options" reference is out of scope for this task and will land once the AI-capabilities pages get a standardized structure.