Repository navigation
docs(reasoner): clarify raw vLLM video sampling - #337
sylvesterkaczmarek wants to merge 1 commit into
Conversation
14418a1 to
eb7efb8
Compare
|
Refreshed this docs PR onto current main today. It is now 0 commits behind and mergeable, and the diff remains limited to the intended documentation file. This has been quiet for over two weeks. Could a maintainer please review/merge it, or let me know if any wording change is needed? |
Refreshed onto current upstream. Signed-off-by: Sylvester Kaczmarek <16242628+sylvesterkaczmarek@users.noreply.github.com>
eb7efb8 to
5e00193
Compare
|
Following up on the raw-vLLM sampling documentation. Could a maintainer review the request example and approve the waiting workflow? |
|
Thanks for this, @sylvesterkaczmarek. The Cosmos cookbooks and evaluation suites have moved to NVIDIA/cosmos-framework under The raw The relative paths are unchanged, just under |
Summary
extra_bodyform and equivalent raw/v1/chat/completionsJSONfpsanddo_sample_framesbelong insidemm_processor_kwargs, not as standalone top-level chat-completion fieldsWhy
Issue #190 reports weak physical-plausibility classification while sending
fpsanddo_sample_framesas top-level fields in a rawrequestspayload. The current Reasoner prompt guide documents video sampling throughextra_body={"mm_processor_kwargs": ...}for the OpenAI client, but the vLLM quickstart does not show the equivalent raw JSON shape.That distinction matters for motion-dependent tasks such as physical plausibility analysis because frame sampling determines which temporal events are presented to the Reasoner. This change makes the raw HTTP configuration explicit next to the vLLM quickstart.
Validation
Documentation-only change. Cross-checked against the current Reasoner prompt guide's
mm_processor_kwargssampling configuration and the request shown in #190.Addresses #190