Readings
What the phenomenon may have been is not part of what was seen: it is a claim about it, written in the same file, stood in the scene and tested against the account. Somebody else's reading is another observation.
Every excerpt below is read-only, and each knows the format: put the caret inside an object and press Ctrl+Space (⌥+I on a Mac) to list every key that could go there, with what the model says of each.
What it was: readings
A recording states angles, and a body in metres is never part of what was seen. It is a
claim about it, and it is tested by standing it in the scene and looking at it from where
the witness stood: it casts its shadow, the ground can hide it, and its outline is measured
against what the witness said at every instant. A reading is shown alone, as the
world it claims; asked to compare (the ◌ button, or compare-account on
<rr0-sighting>), the player draws everything the witness saw beside it as
dashed outlines and lists how far off the direction is and how many times wider and taller
each body looks, in red when a witness could not have been that far off.
The witness's own reading goes in the recording, as interpretation. Someone else's reading is not part of the account: it is another sighting, listed in the case (see below). A account whose witness said what
it was is drawn in the round, as they said; one that says nothing in metres is drawn as the
angles it states. The player offers it and each analyst's reading, one at a time.
{
"interpretation": {
"title": "A craft standing on its legs",
"bodies": [{
"id": "craft",
"explains": ["ufo-1"],
"model": { "id": "ellipsoid" },
"track": [
{ "t": 52000, "eastM": -571.6, "northM": -965.5, "onGround": true,
"sizeM": { "widthM": 3.36, "lengthM": 3.36, "heightM": 1.73 },
"appearance": { "color": "#e8e6df", "albedo": 0.7 } },
{ "t": 83000, "azimuthDeg": 195.9, "altitudeDeg": 4.1, "distanceM": 44 }
]
}]
}
}
| Field | Meaning |
|---|---|
explains | The sourceIds of the phenomena this body claims to be |
model | A shape built here (ellipsoid, sphere, disc, cylinder, cone, box, torus, figure), a model of the catalogue by id, or a glTF file at url with its credit; a relative url is read from the file that states it, not from the page. Stretched to sizeM whichever it is. headingOffsetDeg and credit ({ title, author, license, sourceUrl }) are those of a decor object's model. |
track | Where it is and what it looks like at each t. A position is stated either in the world (eastM/northM from where the witness stood at the start, like the decor, with onGround or altitudeAboveGroundM) or from the witness at that instant (azimuthDeg, altitudeDeg, distanceM). A body onGround stands on the relief; a direction with no distance then meets the ground where that line does. sizeM, attitude (headingDeg, pitchDeg, rollDeg) and appearance (color, albedo, luminanceCdM2, transparency from 0 to 1, haloScale as a multiple of the glare of its own light) hold until a later keyframe restates them, and are blended between two keyframes. present: false takes the body out of the scene from that keyframe on, and present: true brings it back. A flame (lengthM, widthM, color at the nozzle, tipColor, luminanceCdM2) is lit at the keyframe that states it, comes out of the model's node named exhaust (or the one its node names), lights what is around it, raises dust where it meets the ground when raisesDust says so, and is put out by a luminanceCdM2 of 0 |
motions | In a keyframe: how far along each of its model's own movements it is, by the movement's name — the glTF file's animations. 0 is a movement's start, 1 its end, and one that repeats goes on past 1: { "legs-turn": 7 } is seven turns. The model says what moves and how; the track says when. Each movement blends between the keyframes that state it, whatever other keyframes move the body in between, holds after the last and stands at 0 before the first. Valensole's departure is written so: { "t": 246000, "motions": { "pivot-retract": 0 } }, { "t": 248000, "motions": { "pivot-retract": 1, "legs-turn": 0 } }, … { "t": 262000, "motions": { "legs-turn": 7 } } |
lights | In a keyframe: the luminance, cd/m², of each of its model's own lights, by the name of the light's material in the glTF file — so that one body carries lights that each do their own thing, a steady white at each end and a red one flashing between. The model says where each light is, how big and what colour; the track says how bright and when. Each light blends between the keyframes that name it and holds after the last, so a switch is two keyframes a millisecond apart; a light no keyframe names glows at its share of appearance.luminanceCdM2. A light too small to show is seen by its glare, and whatever stands between it and the eye — the body's own hull, a bridge — hides it. Silly-le-Long's red light: { "t": 499, "lights": { "front-red": 1500 } }, { "t": 500, "lights": { "front-red": 0 } } |
outlineNode | The node of the model that is what the witness drew ("hull" for a craft whose legs are not in the drawing): what its outline is measured by |
groups | Parts of its model taken together, so that one event is about them all: { id, title, members }, its members parts of the model (a light by its name) or other groups of the body's, their ids the body's own. Named in an event as a part is, id/group: the two rear lights of observer-silly-le-long.json's craft, engin/rear, which blink together. Optional: a part is named alone as well |
modelParameters, flicker | The settings of its model, by the key its catalogue entry publishes each under ({ "paperColor": "#ff0000" } for a sky lantern's paper, which also filters what its paper gives out); and how much its light wavers, as a flame's does, as a share of it (0.15, some 15 % above and below, a few times a second, alike at every playing). Steady when absent |
shadow, ensemble, lightFromBelow | shadow: false: it casts no shadow (a bird a hundred metres up casts none anyone could see). ensemble: the bodies sharing it are measured as one against what they explain, by all their outlines together: a flock taken for one craft. lightFromBelow ({ lux, color? }): the light coming up at it from a lit ground under it, as the illuminance it gives a surface facing down: what shows the white belly of a bird flying over a town at night. |
smoke | On the reading itself: what it sets burning on the ground, as { eastM, northM, fromT, untilT? }, seen by its smoke carried off by the recording's wind. halfLifeS is how fast it dies down, in seconds to half its thickness (20 by default): a brush fire flares and smoulders. It never quite stops before untilT. |
lanterns | On the reading itself: sky lanterns let go from the ground, each computed into a glowing body. A launch states its site ({ eastM, northM, altitudeM?, originElevationM? }), the wind at the ground and optionally windAloft ({ towardDeg, speedMS, atM }), the airTemperatureC, and its lanterns: one by one in releases ({ t, explains?, eastM?, northM?, altitudeM?, burnedS?, lantern? }, where altitudeM and burnedS start one where it was first seen, already up and partly burnt), or as a group ({ count, fromT, untilT, radiusM?, burnS?: { min, max }, insideExcessK?: { min, max }, burnedS?, explains?, seed? }), whose lanterns are drawn at random within those bounds, the same for the same seed. Each climbs while its hot air lifts more than it weighs, goes with the wind of the height it has reached, each meeting its own gusts (turbulence: { horizontalMS, verticalMS, timescaleS }, the spread of the air's speed about that wind and how long a gust lasts; 0.8, 0.3 and 30 s, a light breeze's, by default, all zero for a still air), so that a group let go together stretches and shifts as it climbs, and vanishes when its fuel is spent: 8 to 15 minutes by the sellers, 480 to 900 s drawn by default. lantern overrides the common 1 m lantern: envelopeVolumeM3 (0.19), massKg (0.065), fuelKg, burnS (600), insideExcessK (150), dragAreaM2, luminousIntensityCd (10, assumed: a bright star at 2 km), widthM, heightM, color (its flame's light through white paper), shape ("classic", round at its mouth and square at its flat top, or "balloon", narrow at its mouth with a wide, lobed top) and paperColor (white by default: what it looks like by day, and what filters its light by night). Each leans the way the air going past pushes it, a few degrees in a gust. |
birds | On the reading itself: birds, alone or in flocks, each computed into a body drawn as a bird of its species (herring-gull, ring-billed-gull, black-headed-gull, brown-pelican, american-white-pelican, canada-goose, snow-goose, mallard, american-golden-plover, killdeer) whose wings beat at the rate its mass, wingspan and wing area predict in the air it flies in (Pennycuick 1996), or at wingbeatHz, flapping all along or, as pelicans do, in bursts with glides between (flight: { kind: "bursts", beats, glideS }). A flock states its count, its formation ({ kind, angleDeg?, asymmetry?, spacing?, wander? }: single, v, j, echelon, column, front, cluster, or flock, a crowd that flies itself, each bird heeding its seven nearest), and its path, points at instants ({ t, eastM, northM, altitudeM }, or { t, azimuthDeg, altitudeDeg, distanceM, eyeHeightM? } from the recording's origin), smoothed between them; each bird points where it goes and banks into its turns. Also colours, lightFromBelow, explains (the flock together, see ensemble) and seed. |
findings | On the reading itself: the tests the claim was put to and how each came out, so that a claim that fails is kept, showing it was examined and why it does not hold. Each is { text, outcome, against?, rationale? }: text says what was tested and what it gave (one per language), outcome is holds, fails or untested (it could not be made with what is known), and against says what it was set against: established (a value stated or derived, a measure on the picture) or supposed (one the recording assumed, or one it fitted to a hypothesis). A reading that fails against what is established contradicts the observation head-on, and the case editor draws it red; one that fails only against a supposition, or could not be tested, is not settled, orange; one whose tests all hold is green. With no findings, nobody has tested it, and it has no colour. |
mechanism | On the reading itself, when the claim is that the instrument made the phenomenon: { kind, explains, of? }, explains the id of the phenomenon's shapes in the account and kind one of fixed-in-frame (standing still in the frame: a speck on the lens or in the gate, a reflection on a pane fixed to the camera), lens-ghost (a ghost of the Sun in the instrument's own lens, at one of the factors its glass throws), stated-ghost (a ghost of the Sun in an optic set before the lens, at whatever factor and offset fit best), driven-one-way (something on the glass driven across the frame one way, never back), ghost-of (a ghost through the lens of a light the reading places itself, of the id of that body: a glint on an aircraft) and real-object (something really in the sky, at any distance along the line of sight). Its most favourable configuration is then searched for within what the account allows (the Sun's heights over the days it allows, the side the picture's light comes from) and measured against where the account shows the phenomenon, instant by instant: how far it stays from it is a finding computed for whoever reads it, which holds within the phenomenon's own size. The reading is always shown in it: the speck, the drop or the object is placed where the search puts it, whatever its file placed there (its distance, size and look are kept) |
Another reading is another sighting
Someone else's reading of an account (an analyst's, an investigator's, a comparison made to test it)
is not part of the account: it is another observation, the one that took place as its author holds
it. So it is listed in the case like the original, as an event of type sighting, marked as a
reading by interpretationOf, and has a recording of its own at url:
{
"id": "McMinnville1950",
"events": [
{ "type": "event", "eventType": "sighting", "id": "trent", "title": "Paul Trent", "url": "observer-mcminnville.json" },
{ "type": "event", "eventType": "sighting",
"interpretationOf": "trent",
"time": "2013-06",
"by": [{ "people": "CousynAntoine" }, { "people": "LouangeFrancois" }],
"title": "A model on a thread under the line",
"url": "interpretation-mcminnville-2.json" }
]
}
| Field | Meaning |
|---|---|
interpretationOf | The id of the case's event it is a reading of ("trent"), or a list of ids when one reading serves several accounts (the photographs and a close-up of them). What tells it from an account: the events without it are the case's witnesses |
sealed | Whether the event is frozen: true once someone has worked ON this reconstruction — an interview held to hear what the witness makes of it, a hypothesis set against it — so that a later edit cannot quietly invalidate that work. The editor then takes nothing typed into it and refuses to delete it or rename its id, until it is thawed; its clone, beside the padlock, is what the author carries on with. Never set by itself: a reconstruction is edited for as long as it is being built, and versions nobody asked for are noise |
time | When the reading was elaborated, as RR0 writes a time ("2013-06"): not when the sighting happened |
by | Who claims it: { "people": id } or { "org": id }, which name an entry that lives elsewhere (on RR0, a people or an org directory), or a person described in value. Absent for a comparison nobody claims |
title | What the reading is called in the player's menu and the editor's picker: a few words, one string or one per language |
url | Its recording, read relative to the case file's own address, like a witness's |
The recording at url is a recording like any other. It shares the place, the time and the witness's
pose of the account it reads, so that a body placed from the witness, or in metres from where they stood,
means the same in both; it draws no shape of its own (an empty timeline); and it holds the bodies in
its own interpretation, described above. A body's explains names the shapes of the account.
{
"version": 4,
"id": "1950-05-11-TrentPaul-interpretation-2",
"time": "1950-05-11T19:45",
"utcOffsetHours": -7,
"place": { "locations": [{ "lat": 45.104167, "lng": -123.330556 }] },
"observerTrack": { "keyframes": [{ "t": 0, "pose": { "lat": 45.104167, "lng": -123.330556, "headingDeg": 41.3, "pitchDeg": 14.85, "fovDeg": 33.4 } }] },
"tags": ["interpretation"],
"timeline": { "keyframes": [], "order": [], "groups": [] },
"interpretation": {
"title": "A model on a thread under the line",
"bodies": [{
"id": "model",
"explains": ["ufo-1"],
"model": { "id": "disc" },
"track": [
{ "t": 0, "eastM": -52, "northM": 118, "altitudeAboveGroundM": 7.5,
"sizeM": { "widthM": 0.3, "lengthM": 0.3, "heightM": 0.1 } }
]
}]
}
}
The player lists the case's witnesses from the events with no interpretationOf and offers each
reading beside the account it names, one at a time (the ◌ button measures it against the account). A recording
standing alone has no reading but its own interpretation. The older form, an event of type
interpretation naming the recording in sighting with its bodies inline or in a file at
url, is still read. The editor opens a case: its picker above the render lists the accounts and
the readings, each opening as the recording it is, with a button to add a reading (a new recording that shares the
account's place, time and pose, and an event for it), one to delete it, and one to export the case and every
recording added or changed as a zip. Try it with
case-mcminnville.json
(play it,
edit it).