QuantumForge 1.1
Open-source, laptop-first computational physics with explicit scientific provenance.
QuantumForge helps students and researchers move from a structure or model to a reproducible calculation plan, local teaching simulation, optional research-backend execution, auditable result record, and benchmark comparison.
QuantumForge does not turn every input into a trustworthy prediction automatically. It makes assumptions, limitations, review gates, convergence evidence, and result origin visible.
What is stable in 1.1
- Fourteen built-in teaching and reduced-model solvers.
- CIF, POSCAR, VASP, XYZ, and optional ASE structure parsing.
- Universal
qforge study material.cifplanning. - Material Builder, DFT Studio, Monte Carlo Lab, and results UI.
- Explicit result classes: teaching, backend, calibrated, reference, pilot, and validated.
- Atomic run records with SHA-256 manifests.
- SQLite project, review, and durable workflow databases.
- Restartable local dependency-ordered workflows for built-in methods.
- Frozen validation specifications for H2O, Si, Fe, SrTiO3, and MnAs.
- Reproducible MnAs paper-study workflow with benchmark table, raw data, figures, and explicit claim boundaries.
- Environment diagnostics and backend capability preflight.
Installation
Core terminal toolkit
python -m venv .venv
# Linux/macOS
source .venv/bin/activate
# Windows PowerShell
# .\.venv\Scripts\Activate.ps1
python -m pip install --upgrade pip
python -m pip install quantumforge-laptop
qforge doctor
Web Studio and structure tools
python -m pip install "quantumforge-laptop[web,atoms]"
qforge-ui
From this repository
python -m pip install -e ".[dev,web,atoms]"
python -m pytest
qforge demo-ui
Periodic GPAW calculations are optional. On Windows, use a validated WSL2/Ubuntu environment for production GPAW work.
Quick start
Run a built-in model:
qforge run tight_binding_ssh
Inspect a structure and generate a review-gated plan:
qforge study examples/materials/SrTiO3.cif --goal full
Create a project and register runs:
qforge project-init SrTiO3 --root .
qforge run tight_binding_ssh --project-root .
qforge project-list --root .
Submit and run a durable workflow:
qforge workflow-submit examples/workflow_teaching.yml
qforge workflow-list
qforge workflow-run <WORKFLOW_ID>
qforge workflow-show <WORKFLOW_ID>
Verify a saved run:
qforge verify-run runs/<RUN_ID>
qforge env-export -o quantumforge-environment.json
Run the MnAs student paper-reproduction case study:
qforge benchmark-mnas-case-study --profile standard --seed 43
List the scientific validation registry:
qforge benchmarks-list
qforge benchmark-describe srtio3
Scientific result labels
| Label | Meaning |
|---|---|
teaching_model |
Transparent educational or reduced-model computation |
backend_calculation |
Result produced by a named external scientific backend |
calibrated_model |
Model contains fitted or literature-calibrated parameters |
literature_reference |
Value copied or digitized from a publication |
experimental_reference |
Measured reference value |
unconverged_pilot |
Executed calculation that has not passed convergence gates |
validated_result |
Converged result that passed the declared validation contract |
Publication-ready status additionally requires resolved review gates and explicit human approval where needed.
Durable workflows
QuantumForge 1.0 runs local workflows in the foreground but commits task state to SQLite before and after each task. This gives deterministic interruption, inspection, cancellation between tasks, and retry/resume behavior without pretending to be a cluster scheduler.
External backend tasks are blocked unless the required capability passes preflight. The executor never silently substitutes a teaching model for a missing DFT backend.
Supported scope
Native Windows: UI, structure tools, study planning, teaching models, Monte Carlo, run verification.
Linux / WSL2: primary target for GPAW periodic DFT.
Optional backends: GPAW/ASE, PySCF, AkaiKKR, and TRIQS. Availability does not imply scientific readiness; qforge doctor checks usable capabilities.
Public development
- Read CONTRIBUTING.md before opening a pull request.
- Scientific-output changes must include benchmark evidence and explicit result classification.
- Report security issues according to SECURITY.md.
- Governance is described in GOVERNANCE.md.
- The stable public API is described in docs/PUBLIC_API.md.
Citation
Use the metadata in CITATION.cff. Archive releases should receive a DOI before publication claims are made.
License
QuantumForge is released under the GNU General Public License v3.0 or later. Optional scientific backends retain their own licenses and are not bundled unless explicitly stated.
Independent project name
QuantumForge Laptop is an independent computational-physics project and is not affiliated with other software projects using the QuantumForge name. The Python distribution name is quantumforge-laptop and the command-line entry point is qforge.
Metadata
Release files for quantumforge-laptop 1.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| quantumforge_laptop-1.1.0.tar.gz | 3.5 MB | With provenance | Details for quantumforge_laptop-1.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| quantumforge_laptop-1.1.0-py3-none-any.whl | Python 3 | none | any | Details for quantumforge_laptop-1.1.0-py3-none-any.whl |
Total release size: 4.7 MB
Release files / quantumforge_laptop-1.1.0.tar.gz
| Download URL | quantumforge_laptop-1.1.0.tar.gz |
|---|---|
| Size | 3.5 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
f33569af64acab693324af7562964f913a4acb43e03db7c888f905c94df91fd3
|
|
BLAKE2b-256 checksum How to use checksums |
63910f6175c26b8a30a216cfcaca0b58df2b85491c6aac2c1ce912bc5ec928ef
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jul 12, 2026.
Transparency logRelease files / quantumforge_laptop-1.1.0-py3-none-any.whl
| Download URL | quantumforge_laptop-1.1.0-py3-none-any.whl |
|---|---|
| Size | 1.2 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
97cecab08c1bebfca36be7e97c17fd6073e4081e3aa561adf905dbb14351a35f
|
|
BLAKE2b-256 checksum How to use checksums |
4119c668a4a08a359bf7dde51921caf664712ee6d5b5ce0dc8539b75724e0c07
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jul 12, 2026.
Transparency logSecurity for quantumforge-laptop 1.1.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for quantumforge_laptop-1.1.0.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jul 12, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.