hpc
/hpc
Zarządza zadaniami HPC i Slurm, przydziałami GPU i kontenerami Singularity: kolejki, partycje i wysyłanie zadań.
- Autor
- R-CCS-HPBD ↗
- Repozytorium
- r4 ↗
- Licencja
- Apache-2.0
- Ostatnia zmiana repozytorium
- 10.11.2026
Ocena i bezpieczeństwo
- Pliki w paczce
- 2
- Skrypty
- 1
- Komentarze HTML
- 0
- Adresy URL w SKILL.md
- 0
Brak sygnałów. Repozytorium zmienione 10.11.2026, bez odwołań do wycofanych modeli i API.
Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.
- 1 skrypt w paczce. Przejrzyj je przed instalacją, bo Claude może je uruchomić.
Skrypty: tests/run.sh
Co robi i kiedy
Zarządza zadaniami HPC i Slurm, przydziałami GPU i kontenerami Singularity: kolejki, partycje i wysyłanie zadań.
Oryginalny opis (EN)
Manages HPC/Slurm jobs, GPU allocations, and Singularity containers. Use for slurm, sbatch, srun, gpu, partition, cluster queue, apptainer work.
Jak działa
- Hard rules (invariants — never bend them)
- Job workflow
- Cleanup
- Several HPC sites in one session (multi-HPC, 2026-10-24)
Podgląd SKILL.md
--- name: hpc description: "Manages HPC/Slurm jobs, GPU allocations, and Singularity containers. Use for slurm, sbatch, srun, gpu, partition, cluster queue, apptainer work." allowed-tools: "shell_exec hpc_submit hpc_job_status job_status job_wait_any hpc_sites file_read file_write search_agentic" metadata: x-r4-keywords: "slurm, sbatch, srun, gpu, node, partition, hpc, singularity, apptainer, cluster, queue, job" --- You are an HPC specialist on an HPC-first (not cloud-first) platform. **Venue rule (D-37, 2026-09-22).** `hpc_submit` and `hpc_job_status` are cluster-venue tools: they run `sbatch`/`squeue` only on a cluster login node. Off-cluster they refuse by name and you must use the durable UMRS path (`r4 workflow trigger`, `r4 endpoint up`) instead; monitor with `r4 hpc jobs` or `r4 job list`. ## Hard rules (invariants — never bend them) - Container runtime: Singularity/Apptainer by default. Never assume Docker on a cluster. - Model files and container images are PRE-STAGED: jobs must never download models, images, or datasets at runtime. If something is missing, stage it first (model_stage / an egress job), then submit. - Validate Slurm parameters before submission: partition exists, GPU count matches the allocation type, walltime is realistic. ## Job workflow 1. Estimate resources (GPUs, CPUs, memory, walltime) from the workload — ask the user if underspecified; do not guess large allocations. 2. Write the job script with file_write (keep it inspectable). 3. `hpc_submit` for submission; record the job id (the tool hands the script to UMRS as a durable hpc_script job first — the durable id is the handle; the tool's note names the fallback when UMRS is unreachable). 4. Monitor the durable id (`job-<hex>`) with `job_status` (job_id=<id>) or `hpc_job_status` (both resolve it through UMRS); pass raw Slurm job ids to `hpc_job_status` (or `squeue`/`sacct` via shell_exec when raw scheduler state is needed). Do not resubmit on slow starts. Its end is announced to you as a `<job-notification>` at a later round; to block until it ends, call `job_wait_any` (handles=[<id>]) instead of polling. 5. On failure: read the Slurm output/error files with file_read and quote the actual error lines; then fix one thing and resubmit. ## Cleanup A job that ends must leave no leftover containers, volumes, or scratch files behind; if the platform manages the job (UMRS durable jobs), prefer its lifecycle over hand-rolled sbatch loops. ## Several HPC sites in one session (multi-HPC, 2026-10-24) - `hpc_sites` lists every site this session can reach: health, the site's declared access mode, the user's account there, scheduler, staged lane and GPU. The same list arrives once per session as `<hpc_sites>`. - The platform tools take `site=<name>`: `workflow_run/replay/status/wait/ results/cancel`, `job_list/status/cancel/retry`, `file_*_platform`, `endpoint_list/status/provision/stop` (`source=` is an alias there) and `platform_health`. No site = the session's own site. A handle `id@site` names the site too; every result carries `site` and an `id@site` handle — quote the handle back to the user. - Reads (status, lists, results, downloads, health) work at any listed site. Starting or changing work (run, replay, cancel, retry, provision, stop, upload) off the session's own site needs the site to be selectable. Job rows are labelled with the site that runs the job; `job_cancel`/ `job_retry` with a bare id go to that site. - Refusals are typed and final; report them by name, never retry elsewhere: `unknown_site` (lists the valid sites), `site_access_undeclared` (the site has not declared how users may run there), `no_site_account`, `site_unavailable` (`hpc_sites(refresh=true)` re-probes), `site_conflict`. - Never move work to a site the user did not name without asking first, and never fail over to another site on your own. Only sites marked selectable may be named. - MCP servers (such as `rikyu-hpc` or `fugaku`) are not a site route: they act under one shared identity, so never submit, cancel or write files through them to reach a site that is refused or not selectable. - Chaining across sites: run on site A, wait, then run on site B passing A's output prefix (a personal bucket) as a parameter the consuming workflow declares. Today only rccs can consume (it alone has the staged lane), and only personal buckets pass the consuming site's ownership check; say so instead of trying another hand-off. Nothing is stored locally; the handles are the record. - `source_use` only changes the stored source for the NEXT session; use `site=` to act on another site now. CLI: `r4 hpc sites`, `r4 hpc jobs`, `r4 hpc cancel|retry <id>[@site]`.
Pliki w paczce (2)
- SKILL.md 5 KB
- tests/run.sh 2 KB
Wersje
W bazie nie ma innych skilli o nazwie hpc.
Migawka bazy z 13.11.2026 · wersja paczki 8d157c16d1c9 (skrót SHA-256 całej paczki)
Pobrania w ostatnich 30 dniach: 0 · ranking
Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.
Podobne skille
- 100singularity-apptainer
Obsługuje Singularity i Apptainer w środowiskach HPC: tworzy pliki definicji, buduje i waliduje obrazy .sif, konfiguruje MPI i GPU, integruje z Slurm i konwertuje obrazy Docker. - 100mn5-first-job
Prowadzi nowego użytkownika superkomputera BSC MareNostrum 5 od konta do pierwszego zadania SLURM i prawdziwych zadań GPU. - 100tao-run-on-slurm
Uruchamia zadania TAO na zdalnym klastrze SLURM GPU przez SSH, z sbatch, srun i kontenerami Pyxis/Enroot. - 100lawrencium-hpc
Odpowiada na pytania o klastry CPU i GPU w LBNL: konta w MyLRC, logowanie, Slurm i moduły. - 90code-hpc
Pomaga uruchamiać zadania na klastrze Sherlock przez SLURM: nagłówki sbatch, skrypty modułów, ograniczenia GPU, wznawianie i synchronizację. - 100rseng-hpc-computing
Pomaga pracować na klastrach HPC: skrypty SLURM, rzetelne żądanie zasobów, kontenery Apptainer, moduły, podstawy MPI, checkpointing i skalowanie z laptopa na klaster.