Skip to content

Move PyHPC profiling notebooks after notebook 02#226

Open
robobryce wants to merge 1 commit into
NVIDIA:event/2026-07-cscs-summer-schoolfrom
robobryce:reorder/pyhpc-kernels-after-02
Open

Move PyHPC profiling notebooks after notebook 02#226
robobryce wants to merge 1 commit into
NVIDIA:event/2026-07-cscs-summer-schoolfrom
robobryce:reorder/pyhpc-kernels-after-02

Conversation

@robobryce

Copy link
Copy Markdown

Summary

Move the three profiling/kernel notebooks immediately after notebook 02 and renumber the remaining PyHPC ladder:

  • 10–1203–05: CuPy asynchrony, copy kernel authoring, histogram kernel authoring
  • old 0306: mpi4py
  • old 04–0907–12: SWE ladder
  • 13: unchanged

Rename all corresponding solution notebooks and update the README, syllabus, notebook cross-references, test order, dependency comments, ignored-artifact comments, and CSCS profiling filter.

Validation

  • validated all 26 notebook files with nbformat
  • verified the top-level notebook sequence is exactly 00 through 13
  • verified every syllabus exercise/solution link resolves and its row number matches its filename
  • verified the test ladder matches the filesystem order
  • verified all numbered notebook filename references resolve
  • confirmed no old renamed basename remains in the repository
  • git diff --check

@copy-pr-bot

copy-pr-bot Bot commented Jul 24, 2026

Copy link
Copy Markdown

This pull request requires additional validation before any workflows can run on NVIDIA's runners.

Pull request vetters can view their responsibilities here.

Contributors can view more details about this message here.

@github-actions

Copy link
Copy Markdown
Contributor

👋 Thank you for your contribution!

This pull request is from a forked repository so GitHub Actions will not be able to run CI. A maintainer will review your changes shortly and manually trigger the CI.

@maintainers Please review this PR when you have a chance and follow the instructions in the CONTRIBUTING.md file to trigger the CI.

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