E15 Data Processing Issue 6/18/121UVIS Team Meeting

Problem description No match between the FUV data and the minimum ray high from geometer. – several seconds discrepancy. Good match of the HSP data with geometer. We were expecting 379 integrations and only 371 could be found in DAPS. Manual processing the data with the (modified) ATLO code shows the code was skipping one integration every 38 integrations. 6/18/122UVIS Team Meeting

Problem Description The problem seems to have been introduced by a code fixe done 11/98 after ICO. The problem is not restricted to the E15 data set. The problem potentially affects all FUV and EUV data sets. 6/18/123UVIS Team Meeting

Problem Description The data processing code skips integrations. The frequency at which integrations are skipped depends on the instrument setup. For most of the 1-window data set it is 1 integration every 471 continuous integrations or 157 continuous integrations – The E15 set up was a 2-window data set 6/18/124UVIS Team Meeting

Which Data Sets Are Affected All the data set taken continuously with a short integration time can be affected: – Rolling IPHSURVEY (12.5 or 25 seconds integration time for 9 hours). – Some aurora imaging (8.0 seconds integration time for several hours). – All occultation data sets (1 second to 5 seconds integration time). 6/18/125UVIS Team Meeting

Examples Jupiter/Sigma Leo (C23, ) – 1 sec integration, 882 integrations, missing 1 integration (#471) UVIS_157SW_IPHSURVEY004_RIDER (S71, ) – 12.5 sec integration, 2585 integrations, missing 5 integrations (471, 942….) UVIS_157SA_AURSTARE001_PIE (S71, ) – 8 sec integration, 1087 integrations, missing 2 integrations (471, 942) 6/18/126UVIS Team Meeting

Examples UVIS_138SA_USUNOCC001_PRIME (S70, ) – 1 sec integration, 3349 integrations, 7 integrations missing 6/18/127UVIS Team Meeting

Since Last Meeting (1) A yearly list of affected data sets was provided last March (see backup slides) for 2004 to 2011 – Not included in the list are the IPHSURVEYs when the S/C is rolling (that is a large number of data set) – As expected: atmospheric occultation, Icy satellite occultation, some ring occultation, early system scan, some aurora scan – But also all the IMPACT 6/18/12UVIS Team Meeting8

Since Last Meeting (2) The code has been fixed Regression testing is in progress (looks Ok so far) Regression test step 1 6/18/12UVIS Team Meeting9 DAPS Test DB Selected un-affected level 0 files Compare level 1 data set Test successful if 1.Metadata identical 2.Data identical

Since Last Meeting (3) Regression testing step 2 6/18/12UVIS Team Meeting10 DAPS Test DB Selected affected level 0 files Compare level 1 data sets Test successful if 1.Metadata identical 2.Missing integrations are recovered

What’s Next Decide what to re-process Re-process as needed (DAPS) – Alain and Dave Re-deliver the PDS volumes that are affected – Dave 6/18/1211UVIS Team Meeting

Reprocessing Overview 1.Copy current DAPS database to a development database 2.On a sequence basis (or yearly basis) – Delete the affected data sets – Re-process the affected data sets – Verify the integrity of the database 3.When all done copy the development database to the DAPS database 6/18/12UVIS Team Meeting12

Backup Slides 6/18/12UVIS Team Meeting13

2004 6/18/12UVIS Team Meeting14

2005 (1) 6/18/12UVIS Team Meeting15

2005 (2) 6/18/12UVIS Team Meeting16

2006 (1) 6/18/12UVIS Team Meeting17

2006 (2) 6/18/12UVIS Team Meeting18

2007 6/18/12UVIS Team Meeting19

2008 (1) 6/18/12UVIS Team Meeting20

2008 (2) 6/18/12UVIS Team Meeting21

2009 6/18/12UVIS Team Meeting22

2010 6/18/12UVIS Team Meeting23

2011 6/18/12UVIS Team Meeting24