broken parmetis link fix

[lepotatoguy]

Previous link of Parmetis 4.0.2 is invalid/broken. I have updated it with the latest working link of Parmetis v4.0.2.

[showrav-ansary]

+1

[rupertnash]

Thanks for the help.

[rupertnash]

I see that this is a known problem due to the Karypis group moving their website to Github
KarypisLab/ParMETIS#27

The replacement URL should be https://karypis.github.io/glaros/files/sw/parmetis/parmetis-4.0.2.tar.gz rather than the CP2K website

Thanks for this.

[lepotatoguy]

I see that this is a known problem due to the Karypis group moving their website to Github KarypisLab/ParMETIS#27

The replacement URL should be https://karypis.github.io/glaros/files/sw/parmetis/parmetis-4.0.2.tar.gz rather than the CP2K website

Thanks for this.

Updated the link. Thank you.

[rupertnash]

Can you please rebase and squash the commits into 2 or 3? Thanks!

[lepotatoguy]

Can you please rebase and squash the commits into 2 or 3? Thanks!

Yes. Done from my side. Thank you.

Update:
I noticed that the numpy version comment was still missing and the hemelb-spec-2024-12-06.txt file you requested to remove was still present.
I have corrected both issues — the comment has been added back and the file has been removed.
The commits have been updated accordingly. It should be ready for review now.

[lepotatoguy]

I have pushed the commit ff6f3ae, where you updated GH action version, in my fork.

[rupertnash]

Hi - thanks for spotting this and making the change. There are a whole load of minor edits to things that I can't accept (e.g the reflowing of large bits of the docs). I have cherry picked to main the change at the crux of this PR. If you wish to do a documentation tidy that would be gratefully accepted but needs to not make large amounts on unneeded and undesired changes. Thanks

[lepotatoguy]

Hi - thanks for spotting this and making the change. There are a whole load of minor edits to things that I can't accept (e.g the reflowing of large bits of the docs). I have cherry picked to main the change at the crux of this PR. If you wish to do a documentation tidy that would be gratefully accepted but needs to not make large amounts on unneeded and undesired changes. Thanks

@rupertnash Thank you for your earlier feedback.

I’ve submitted a new PR with only minimal and relevant documentation updates, available here: #824. It only changes to essential clarifications, structural fixes, and new machine-specific content.

Please let me know if any revisions are needed.

Thanks!