메뉴
Use when Julia is missing, wrong-version, uninstantiated, or mirror-misconfigured — symptoms like `julia: command not found`, missing `julia-env/Manifest.toml`, package downloads timing out, fresh cluster account, fresh laptop, package-mirror change, or Julia-version bump.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Use when the user wants a numerical result (ED / DMRG / QMC / VMC / any method) checked against an exact solution, or names a model from the solvable-models catalog in a verification context. Trigger phrases: "verify against the exact solution", "check my DMRG/ED/QMC result", "benchmark <method> on <model>", "is this energy right", "does this match the exact answer", "sanity-check this against Bethe ansatz / Onsager / free-fermion solution". Also fires when the user names any of the 63 catalog models below in a verification context — not only when they use the word "verify": - T1 quadratic/free-particle: tfim-chain (TFIM), xy-chain, kitaev-chain, ssh-chain, kitaev-honeycomb, hofstadter-harper, haldane-chern, anderson-1d, harmonic-chain - T2 2D classical/transfer matrix: ising-2d-onsager (Onsager / 2D Ising), ising-triangular, dimer-kasteleyn, six-vertex, eight-vertex, hard-hexagons - T3 Bethe ansatz/Yang–Baxter: xxz-chain, heisenberg-xxx, hubbard-1d-lieb-wu (Lieb–Wu / 1D Hubbard), lieb-liniger, yang
Use when an exact diagonalization track, ED reproduction, full spectrum, symmetry sector, scar, ETH, level statistics, quench dynamics, finite-temperature ED (FTLM/TPQ), spectral function, interior-spectrum / MBL eigenstates, or finite-cluster oracle needs method-level route and tool selection.
Use when the user names or describes a harness-tracked quantum lattice model. Match user prose to one of: - transverse-field-ising (TFIM): quantum-critical Ising chain / 2D Wilson-Fisher - heisenberg: SU(2) magnet, AFM or FM by sign of J - xxz-chain: spin-1/2 XXZ, Bethe-ansatz integrable, Δ tunes FM / Luttinger / Néel - j1-j2: frustrated Heisenberg, J2/J1≈0.5 spin-liquid candidate - shastry-sutherland: orthogonal-dimer AFM, exact dimer phase, magnetization plateaus - spin-1-xxz: Haldane phase, single-ion anisotropy - aklt: spin-1 bilinear-biquadratic, exact VBS ground state - kitaev-honeycomb: bond-dependent exchange, exactly solvable Z2 spin liquid, anyons - spin-ice-pyrochlore: 2-in-2-out ice rule, Coulomb phase, magnetic monopoles - mbl-disordered-heisenberg: random-field XXZ chain, ETH-to-MBL transition - rydberg-pxp: blockaded Rydberg chain, quantum many-body scars, |Z2⟩ revivals - dissipative-spin-lindblad: open spin lattice, Liouvillian spectrum, steady states - potts-clock: q-state, first-order / cont
Use when the user wants to reproduce a paper's figure or main result. Triggers include "reproduce paper X", "redo the figures of Y", "reproduce arXiv <id>", "put this paper through the harness as a calibration target", "walk me through reproducing this paper", "beginner reproduction", "I don't know what size to choose", "explain while reproducing", or right after `/download-ref` lands a new paper.
Use when choosing or running QuSpin as the Python fallback for exact diagonalization, constrained-basis ED, spin-chain ED examples, or QuSpin setup failures.
Use when choosing or running XDiag.jl for exact diagonalization, symmetry-resolved sectors, Lanczos/Krylov calculations, or XDiag setup failures.
| name | setup-julia |
| user-invocable | false |
| description | Use when Julia is missing, wrong-version, uninstantiated, or mirror-misconfigured — symptoms like `julia: command not found`, missing `julia-env/Manifest.toml`, package downloads timing out, fresh cluster account, fresh laptop, package-mirror change, or Julia-version bump. |
Install and configure Julia for the harness — install via juliaup, configure the package mirror (defaults to Chinese mirror if region == mainland_china in the cluster profile), and instantiate the project env (julia-env/). Generic over target (local or remote ssh alias). Idempotent — re-running is safe and quick.
Idempotence is enforced, not aspirational:
- (a) Probe MUST succeed before any install attempt — step 3 short-circuits when `julia` is already at the requested version. - (b) Mirror config replaces (NEVER appends) the `JULIA_PKG_SERVER` line in `startup.jl` and the matching lines in shell rc files. - (c) `Pkg.instantiate()` is safe to re-run; subsequent runs no-op on already-resolved manifests. - (d) `verify` MUST pass on the no-op path (re-running the whole workflow on an already-set-up host exits 0 without modifying anything).This skill is for Julia-specific configuration. Cluster-side conventions (ssh, scheduler, partitions) live in skills/using-slurm/profiles/<active>.toml and are read here for region defaults and (when target is remote) the ssh alias and repo_path_remote.
Julia package stacks are declared separately in skills/<stack>/stack.toml.
This skill only makes Julia itself and julia-env/ usable locally or remotely;
after that, the selected stack's install command (for example make install itensors,
make install sse, or make install pepskit) installs method packages.
julia not installed.--version 1.11.x)./using-slurm's pre-submit check sees julia-env/Manifest.toml not yet instantiated on the cluster.| flag | type | default | source-of-default |
|---|---|---|---|
--target | local | remote:<alias> | local | CLI; for remote, <alias> matches skills/using-slurm/profiles/<active>.toml's connection.ssh.alias field; the skill reads repo_path_remote for where the project lives. |
--region | name | from cluster profile's region field | See Mirror reference. |
--mirror | URL | unset | Advanced override for JULIA_PKG_SERVER. |
--version | X.Y.Z | release | release | juliaup's stable channel. When release, the project's julia_version is also consulted. |
--instantiate / --no-instantiate | flag | --instantiate | Runs Pkg.instantiate() after install. |
Recognized regions for --region (see Mirror reference for the contract):
| region | JULIAUP_SERVER | JULIA_PKG_SERVER | source |
|---|---|---|---|
mainland_china | https://mirror.nju.edu.cn/julia-releases/ | https://mirrors.nju.edu.cn/julia | Jinguo guide (Nanjing University mirror) |
| other / unset | unset | unset | Julia defaults (no mirror config) |
This skill follows the Jinguo-group recipe verbatim (https://book.jinguo-group.science/stable/chap2/julia-setup/). Mirror first, then install — juliaup itself respects JULIAUP_SERVER if exported before the curl installer runs.
Probe target: detect if julia is reachable (PATH, module load, or ~/.juliaup/bin/julia). For remote: ssh <alias> 'command -v julia || command -v juliaup'. Also read the manifest's julia_version to verify version compatibility against any pre-existing Julia.
Configure mirror first (only if --region resolves to a mirror): scripts/setup-julia.sh mirror --region <name>. This step runs BEFORE installing Julia even though the Jinguo guide numbers it "Step 2" — the mirror env var MUST be exported before the curl installer fetches juliaup. See Mirror reference for region defaults and URLs.
The script writes BOTH JULIAUP_SERVER and JULIA_PKG_SERVER env vars to every shell rc the script detects (any of ~/.bashrc, ~/.zshrc, ~/.profile); idempotently replaces any prior JULIAUP_SERVER= / JULIA_PKG_SERVER= line. Login-shell user ($SHELL) is ALSO written to ~/.profile to cover non-interactive ssh. AND writes JULIA_PKG_SERVER to ~/.julia/config/startup.jl for julia subprocesses.
Precedence note: shell-rc env var beats startup.jl for julia subprocesses launched in interactive shells; startup.jl beats nothing for julia subprocesses launched without env (e.g., julia invoked from a Slurm script). Both are rewritten on every mirror invocation so they cannot drift.
Install Julia. Skip if step 1's probe found a working julia whose julia --version matches --version (or matches the project's julia_version when --version release). Otherwise: scripts/setup-julia.sh install [--region <name>] [--version X.Y.Z].
The skill verifies AFTER the script returns — all binary, ALL MUST pass:
- (a) `julia --version` reports the requested version (or matches the project's `julia_version` when `--version release`). - (b) `~/.julia/config/startup.jl` contains the `JULIA_PKG_SERVER` mirror line (when a mirror region was set). - (c) `julia -e 'using Revise'` exits 0.Instantiate. Local: scripts/setup-julia.sh instantiate <project_dir> (runs Pkg.instantiate(); Pkg.precompile() inside <project_dir>). Remote: same via ssh <alias> 'cd <repo_path_remote> && scripts/setup-julia.sh instantiate julia-env'.
Verify: scripts/setup-julia.sh verify <project_dir> <package_name> — three binary items, ALL MUST exit 0:
Hand back: Julia version, mirror url, project env state. Hand-back report per AGENTS.md → Output norms.
$PATH; ~/.julia/config/startup.jl configured; julia-env/ instantiated and precompiled.<alias>:<repo_path_remote>.Callers (who calls /setup-julia):
/onboard — if the user signals they will write Julia code (e.g., DMRG / ITensors workflows)./using-slurm — pre-submit when the remote cluster's julia-env/Manifest.toml hasn't been instantiated yet.make install julia and make install itensors recipes (the makefile recipes can dispatch the skill via ${CLAUDE_SKILL_DIR}/setup-julia/... once registered).Downstream (what runs after /setup-julia):
language = "julia" stack contract in skills/<stack>/stack.toml — /setup-julia precedes the stack's install command.Data dependencies (what /setup-julia reads):
skills/using-slurm/profiles/<active>.toml — for the region default mirror and (for remote) the ssh alias and repo_path_remote.Single source of truth for region → mirror mapping and mirror-config semantics. The Inputs table, step 2, and Anti-patterns all link here.
For users in mainland China, package downloads from pkg.julialang.org are typically slow or unreliable. The Jinguo-group setup guide (https://book.jinguo-group.science/stable/chap2/julia-setup/) configures two mirror env vars, both pointing at Nanjing University:
export JULIAUP_SERVER=https://mirror.nju.edu.cn/julia-releases/ # for the juliaup binary download
export JULIA_PKG_SERVER=https://mirrors.nju.edu.cn/julia # for Pkg downloads
JULIAUP_SERVER matters for the initial Julia install — without it, juliaup downloads from AWS S3 (slow from mainland China). JULIA_PKG_SERVER matters for every subsequent Pkg.add / Pkg.instantiate. The mirror MUST be set before invoking the curl installer; this skill orders step 2 before step 3 when --region mainland_china.
This skill applies the NJU mirror automatically when the cluster profile's region field is mainland_china. For other regions, no mirror is set. For an institutional mirror, pass --mirror <url> to override JULIA_PKG_SERVER.
julia-env/Project.toml is committed (the dependency contract); julia-env/Manifest.toml is gitignored and regenerated per machine on first Pkg.resolve() + Pkg.instantiate().julia_version and don't port across Julia major versions, so committing one would break cross-machine setup.module load julia/1.10.9) and juliaup-installed Julia are supported. Default: juliaup — user-controlled Julia version makes Project.toml compatibility easier across laptop + cluster + collaborators. Use module-loaded Julia ONLY when the admin enforces it or the cluster blocks user binaries./onboard's cluster-setup stage and the cluster profile's bootstrap_one_time.