Standardized JSON Schema for authoring multi-mission sequences. You can read the schema definition here.
You can use our validation site to validate a .seq.json
document against the latest schema.
Spacecraft are often controlled via sets of time ordered commands called sequences. Although spacecraft are built with a variety of different on-board flight softwares, each of which have different commanding interfaces, there are sufficient commonalities between these interfaces to justify creating a common sequencing specification that works for a number of flight software types.
If organizations must support operating different missions with different flight software, operators can use this common specification (with potential customization) for these different missions. Operators would author and transport the set of commands they want to send to the spacecraft in this common specification and then perform a final translation from this specification to the format required by the flight software for final verification.
Interested in proposing a change to the schema? Begin by writing a change request issue.
npm install @nasa-jpl/seq-json-schema --save
import seqSchema from '@nasa-jpl/seq-json-schema/schema.json' assert { type: 'json' };
console.log(seqSchema);
This library also ships with automatically generated TypeScript types from the schema. For example:
import type { Command, SeqJson } from '@nasa-jpl/seq-json-schema/types';
const command: Command = {
args: [],
stem: 'SEND_DATA',
time: { type: 'COMMAND_COMPLETE' },
type: 'command',
};
const seqJson: SeqJson = {
id: 'sequence0',
metadata: {},
steps: [command],
};
console.log(seqJson);
pip install seq-json-schema
import importlib.resources
import json
with importlib.resources.path('seq-json-schema', 'schema.json') as schemaPath:
file = open(schemaPath)
schema = json.load(file)
print(schema)
Note if you are using a Python version lower than 3.7 you will have to import the schema using the importlib-resources library.