From 74e2cfe134140677039dd23f0847f62ad1883fcc Mon Sep 17 00:00:00 2001 From: Robert Young Date: Tue, 28 Jul 2026 13:46:07 -0400 Subject: [PATCH 1/4] fixed admonitions --- docs/hpc/05_submitting_jobs/01_slurm_submitting_jobs.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/hpc/05_submitting_jobs/01_slurm_submitting_jobs.md b/docs/hpc/05_submitting_jobs/01_slurm_submitting_jobs.md index ece0048730..a212c61ba6 100644 --- a/docs/hpc/05_submitting_jobs/01_slurm_submitting_jobs.md +++ b/docs/hpc/05_submitting_jobs/01_slurm_submitting_jobs.md @@ -49,7 +49,7 @@ You can find the available types of GPUs at [Torch Spec Sheet](../10_spec_sheet. `SLURM` partitions on Torch control stakeholder resource access. No physical nodes are tied to partitions — instead, equivalent compute resources are allocated via partition `QoS`([QualityOfService](https://slurm.schedmd.com/qos.html)). -:::tip Partitions +:::tip[Partitions] Do not specify partitions manually, except for preemption which is described later. ::: @@ -67,7 +67,7 @@ Non-stakeholders to temporarily use stakeholder resources (a stakeholder group t ## Job Submission on Torch As stated in the tutorial, be sure to only request the compute resources (e.g., GPUs, CPUs, memory) needed for the job. Requesting too many resources can prevent your job from being scheduled within an adequate time. The `SLURM` scheduler will automatically dispatch jobs to all accessible GPU partitions that match resource requests. -:::danger Low GPU Utilization Policy +:::danger[Low GPU Utilization Policy] Jobs with low GPU utilization will be automatically canceled: | Node Pattern | Cancellation Criteria | Warning Criteria | | :----------- | :-------------------: | :--------------: | @@ -84,7 +84,7 @@ Enforcement will be very aggressive. ## Preemptible Jobs on Torch On Torch, users may run "preemptible" jobs on stakeholder resources that their group does not own. This allows the stakeholder resources to be utilized by non-stakeholders which may otherwise be idle. To make the best use of these resources, you are encouraged to adopt checkpoint/restart to allow for resumption of the workload in subsequent jobs. -:::warning Preemption Policy +:::warning[Preemption Policy] Jobs become eligible for preemption after 30 minutes of runtime. Jobs will not be canceled within the first 30 minutes. ::: From 54e62e6eb75af1b4a18507b1843199914697b532 Mon Sep 17 00:00:00 2001 From: Robert Young Date: Tue, 28 Jul 2026 14:22:10 -0400 Subject: [PATCH 2/4] attempt to fix and get around linter --- docs/hpc/05_submitting_jobs/01_slurm_submitting_jobs.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/hpc/05_submitting_jobs/01_slurm_submitting_jobs.md b/docs/hpc/05_submitting_jobs/01_slurm_submitting_jobs.md index a212c61ba6..a2c84e17ff 100644 --- a/docs/hpc/05_submitting_jobs/01_slurm_submitting_jobs.md +++ b/docs/hpc/05_submitting_jobs/01_slurm_submitting_jobs.md @@ -49,7 +49,7 @@ You can find the available types of GPUs at [Torch Spec Sheet](../10_spec_sheet. `SLURM` partitions on Torch control stakeholder resource access. No physical nodes are tied to partitions — instead, equivalent compute resources are allocated via partition `QoS`([QualityOfService](https://slurm.schedmd.com/qos.html)). -:::tip[Partitions] +:::tip Partitions Do not specify partitions manually, except for preemption which is described later. ::: @@ -67,7 +67,7 @@ Non-stakeholders to temporarily use stakeholder resources (a stakeholder group t ## Job Submission on Torch As stated in the tutorial, be sure to only request the compute resources (e.g., GPUs, CPUs, memory) needed for the job. Requesting too many resources can prevent your job from being scheduled within an adequate time. The `SLURM` scheduler will automatically dispatch jobs to all accessible GPU partitions that match resource requests. -:::danger[Low GPU Utilization Policy] +:::danger Low GPU Utilization Policy Jobs with low GPU utilization will be automatically canceled: | Node Pattern | Cancellation Criteria | Warning Criteria | | :----------- | :-------------------: | :--------------: | @@ -84,7 +84,7 @@ Enforcement will be very aggressive. ## Preemptible Jobs on Torch On Torch, users may run "preemptible" jobs on stakeholder resources that their group does not own. This allows the stakeholder resources to be utilized by non-stakeholders which may otherwise be idle. To make the best use of these resources, you are encouraged to adopt checkpoint/restart to allow for resumption of the workload in subsequent jobs. -:::warning[Preemption Policy] +:::warning Preemption Policy Jobs become eligible for preemption after 30 minutes of runtime. Jobs will not be canceled within the first 30 minutes. ::: From 6ff022784c5a82ac392dcea3236b0f313730f335 Mon Sep 17 00:00:00 2001 From: Robert Young Date: Tue, 28 Jul 2026 14:32:56 -0400 Subject: [PATCH 3/4] fixed admonitions and not triggering false positive from linter --- docs/hpc/05_submitting_jobs/01_slurm_submitting_jobs.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/hpc/05_submitting_jobs/01_slurm_submitting_jobs.md b/docs/hpc/05_submitting_jobs/01_slurm_submitting_jobs.md index a2c84e17ff..c0f19e14c6 100644 --- a/docs/hpc/05_submitting_jobs/01_slurm_submitting_jobs.md +++ b/docs/hpc/05_submitting_jobs/01_slurm_submitting_jobs.md @@ -49,7 +49,7 @@ You can find the available types of GPUs at [Torch Spec Sheet](../10_spec_sheet. `SLURM` partitions on Torch control stakeholder resource access. No physical nodes are tied to partitions — instead, equivalent compute resources are allocated via partition `QoS`([QualityOfService](https://slurm.schedmd.com/qos.html)). -:::tip Partitions +:::tip{title="Partitions"} Do not specify partitions manually, except for preemption which is described later. ::: @@ -67,7 +67,7 @@ Non-stakeholders to temporarily use stakeholder resources (a stakeholder group t ## Job Submission on Torch As stated in the tutorial, be sure to only request the compute resources (e.g., GPUs, CPUs, memory) needed for the job. Requesting too many resources can prevent your job from being scheduled within an adequate time. The `SLURM` scheduler will automatically dispatch jobs to all accessible GPU partitions that match resource requests. -:::danger Low GPU Utilization Policy +:::danger{title="Low GPU Utilization Policy"} Jobs with low GPU utilization will be automatically canceled: | Node Pattern | Cancellation Criteria | Warning Criteria | | :----------- | :-------------------: | :--------------: | @@ -84,7 +84,7 @@ Enforcement will be very aggressive. ## Preemptible Jobs on Torch On Torch, users may run "preemptible" jobs on stakeholder resources that their group does not own. This allows the stakeholder resources to be utilized by non-stakeholders which may otherwise be idle. To make the best use of these resources, you are encouraged to adopt checkpoint/restart to allow for resumption of the workload in subsequent jobs. -:::warning Preemption Policy +:::warning{title="Preemption Policy"} Jobs become eligible for preemption after 30 minutes of runtime. Jobs will not be canceled within the first 30 minutes. ::: From 55b72e22afdf835615a473feaf6bb6ff320d1fed Mon Sep 17 00:00:00 2001 From: Robert Young Date: Tue, 28 Jul 2026 14:42:23 -0400 Subject: [PATCH 4/4] added fix to package.json instead of changing doc --- .../05_submitting_jobs/01_slurm_submitting_jobs.md | 6 +++--- package.json | 13 +++++++++++++ 2 files changed, 16 insertions(+), 3 deletions(-) diff --git a/docs/hpc/05_submitting_jobs/01_slurm_submitting_jobs.md b/docs/hpc/05_submitting_jobs/01_slurm_submitting_jobs.md index c0f19e14c6..a212c61ba6 100644 --- a/docs/hpc/05_submitting_jobs/01_slurm_submitting_jobs.md +++ b/docs/hpc/05_submitting_jobs/01_slurm_submitting_jobs.md @@ -49,7 +49,7 @@ You can find the available types of GPUs at [Torch Spec Sheet](../10_spec_sheet. `SLURM` partitions on Torch control stakeholder resource access. No physical nodes are tied to partitions — instead, equivalent compute resources are allocated via partition `QoS`([QualityOfService](https://slurm.schedmd.com/qos.html)). -:::tip{title="Partitions"} +:::tip[Partitions] Do not specify partitions manually, except for preemption which is described later. ::: @@ -67,7 +67,7 @@ Non-stakeholders to temporarily use stakeholder resources (a stakeholder group t ## Job Submission on Torch As stated in the tutorial, be sure to only request the compute resources (e.g., GPUs, CPUs, memory) needed for the job. Requesting too many resources can prevent your job from being scheduled within an adequate time. The `SLURM` scheduler will automatically dispatch jobs to all accessible GPU partitions that match resource requests. -:::danger{title="Low GPU Utilization Policy"} +:::danger[Low GPU Utilization Policy] Jobs with low GPU utilization will be automatically canceled: | Node Pattern | Cancellation Criteria | Warning Criteria | | :----------- | :-------------------: | :--------------: | @@ -84,7 +84,7 @@ Enforcement will be very aggressive. ## Preemptible Jobs on Torch On Torch, users may run "preemptible" jobs on stakeholder resources that their group does not own. This allows the stakeholder resources to be utilized by non-stakeholders which may otherwise be idle. To make the best use of these resources, you are encouraged to adopt checkpoint/restart to allow for resumption of the workload in subsequent jobs. -:::warning{title="Preemption Policy"} +:::warning[Preemption Policy] Jobs become eligible for preemption after 30 minutes of runtime. Jobs will not be canceled within the first 30 minutes. ::: diff --git a/package.json b/package.json index 4e55f35cb8..ce4ef6f272 100644 --- a/package.json +++ b/package.json @@ -73,5 +73,18 @@ "last 3 firefox version", "last 5 safari version" ] + }, + "remarkConfig": { + "plugins": [ + "remark-lint", + [ + "remark-lint-no-undefined-references", + { + "allow": [ + "/^:::/" + ] + } + ] + ] } }