#################
EPS Package
#################

The EPS package is a collection of files that allows to simulate and verify the
result of the segmentation process using the EPS software.

The bundle contains 4 pre-configured EPS input folders that allow the user to
check the resource consumption from different perspectives:

   * General perspective
   * Instrument Type perspective
   * Target perspective
   * Segment Type perspective


Package Structure
=================

The four perspectives share the same input folder structure::

   ----
   |  |- EDF
   |  |  |- EDFs (e.g. CAL_PLA_IN_SIT.edf)
   ...
   |  |  |- TOP_experiments.edf
   |  |  |- juice__spacecraft.edf
   |  |  |- juice__spacecraft_comms.edf
   |  |  |- juice__spacecraft_platform.edf
   |  |  |- juice__spacecraft_ssmm.edf
   |  |- ITL
   |  |  |- ITLs (e.g CAL_PLA_IN_SIT.itl)
   ...
   |  |  |- TOP_timelines.itl
   |  |  |- downlink.itl
   |  |  |- platform.itl
   |  |- TOP_events.evf
   |  |- downlink.evf
   |- instrument_type
   |  |- EDF
   |  |  |- EDFs (e.g. GEOPHYSICS.edf)
   ...
   |  |  |- TOP_experiments.edf
   |  |  |- juice__spacecraft.edf
   |  |  |- juice__spacecraft_comms.edf
   |  |  |- juice__spacecraft_platform.edf
   |  |  |- juice__spacecraft_ssmm.edf
   |  |- ITL
   |  |  |- ITLs (GEOPHYSICS.itl)
   ...
   |  |  |- TOP_timelines.itl
   |  |  |- downlink.itl
   |  |  |- platform.itl
   |  |- TOP_events.evf
   |  |- downlink.evf


The EDF folder
--------------

Collects the EPS modelling for spacecraft and categories at each level.
The modelling of the experiment is a trivial one with two states (CUSTOM/OFF).
CUSTOM and OFF imply an zero power consume and data rate.

Additionally, there is a basic set that models the JUICE platform:

   * juice__spacecraft_comms: communications (experiment HGA, connected to
     downlink.itl and downlink.evf) drives the simulation of the downlink.
   * juice__spacecraft_platform: platform power (experiment PLATFORM, connected
     to platform.itl) drives the simulation of the power consumption.
   * juice__spacecraft_ssmm: memory storage (experiment SSMM, trivial
     implemention unique partition 900Gbits ) models the solid state mass memory.


The ITL folder
--------------

Collects the segment activity in time boxes and reflects the resource consumption.
The ITL for each category (e.g. GEOPHYSICS.itl) is a sequence of entries with
the following basic format per instance::

   # Experiment GEOPHYSICS
   2030-05-31T09:07:14.000Z GEOPHYSICS # SWITCH_MODE (CURRENT_MODE=CUSTOM [ENG] DATA_RATE_PROFILE= 00:00:00 2020000.0 [bits/sec])
   2030-05-31T09:22:48.000Z GEOPHYSICS # SWITCH_MODE (CURRENT_MODE=OFF [ENG])
   # Duration: 934.0 secs

It reflects the name of the segment, its time boundaries, its duration and the
**data rate** while it is active.

The downlink.itl is a simplified representation of the HGA behaviour, it is
connected to the events stored in downlink.evf

The platform.itl is a simplified representation of the platform power consumption.
It reflects the name of the segment, its time boundaries and the
**power consumption** while it is active.

The platform has a base power consumption (defined in SHT) that applies to the
BASE state.


The Downlink EVF file
---------------------

The downlink.evf is the sequence of DL_START/DL_END events, it is connected to
the behavior expressed in downlink.itl


Resource Priorities
===================

At segment definition level
---------------------------

For a given instrument type:

   * Information provided at instrument level should have highest priority
     (for a given instrument type) and overwrite what is provided at instrument
     type level. the resulting information at instrument type level (in EPS
     package) should consider the combination of all resources provided for
     instruments of a given type (RS: MAJIS, JANUS, UVS, SWI; IS: JMAG, RPWI,
     PEP; GPH: GALA, 3GM, RIME)
   * Information provided for instrument type level should have lowest priority


At segment instance level
-------------------------

**WHEN** a segment instance is updated, all information at segment definitions
are DISREGARDED. All information that should be kept as part of the EPS package
need to be re-entered at instance level.

**THEN**

   * Information provided by instrument should have highest priority (for a
     given instrument type) and overwrite what is provided at instrument type
     level.
   * Information provided for instrument type level should have lowest priority.


At group level
--------------

**WHEN** a segment group instance is created and updated, all information at
segment definitions or segment instance are DISREGARDED. All information that
should be kept as part of the EPS package need to be re-entered at group
instance level.

**THEN**

   * Information provided by instrument should have highest priority (for a
     given instrument type) and overwrite what is provided at instrument type
     level.

   * Information provided for instrument type level should have lowest priority.