Events

Events

First, as for maneuvers or attitude sequences, the user will have to select a reference date with two possibilities:

• “custom” : a specific date will be entered by the user
• “external” : in that case no modification of the date is available as it corresponds to the date defined in the initial orbit parameters (note that this date is automatically updates if the initial orbit date is modified).

Then, the user will have access to a list of orbital events. These events will be stored in the output files.

The available events to detect are:

• Absolute date
• Recurrent Absolute date: same as above but with possibiliries of recurrent events (since V11.4).
• Relative date: defined with respect the reference date defined at the top of the events tab.
• Recurrent Relative date: same as above but with possibiliries of recurrent events (since V11.4).
• AOL: argument of latitude defined by the angle value, the anomaly type (true, eccentric or mean) and the reference equator with respect the AOL is computed (GCRF, EME2000). and CIRF).
• Altitude: permits to define a certain geodetic altitude.
• Eclipse: eclipse events either “entering the eclipse” or “exiting the eclipse” or both are registered.
• Local time: permits to define a certain local time.
• Station visibility: events entering the field of view or existing the field of view are registered. The station visibility is determined thanks to the station’s location (latitude, longitude and altitude).
• Node: ascending or descenfing ones (since V11.4).
• Apside: perigee or apogee events (since V11.4).

Warning : for events which allows distinguishing between "enter"/"exit" events (as eclipse or ground stations visibility), the fact to select "both" (see next figure), does not mean to select "enter" AND "exit" but "enter" OR "exit".