You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The `--serve`*serve* task always lands on a GPU partition (the cluster's `sdg_serve_partition` in `env.toml`, defaulting to `interactive`); the *client* task uses the regular `run_partition` / `batch_partition` of the env profile.
172
172
173
-
### Lustre paths
173
+
### Shared output paths
174
174
175
-
-`seed_path`, `output_dir`, `artifact_path` should all be absolute paths on shared storage (Lustre on dlw). Relative paths resolve to the slurm job's working directory, which is generally not what you want.
175
+
-`seed_path`, `output_dir`, `artifact_path` should all point at durable shared output storage. The examples below use `${NEMO_RUN_DIR:-.}/output/data/sdg/long-document`; set `NEMO_RUN_DIR` to a path visible to the client job and any manually launched model server for your cluster.
176
176
- The serve sentinel lives at `${remote_job_dir}/sdg-deploy/<recipe-name>/<timestamp>/endpoint`.
- Add focused static coverage for the scoped README and OCR config comment.
8
+
9
+
## Boundaries
10
+
11
+
- No production Python, deployment YAML, CLI behavior, generated artifacts, or unrelated docs.
12
+
- No live long-document SDG data prep, `--serve` launch, endpoint calls, downloads, training, eval, W&B, cluster jobs, deploy, artifact transfer, main push, or self-merge.
- Long-document SDG examples should use `${NEMO_RUN_DIR:-.}/output/data/sdg/long-document/...` so docs do not steer users into named-user or cluster-specific storage.
4
+
- The task is documentation/comment/static-test only; manual vLLM and `--serve` examples must remain recognizable and keep the same CLI options.
0 commit comments