Credibility

Validation & Limitations

VEHRON becomes more trustworthy when the website states scope calmly and directly. This page explains what is verified in software, what is reproducible today, and what users should not infer from the existence of repository scaffolding or low-order public models.

What is verified in software

  • Documented BEV simulation path
  • CLI-driven runnable public workflows
  • Deterministic packaged outputs for repeatable case review

What is reproducible today

  • Vehicle and testcase YAML driven studies
  • Optional drive-cycle CSV based route inputs
  • Case packages containing outputs and configuration snapshots

What should not be overclaimed

  • Broad physical validation across many real vehicles and climates
  • High-fidelity thermal resolution
  • Broad public multi-powertrain maturity

Battery limitations

  • Public battery models are low-order electrical reference models
  • The site should not imply built-in electrochemical solver fidelity
  • External model slots exist for teams with deeper local models

Thermal limitations

  • Thermal behavior is trend-level / low-order in the public path
  • The site should not claim high-fidelity thermal networks or CFD-level detail
  • Use the public path for engineering trend studies, not precision thermal certification claims

Scope limitations

  • VEHRON is not currently a broad public multi-powertrain platform
  • Visible non-BEV scaffolding should not be presented as equal maturity
  • Current route support does not imply a full GPS/lat-lon replay framework