cross-method-check

Validate quantum simulation results against independent computational methods at identical parameter points.

60|92|Updated Apr 30, 2026
One-click install
npx skills add https://github.com/QuantumBFS/quantum.harness --skill cross-method-check
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cross-method-check
Source: https://github.com/QuantumBFS/quantum.harness/tree/main/skills/cross-method-check
Command: npx skills add https://github.com/QuantumBFS/quantum.harness --skill cross-method-check

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This skill addresses the risk of numerical artifacts or setup errors in quantum simulations by providing a structured framework to verify results against an independent computational method.

Core Features & Use Cases

  • Independent Verification: Automatically cross-references primary simulation results with secondary methods like TEBD or alternative geometries to ensure physical accuracy.
  • Rigorous Error Analysis: Enforces strict comparison against accuracy budgets, preventing the acceptance of biased or unconverged data.
  • Use Case: When a DMRG simulation result is near a phase boundary, use this skill to run a TEBD imaginary-time evolution to confirm that the observed physics is not an artifact of bond-dimension truncation.

Quick Start

Use the cross-method-check skill to verify the current ground state calculation against an independent method defined in the model card.

Frequently Asked Questions about cross-method-check

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I verify quantum simulation results against an independent method?

To verify quantum simulation results, execute an independent computational method at identical parameter points to cross-reference observables and confirm physical accuracy. This structured framework prevents the acceptance of biased or unconverged data from numerical artifacts.

When do I need cross-method verification for DMRG calculations?

You need cross-method verification for DMRG calculations when results are near a phase boundary or at risk of bond-dimension truncation artifacts. Running an independent TEBD imaginary-time evolution confirms the observed physics without relying on a single setup.

What is an accuracy budget comparison in quantum reproducibility?

An accuracy budget comparison in quantum reproducibility enforces strict numerical thresholds when matching observables across independent methods. It systematically reports failure modes to ensure cross-method agreement meets scientific standards before accepting the data.

Can I use TEBD imaginary-time evolution to confirm DMRG phase boundary data?

Yes, you can use TEBD imaginary-time evolution to confirm DMRG phase boundary data by running both methods at identical parameter points. This independent verification checks that the observed physics is not an artifact of truncation.

What is the best way to check for numerical artifacts in quantum physics simulations?

The best way to check for numerical artifacts in quantum physics simulations is cross-referencing primary results with secondary methods like TEBD or alternative geometries. This enforces rigorous error analysis against strict accuracy budgets to guarantee reproducibility.

Why does cross-method agreement matter for phase boundary analysis?

Cross-method agreement matters for phase boundary analysis because it validates diagnostic robustness against setup errors and numerical truncation. Confirming observables across independent computational methods ensures the observed physics is genuinely reproducible.