- General Client
- Mission Database
- TM/TC Processing
- Archive
- Link Management
- Object Storage
- File Transfer
- Time Correlation (TCO)
- Activities
- Timeline
- Examples
Activities¶
Activities are executable units of work within Yamcs. They provide a structured way to trigger commands, run scripts, or execute stacks.
The Python client allows you to define these activities programmatically and schedule them on the Yamcs Timeline.
Core Concepts¶
Each activity type inherits from the base Activity class. Yamcs currently supports three primary built-in types:
CommandActivity: Executes a single telecommand.ScriptActivity: Runs a system script or executable.StackActivity: Executes a pre-defined stack stored in a Yamcs bucket.
API Reference¶
- class yamcs.client.Activity¶
Bases:
objectSuperclass for activities. Core implementations:
Note
This is an abstract base class. You should instantiate one of the subclasses below.
- class yamcs.client.CommandActivity(command: str, args: ~typing.Mapping[str, ~typing.Any] = <factory>, extra: ~typing.Mapping[str, ~typing.Any] = <factory>, processor: str | None = None)¶
Bases:
ActivityAn activity that executes a single command
- class yamcs.client.ScriptActivity(script: str, args: str | List[str] | None = None, processor: str | None = None, runner: str | None = None)¶
Bases:
ActivityAn activity that runs a script
- args: str | List[str] | None = None¶
Optional script arguments, passed verbatim in the command line.
- processor: str | None = None¶
Optional processor name. If provided, this is forwarded to the script as the environment variable
YAMCS_PROCESSOR.