← ClaudeAtlas

pyqcm-skilllisted

Assists with pyqcm, the Python/C++ library for quantum cluster methods (CPT, VCA, CDMFT) used to study strongly correlated electron models like the Hubbard model. Use this whenever the user is writing or debugging a pyqcm script (defining clusters, lattice models, operators, parameters, running model_instance calculations), interpreting pyqcm output (spectral functions, Green's functions, self-energy, order parameters, ground state averages, phase diagrams), installing or building pyqcm, or reading/modifying the pyqcm source itself (the src_ed exact-diagonalization solver, the src_qcm lattice/CPT-VCA-CDMFT engine, or the src_python nanobind bindings). Also trigger on mentions of cluster perturbation theory, exact diagonalization impurity solver, Lanczos, Lehmann representation, or the qcm_wed/pyqcm-project repository, even if the user doesn't say "pyqcm" by name.
pyqcm-project/pyqcm-skill · ★ 0 · AI & Automation · score 67
Install: claude install-skill pyqcm-project/pyqcm-skill
# pyqcm Pyqcm implements three related quantum cluster methods, Cluster Perturbation Theory (CPT), the Variational Cluster Approach (VCA), and Cellular/Cluster Dynamical Mean Field Theory (CDMFT), for approximating strongly correlated (Hubbard-like) lattice models. The impurity solver is exact diagonalization (Lanczos and variants) on sparse matrices. Core numerics are C++; the day-to-day interface is Python. ## First: locate the pyqcm source tree This skill ships no pyqcm source. Nearly everything below refers to a **pyqcm checkout**, written `$PYQCM_ROOT`. Resolve it before doing anything else, in this order: 1. `$PYQCM_ROOT`, if the user has it set. 2. Derive it from an installed package: `python3 -c "import pyqcm, pathlib; print(pathlib.Path(pyqcm.__file__).resolve().parent.parent)"`, then **confirm `src_ed/` exists there**. A pip-installed pyqcm ships only the Python package plus the compiled extension, so this check fails for wheel installs and that is the expected outcome, not an error. 3. Ask the user for the path. If no checkout is reachable, say so plainly and carry on: the scripting and physics jobs still work from the reference files alone. Do not hand out paths under `$PYQCM_ROOT` that you have not confirmed exist. The checkout is also the install source. pyqcm on PyPI is **sdist-only**, so every install compiles from source and needs CMake, a C++ compiler, and BLAS regardless of how it is invoked. ## The four jobs Work out which one the user