Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Introduce consistent and intuitive parameter naming for NeMo TensorRTLLM class vs TensorRT-LLM library, and across all export and deploy options

Open
#412 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
python
Domain
tooling

Research direction

No files or tests are named. Start by inventorying parameter names in the NeMo TensorRTLLM class, its TensorRT-LLM integration, and each export and deploy option. Define a consistent naming scheme, then verify that the affected interfaces use it consistently across all options.

Written by the indexing model from the issue text.

Description

enhancement

Is your feature request related to a problem? Please describe.
We have many export and deploy options and the parameter naming can be inconsistent. We should standardize it as much as possible.

Dominant language
Python
Stars
43
Forks
18
Avg merge
7h 17m
Merged PRs (30d)
3

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from NVIDIA-NeMo/Export-Deploy

All issues in NVIDIA-NeMo/Export-Deploy

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.