NVIDIA-NeMo / NVIDIA-NeMo/Export-Deploy
Introduce consistent and intuitive parameter naming for NeMo TensorRTLLM class vs TensorRT-LLM library, and across all export and deploy options
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Python
- Stars
- 42
- Forks
- 18
- Avg merge
- 1d 2h
- Merged PRs (30d)
- 8
Description
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.
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
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.
Assessment
- Tech stack
- python
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100