1. CAA PEACE Status A. Fazakerley, B. Mihaljčić, C. Anekallu, N. Doss and Gill Watson MSSL 21 st Cross-Calibration Workshop, Leiden, The Netherlands, 24-26 March 2015

2. Personnel Summary of progress since last meeting PEACE CAA delivery status Software development progress since last meeting Calibration progress since the last meeting PEACE documentation Open Issues Computing Issues Future plans Status of action items MSSL Outline of talk

3. PI: Andrew Fazakerley CAA post: Natasha Doss (On maternity leave from 23 rd April 2014; planned return 01 st April 2015) PLS posts: Gill Watson and Branislav Mihaljčić (PLS funds dropped from 3 FTE to 2 FTE from end of 2013) Supplementary post: Chandrasekhar Anekallu (previous member of the team). Currently effectively provides maternity cover, but can be supported for a tbc period after Natasha resumes work. In post since May 2014 (currently vacationing in India). Funding: currently working without either a CAA contract or PLS team support from ESA MSSL Personnel

4. Summary of Progress Since the Last Meeting MSSL Overview Delivered a further 6 months data Improved coordinate system descriptions in metadata and caveat files Studied how to alter coordinates to ISR2 in re-delivered data (for future mass reprocessing) Responded to FGM changes Completed many actions items Preparations for bulk redelivery 2001-7 requested at last Progress Meeting (3D and PITCH 3D products) to deal with gaps or mismatch in file sizes between units

5. Delivery Progress Since the Last Meeting MSSL Deliveries Summary Delivered all CL-1234 products for Q1/Q2 2013 (up to 30/06/2013) For C3 there are some issues to note C3 stopped operations in dual processor mode on the 27 th of April 2013 at ~16:00. From 28 th April – 22 nd May 2013 there is no C3 science data and fill files were delivered. From 23 rd May 2013 operations for C3 are in single processor science mode; some related software work has been required (see later). Some C3 bit-flip data was not delivered (but should have been delivered with a bad quality indicator) Some products are no longer available, e.g. OMS Delivered CL-1234 Prime Parameter data until end-of-June 2013. Deliveries done to close PEA13-AI-08, PEA14-AI-06, PEA14-AI-17

6. MSSL Deliveries: additional notes MOMENTS: Many missing Burst Modes intervals were delivered following a bug fix in the peacemoments software (for cases of full energy coverage overlap between the sensors). Some intervals still need to be delivered once the related software problem has been resolved (special case of 3DR and 3DX from same sensor, < 150 files per s/c). PITCH family: We re-delivered all PITCH family products for specific dates when FGM has updated their calibrations for C1 (orbits 1450–1462,1641 & 1813-1825) & C3 (orbit 139) Header files: Updated to better reflect coordinate system MOMENTS for C2 are likely incorrect since 2011, as they are based on EFW potential which appears unreliable since 2011. For Q1/Q2 2013 we estimated potential ourselves (slow) 3DX data: We plan to split 3DX* MAR and HAR mode data into separate files. We are piloting the process with Double Star PEACE data. Corresponding PITCH_3DX* files will also be affected. 3DR is not affected.. Delivery Progress Since the Last Meeting

7. Product name20002001200220032004200520062007200820092010201120122013 MOMENTSDDDDDDDDDDDDDPD (June) PITCH_SPINDDDDDDDDDDDDDPD (June) 3DRH/LDDDDDDDDDDDDDPD (June) PITCH_3DRH/LDDDDDDDDDDDDDPD (June) PITCH_FULLDDDDDDDDDDDDDPD (June) PITCH_FULL_LARDDDDDDDDDDDDDPD (June) 3DXPH/LDDDDDDDDDDDDDPD (June) 3DXH/LDDDDDDDDDDDDDPD (June) PITCH_3DXH/LDDDDDDDDDDDDDPD (June) 3DXPAH/LDDDDDDDDDDDDDPD (June) PITCH_3DXPAH/LDDDDDDDDDDDDDPD (June) 3DXPLARH/LDDDDDDDDDDDDDPD (June) 3DXLARH/LDDDDDDDDDDDDDPD (June) PITCH_3DXLARH/LDDDDDDDDDDDDDPD (June) 3DXPALARH/LDDDDDDDDDDDDDPD (June) PITCH_3DXPALARH/LDDDDDDDDDDDDDPD (June) PADMARDDDDDDDDDDDDDPD (June) PADHARDDDDDDDDDDDDDPD (June) PADLARDDDDDDDDDDDDDPD (June) LERH/LDDDDDDDDDDDDDPD (June) NOIH/LDDDDDDDDDDDDDD OMSH/LDDDDDDDDDDDDDD

8. Software Development Progress Since the Last Meeting MSSL CAA Production Software MOMENTS s/w was fixed to allow the production of (most) missing BM intervals PITCH_FULL s/w was for fixed cases of “PAD_PATCH” (LEEA using all PAD TM) PITCH_3DR s/w updated to allow use for post-2012 data Header Production Software Fixed production s/w for PITCH_FULL* family for various bugs (e.g. line breaks) Fixed production s/w so that the coordinate-system variable is now “Instrument” instead of “SR2” while it is “MFA” where applicable. PITCH_FULL and PITCH_3D product Azimuths have “Other” while Pitch Angles have “MFA. Status Flag/Caveat Software Existing status-flag/in-house software was updated to allow CSA downloads Preliminary flag insertion s/w for 3D*, PAD* & PITCH* products is complete Updated Partial Coverage s/w to use EFW CAA potential instead of EFW_PP Cluster caveats s/w was updated to include info on the SR2 coordinate rotation Other Software Design s/w to check CAA files before delivery (e.g. number of records for all units) s/w to remove 1st spin of 3DR & LER data after mode change on C3 (due to single processor operations)

9. Calibration progress since the last meeting MSSL No change since last Cross-Cal workshop. We note that WHI density for magnetosheath intervals is now available through to end Feb 2014. Work will likely resume after Easter when Natasha returns Already Achieved Calibrations version 6.0 covers Jan – Jun 2013 α-factors for all sensors between Jan-Jun 2013 were determined & validated. Cross-Calibration Checks We are now comparing v5.0 and v6.0 alpha factor calibrations during 2001-2004, with detailed cross-calibrations checks between PEACE and WHISPER before any mass-regeneration (in the early years) as we found disagreements. There is evidence that improvements may be needed during some intervals. Work in progress allows comparison of e.g. Natasha’s (v6.0) calibration vs WHI spectra and can be extended to allow check of the original calibration (v5.0) and new versions.

10. Calibration progress since the last meeting MSSL Checking of 2001-4 PEACE calibrations; comparing methods We developed code to allow visualisation of WHI density and PEA density (could be determined in different ways) in relation to WHI spectra available at CSA Upper panel WHI density; lower panel PEA density (assumes “plasma frequency”) Example of good match

11. Calibration progress since the last meeting MSSL Checking of 2001-4 PEACE calibrations; comparing methods We developed code to allow visualisation of WHI density and PEA density (could be determined in different ways) in relation to WHI spectra available at CSA Upper panel WHI density as plasma freq; lower panel PEA density Example of bad match: PEACE density too low

12. Calibration progress since the last meeting MSSL Checking of 2001-4 PEACE calibrations; comparing methods We developed code to allow visualisation of WHI density and PEA density (could be determined in different ways) in relation to WHI spectra available at CSA Upper panel WHI density as plasma freq; lower panel PEA density Example of bad match: PEACE density too high a few days later; MCP levels were raised on April 06th

13. Calibration progress since the last meeting MSSL Checking of 2001-4 PEACE calibrations; comparing methods We developed code to allow visualisation of WHI density and PEA density (could be determined in different ways) in relation to WHI spectra available at CSA Upper panel WHI density as plasma freq; lower panel PEA density Example of bad match: PEACE density seems good, then bad minutes later!

14. Calibration progress since the last meeting MSSL Checking of 2001-4 PEACE calibrations; comparing methods We developed code to allow visualisation of WHI density and PEA density (could be determined in different ways) in relation to WHI spectra available at CSA Upper panel WHI density as plasma freq; lower panel PEA density Example of bad match: PEACE density seems good, then bad minutes later p partial coverage effect tbc

15. Calibration progress since the last meeting MSSL Checking of 2001-4 PEACE calibrations; comparing methods We developed code to allow visualisation of WHI density and PEA density (could be determined in different ways) in relation to WHI spectra available at CSA Upper panel WHI density as plasma freq; lower panel PEA density Example of bad match: PEACE density seems far too low; revisit calibration!

16. The CAA currently has: User Guide to the PEACE measurements in the CAA V2.5 (recently updated) Calibration Report of PEACE measurements in the CAA V1.5 (recently updated) Interface Control Document for PEACE in the CAA V6.4 Interface Control Document for DS PEACE in the CAA V4.1 (not public yet ) CAA-related papers by PEACE team: In-flight calibration of the Cluster PEACE sensors, Doss et al,. gi-2013-21 PEACE data contributions to the CAA, Khan et al., 2005 PEACE data in the CAA, Fazakerley et al., 2010 Cluster-PEACE in-flight calibration status, Fazakerley et al., 2010 The CAA Documentation page provides a link to the PEACE Operations History webpages. No changes yet; but UG/ICD updates will be needed if planned changes are made PEACE Documentation MSSL

17. No computing system failures since last cross-calibration workshop Procurement of a new NAS still ongoing; old machines are out of warranty (we want this machine in place before we start major re-processing work) An IDFS server machine needs replacement Computing Issues MSSL

18. Future Plans (1/2) MSSL 1.Due deliveries Extend the WHI-PEA calibration to winter 2013-4 Deliver CAA data products for corresponding interval Deliver CSDS data products for corresponding interval 2.Relatively minor software fixes MOMENTS when have 3DR and 3DX from same sensor Check/fix zeros in PITCH_SPIN background counts PITCH_SPIN and PITCH_FULL : case of LAR-HAR sensor combination (PITCH_)3DXPA(LAR) azimuths issue 3.Specific Problems broken anodes (CL-3 HEEA and CL-2 LEEA) Decide on approach and redeliver C3/C2 MOMENTS from Aug 2005/May 2011 onwards

19. Future Plans (2/2) MSSL 4.Calibration Corrections to  –factor calibration for 2001-7 where needed (tbc) 5.Bulk regeneration of early mission years to resolve problems with missing data Preparation work : change 3D data to ISR2 coordinates Preparation work : separate MAR and HAR 3D data products (not needed for 3DR) Preparation work : complete preparation of status parameters Preparation work : test 6 p.a. version of PITCH_3DR 6.Inter-anode Calibration Needed for post-2007 data May need improving for pre-2007 data in some cases Large scale re-deliveries are implied whenever a significant calibration change is indicated

20. Based on CAA list of Action Items that are open or not formally closed Action Item Status Summary TypeOpenIn ProgressTo CloseTotal Operations Reviews131 5 Cross-Calibration Meetings22 26 Progress Meetings242430 Total592741

21. Operational Reviews AIs

22. MSSL Status of OR recommendations OR6-R07 to CAA and PEACE Overall, the board is encouraged by the progress made by the PEACE team in the delivery of data. However, the board notes that delivery is still behind the necessary schedule. A specific issue that should be addressed immediately is the implementation of a work-around for the broken anode problem on C3: the board recommends that extrapolation over the broken anode is used for the generation of moments, and fill- values are used in other circumstances. The board encourages (1) the start of the provision of the PITCH_3DX family of data products, and (2) the completion of calibration activities for recent years, both very soon. IN PROGRESS (i) A pilot study in relation to broken anodes has been carried out, please see PPT by Chandra Anekallu (ii) The PEACE team keeps the alpha-factor calibrations as up to date as the availability of supporting datasets allows. The inter-anode calibrations make a more subtle correction that primarily affects the Vz velocity component. The analysis is a challenging activity which will require concerted effort - the last work done on this was incomplete when the person responsible left the team. OR7-R3 to All: The board recommends that instrument teams provide information regarding “special operations”, e.g. special modes, solar wind operations, guest investigator campaigns, etc., including their description and time of operation. The CAA is to coordinate this activity and to make the information available through their web pages. OPEN At present, users may refer to the Cluster PEACE Home Page to find comprehensive commanding information including dedicated lists of when certain types of operation occurred. The PEACE team recognises that a more user-friendly facility is being requested, and is considering how best to achieve this.

23. MSSL Status of OR recommendations OR7-R4 to PEACE: The board recommends that the PEACE team resolves their bad anode problem and spurious 0s in their pitch angle datasets. IN PROGRESS A pilot study has been carried out, see PPT by Chandra Anekallu. OR7-R5 to PEACE: The board recommends that the PEACE team resolves their bad anode problem and spurious 0s in their pitch angle datasets. IN PROGRESS (i) A pilot study is in progress in relation to how best to handle the broken anodes. (ii) There are no longer spurious 0's in the PITCH_SPIN data, following a correction to production software, however it has been suggested that there may be a residual problem affecting the "background" data which remains to be investigated. OR8-R15 to PEACE: The board recommends that all teams investigate data quality at mode changes and instrument switch-on or switch-off.. PROPOSE TO CLOSE (i)There are no specific data quality issues associated with mode changes; typically there is simply a short data gap while the DPU changes its processing activity. (ii)There are no specific data quality issues associated with instrument turn on or off. Science data processing starts some time after turn on, and ends before turn off. (iii)There is a short interval (~30 sec) at beginning of science operations after a turn on during which MCP voltages are raised so that fluxes increase steadily, but it is doubtful that a user would misinterpret this.

24. Cross-Calibration Meetings AIs

25. Status of action items from Cross-calibration meetings MSSL CC12-AI-11 to PEACE: to process datasets for C3-HEEA. For the bad (broken) anode use interpolation. IN PROGRESS A pilot study on how to handle the broken anodes has been carried out, see PPT by Chandra Anekallu. CC19-AI-13 to PEACE: to investigate why four spacecraft show large offset in the solar wind velocity with respect to other spacecraft in 2002 (see e.g. slide 6 in CC19-Annex-28). In addition to investigate if similar situations occur in other years IN PROGRESS The solar wind electron temperature and density are relatively low. The spacecraft potential is relatively high. The distinction between the spacecraft photoelectron and solar wind fluxes is poor. The Status_PartialCoverage flag warns of such cases. CC20-AI-02 to PEACE: reprocess all the datasets that require magnetic field data from the reprocessed FGM intervals (slide 8 of annex 6) PROPOSE TO CLOSE (i)Downloaded FGM daily calibrations files from CSA for C1 (orbits 1450 – 1462, 1641 and 1813 - 1825) and C3 (orbit 139) (ii)(ii) Generated and ingested CFUNIT data for these orbits (iii)(iii) Reprocessed and delivered all PITCH products for C3 and C1

26. Status of action items from Cross-calibration meetings MSSL CC20-AI-16 to PEACE: to investigate if and how the developed inventory tool could be used for their dataset monitoring (see Annex 12) PROPOSE TO CLOSE (i)The MSSL inventory plot tool is used only when investigating small scale specific action items from OR’s, PM’s or xCal meetings and an extension to dataset monitoring would require an extensive design process as there are many PEACE products (ii)Having the CAA dataset monitoring tool helps in the identification of problems as the lists for each product are self-explanatory (iii)We could use the lists as an input to our wrapper software to regenerate the relevant problem dates CC20-AI-20 to PEACE: to explain a large variability in the velocity components (e.g. see comparisons in Annex 15) OPEN CC20-AI-21 to PEACE: to tell the CAA team which of the JSOC datasets and documents can be useful for the instrument teams (think also the post-operations phase) OPEN

27. Progress Meetings AIs

28. MSSL PEA11-AI-13 to PEACE: to check if the merging of the PITCH version of the 3DX and 3DXP datasets is what is wanted. OPEN This is still under discussion PEA12-AI-05 to PEACE: to check why PITCH_SPIN/FULL do not have the same coverage as PAD datasets. Examples from C1: Jan 07, Apr 07, May 07, Jan 08, Feb 08, Mar 08, May 08, Apr 09 IN PROGRESS Regeneration of entire missing days (as for PEA12-AI-02) has corrected some cases. Cases where a HAR/LAR combination or a PADAL pitch angle distribution was commanded cannot be processed with existing codes. Cases where PITCH_FULL is missing, but PITCH_SPIN is available need to be resolved. PEA12-AI-08 to PEACE: to investigate if the mode dataset could be created for PEACE and what information are the most useful/relevant while searching PEACE in a given mode in a given region of OPEN This is still under discussion PEA13-AI-03: to clarify the MOMENTS strategy when only either 3DRH or 3DRL is available, see e.g. C2 on 29 Apr 2001 PROPOSE TO CLOSE The question for this interval should be why 3DXPH and 3DRH (made from 3DXPH) do not appear in the Inventory plot as 3DRH was not commanded during the time in question? So this reverts to a generic missing data issue. As for the specific question, MOMENTS data will be produced using the available 3D data whether or not this provides complete energy range coverage of the plasma. Cases where complete coverage is not available will be flagged by Status_PartialCoverage. Status of action items from Progress Meetings

29. MSSL PEA13-AI-06 to PEACE: to check why some of 3DX pitch family datasets are empty while there are 3D datasets and B-field so that some pitch angle datasets contain data, for examples see e.g. C1- Apr-May 2001 IN PROGRESS This is an extension of PEA12-AI-06 PEA13-AI-07 to PEACE: to check why pitch 3D dataset contains data while the 3D source file has a gap, e.g. Sep 2005; similar situation for 3DR products in Aug - Nov 2009 PROPOSE TO CLOSE (i)This is an extension of PEA12-AI-06 (ii)The affected dates have been regenerated and redelivered to the CAA, ensuring that all units have data with the MSSL inventory plot tool. (iii)(iii) We have regenerated a few examples if 3DR files in Sep 2005 and Aug-Nov 2009 and were able to produce data files with data, which will solve the above problem PEA13-AI-08: to check the production of the datasets on 1 Jan 2004 PROPOSE TO CLOSE Similar to PEA11-AI-10; only MOMENTS and PP are seen in the Inventory plots on all 4 spacecraft. Probably not fixed in earlier “whole day” hole-plugging due to being “partially missing” days. All datasets now delivered. Status of action items from Progress Meetings

30. MSSL PEA14-AI-02 to PEACE: to investigate why the inventory tool used by PEACE does not report on missing files, inconsistencies (some datasets were not reprocessed while this should have been done) etc. PEACE team should run a comparison and see if their results are similar to the CAA Inventory Analysis results in Annex 2. PROPOSE TO CLOSE (i)We do not use the inventory MSSL plotting tool for the entire mission as its very time-consuming and use it only when we investigate action items set at meetings, to see detail. (ii)Instead, we have simple perl codes that search for CEF files that were not made AND also report on the file-size, which can be run for different units. (iii)We cannot not run a like-for-like comparison with CAA Inventory analysis, but we have compared file- size information for a few cases, which seems to be the same (iv)We have recently developed a code to also compare the number of records in each unit. PEA14-AI-04 to PEACE: to consider using the same version number for the different units of the same dataset type (e.g. PITCH_SPIN) for the given day. This is because if a regeneration was done, all units should have been regenerated. If this was not the case, it was a processing/delivery/ingestion error. Currently the version numbers are out of sync, so it is recommended that when the next regeneration is done, all units are regenerated and their version number is higher than the highest version number currently by 1. Note that the version numbers of different days do not need to be the same PROPOSE TO CLOSE The PEACE team agreed (at the last Progress Meeting in Nov 2014) to use the highest version number for ALL units for either only a given date or when delivering in bulk. Status of action items from Progress Meetings

31. MSSL PEA14-AI-06 to PEACE: (3DRH/L) to produce the files in COUNTS for 2009 Aug-Nov (see inventory lists in Annex 2). PROPOSE TO CLOSE The CL-1 data files for 3DRH/L were regenerated in counts units as version 7 and re-delivered. PEA14-AI-07 to PEACE: (3DRH/L) to check why some units have different record numbers in some days of 2008-9 (see inventory lists in Annex 2). PROPOSE TO CLOSE The number of records in each file was obtained and checked against the list provided in Annex 2 of the 14 th Progress Meeting and were found to match exactly. Hence regeneration has fixed the problems and now the version number and the number of records match exactly for all units. No redelivery yet PEA14-AI-08 to PEACE: (3DXH/L) to check why some days of 2009 (C2-3), COUNTS are empty while the other units contain data (see inventory lists in Annex 2). PROPOSE TO CLOSE Regeneration of few 3DXH/L test dates from Annex 2 lists for C2 and C3 have shown that the files can be made successfully and the number of records agrees exactly with other units, which solves the problem. PEA14-AI-09 to PEACE: (3DXPH/L) to check why some days of 2009 COUNTS files are empty while the other units have records (see inventory lists in Annex 2). PROPOSE TO CLOSE Regeneration of a few 3DXPH/L test dates from Annex 2 lists for C1, C2, C3 and C4 have shown that the files can be made successfully, so that all units have the same number of records, which solves the problem. Status of action items from Progress Meetings

32. MSSL PEA14-AI-10 to PEACE: (PITCH_3DRH/L) to check why the record numbers do not match between different units for some days in post-2007 era. PROPOSE TO CLOSE Regeneration of a few PITCH_3DRH/L test dates showed that the files can be made successfully without errors, which solves the problem. PEA14-AI-11 to PEACE: (PITCH_3DRH/L) to check why some files in PSD were not regenerated in Nov 2010-11 PROPOSE TO CLOSE These files were generated, but not delivered for some reason, although many seem to be in our repository; hence in the next mass-regeneration effort we can deliver all units with a higher version number. PEA14-AI-12 to PEACE: (PITCH_3DXH/L) to check the processing errors (see inventory lists in Annex 2). They include record number errors and version number errors (no regeneration done for some units). PROPOSE TO CLOSE From the Annex 2 listing the C2, C3, C4 spacecraft had the version issue in PITCH_3DRH or PITCH_3DRL during 1 st -30 th Nov 2011, for example. Namely, all units have identical number of records, except that various units may not have the same version number. Hence, there is nothing wrong with the data apart from the version number. Future regeneration in all units will have the same version number as agreed in action item PEA14-AI-04. For other cases the number of records does not match, however recent test on example cases have shown that all units can be made with the same number of records, which will solve this problem. Status of action items from Progress Meetings

33. MSSL PEA14-AI-13 to PEACE: (PITCH_3DXLARH/L) to check the processing errors (see inventory lists in Annex 2). They include record number errors and version number errors (no regeneration done for some units). PROPOSE TO CLOSE Regeneration of random example dates confirms that all units can be made with the same number of records, which will solve this problem. PEA14-AI-14 to PEACE: (PITCH_3DXLARH/L) to check the record number errors (see inventory lists in Annex 2), they appear in five days for C3 in 2011 PROPOSE TO CLOSE Regeneration of random example dates confirms that all units can be made with the same number of records, which will solve this problem. PEA14-AI-15 to PEACE: (PITCH_FULL) to investigate why files became empty during reprocessing while earlier versions had full of data (C4, 2009/04/02) PROPOSE TO CLOSE In our repository we have C4 PITCH_FULL files V02 for 2009-04-02 in all units with the same version number and number of records (9370 records), so it’s possible that during a transfer to the CAA a glitch may have occurred. PEA14-AI-16 to PEACE: (PITCH_FULL) to investigate the record number differences between units; many files were generated very recently (see inventory lists in Annex 2) PROPOSE TO CLOSE We have investigated a random date 2012-11-30 for C1 in our repository and we can confirm that the records for PSD are zero (i.e. empty) when they should have been 5092, just as the Annex 2 listing is showing. Having regenerated PITCH_FULL in PSD units for the same date the file is now full of data and has 5092 records, so this problem can be solved by regeneration. Status of action items from Progress Meetings

34. MSSL PEA14-AI-17 to PEACE: (PITCH_FULL_LAR) to investigate why the PSD file is empty while the other units contain data (C1 on 2000 Dec 22) PROPOSE TO CLOSE All units were regenerated successfully and redelivered to the CAA with the same number of records (16121 records) and all with the same version number as V02. PEA14-AI-18 to PEACE: to perform a full inventory of PITCH_SPIN. Reprocess everything for 2001-7 and in later years the days with missing files, different calibration versions, different record numbers IN PROGRESS Preparations are underway to first check why there is a difference in C1, C2, C3 and C4 calibrations (for some cases) between v5 (based on MCP tests) and v6 (based on comparisons between PEACE and WHISPER densities) for years 2001-2004 before mass-production takes place. PEA14-AI-19 to PEACE: to investigate why MOMENTS do not exist while the other datasets exist. Plenty of intervals exist, but here are a few examples: C1 on 7-8 and 21-22 Mar 2001 and 6-7 Aug 2002 IN PROGRESS (i)The burst mode software fix (when both sensors have the same energy overlap) we applied previously to peacemoments has fixed the majority of cases, which were redelivered to the CAA. (ii)The particular dates mentioned above are part of those cases we have not fixed yet as they don’t seem to fall into the same category as the previous fix. Upon closer inspection these cases seem to have a mixture of 3D data collected simultaneously from the same sensor. A software fix for these cases is now being sought. Status of action items from Progress Meetings

35. MSSL PEA14-AI-20 to PEACE: to investigate why PITCH_3DRH/L are empty while all input datasets have records. Plenty of intervals exist, but here are a few examples: C1 on 2-3 Apr, 31 Jul, 2 Aug 2001, and 9 and 15 Aug 2002 PROPOSE TO CLOSE (i)We were able to regenerate the above mentioned example dates in all units when PITCH_3DR was missing, except when there was no data. (ii)For the dates in 2001 we found that 3DR IDFS data was partially missing. (iii)For the dates in 2002 the 9th of Aug has 3DR data is missing in IDFS and for 15 Aug we could regenerate PITCH_3DR for the entire day in all units. (iv)Hence, some data gaps in our IDFS database still exists, which need to be fixed. PEA14-AI-21 to PEACE: to check why PITCH_SPIN has gap while PITCH_FULL has data. Plenty of intervals exist, but here is on example: C1 on 11 Feb 2002 PROPOSE TO CLOSE (i)We compared the February 2002 Annex 3 inventory plot from the 14th Progress Meeting and the CSA inventory plot for this date and can confirm that they agree. (ii)Namely, PITCH_SPIN has no data between 00:00-18:00, but there is data from 18:00 to 24:00, while PITCH_FULL has data for the entire day. (iii)PITCH_SPIN data files in all units at MSSL have also missing data between 00:00-18:00. (iv)We reprocessed this date and were able to successfully regenerate data in all units with data starting from 00:07:57 until 23:59:48 with a total of 21359 records per data file, so this problem can be solved by regeneration in the next mass-production effort. Status of action items from Progress Meetings

36. MSSL PEA14-AI-23 to PEACE: to check why 3DX file is empty while the corresponding PITCH 3DX dataset has records. Several intervals exist, but here is on example: C1 on 27 Feb 2002 PROPOSE TO CLOSE (i)We compared the February 2002 Annex 3 inventory plot from the 14th Progress Meeting and the CSA inventory plot for this date and they do agree, namely, there is PITCH_3DXL data between (~16:00- ~20:00 on 27-Feb-2002), but no 3DXL data in the inventory plots for 2002-02-27, but please see next comment about commanding. (ii)CL-1 PEACE was commanded into 80m20-68m08-cplxt-apl-60w08 (from 16:10-20:10), this means, that we should have for cplxt: CORE, PAD, LER, 3DX from LEEA and 3DR from HEEA, but as we also have apl: all basic segments, add together pairs of anodes and data is from LEEA, which means we should have 3DXPL only for LEEA. (iii)So, not having any 3DX(L) is justified, but we are missing 3DXPL on the inventory plots. (iv)However, when we reprocessed 3DXPL from scratch, we could make CAA files in all units with the same number of records (3576), therefore in the next mass-regeneration this problem will be solved. PEA14-AI-24 to PEACE: (MOMENTS) to clarify why duplicate time stamps occur (removed) and why time stamp sorting is necessary. Do duplicate time stamps have identical or different records, and if the latter, which one is removed? PROPOSE TO CLOSE (i)The “peacemoments” software does not make a 24-hour file immediately; instead it makes small moments files for each 3DR or 3DX interval when PEACE was commanded. (ii)The many small files sometimes have one overlapping timestamp in the last record, which is identical to the first timestamp record in the next small moments file. (iii)The data from all the small files is then gathered into one 24-hour MOMENTS file, BUT the data is not in the first instance gathered in time order. (iv)Hence, for this reason any duplicate timestamps are removed and then all timestamps are sorted in ascending time order. Status of action items from Progress Meetings

37. MSSL PEA14-AI-25 to PEACE: to use only CAA EFW_L3_P data; note that PP has significantly lower quality and much more data gaps than CAA files PROPOSE TO CLOSE (i)The Cluster partial coverage status flag software was updated to use EFF CAA potential instead of the EFW PP potential. (ii)Partial coverage status flag regeneration for 2001-2013 has been completed. PEA14-AI-26 to PEACE: to note that FGM science datasets have unintentional data gaps which will be filled in in near future. This will cause modifications in GAPF and VALF files, and thus also in Status_FGM flag. Note also that PEACE has B-field data in these gaps as it uses software and RDM data and not the CAA files. PROPOSE TO CLOSE (i)We have modified our software to download the GAPF and VALF files from CSA (rather than CAA) for the entire mission (ii)We have regenerated the status FGM flags for the entire mission PEA14-AI-27 to PEACE: to update the 3D dataset header: ref frame = other, caveats explain the details on how to present data in SR2. However, in future one should remove the time dependence in the datasets and use ISR2 coordinate system as CIS uses PROPOSE TO CLOSE (i)Metadata corrections have been applied to the Cluster II header files and delivered (ii)Cluster II caveats now have details on how to convert to the SR2 frame of reference. Status of action items from Progress Meetings

38. MSSL Thank you for listening!