EPS (Experiment Planning System)
EPS Overview
From [EPSD], The Experiment Planning System (EPS) is a software tool developed for the creation of th experiment operations for a specific time period (mission scenario). An operation timeline (ITL) is first entered, which comprises a list of experiment operations and a specific time for when each operation has to be executed. The EPS then checks for constraint violations one ach of the experiments and their operations.In order to use the EPS, the experiment operational procedures/requirements, and the experiment environment must first be modelled and implemented. This is done using an Experiment Description File (EDF) for the experiment model, and an Event File (EVF) for the environment model. The EDF provides a generic way to model experiment operations.
The environment model in turn generates operational boundaries, which can either affect the experiment as a whole or can be restricted to a specific experiment operation. After describing the experiments, operations can be requested through an operations timeline, known as an Input Timeline (ITL). The EPS will run the timeline checking for conflicts.
The EPS uses a modular approach for defining an experiment, and can therefore still be used even if only limited information about an experiment is provided.In order to perform conflict resolving at different levels and using
EPS Configuration
Writing PORs
Tha maximum lenght of the observation label is set to 100 characters.
Instrument Timeline Files (ITL/OTL)
The same way, the ITL files need to start with ITL_ or OTL_.
Payload Operations Requests (POR/PDOR)
The way EPS identifies POR XML files is by its prefix (it checks that the POR filename starts with the first 4 letters set to POR_).
The validity range is not needed when using a top-level ITL that provides start and end times.
The validity range of the event timeline should always be greater or equal to the validity range of the action timeline
EPS Simulation
The EPS simulation starts after (1 second) the simulation start time, any action or observation that is scheduled at the simulation start time will not be taken into account in the simulation. The following EPS configuration keywords modify the generation of PORs with EPS:
POR_write_action_default_params: <PARAM_ONLY|PARAM_AND_VALUE>
ITL_write_action_default_params: <NONE|PARAM_ONLY|PARAM_AND_VALUE>
For example:
POR_write_action_default_params: PARAM_AND_VALUE ITL_write_action_default_params: NONE
“All action parameter values will be explicitly written in the PORs sent to the MOC. ITL will omit default parameters (saving disk space).”
Thus, the values are:
NONE: No default values are written (only available in ITLs or JITLs)PARAM_ONLY: Only the name of the default parameters are written but not their values (Current behaviour)PARAM_AND_VALUE: The name and the value of the defaults parameters are written
The validity range of the event timeline should always be greater or equal to the validity range of the action timeline
IMPORTANT: The EPS simulation starts after (1 second) the simulation start time, any action or observation that is scheduled at the simulation start time will not be taken into account in the simulation.
POR and PDOR
The validity range of a POR is not required, but it can be used by EPS when there is no start and end times on a top-level ITL.
During the checks of PCW3 PORs the FCT requested to deviate from the current version of the PLID: JUI-ESOC-MOC-ICD-003, Is.1, Rev.1 in order to be able to accommodate reasonable requests from PEP Hi and PEP Lo.
These requests are currently implemented in EPS and are as follows:
Allow for a
descriptionparameter for theoccurrenceListelement and its occurrences (present as optional in previous versions of the PLID but removed).Relax the 20 character length of the uniqueId parameter to maximum length. From the PLID it is open to interpretation whether if it is set to exactly 20 characters or up to 20 characters.
Derived Events
The EPS Derived Events allow the user to define events derived from already existing events by applying a number of operations.
In order to include them a new file called derived_events.def must be present in the same directory
where the file events definition file is.
For example, we can defined an event derived from an Europa flyby with a given time shift:
CA_EUROPA_DER = (CA_EUROPA+00:15:00)
Then we would need to add the following line in the event definition file:
5282 CA_EUROPA_DER CA_EUROPA_DER - - - FALSE - 0 GLOBAL MOMENTARY INACTIVE
In this case, it will generate the same events as CA_EUROPA_DER but starting 15 minutes later.
For complete documentation (restricted access): [Derived Events Query Language](https://s2e2.cosmos.esa.int/confluence/display/PSS/On+Events+Query+Language)
EPS Inputs
Observation Definition Files (ODF)
Tha maximum lenght of the observation label is set to 100 characters.
Instrument Timeline Files (ITL/OTL)
The same way, the ITL files need to start with ITL_ or OTL_.
Payload Operations Requests (POR/PDOR)
The way EPS identifies POR XML files is by its prefix (it checks that the POR filename starts with the first 4 letters set to POR_). The validity range is not needed when using a top-level ITL that provides start and end times. The validity range of the event timeline should always be greater or equal to the validity range of the action timeline
The validity range of a POR is not required, but it can be used by EPS when there is no start and end times on a top-level ITL.
During the checks of PCW3 PORs the FCT requested to deviate from the current version of the PLID: JUI-ESOC-MOC-ICD-003, Is.1, Rev.1 in order to be able to accommodate reasonable requests from PEP Hi and PEP Lo.
These requests are currently implemented in EPS and are as follows:
Allow for a
descriptionparameter for theoccurrenceListelement and its occurrences (present as optional in previous versions of the PLID but removed).Relax the 20 character length of the uniqueId parameter to maximum length. From the PLID it is open to interpretation whether if it is set to exactly 20 characters or up to 20 characters.
EPS Simulation
The EPS simulation starts after (1 second) the simulation start time, any action or observation that is scheduled at the simulation start time will not be taken into account in the simulation.
The validity range of the event timeline should always be greater or equal to the validity range of the action timeline.