Skip to content
ValiTracAI

Analyse a mapping dataset.

Upload a logger export and the mapping engine runs the whole deterministic pipeline on it: pre-flight, the temperature-unit gate, the data-quality checks, the statistics, the hot and cold spots, the excursions against your limits, and a draft report. No model writes any of the numbers, and nothing it produces is approved.

Sign in to upload a dataset.

This is the one part of the site that is not open. It accepts a file, hands it to a parser and runs a real analysis, so it requires an account — and mapping data describes a real facility: its layout, its weak corners and when its doors open. That is not something to accept from, or return to, an anonymous caller.

An account is free and takes an email and a password. It used to need a purchase receipt, which meant this page had an audience of nobody; that was a worse answer than a door.

If you are signed in and still see this, the account service could not be reached from this page — the sign-in link above will say so plainly rather than looping you back here.

What runs when you upload

01

Pre-flight and the unit gate

The file is hashed, parsed, and its columns matched by header. The temperature unit has to be stated — by you, by a unit column, or by the temperature column's own header. It is never inferred from the values, so a run with no unit stops here rather than producing numbers in an unknown scale.

02

Data quality before statistics

Missing, invalid, duplicated and non-monotonic timestamps; missing and non-numeric readings; sampling gaps against the modal interval; flatlines and abnormal jumps per sensor; completeness per sensor against expected readings. Each finding is classified CRITICAL, REVIEW_REQUIRED, WARNING or INFO.

03

Statistics, spots and excursions

Min, max, mean, median, standard deviation, range and percentiles per sensor; spatial and temporal variation; the hottest and coldest single readings and the hottest and coldest sensors by mean; and, when you set limits, excursion counts, durations and magnitudes with the duration rule stated.

04

A draft, and a review gate

The output is a fifteen-section draft report that says DRAFT — NOT TECHNICALLY APPROVED on its face, lists the checklist a reviewer works through, and names the gate rules that must hold before an approval can be recorded. The approval is a separate document, so the reviewed bytes stay exactly what was reviewed.

Where this file goes

  • This page is not one of the browser calculators. The file leaves your machine: it is uploaded, analysed on the server and the draft report comes back. The temperature mapping data analyser does a smaller version of the same arithmetic without the file ever leaving the browser — use it if that matters more to you than the full pipeline.
  • The upload is streamed and size-checked as it arrives, refused past 25.0 MB, and staged under a generated name in a temporary directory that does not outlive the request. Your filename is kept only as a label, never used as a path.
  • Only .csv, .xlsx, .xls are accepted, and the extension — not the content type your browser claims — decides which parser runs.
  • 12 uploads per 10 minutes per connection. Re-uploading a corrected export a few times is fine; a script hammering it is not.

What it will not do

  • It will not approve anything. Every run comes back with approved: false and a report that says NOT TECHNICALLY APPROVED on its face. A file arriving over HTTP does not make its analysis any more reviewed than one arriving by email.
  • It will not set your acceptance limits. Leave them blank and the report says excursions were not evaluated. The figures that decide whether a mapping study passes come from your protocol, not from here.
  • It will not write the narrative. The upload runs with interpretation switched off, so no model text is produced at all — section 12 says so explicitly. Every number you see came from the deterministic calculations.
  • It will not guess a unit, a column or a timestamp. Where it is not confident it stops and tells you what was missing, which is the whole reason the pipeline is shaped this way.

Before you upload