Skip to main content
Version: 4.14

Conditions

Conditions are assigned to operational modes to drive ConOps logic. For example, you can use a condition to require line of sight to your groundstation for entry into downlink operational mode. Additionally, they can be used to filter targets in a Target Group, determine when Sensors produce data, and terminate the simulation. There are four types of conditions.

Compare Conditions​

A compare condition is fulfilled when two parameters (A and B) must satisfy the relationship defined upon the creation of the condition. Parameter A may fall in one of three categories:

  • Satellite - These parameters are related to the satellite itself, for example latitude, battery state of charge, eclipse state, beta angle, etc.
  • Target - These parameters are related to a target or target group, for example line of sight (access), range, satellite elevation, solar elevation, etc.
  • Date and Time

Parameter B may be either a constant value (scalar or boolean) or a satellite or single target parameter.

Finally define the relationship, which is an equality or inequality (for example, <, >= etc.).

If a Target Group parameter is chosen for Parameter A, you will be prompted to select a group "roller", which is a method to combine the individual target parameters into a single comparable quantity. Available rollers include "all", "any", "count", etc. You can choose to have this Condition filter the Target Group by clicking the checkbox.

Field of View Conditions​

Field of view conditions evaluate whether a Target, Reference Vector, or celestial body lies within a Field of View. Select "Negate" to instead evaluate whether the target/vector/body is outside of the field of view.

The FoV evaluation for targets includes checking for eclipse by the Earth, moon, and other celestial bodies, evaluating to false if the target is blocked.

Evaluation of vector in FoV does not take eclipsing into account.

Compound Conditions​

Compound conditions combine multiple previously defined conditions into one. Using the "and" operator, this can simplify the definition of Operational Modes and any other place where Conditions are selected. The "any" and "count" operators can be used to define more complex logic, since "all" is assumed when assigning Conditions to an Operational Mode, for example.

Same Target Multi-Condition​

This is a variant of Compound Condition that combines conditions associated with a single Target Group. The difference is that these evaluate to "true" only if all of the conditions are "true" for at least one target. For instance, if a ground target can only be imaged during certain local time and satellite elevation conditions, combining the two conditions into a Same Target Multi-Condition will allow ConOps logic to access whether any target can be imaged.

It is recommended to use a Same Target Multi-Condition any time that multiple conditions are imposed on a Target Group (such as in an Operational Mode) since it will assure that the Agent considers the Target Group in an intuitive manner.