tip-and-cue (scenario kind)
Scenario kind of the engine v0.41.0, family Space RF survey. Advisory: analysis output from a research and engineering tool, not type-approved navigation equipment and not a safety-of-life service. Every label here is the engine's or the verification matrix's; a kind is MODELLED unless the matrix says otherwise (how a label is earned: the README's Evidence section).
Qué hace#
MODELLED revisit and tip-and-cue latency of a two-layer maritime survey over the Baltic Sea: an RF survey layer and an optical layer, each a Walker star pattern of 550 km sun-synchronous orbits propagated with the secular J2 drift on a spherical Earth, with an elevation mask for the RF layer and an off-nadir field of regard (and optionally daylight) for the optical layer. Reports R, the area-weighted mean gap between RF accesses per point; F, the mean wait until every sea point has been in view; and Q, the mean wait from an RF access to an optical look, each with its median, 95th percentile and largest value. Geometry and timing only: no detection, weather or tasking latency. A cross-check of published simulation figures, never a validation.
One run of scenarios/tip-and-cue-short.toml summarises as: tip-and-cue: 1 cases over 996 area points (minutes)
rf-16-optical-16: revisit 25.8, full-area refresh 15.3, RF-to-optical reaction 22.6
Entradas#
Del esquema (kshana kinds --json):
- Campos obligatorios: ninguno
- Optional fields:
kind,title,seed,area,step_s,span_days,m2,cases
El ejemplo scenarios/tip-and-cue-short.toml establece, entre otros:
| Campo | Valor | Unidad |
|---|---|---|
cases[0].name |
rf-16-optical-16 | texto |
cases[0].optical.node_offset |
0.5 | 1 |
cases[0].optical.phasing |
1 | 1 |
cases[0].optical.planes |
8 | recuento |
cases[0].optical.total |
16 | recuento |
cases[0].optical_off_nadir_deg |
45 | deg |
cases[0].rf.node_offset |
0 | 1 |
cases[0].rf.phasing |
1 | 1 |
cases[0].rf.planes |
8 | recuento |
cases[0].rf.total |
16 | recuento |
cases[0].rf_mask_deg |
10 | deg |
kind |
tip-and-cue | texto |
Ejecútelo#
kshana scenarios/tip-and-cue-short.toml
2 bundled scenarios use this kind; the others are in scenarios/.
Qué proporciona#
Los resultados escalares de esa ejecución, con las unidades que indica el motor:
| Resultado | Valor | Unidad |
|---|---|---|
evidence.id_rule |
el identificador estable de la fila de la matriz (el ID | texto |
evidence.matrix |
docs/VERIFICATION-MATRIX.md | texto |
evidence.tier |
MODELLED | texto |
inputs.area |
baltic | texto |
inputs.epoch_utc |
2025-01-01T00:00:00Z | texto |
inputs.inclination_deg |
97.59 | deg |
inputs.points |
996 | recuento |
inputs.semi_major_axis_m |
6928137 | m |
inputs.span_s |
172800 | s |
inputs.step_s |
60 | s |
Result label (the engine's): MODELLED: revisit, full-area refresh and RF-to-optical reaction of a two-layer survey from stated Walker star layers on 550 km sun-synchronous orbits (secular J2), spherical Earth, stated fields of regard; geometry and timing only, no detection, weather or tasking latency; a cross-check of published
Evidencias#
No matrix row names this kind by name; the label on its result is the engine's own, above.
Las filas que la propia ejecución puso a prueba, con la referencia independiente que da la matriz a cada una (las fuentes públicas se nombran allí):
- MODELLED Determinista, con hash de escenario, SBOM + barreras golden multiplataforma. Referencia independiente (ExternalDataset): ajuste a la norma del SBOM al esquema JSON oficial de CycloneDX 1,5 (+ identificadores SPDX válidos) — un estándar externo publicado, cero errores de validación en todo el grafo de dependencias; la parte de determinismo de FoM / reproducibilidad byte a byte sigue siendo una comprobación de autoconsistencia fijada, por lo que la fila sigue siendo MODELLED
- VALIDATED The
constellation-designkind's generators: Walker delta and star patterns in the T/P/F convention (node spacing 360/P or 180/P, in-plane spacing 360·P/T, int. Oracle (ExternalDataset): Published agency documents: Galileo Open Service Service Definition Document issue 1.1 (European GNSS Service Centre) Tables 1 and 23, the reference constellation at 2016-11-21 00:00 UTC; GLONASS Interface Control Document edition 5.1 (2008) section 5.2, the slot formula for node longitude and argument of latitude; GPS Standard Positioning Service Performance Standard 5th edition (April 2020) Tables 3.2-1, 3.2-2 and
Limitaciones#
Lo que el propio informe de la ejecución dice que no está modelado o no está validado:
- MODELLED: revisit, full-area refresh and RF-to-optical reaction of a two-layer survey from stated Walker star layers on 550 km sun-synchronous orbits (secular J2), spherical Earth, stated fields of regard; geometry and timing only, no detection, weather or tasking latency; a cross-check of published simulation figures, never a validation (result
label) - MODELLED revisit and tip-and-cue latency of a two-layer maritime survey over the Baltic Sea: an RF survey layer and an optical layer, each a Walker star pattern of 550 km sun-synchronous orbits propagated with the secular J2 drift on a spherical Earth, with an elevation mask for the RF layer and an off-nadir field of regard (and optionally daylight) for the optical layer. (kind catalogue (
kshana kinds --json)) - A short tip-and-cue run: the M2 primary 16-satellite RF layer cueing its optical layer over the Baltic Sea for 2 days at a 60 s step (fast; for the full pre-registered run see tip-and-cue-baltic-m2.toml). Geometry and timing only; MODELLED. (scenario file comment, lines 1 to 3)
- La reproducibilidad y el aseguramiento del software son MODELLED, no están validados: una subafirmación se comprueba externamente, pero la capacidad completa compone piezas modeladas, por lo que la capacidad sigue siendo modelada. (matriz de verificación (docs/MODELLED-RATIONALE.md))
Véase también#
- Family page: Space RF survey
- Todos los tipos de escenario: KINDS.md
- Topic page: TIP-AND-CUE.md