Reading Planning Reports | A.T.O.M Documentation

Markdown and printable HTML use the same report model, quantities, interpretation and conditional sections. Start with Decision summary: it identifies the Scenario, saved Version or unsaved plan, source Runs, selected Cells, primary result and evaluation completeness. A score can exist after Evaluate Network without an optimization search. Standalone interference and the optimizer's radio-quality objective have separate status entries.

Find the evidence in the report

Continue through the report in this order:

Planning map & Cells ties stable numbered callouts to full Cell IDs and configured or recommended azimuths. Leader lines point to the true locations of co-located Cells. The schematic map shows at most 300 RF segments, sampled across Cells, with bounds from the full retained geometry. Sampling never changes KPIs. Its caption identifies the simulation source and warns when a locally reranked recommendation differs from that simulation. Markdown omits the SVG; a review package links its actual sibling map and HTML files.
Network evaluation explains quantities, denominators, the evaluation domain and configured priorities. A compatible recorded baseline enables before/after comparison; an evaluated configuration alone does not create one. Pareto alternatives and marginal Cell effects appear only when retained.
RF configuration & receiver assumptions records common fields once. A reference profile names how many Cells match it and lists lossless per-Cell deviations. Missing historical inputs say Not recorded instead of inheriting current defaults.
Dataset, model & provenance identifies the source computation separately from the application and report generator used for this export. Dataset-wide counts and pack QA describe the pack, not the selected network domain or physical accuracy.
Engineering appendix holds metric definitions, full source IDs, fingerprints, dataset hashes, receiver/model contracts and retained supporting evidence. Hashes establish identity or byte integrity, not physical validation.

Read quantities and missing analyses

Read the units before comparing figures:

Report quantity	Meaning
Optimization score, `/100`	Normalized preference-weighted planning utility under the current priorities. It is not coverage percentage, probability, measured accuracy or confidence. Unavailable objectives are excluded from scoring.
Modeled demand weight served	Served weight divided by relevant weight. For example, six demand building entities can carry a total weight of 260; neither quantity is a population estimate.
Residential building entities served	Positive-residential building entities served out of the relevant entities whose footprints intersect the selected-Cell radius union. It is not residents or dwellings.
Normalized propagation reach	A ray-distance score, with up to 100 units per configured ray and distance normalization capped at the lesser of radius and 500 m. It is not meters or area coverage.
Served building entities	Building entities with best modeled building Rx strictly above the recorded building-service threshold; multipart footprint records can be separate entities.
Multi-Cell overlap	Share of served building entities served by multiple Cells. It does not establish interference performance.
Ray-endpoint Rx and obstruction	Terminal-ray diagnostics. Rays terminate at receiver sensitivity or the planning radius; low endpoint Rx and high building service can coexist because building service uses a different population and threshold. Network means retain the existing mean of per-Cell summaries.

The interpretation uses recorded values and availability, without adding a grade. Rounded 100.0% is described as all only when the recorded numerator equals the positive denominator. Not evaluated, Not retained, Not recorded and Unavailable identify different evidence boundaries; none is a zero result. In 6G research mode, unsupported interference remains unavailable. Optimizer radio quality uses its fixed sampled domain, including no-carrier samples as denominator failures; standalone interference has its own sampled and signal-only denominators.

Print to PDF

For PDF export, use A4 portrait, default scale and the report's CSS margins, and turn browser headers and footers off. Current Chromium is the reference print path: it supports the report's running identity, generation time and Page X of Y. Other browsers or user print overrides may paginate differently or omit margin-box chrome. The in-app export/reopen path waits for document fonts and images before opening print; the self-contained HTML button invokes the browser's print command directly. The report remains selectable text; browser output is not a claim of PDF/UA conformance.

File identity and regeneration

New report downloads share a name such as ankara-plan-network-plan-2-v3-20261019-083612z-network-evaluation-report.html, with matching Markdown/map stems and UTC time. All displayed generation dates use YYYY-MM-DD HH:mm UTC; legacy timestamps without a recorded zone remain unknown. Regeneration uses the current report generator, while downloading an already retained artifact preserves its original bytes, filename, timestamp and hash. A Review package collects existing saved-Version evidence locally and does not run RF or rebuild missing results.

In Review → Report, read Report source before generating anything. A saved Version identifies immutable inputs within a Scenario; a Run identifies an execution against its recorded dataset/model. Current unsaved plan is not tied to a saved Version. A historical Report describes the evidence retained when it was generated, not the currently edited plan, and Runs: None must not be filled by inference. Use Open source Version when available to inspect its inputs; opening a source does not perform RF computation.

The decision summary's completeness entries distinguish an evaluated network from an optimized recommendation. A standalone interference analysis can be Not evaluated even when an optimization score exists; the optimizer's optional radio-quality objective is separate. Missing map geometry is Not retained, missing old inputs are Not recorded, and unavailable/unsupported analyses are not zero-valued results. Never use a Pareto alternative's ray map as fresh simulation evidence merely because that alternative is selected for inspection.

Download the right evidence

Choose Markdown to generate, retain and download a Markdown Report for the current source. It is readable offline and omits inline SVG maps; it is not an editable project.
Choose PDF / Print to generate retained HTML and open the browser print surface. Saving a PDF is a browser print action, not a separate stored PDF artifact. Allow the local report popup when prompted.
In Reports, Download Report downloads the retained HTML or Markdown bytes in their recorded format without running RF or opening the print surface. Open a downloaded HTML file in a browser to read it offline or use its print control. Regenerate as a new Report uses the current generator and creates a new artifact; it does not overwrite historical bytes or run new RF to reconstruct missing evidence.
For a saved Version, Review package downloads a local ZIP with HTML and Markdown reports, a project file, map and manifest. It refuses an unsaved draft until a Version is saved. Check the file hashes against the manifest after transfer; matching hashes establish byte integrity, not authorship, signing or physical RF accuracy.
Export the project separately from the project menu when the reviewer needs editable retained inputs/Scenario evidence. See the portable-project format and worked comparison before assuming an export contains a particular result.

What survives where

Evidence	Retention and transfer boundary
Working draft	Inputs autosave in this browser; a draft does not retain a complete live execution or all map layers.
Scenario/Version and retained Scenario artifacts	Portable project export carries bounded retained evidence and remaps imported local IDs with provenance. The five most recently used Scenarios retain complete map layers; older ones can need an explicit rerun.
Separate Run History	Its own browser-local database; it is not exported as the complete Run History database in a project file. Embedded Run metadata in a retained Scenario does not change this boundary.
Generated Reports	Separate artifact storage. Download the desired bytes or a review package outside browser storage; project export does not include the generated Report store.
Coverage surfaces and view/Undo state	Not a portable project backup. A transient surface may need regeneration from compatible retained inputs.

Browser site-data deletion, quota failures or explicit deletion can remove local evidence. A .atom-project.json file is not a full-browser archive. Existing encoded/decoded size and complexity limits still apply: if an export/import is refused, current evidence remains in this browser; download a readable Report and follow the recovery guidance, rather than assuming a partial project was saved.