This page is for version 0.7.1.
For other versions, use one of these documentation indexes:
- Latest (default): https://docs.nvidia.com/nemo-helix/latest/llms.txt
- 0.8.0: https://docs.nvidia.com/nemo-helix/v0.8.0/llms.txt
- 0.7.1: https://docs.nvidia.com/nemo-helix/v0.7.1/llms.txt
- 0.7.0: https://docs.nvidia.com/nemo-helix/v0.7.0/llms.txt
- 0.6.0: https://docs.nvidia.com/nemo-helix/v0.6.0/llms.txt
- 0.5.1: https://docs.nvidia.com/nemo-helix/v0.5.1/llms.txt
- 0.5.0: https://docs.nvidia.com/nemo-helix/v0.5.0/llms.txt
- 0.4.0: https://docs.nvidia.com/nemo-helix/v0.4.0/llms.txt
- 0.3.0: https://docs.nvidia.com/nemo-helix/v0.3.0/llms.txt
- 0.2.0: https://docs.nvidia.com/nemo-helix/v0.2.0/llms.txt
Many CLI options and API parameters accept entity references—a consistent string format for referring to entities (and optionally a sub-resource) across the platform.
Examples
default/my-fileset — Fileset named my-fileset in workspace default.my-fileset — Same entity when your current context already specifies the workspace.prod/my-fileset#data/training.parquet — A specific path inside that fileset (when the entity type supports fragments).
Can use the full form workspace/entity_name to keep the reference unambiguous regardless of context.
