NVIDIA / NVIDIA/TensorRT-Model-Connect
[Demo] Create the canonical three-step Model Connect demo
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 254
- Forks
- 58
- Avg merge
- 1d 7h
- Merged PRs (30d)
- 235
Description
Summary
Create one polished demonstration that communicates the core TensorRT Model Connect experience:
- Build a supported model.
- Run the generated bundle.
- Produce an observable result.
Tasks
- Select and pin a representative model and checkpoint with reliable setup, build, and runtime behavior.
- Define the supported hardware, operating system, TensorRT Model Connect revision, and dependency versions.
- Keep the primary path to the minimum required commands.
- Show the expected bundle artifact and observable inference output.
- Demonstrate that the deployed native runtime does not require Python or PyTorch.
- Include approximate setup, build, and inference times while identifying them as hardware-dependent.
- Provide copyable commands and troubleshooting guidance for common failures.
- Prepare both a live-demo path and prerecorded fallback assets.
- Validate the complete workflow from a clean environment.
- Add an automated smoke check for the documented command and output contract where practical.
- Link the demo from the repository and documentation.
- Package the material so it can be reused for talks, livestreams, and technical demonstrations.
Acceptance criteria
A new user can reproduce the complete build, bundle, native-run, and observable-output workflow from the published instructions in a clean supported environment.
The same validated material can be delivered live or prerecorded without changing the documented technical path.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by selecting and pinning a representative model, checkpoint, supported environment, and dependency versions, then reduce the workflow to copyable build, bundle, native-run, and observable-output commands. Validate the complete path from a clean environment, including the no-Python/no-PyTorch runtime claim, timing notes, troubleshooting, live and prerecorded delivery, and an automated smoke check where practical.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python, pytorch
- Domain
- documentation, machine-learning
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100