SimulationBaseClass
- class SimulationBaseClass.EventHandlerClass(eventName, eventRate=1000000000, eventActive=False, conditionList=None, actionList=None, conditionFunction=None, actionFunction=None, conditionTime=None, terminal=False, exactRateMatch=True)[source]
Bases:
objectClass for defining event checking behavior, conditions, and actions.
Three checking strategies are supported:
Exact Interval Checking: (default) The event is checked only when the current time is an exact multiple of the
eventRate. This behavior is similar to how tasks are scheduled in Basilisk. Note that if no task leads to a timestep at a checking time, the event will not be checked.Elapsed Interval Checking: The event is checked whenever the
eventRatehas elapsed since the last check. This is enabled by settingexactRateMatchtoFalse. This behavior is similar to how Basilisk loggers operate.Condition Time Checking: An alternative to interval-based checking when an event should occur at a specific time. This is enabled by setting
conditionTime, and will lead to the event being triggered at the first timestep at or after the specified time.
When an event is checked, the
conditionFunctionis called to determine if the event should occur. If the condition returnsTrue, theactionFunctionis executed. and the event is deactivated. To continue checking the event, it must be reactivated. If the event is marked asterminal, the simulation will be instructed to terminate when the event condition occurs.- Parameters:
eventName (str) – Name of the event
eventRate (int) – Rate at which the event is checked in nanoseconds
eventActive (bool) – Whether the event is active or not
terminal (bool) – Whether this event should terminate the simulation when it occurs
conditionFunction (function) – Function to check if the event should occur. The function should take the simulation object as an argument and return a boolean. This is the preferred manner to set conditions as it enables the use of arbitrary packages and objects in events and allows for event code to be parsed by IDE tools.
conditionTime (int) – Alternative to conditionFunction, a time in nanoseconds to trigger the event. Does not depend on eventRate for checking.
actionFunction (function) – Function to execute when the event occurs. The function should take the simulation object as an argument. This is the preferred manner to set conditions as it enables the use of arbitrary packages and objects in events and allows for event code to be parsed by IDE tools.
exactRateMatch (bool) – If True, the event is checked only when the current time is an exact multiple of the eventRate. If False, the event is checked whenever the
eventRatehas elapsed since the last check.conditionList (list) – (deprecated) List of conditions to check for the event, expressed as strings of code to execute within the class.
actionList (list) – (deprecated) List of actions to perform when the event occurs, expressed as strings of code to execute within the class.
- class SimulationBaseClass.SimBaseClass[source]
Bases:
objectSimulation Base Class
- AddModelToTask(TaskName, NewModel, ModelData=None, ModelPriority=-1)[source]
This function is responsible for passing on the logger to a module instance (model), adding the model to a particular task, and defining the order/priority that the model gets updated within the task.
- Parameters:
(str) (TaskName) – Name of the task
(obj) (NewModel) – Model to add to the task
ModelData – None or struct containing, only used for C BSK modules
(int) (ModelPriority) – Priority that determines when the model gets updated. (Higher number = Higher priority)
- Returns:
- ConfigureStopTime(TimeStop, StopCondition: Literal['<=', '>='] = '<=')[source]
Set the simulation stop time in nano-seconds.
- Parameters:
TimeStop (int) – Time to stop the simulation in nanoseconds
StopCondition (str) –
Condition for meeting the stop time. Two behaviors are supported:
<=: (default) The simulation will run as far as it can such that theStopTimeis met if possible, but not exceeded.>=: The simulation will run as far as it can such that theStopTimeis minimally exceeded, but met if possible.
- CreateNewProcess(procName, priority=-1)[source]
Creates a process and adds it to the sim
- Parameters:
(str) (procName) – Name of process
(int) (priority) – Priority that determines when the model gets updated. (Higher number = Higher priority)
- Returns:
simulationArchTypes.ProcessBaseClass object
- CreateNewTask(TaskName, TaskRate, InputDelay=None, FirstStart=0)[source]
Creates a simulation task on the C-level with a specific update-frequency (TaskRate), an optional delay, and an optional start time.
- Parameters:
TaskName (str) – Name of Task
TaskRate (int) – Number of nanoseconds to elapse before update() is called
InputDelay (int) – (depreciated, unimplemented) Number of nanoseconds simulating a lag of the particular task
FirstStart (int) – Number of nanoseconds to elapse before task is officially enabled
- Returns:
simulationArchTypes.TaskBaseClass object
- InitializeSimulation()[source]
Initialize the BSK simulation. This runs the SelfInit() and Reset() methods on each module.
- SetProgressBar(value)[source]
Shows a dynamic progress in the terminal while the simulation is executing.
- ShowExecutionFigure(show_plots=False)[source]
Shows in what order the Basilisk processes, task lists and modules are executed
- ShowExecutionOrder()[source]
Shows in what order the Basilisk processes, task lists and modules are executed
- createNewEvent(eventName, *args, **kwargs)[source]
Create an event sequence that contains a series of tasks to be executed.
- Parameters:
eventName (str) – Name of the event
*args – Arguments to pass to the
EventHandlerClassconstructor**kwargs – Keyword arguments to pass to the
EventHandlerClassconstructor
- setAllButCurrentEventActivity(currentEventName, activityCommand, useIndex=False)[source]
Set all event activity variables except for the currentEventName event. The
useIndexflag can be used to prevent enabling or disabling every task, and instead only alter the ones that belong to the same group (for example, the same spacecraft). The distinction is made through an index set after the_symbol in the event name. All events of the same group must have the same index.