Citation

DispatchAtlas has not published a tagged release or evidence bundle yet. Cite the project with this interim entry and refresh it once release metadata is available.

@software{dispatchatlas_preview,
  title = {DispatchAtlas},
  author = {Gad, Ahmed G.},
  year = {2026},
  url = {https://dispatchatlas.ahmedgad.com},
  note = {Preview software record; replace with release metadata before citation.}
}

📌 When To Cite

Cite DispatchAtlas when your work uses the toolkit itself — the benchmark atlas, the solver registry, the campaign engine, or the analysis exports — or when it references evidence the project has published. A passing mention of the documentation does not need a citation; reuse of instances, solvers, runs, or exported numbers does.

🧾 What To Cite

• The software: use the interim entry above today; replace it with the tagged release entry (version, release date, and archival identifier) once one is published.
• Benchmark sources: instances derived from named standard corpora (OR-Library, Taillard, PSPLIB, and peers listed in the benchmark model) cite their original sources in addition to DispatchAtlas. The corpora are cited and linked only and are never redistributed inside the repository.
• Solver families: every named solver family in the registry carries its canonical reference in metadata — see solver system — so a comparison that features a specific family can cite that family's origin directly.

🔬 Evidence Basis

A citation should match the strength of the evidence behind it. Current exports are smoke-development evidence: they demonstrate the toolkit's interfaces and pipelines, not comparative solver performance. Comparative claims become citable only after campaigns pass the statistical and release gates described in readiness, with the resulting evidence bundles as the citable artifacts.

🗺️ Citation Surfaces