20 th CAA Cross-Calibration Workshop MPS, Göttingen, Germany Oct ESOC datasets

20 th CAA Cross-Calibration Workshop MPS, Göttingen, Germany Oct CAA Action Items on ESOC Datasets

20 th CAA Cross-Calibration Workshop MPS, Göttingen, Germany Oct ESOC Archives  ESOC source datasets contain following files:  Documents in pdf  Digital data in xls or txt  Some datasets are based on a single file that is updated annually  Most digital ESOC files have been converted into CEF by CAA  6 documentation categories of miscellaneous sets of documents  These appear in the normal CAA document area  Weekly and monthly reports are ingested as non-CEF datasets

20 th CAA Cross-Calibration Workshop MPS, Göttingen, Germany Oct ESOC Documentation Note: AGC fluctuation intervals will be taken out from the weekly reports for a digital AGC_Fluctuations dataset Documents are not up-to-date as the current documentation was received in 2007

20 th CAA Cross-Calibration Workshop MPS, Göttingen, Germany Oct ESOC Anomaly Reports  Timing of anomalies is non-trivial because it is not always clear when they started and ended, and most importantly, some of them are reoccurring  Most likely user wants to find anomaly report according to other reasons than its exact occurrence time Key path to an anomaly report is weekly reports where the anomalies are reported and discussed (and Anomaly Report Number is given): user wishes to read Anomaly Report #NNN  ESOC maintains a large excel sheet on anomaly maintenance, see underneath the first few columns of their table CAA has created a simple xml table for the access of anomaly reports

20 th CAA Cross-Calibration Workshop MPS, Göttingen, Germany Oct ESOC Anomaly Reports  Only key parameters are listed in order to keep the table concise  Behind ID number there is a link to the anomaly report (in pdf)  It is expected that the new anomaly reports are forwarded to the CAA once a year  Page is available under ESOC Documentation

20 th CAA Cross-Calibration Workshop MPS, Göttingen, Germany Oct Eclipse Dataset  Source dataset was changed; now the dataset is based on the FD files o C[n]_CP_AUX_ESOC_FD_ECLIPSE o Parameters are  Penumbra_entry (=time_tag)  Umbra_Entry  Umbra_Exit  Penumbra_exit  Duration_eclipse  Duration_umbra  Moon  Umbra  MinAngle

20 th CAA Cross-Calibration Workshop MPS, Göttingen, Germany Oct RUN ON 2008/10/14 AT 10:04:38 Z INPUT: EXPECTED SATELLITE ID = 1 INPUT: START TIME OF ECLIPSE SEARCH = 2008/12/28 00:00:00 INPUT: NUMBER OF HOURS TO SEARCH = 24 DETAILED PRINT OF ECLIPSE OF SUN BY MOON & EARTH ================================================ DISTANCE FROM (KM, NEGATIVE = INSIDE) VISIBLE TIME MOON PENUMBRAUMBRA EARTH PENUMBRA UMBRA FRACT. ================================================================================= 2008/12/28 0: 0: 0 START OF ECLIPSE SEARCH NO ECLIPSES 2008/12/28 15:11: /12/28 15:12: /12/28 15:13: /12/28 15:14: /12/28 15:15: /12/28 15:16: /12/28 15:45: /12/28 15:46: /12/28 15:47: /12/28 15:48: New dataset: Eclipse Profiles

20 th CAA Cross-Calibration Workshop MPS, Göttingen, Germany Oct ESOC Archive: Spacecraft Telemetry Mode (TDA)  The mode dataset is currently created from the AUX dataset (1-min resolution); the dataset is called TMMODE  These data are created in HDC and the values are based on RDM/CMDH files although the values are compared with TDA dataset  If there is a difference larger than 1-2 mins between the command giving (CMDH) and the execution time (TDA_MODE file), TMMODE value is corrected  ESOC TDA dataset seems to give a better time resolution although it does not represent the timing of the mode changes because subsystems and instruments are handled individually.  SPEVAL and TDA dataset have somewhat different values and ESOC does not recommend to use TDA values

20 th CAA Cross-Calibration Workshop MPS, Göttingen, Germany Oct Command History Files (from SPEVAL) The printout is made once a year (TBC), so Line number is a running number of command in the given year The file is saved as daily non-CEF files in order to keep the structure which helps reading the parameters If necessary, the dataset could be converted into CEF dataset where the last parameter gives all the parameters separated by semi-colon