1. ESAC | Chris Watson | ESA/ESAC | Page 1 “Day in the life” testing of LL VMs CHRIS WATSON ESAC

2. ESAC | Chris Watson | ESA/ESAC | Page 2 Day-in-the-life testing In the last teleconference day-in-the-life testing was raised in the context of exposing the pipelines to realistic division of products across pass boundaries. I am going to address this specific situation in this presentation More generally “day in the life” could also refer to wider system-level scenario tests I am not addressing this in this presentation This will be difficult to organise for the low-latency because of the lack of a suitable test source MOC simulator will not produce correctly structured science packet content ETB probably not available to Ops until after launch No FM time allocated for scenario tests

3. ESAC | Chris Watson | ESA/ESAC | Page 3 Day-in-the-life testing SOC focus at the moment is in the testing of individual pipelines (purple boxes) Maybe Instrument team interest is more in the full picture (including the downstream visualisation and distribution)?

4. ESAC | Chris Watson | ESA/ESAC | Page 4 Option 1 - Instrument SFTs, FFTs We will listen-in to these tests (best-effort basis) Where it makes sense to expose some of the data from these test to the pipelines we will do it the datasets are liable to be rather short, given the limits of the SFT, FFTs the datasets are also liable to be rather ”boring”. E.g. Possibly MAG showing stable Earth field Possibly EPD showing zero particle detections Some instruments might have EGSE that allows to give simulated science however Some instruments might generate a “test card” image however We will store the data in order to be able to run the test again at a later date IF we implement the ability to time-shift these data-sets, we can simulate pass divisions, within the limits of the short data sets May not be possible to create a complete pseudo-day for IS in this way for example. We could also do things like creating some artificial packet gaps

5. ESAC | Chris Watson | ESA/ESAC | Page 5 Option 2 – Instrument-team supplied packets If the instrument teams can supply long data sets of simulated LL-science then SOC could potentially form pass-based mock-EDDS retrievals from them, wrapping them in the correct EDDS XML etc. Data sets would have to be supplied as correctly formatted SOLO packets Longer datasets ought to be possible Realistic varying science content ought to be possible N.b. Datasets will not be consistent between different pipelines The more clever we want to be, the more organisation is necessary. E.g. agreeing the attitude / sun-distance etc. in advance.

6. ESAC | Chris Watson | ESA/ESAC | Page 6 Summary Option 2 looks more flexible Option 1 has the advantage that it uses genuine TM from the spacecraft Testing this at SOC isn’t in principle different from tests that could be done on the pipeline by the Instrument Teams, covering e.g. Data gaps Division of products across passes Wider scenario tests would require further discussion