Data Handling
The Data Handling subsystem is responsible for the collection, storage, and transmission of data within and between agents.
Data Types
Before configuring the data handling behavior for an agent, you must first define the types of data that the system will manage. You could treat all data as the same type, but specifying different data types here allows for dedicated data interfaces and simulation results specific to each data type.
Create a data type
Add the following data types:
Data Type Name |
---|
Telemetry |
Remote Sensing |
Data Storage
Data storage is attached to other components and is where data of any type can be stored. Data flowing to a component will either pass through the component if there is an active data interface that allows it, or it will be stored in the component's data storage until such an interface becomes active.
Create data storage
Create the following data storage devices:
Storage Name | Storage Capacity (bits) | Max Write Bitrate (bit/s) | Max Read Bitrate (bit/s) | Component |
---|---|---|---|---|
TT&C Storage | 50000000000 | 1000000 | 3000000 | Flight Computer |
Sensing Storage | 350000000000 | 100000000 | 100000000 | Payload Computer |
Crosslink Modem Storage | 64000000000 | 50000000 | 100000000 | Crosslink Modem |
Data Handling Devices
Data handling devices are components that are specifically responsible for receiving and transmitting data.
Create a data handling device
Create the following data handling devices:
Device Name | Device Type | Field of View |
---|---|---|
Crosslink Antenna | Antenna | Crosslink FoV |
Crosslink Modem | Modem |
Data Interfaces
Data interfaces facilitate the flow of data. Internal data interfaces connect components within an agent and external data interfaces connect the data handling devices of different agents in a scenario.
Create a data interface
Create the following internal data interfaces:
Data Interface Name | Bitrate (bit/s) | Data Type | Interface Type | Data Source | Data Sink | Data Bus | Always Active | Operational Modes |
---|---|---|---|---|---|---|---|---|
Comp. to Crosslink Modem Inter. | 60000000 | Telemetry | Internal Data Interface | Flight Computer | Crosslink Modem | Crosslink | ||
Cam to Payload Comp. Interface | 100000000 | Remote Sensing | Internal Data Interface | Payload Camera | Payload Computer | Imaging | ||
Payload Comp. to CL Modem Inter. | 80000000 | Remote Sensing | Internal Data Interface | Payload Computer | Crosslink Modem | Crosslink |
Create the following cooperative transmit interfaces:
Data Interface Name | Bitrate (bit/s) | Data Type | Interface Type | Modem | Directed Energy Device | Link Target | Always Active | Operational Modes |
---|---|---|---|---|---|---|---|---|
Crosslink Interface (T) | 80000000 | Telemetry | Cooperative Transmit Interface | Crosslink Modem | Crosslink Antenna | LaserComm Relays | Crosslink | |
Crosslink Interface (RS) | 80000000 | Remote Sensing | Cooperative Transmit Interface | Crosslink Modem | Crosslink Antenna | LaserComm Relays | Crosslink |
Data Modes
Data modes are necessary if you want to create or delete data on a component without using external data interfaces. For Wildfire, we will use data modes as the origin of our two data types.
Create a data mode
Create the following data modes:
Data Mode Name | Components | Data Types | Input Bitrate (bit/s) | Output Bitrate (bit/s) | Always Active | Operational Modes |
---|---|---|---|---|---|---|
Operating | Flight Computer | Telemetry | 0 | 500000 | ||
Remote Sensing | Payload Camera | Remote Sensing | 0 | 64000000 | Imaging |
Data Buses
Data buses allow you to group internal data interfaces together for analytical purposes. You do not have to add any data buses to Wildfire.