Scenario kind pagesEdit on GitHubSource: docs/kinds/by-kind/space-packet.md

space-packet (scenario kind)

Scenario kind of the engine v0.38.0, family Mission analysis, links and space operations. 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).

What it does#

CCSDS 133.0-B Space Packet Protocol framing: encode a synthetic TM/TC packet stream (6-octet primary header + data field) and report the per-packet header decode, total octets and an exact encode↔decode round trip. Deterministic exact bit-layout framing — the agency packet-format interop layer; NOT a conformance certification (no secondary-header/CRC/segmentation logic beyond the flags).

One run of scenarios/space-packet.toml summarises as: space-packet: framed 4 CCSDS-133.0 TM packet(s) APID 100, 152 octets total, round-trip exact (true)

Inputs#

From the schema (kshana kinds --json):

  • Required fields: none
  • Optional fields: apid, telecommand, packet_count, data_len

The example scenarios/space-packet.toml sets, among others:

Field Value Unit
apid 100 1
data_len 32 not stated
kind space-packet text
packet_count 4 count
telecommand false flag

Run it#

kshana scenarios/space-packet.toml

What it gives#

The scalar results of that run, with the units the engine states:

Result Value Unit
apid 100 1
data_len_octets 32 octet
first_packet.apid 100 1
first_packet.data_length_field 31 1
first_packet.index 0 1
first_packet.primary_header_hex 00 64 40 00 00 1F text
first_packet.sequence_count 0 1
first_packet.sequence_flags First text
first_packet.total_octets 38 octet
first_packet.type TM text

Result label (the engine's): CCSDS 133.0-B Space Packet primary-header framing — exact, deterministic bit layout, encode↔decode round-trip verified; NOT a conformance certification (no secondary header / CRC / segmentation logic beyond the flags)

The chart the engine writes for scenarios/space-packet.toml, kind space-packet

Evidence#

VALIDATED: the verification matrix rows that name this kind.

  • VALIDATED CCSDS 133.0-B Space Packet primary-header encode/decode (version/type/sec-hdr/APID/seq-flags/count/data-length) + a framing scenario. Tests: ccsds_space_packet_reference.rs.
  • VALIDATED CCSDS 133.0-B-2 Space Packet extensions beside the primary header: a secondary header carrying a CCSDS 301.0-B time code (CUC or CDS, explicit or implicit P-field) and ancillary data, the CRC-16 packet error control field, segmentation of a Tests: space_packet_ext_oracle.rs.

The rows the run itself exercised, with the oracle the matrix gives each (the public sources are named there):

  • MODELLED Deterministic, scenario-hashed, SBOM + cross-platform golden gates. Oracle (ExternalDataset): SBOM conformance to the official CycloneDX 1.5 JSON Schema (+ valid SPDX identifiers) — an external published standard, zero validation errors over the full dependency graph; the FoM-determinism / byte-reproducibility part remains a pinned self-consistency check, so the row stays MODELLED
  • VALIDATED CCSDS 133.0-B Space Packet primary-header encode/decode (version/type/sec-hdr/APID/seq-flags/count/data-length) + a framing scenario. Runnable from the CLI/bind. Oracle (ExternalDataset): spacepackets 0.32.0 (us-irs/spacepackets-py, R. Mueller, Apache-2.0) — an independent third-party implementation of CCSDS 133.0-B-2; kshana's encode_packet/decode_packet matched byte-exact (the 6-octet primary header for 33 cases + the full encoded packet for 12)

Limitations#

What the run's own report says is not modelled or not validated:

  • Reproducibility & software assurance is MODELLED, not validated: a sub-claim is externally checked, but the whole capability composes modelled pieces, so the capability stays Modelled. (verification matrix (docs/MODELLED-RATIONALE.md))

See also#