Skip to content

Conversation

@kevinstratford
Copy link
Contributor

We probably need to confirm the text of the acknowledgment with a higher power.

consumes CPUhs from your budget. You can find out more about coreh and
how to track your usage in the [resource management section](../resource_management/)
Cirrus is a CPU-only system and usage of the queue system (SLURM) is
accounted for in "CPUh" (aka "core hours"). For example, a job requesting
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This should be "coreh", not "CPUh" to match the label in SAFE

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

replaced

how to track your usage in the [resource management section](../resource_management/)
Cirrus is a CPU-only system and usage of the queue system (SLURM) is
accounted for in "CPUh" (aka "core hours"). For example, a job requesting
one node exclusively for one hour will be charged 288 CPUh (288 core hours)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

coreh

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

replaced


The SLURM workload manager provides access to a total of 256 back end or
compute nodes. All compute nodes have two 144-core AMD 9825 processors (a
total of 288 physical codes per node). There are 192 standard compute
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Typo "codes" -> "cores"

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

corrected

@aturner-epcc
Copy link
Contributor

Thanks @kevinstratford. I cannot see the changes in the PR, can you update the PR and then I can merge this?

Copy link
Contributor

@aturner-epcc aturner-epcc left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @kevinstratford I'll merge this now

@aturner-epcc aturner-epcc merged commit a3b74fe into EPCCed:cirrus2025 Nov 20, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants