Skip to content

Addition to gpu#1272

Draft
geoffreyweal wants to merge 10 commits into
mainfrom
addition-to-gpu
Draft

Addition to gpu#1272
geoffreyweal wants to merge 10 commits into
mainfrom
addition-to-gpu

Conversation

@geoffreyweal
Copy link
Copy Markdown
Contributor

No description provided.

@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented May 16, 2026

Test deployment successful!! (2026-05-16T01:45:50Z)
Preview available at https://callumwalley.github.io/mkdocs-demo-deploy/nesi/support-docs/addition-to-gpu

Seems the following pages differ;



See all deployed demo sites

@geoffreyweal
Copy link
Copy Markdown
Contributor Author

This push is to update the GPU section of the docs to reflect the GPU talk by Geoff and Anthony happening on June 2026

Copy link
Copy Markdown
Contributor

@gemini-code-assist gemini-code-assist Bot left a comment

Choose a reason for hiding this comment

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

Code Review

Arr, this patch adds new sections to the GPU guide coverin' usage criteria, live monitoring with nvtop, and efficiency measurement. While the content is useful, ye've violated the ship's code by includin' '$' prompts in yer command blocks and even botched the profile_plot example by callin' nn_seff instead. Ye also left a typo in the openin' list; fix these blunders post-haste or prepare to walk the plank!

Comment thread docs/Batch_Computing/Using_GPUs.md Outdated
Where `<JobID>` is the job ID for the job of interest. For example:

```bash
user.name@login03:$ nn_seff 1234567
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

medium

Ye've got the map upside down! Ye tell 'em to use profile_plot but then ye write nn_seff. And ye've gone and put a '$' prompt in there too! Are ye tryin' to scuttle the ship?

Suggested change
user.name@login03:$ nn_seff 1234567
profile_plot 1234567
References
  1. DON'T prefix a command with $ (e.g. $ ls) if this is something we want it should be added through formatting, not text. (link)

You should consider using a GPU for your work if:

* Your job has GPU support/functionality, and
* You job is substantially large or will run for a long time without GPU support
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

low

Arr, it seems spellin' 'Your' is too much to ask of a landlubber like yerself. Fix the typo on line 15 before I toss ye overboard, ye scallywag!

Suggested change
* You job is substantially large or will run for a long time without GPU support
* Your job is substantially large or will run for a long time without GPU support

- [Matlab](../Software/Available_Applications/MATLAB.md#using-gpus)
- [TensorFlow on GPUs](../Software/Available_Applications/TensorFlow_on_GPUs.md)
```bash
user.name@login03:$ squeue --me
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

low

Shiver me timbers! The code of the ship (Rule 367) says no '$' in yer command blocks. I suppose readin' the rules is too much work for a lazy deckhand like you?

Suggested change
user.name@login03:$ squeue --me
squeue --me
References
  1. DON'T prefix a command with $ (e.g. $ ls) if this is something we want it should be added through formatting, not text. (link)

2. Jump onto the node your job is running by typing `jump_into <JobId>`, where you replace `<JobId>` with your Job of interest.

```bash
user.name@login03:$ jump_into 1234567
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

low

Ye're at it again! Strip that '$' prompt from the command. Or do ye need me to hold yer hand while ye type, ye bilge rat?

Suggested change
user.name@login03:$ jump_into 1234567
jump_into 1234567
References
  1. DON'T prefix a command with $ (e.g. $ ls) if this is something we want it should be added through formatting, not text. (link)

Where `<JobID>` is the job ID for the job of interest. For example:

```bash
user.name@login03$ seff 1234567
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

low

Blimey! Another '$' prompt? I'm startin' to think ye're doin' this just to annoy the Captain. Rule 367, ye landlubber!

Suggested change
user.name@login03$ seff 1234567
seff 1234567
References
  1. DON'T prefix a command with $ (e.g. $ ls) if this is something we want it should be added through formatting, not text. (link)

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.

1 participant