daa peace status a. fazakerley, b. mihaljčić, i. rozum, a. lahiff, g. watson, d. kataria ucl...

DAA PEACE Status

A. Fazakerley, B. Mihaljčić , I. Rozum, A. Lahiff, G. Watson, D. Kataria

UCL Department of Space and Climate Physics

Mullard Space Science Laboratory

CAA Cross Calibration Meeting 15, UCL, UK, 19th April 2012

DAA Progress Summary: (1) Missing Data

• DS IDFS and DAA codes have been ported to the dedicated PEACE Operations computer system (“NAS”)

• DS IDFS data (3DF and RPAD) have been regenerated on the NAS using both the original and new raw IDFS datasets. (Just as for Cluster, we think there were problems leading to missing IDFS data on the SAN)

• These problems apparently lead to some confusion and an incorrect presentation on missing PEACE data at the previous (York) meeting


2

DAA Progress Summary: (2) Production Software Testing

• Using the original raw dataset, we have generated DAA PITCH_SPIN for the full mission.

• As FGM science data from the new G version was not available (de-spiked etc) so we couldn’t make PITCH_SPIN for the “G” data yet

• A PhD student is working on a statistical study with DAA PITCH_SPIN data, which has the useful side-effect of providing a cost-effective way to identify possible problems with the dataset.


3

DAA Progress Summary: (3) Summary Plots

• Summary plots of the IDFS data are being produced from the “original” and “reprocessed” datasets to assist in planning how to merge the datasets for DAA production purposes

• Due to continuing non-availability of DSDSWeb coverage for the mission, PEACE summary plots with some DSDS PP data included have been made available on the MSSL website


4

DAA Progress Summary: (4) Calibration

• A study of these variations of MCP sensitivity with time has been completed, based on results from weekly MCP tests. The calibration study used magnetosheath density estimates from HIA as a relative cross-calibration, in the absence of absolute density values from WHISPER.

• The calibration files currently in the IDFS database do not contain this information, however work is in progress to transfer this knowledge to the calibration files.

• (Note the DAA PITCH_SPIN test dataset mentioned earlier will be regenerated later using the improved calibrations)


5

DAA Open Work:(1) Decide how to combine the two raw datasets (include Status flag to show origin,

possibly spin by spin)(2) Check how well DAA PEACE production software handles noisy data (e.g. does it

ever lose synchronisation of high energy spins vs low energy spins) and improve codes where possible else provide Status flag warning of bad data

(3) Develop validation software for 3DF(4) Produce, validate, deliver 3DF dataset (including fill files as appropriate)(5) Possible software modifications to use DAA produced high resolution magnetic

field datasets in pitch angle production codes for IDFS and hence DAA PEACE files

(6) Develop validation software for PITCH_SPIN(7) Produce, validate, deliver PITCH_SPIN dataset (including fill files as appropriate)(8) Provide improved spacecraft potential estimates where possible (needed for

moments production)(9) Develop validation software for MOMENTS(10)Produce, validate, deliver MOMENTS dataset (including fill files as appropriate)(11)Following deliveries of these products, return to e.g. secondary code products

(3DR, PAD) if resources allow(12) Provide DAA Documentation updates as needed


6

7

Mission Operations History

TC-1 Timeline

Launch 29 Dec 2003Comm./non- EPOS Ops 26 Jan – 01 Mar 2004Last data 28 Sep 2007Re-entry 14 Oct 2007

TC-2 Timeline

Launch 25 Jul 2004Comm./non- EPOS Ops 30 Jul - 06 Sep 2004Major data gap Aug-Dec 2007Major data gap Feb-Mar 2008Last data 03 Aug 2008

There are “known” time intervals (sometimes > 1 day) for which data return was unsuccessful and the data is missing.


8

Data Return History

There are “known” time intervals (sometimes > 1 day) for which data return was unsuccessful and the data is missing.

TC-1

Missing Days in latest PEA datared means DOMC reported a reason for no data that day (no reports after Oct 2005)

15-7 & 25 Feb 2004 ( pre-JSOC ops)18 Jun 200422 Oct 200409 Dec 200416 Aug 200521-5 Oct 200511 Nov 200515 Feb 200614 May 200607-11 Jun 200629-30 Aug 200611 Feb 200719 Aug 200717-9 Sep 200723 Sep 2007

TC-2

Missing Days in latest PEA datared means DOMC reported a reason for no data that day (no reports after Oct 2005)

8-9 ; 21-4 Oct 200516-7; 23; 27-29; 29-30 Aug 200623-5, 30 Sep 200612-13 Oct 200609 Dec 200609, 13-7; 23-6 Feb 200705-7; 14-16 Mar 200711 May 200708 Jul 2007

04-6 Aug 2007 and 08 Aug- 17 Sep 2007

25 Jan - 14 Feb 2008 and 08-23 Mar 2008

02 May 200826 -9 Jun 200804-28 Jul 2008


9

Checking if PEACE data exists, at times for which operations of PEACE were commanded

We have determined the number of total seconds each day that we expect to get Science (SCI) and Housekeeping (HK) data based on commanding files in Double Star PIORs

Note that during real time contacts we may get HK (including energy spectra summed over anodes). If the science data taken at those times is later lost, these data could be of some interest.

As a rough measure of telemetry noise problems, we counted the number of seconds for which a selected HK parameter gave values that were different from the allowed values for that parameter.


10


TC-1

Data return checks on the original and new raw datasets, and comparing which has more data on each day


11

TC-1: Housekeeping Data Assessment

Reprocessed (G version, Sep 2011)

Original (ABCDetc version Sep 2011)

Change: Reprocessed minus Original

Better

Worse

New version of raw data is more complete but in some cases the original is more complete; => some merging of the two is needed


12

TC-1: Science Data Assessment

Better

Worse

Expected data gap






13

TC-1: Noisy Data Assessment

Worse

Better

At times when both original and raw datasets exist, we should compare the noise level and pick the least noisy





14


TC-2

Data return checks on the original and new raw datasets, and comparing which has more data on each day


15

TC-2: Housekeeping Data Assessment

Better

Worse

Expected data gap

After last contact






16

TC-2: Science Data Assessment

Better

Worse




Expected data gap

After last contact



17

TC-2: Noisy Data Assessment

Worse

Better




Expected data gap

After last contact

At times when both original and raw datasets exist, we should compare the noise level and pick the least noisy


daa peace status a. fazakerley, b. mihaljčić, i. rozum, a. lahiff, g. watson, d. kataria ucl...

Documents