get_event¶

Science¶

get_event returns one catalogue origin as the session's view allows: origin time, hypocentre, local magnitude, phase count, NonLinLoc RMS and azimuthal gap, and a civil-time breakdown in the configured timezone. View-dependent keys (pipeline, config_version, post-processing flags, created_at_utc) are omitted entirely when the view withholds them — absent, not null.

A small RMS on few phases is underdetermined, not good. Magnitude is null when fewer than two station magnitudes entered the network value; that is the IASPEI-style two-station minimum, not a tool failure. Depth near 0 km or the catalogue grid floor, fewer than six phases, and a gap above 180° are warned, not rejected.

The row is a stored automatic (or reviewed) solution. This tool does not re-locate or re-evaluate it.

Contract¶

Generated from the live registry (ToolSpec). Field names, types and defaults come from the input and payload models; they are not hand-typed.


Group	`catalog`
Class	1
Tool version	`1.0.0`
Highest declared tier	F
Timeout	5 s
Budget key	`none`
`readOnlyHint`	true
`idempotentHint`	true

Input¶

Field	Type	Required	Notes
`event_id`	integer	yes

Payload¶

Field	Type	Required	Notes
`event_id`	integer	yes
`origin_time_utc`	string	yes
`latitude_deg`	number	yes
`longitude_deg`	number	yes
`depth_km`	number \| null	yes
`magnitude_ml`	number \| null	yes
`magnitude_station_count`	integer \| null	yes
`num_phases`	integer \| null	yes
`rms_s`	number \| null	yes
`gap_deg`	number \| null	yes
`local_time`	object	yes
`local_time.tz`	const `IANA timezone of the configured region`	yes
`local_time.hour`	integer	yes
`local_time.minute`	integer	yes
`local_time.weekday`	string ∈ {`mon`, `tue`, `wed`, `thu`, `fri`, `sat`, `sun`}	yes
`pipeline`	string \| null	no	default `null`
`config_version`	string \| null	no	default `null`
`flags`	object \| null	no	default `null`
`flags.is_teleseism_suspect`	boolean	yes
`flags.teleseism_match`	string \| null	yes
`flags.is_depth_suspect`	boolean	yes
`flags.is_out_of_region`	boolean	yes
`created_at_utc`	string \| null	no	default `null`

Example request¶

{
  "event_id": 1001
}

Example payload¶

{
  "event_id": 1001,
  "origin_time_utc": "2024-06-15T08:12:03.417Z",
  "latitude_deg": 47.15,
  "longitude_deg": 24.5,
  "depth_km": 10.0,
  "magnitude_ml": 2.1,
  "magnitude_station_count": 3,
  "num_phases": 9,
  "rms_s": 0.27,
  "gap_deg": 112.0,
  "local_time": {
    "tz": "configured_iana_tz",
    "hour": 11,
    "minute": 12,
    "weekday": "sat"
  }
}

What this tool does not tell you¶

What this tool does not tell you: anything about correctness. A small RMS on few phases means underdetermined, not good. The magnitude is null below two station magnitudes by design, not by failure.

Warnings named for this tool¶

Code	When
`depth_at_grid_boundary`	depth within 5 km of 0 or the grid floor
`few_phases`	fewer than 6 phases
`large_gap`	azimuthal gap greater than 180°

Errors named for this tool¶

Code	When
`E_UNKNOWN_EVENT`	no such event_id in the session view
`E_POLICY`	the event is not the session subject (`subject_mismatch`)