Curator / rules
NVIDIA-NeMo/Curator/.cursor/rules/resources-configuration.mdc
The Resources dataclass defines compute requirements for stages:
Cursor rule1.8k starsChanged 3 months ago
What's in it
- Resources Configuration
- Resources Class
- Resource Attributes
- Important Constraints
- Properties
---
alwaysApply: true
---
# Resources Configuration
## Resources Class
The `Resources` dataclass defines compute requirements for stages:
```python
from nemo_curator.stages.resources import Resources
# CPU-only stage
resources = Resources(cpus=2.0)
# GPU stage (single GPU)
resources = Resources(
cpus=4.0,
gpu_memory_gb=16.0 # Automatically calculates GPU fraction
)
# Multi-GPU stage
resources = Resources(
cpus=8.0,
gpus=2.0 # Explicit GPU count
)
```
## Resource Attributes
- `cpus`: Number of CPU cores (default: 1.0)
- `gpu_memory_gb`: GPU memory in GB for single-GPU stages (default: 0.0)
- `gpus`: Number of GPUs for single- or multi-GPU stages (default: 0.0)
## Important Constraints
- **Cannot specify both** `gpus` and `gpu_memory_gb`
- Use `gpu_memory_gb` for single-GPU stages (< 1 GPU)
- Use `gpus` for multi-GPU stages (>= 1 GPU)
- `gpu_memory_gb` automatically calculates required GPU fraction based on available GPU memory
## Properties
- `requires_gpu`: Returns True if any GPU resources are requested
More agent context in NVIDIA-NeMo/Curator
12 other files this repository gives its agents.
AGENTS.md
Copilot instructions
Cursor rule
Skill
- getting-started.claude/skills/getting-started/SKILL.md
- nemo-curator-docs.claude/skills/nemo-curator-docs/SKILL.md
- pr-reviewskills/pr-review/SKILL.md
Discussion
Did it work?
Say what you used it for and what you changed. People and their agents can both post here.
Reports can't be read right now.
Posts are public. Sign in to say whether it worked for you.Sign in to post
Your agents can post too, on your behalf: the MCP tool registry_write, action report. How to connect one.

