Evidence¶
Every number in the atlas comes from somewhere. Studies are short reports of one piece of work each; they produce parameters (the numbers, each with its status and spread) and support observations (general facts about the data). Studies are grouped by method, the way they get at the answer, and share techniques.
| Studies | 69 | One piece of work that produced insight: a mini report. |
| Observations | 54 | A general fact about the dataset's timing or recording, with its evidence and what it means. |
| Parameters | 49 | One number the atlas relies on, with its uncertainty and where it came from. |
| Methods | 9 | A methodology group: studies that get at timing the same way. |
| Techniques | 12 | A reusable building block that studies share. |
Methods¶
| Method | Studies | What it does |
|---|---|---|
| Reading the stamps | 11 | Fit drift and corrections from the record time stamps themselves, against the number of samples each record holds. |
| One event, two clocks | 12 | Find an event that two independently clocked signals both record, and read the offset between their clocks from where each puts it. |
| Clocks carried in the signal | 9 | Use a regular rhythm inside the recorded signal (a pacemaker, a monitor's frame clock, an output or mains line) as a third clock, independent of the clocks being tested. |
| Does the waveform run on? | 4 | Test whether a waveform continues smoothly across a boundary (a record junction, a reset, a gap) to tell lost samples from lost time, and to find samples written out of order. |
| Data continuity | 4 | How completely each signal was recorded: where its gaps are, how long its unbroken stretches run, how it was packaged into messages, and whether a break in the stamps lost data or only moved the clock. |
| Delays and averaging windows | 10 | Work out how long after the event a value is stamped, and what span of signal it summarises, by recomputing monitor numbers from the waveforms they come from. |
| Clinical and laboratory times | 13 | Find out what a time in the clinical and lab tables marks (an event, its documentation, a rounding), using signatures the event leaves in the signals. |
| Reading the source | 5 | Read firmware, manuals and loader code to explain a timing behaviour seen in the data, or to predict one to test. |
| Rounding, heaping and value resolution | 27 | How far a recorded number is from the true one because of how it was written down: the resolution it was recorded at, and the coarser values people round to. |
How sure¶
Observations: 39 established, 7 likely, 7 open, 1 withdrawn. Parameters: 42 measured, 5 assumed, 1 estimated, 1 derived.