1. CAA PEACE Status Andrew Fazakerley, Natasha Doss, Branislav Mihaljčić, Chandrasekhar and Gill Watson MSSL 20 th Cross Calibration Workshop, Gottingen, Germany, 15-17 October 2014

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) PLS: Gill Watson and Branislav Mihaljčić (PLS funds dropped from 3 FTE to 2 FTE from end of 2013) An additional person has been recruited, using unspent and internal funds. Chandrasekhar Anekallu, effectively provides maternity cover initially, but can be supported for a while longer even when (if) Natasha resumes work MSSL Personnel

4. Summary of Progress Since the Last Meeting MSSL CAA Regenerated Status_PADSelectionQuality flags between 2001-2012 for all spacecraft to also include times when PAD_PATCH was run. Updated production software for PITCH_FULL to insert correct HEEA azimuth values and the correct azimuth when PEACE is in HAR mode for HEEA & LEEA. Redelivered CL-1,2,3,4 PITCH_FULL datasets for Jan 2001 - Dec 2012 Updated CL-1,2,3,4 our FGM cal files for dates when FGM calibration has changed. Redelivered all CL-1,2,3,4 datasets for dates when FGM calibrations were updated Delivered CL-1,2,3,4 MOMENTS data for all spacecraft for year 2000 Checked all headers for all products, spacecraft, units and corrected some aspects Calibrations Work has finished on producing alpha-factors v6.0 for Jan – Jun 2013 IDFS_ARCHIVE Currently in the public IDFS archive: VIDFs v5.2/v5.3 – from start of mission till 31-12-2007 VIDFs v6.0 – from 01-01-2008 till 31-12-2012

5. PEACE CAA Delivery Status (excluding 2000 data) MSSL All Products: No change since last xCal meeting; bulk deliveries made through to end 2012 Completion of deliveries of data from 2000 (we had to produce our own FGM PP style data files for certain dates in order to facilitate this)

6. Software Development Progress Since the Last Meeting MSSL Updated Status_PADSelectionQuality flag production software to incorporate flags that are made during periods when PAD_PATCH was also run. Updated CAA Cluster production software for PITCH_FULL to insert correct Sweep_Azimuth and its DeltaUpper/DeltaLower values for HEEA azimuth values as well as to insert correct SweepAzimuth when PEACE is in HAR mode for HEEA and LEEA sensors. Developed software to download new FGM calibration files from CAA to make daily FGM calibration files for CL-1234 Work on fixing and testing the Status_ASPOC flag in peacemoments software for Cluster and Double Star has been completed. Updated the Cluster CAA production software to extend the derivation of the Sun-Pulse information beyond 2012 Updated CAA MOMENTS production software for Cluster to include selection of unique timestamps (eliminating duplicates) and the ability to sort timestamps

7. Calibration progress since the last meeting MSSL Calibrations version 6.0 extended to cover Jan – Jun 2013 LEEA and HEEA alpha factors for all spacecraft and sensors between Jan-Jun 2013 have been determined and validated. NOTE 1: Good calibration intervals were available for all spacecraft between Jan-Jun 2013, after which the dawn magnetosheath season ended for all spacecraft – calibration estimates for the magnetotail season need to be interpolated using data from the dusk magnetosheath that is not yet available NOTE 2: C3 is in single processor mode after 17 May 2013, but we still get 3D data for HEEA and LEEA to enable calibration work, although we have some constraints on 3D data availability. NOTE 3: For C2 calibration between Jan-Jun 2013 we adjusted the EFW potential manually NOTE 4: C2 calibration between 21-Apr-2011 to 31-Dec-2012 will have to be redone as we have found that the EFW potential is incorrect, see examples in PPT by Chandra Anekallu.

8. Key: V6.0 alpha factors V5.2 alpha factors MCP operational level changes Thruster firings All LEEA sensors show significantly reduced sensitivity. The least sensitive is C3 LEEA Alpha (op level) as at 2013-06-30 to 08-31: C1 ~ 0.2016 C2 ~ 0.1339 C3 ~ 0.0439 C4 ~ 0.1273 Cluster-1 LEEA Cluster-2 LEEA Cluster-3 LEEA Cluster-4 LEEA Plots show comparison of v5.2 & v6.0 α-factors for LEEA sensors for Jan 2007 to Jun 2013 NOTE: The alpha-factor values are interpolated from the last interval on the 30-Jun-2013 to 31-Aug-2013 for all spacecraft except for C3. For C3 the last interval was in early May 2013.

9. Key: V6.0 alpha factors V5.2 alpha factors MCP operational level changes Thruster firings All HEEA sensors show significantly reduced sensitivity. The least sensitive is C3 HEEA Alpha (op level) as at 2013-06-30 to 08-31: C1 ~ 0.1260 C2 ~ 0.2098 C3 ~ 0.0353 C4 ~ 0.1412 Cluster-1 HEEA Cluster-2 HEEA Cluster-3 HEEA Cluster-4 HEEA Plots show comparison of v5.2 & v6.0 α-factors for HEEA sensors for Jan 2007 to Jun 2013 NOTE: The alpha-factor values are interpolated from the last interval on the 30-Jun-2013 to 31-Aug-2013 for all spacecraft except for C3. For C3 the last interval was in early May 2013.

10. 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 y et) 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. PEACE Documentation MSSL

11. Issues affecting the quality of the PEACE dataset PEACE-centric CL-3 HEEA bad anode 3 (from 22 August 2005) CL-2 LEEA bad anode 2 (from 15 May 2011) A pilot study on how to handle the broken anodes has been carried out (see PPT by Chandra Anekallu) Penetrating radiation during some perigee passes (cleaning is possible) Required input information from other teams (info from CAA) WHISPER densities – available till end of Oct 2013 (dusk ‘sheath starts late Nov) EFW data – available till end of Jun 2014 AUX SUMMARY – available till end of Sep 2014 FGM cal files – available till end of May 2014 MSSL Open Issues

12. NAS1: One physical disk failed and was replaced with no data loss. NAS2: The server operating system software failed. It was successfully repaired, but nevertheless data was lost, specifically the entire PITCH family (resolved files, VAL files and plots). NAS3 : Three disks physical disks failed in succession, and hence data was lost. This included MOMENTS files for all years and spacecraft, resolved CEFs, plots and VAL files for all products, spacecraft and units. Recently, another physical disk failed, but RAID was successful so no data loss occurred. NAS4 and NAS5: No change These problems consumed team effort, which delayed direct CAA work. Several of the NAS systems are out of warranty. Replacement hardware is being sought. Due to the Shellshock Bash vulnerability we had to update all our NAS servers and updates to our SAN servers are in progress. Older machines that underpin the IDFS system require replacement (risk of system downtime) Computing Issues Since the Last Meeting MSSL

13. Future Plans MSSL 1.Calibration extend cross-calibration work for rest of 2013 finish v6.1 inter-anode calibration for 2005 – 2008 extend v6.1 inter-anode calibration to 2009 – 2012 extend v6.0 to 2000 – 2004 2.Short-term work Check/fix zeros in PITCH_SPIN background counts Fix LAR-HAR problem in PITCH_SPIN and PITCH_FULL Produce 4/8 azimuth version of (PITCH_)3DXPA(LAR) and deliver Produce 6 p.a. Version of PITCH_3DR and deliver. 3.Produce version of CAA production codes that work with data from C3 PEACE single processor 4.Status parameter completion. 5.Deliveries: Produce and deliver 2013 data products when possible 6.Deal with problem of broken anodes (CL-3 HEEA and CL-2 LEEA) – redeliver C3 MOMENTS from 2005 onwards when we decide how to best deal with the problem. 7.When calibration v6.1 available regenerate and deliver all datasets (2000 – latest data) with the latest calibrations and status parameters.

14. Based on CAA list of Action Items that are not formally closed Action Item Status Summary TypeOpenIn ProgressTo CloseTotal Operations Reviews241014 Cross-Calibration Meetings02810 Progress Meetings341522 Total5103348

15. Status of action items from Cross-calibration meetings MSSL CC12-AI-11 to PEACE (due 30-10-2010): 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. CC17-AI-2 to All (due 15 May 2013): to investigate how to implement the time glitch information described in ESOC anomaly report in the instrument processing software IN PROGRESS Detailed checks were made on a number of cases and often, but not always, there are missing PEACE distribution data. The mistimed data seems to be well handled by our processing software. Surprisingly, sometimes PEACE does not show a gap when CAA report a gap, e.g. C2 2005-10-15 21:28:31-41. Further investigation is required. CC17-AI-5 to PEACE (due 15 May 2013): to consider to use both HIA and WHISPER to identify suitable intervals for the determination of alpha factors in 2001-2004, i.e. only the data points where the two measurement are near to each other are used. PROPOSE TO CLOSE This action arose because PEACE-LEEA/WHISPER comparisons gave poorer agreement with PEACE calibrations based on the weekly MCP test method than in later years. One possibility we considered was that earlier years WHISPER data was less reliable than in more recent times. A comparison with HIA might help to support or rule out this scenario. So we intend to look at HIA/WHISPER comparisons provided by CAA for time intervals that we have used for PEACE/WHISPER comparisons already. A comparison between PEACE/WHISPER and PEACE/HIA moments has now been done for select dates between 2001 and 2004 and reported at this meeting (Cross-Cal 20).

16. Status of action items from Cross-calibration meetings MSSL CC18-AI-8 to CIS, PEACE, RAPID (due 30 Nov 2013): to investigate how to ensure that PAD and MOMENTS are regenerated if new FGM science files are redelivered. This can be done using command-line tool using ingested since flag. PROPOSE TO CLOSE PEACE PITCH* production uses FGM CoI codes not CAA FGM data, so this is not literally applicable to PEACE, however we have looked at updated FGM calibration files and our study has revealed that in the majority of the cases there is a significant change in term of the accuracy we need for pitch angle production. We have subsequently updated calibration files with information from CAA FGM calibration files and have regenerate/validated and delivered the select dates for all the PITCH* family including MOMENTS. CC18-AI-13 to All (due 30 Nov 2013): to use a file listing flag in command line to get a listing of active files on the CAA. PROPOSE TO CLOSE We have rediscovered this option thanks to this action (it is used in some of our automated software written by earlier team members that checks file holdings at CAA). CC19-AI-01 to All: Check that the headers are complete and correct. This concerns particularly various descriptions in different levels (experiment, instrument, dataset). PROPOSE TO CLOSE The experiment/instrument/dataset description headers have been checked and updated where necessary. The main change was to update email addresses. Updated headers have been submitted to CAA CC19-AI-04 to All: To reprocess the pitch-angle products for the reprocessed FGM dates (see slide 7 of annex 7) PROPOSE TO CLOSE See CC18-AI-8

17. Status of action items from Cross-calibration meetings MSSL CC19-AI-07 to PEACE: to provide the DWP team with a source code of the software required to read PEACE HK data (both CLUSTER and DOUBLE STAR) PROPOSE TO CLOSE We have provided the required software and DWP have confirmed that it was effective. 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 PROPOSE TO CLOSE 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. CC19-AI-16 to PEACE: to study if the intervals like 4 Mar 2002, 0-1 UT are flagged as a poor quality interval for moments PROPOSE TO CLOSE This interval is flagged Quality = 3 in existing files. Status_PartialCoverage will provide a warning for this period and the Quality flag will hence be set to Quality = 2 in a future release of this and similar intervals.

18. MSSL PEA11-AI-10 to PEACE (due 15-02-2012): to check why all except MOMENTS have missing files, e.g. 16 Aug 2003, 27 Feb 2005, 9 Nov 2005, 22 Dec 2006, 1 Jan 2008 PROPOSE TO CLOSE See response for PEA12-AI-02. PEA11-AI-13 to PEACE (due 15-02-2012): to check if the merging of the PITCH version of the 3DX and 3DXP datasets is what is wanted. OPEN PEA12-AI-02 to PEACE (due 15-12-2012): to check why a large number of datasets were not produced. Examples from C1: Aug 03, Jan 04, Feb 05, Nov 05, Dec 06, Jan 08, Dec 08. PROPOSE TO CLOSE Lists have been produced for all spacecraft, for all products (except MOMENTS), for all units, for entire days (not partial days) where we are missing a file in our repository. All missing days for all products & units for C1,2,3,4 have been regenerated. Validation checks for the specific days noted above were successful, and many more days were corrected. The root cause of the gaps is thought to be holes in our IDFS database that were fixed in Autumn 2010, but only after the affected files had been delivered to CAA. Problems with partial days remain, which should be handled under PEA13-AI-08. Status of action items from Progress Meetings

19. MSSL PEA12-AI-03 to PEACE (due 15-12-2012): to check why MOMENTS files were not complete (e.g. compared to PITCH datasets). Examples from C1: Jun 04, Jul 04, Nov 05, Dec 05, Feb 05, Jul 06, Apr 07, May 07, Nov 07, Feb 08. PROPOSE TO CLOSE As noted under PEA12_AI-02 there have been problems with our IDFS database, which are now corrected. Missing data (entire days, not partial days) for C1 2001 – May 2008 have been produced and delivered to the CAA. Fill files were also produced as necessary and we have ensured that daily MOMENTS files rather than partial day files have been delivered. Inventory plot comparisons show that all the dates mentioned above have been fixed. PEA12-AI-04 to PEACE (due 15-12-2012): to check why PP files were not available (e.g. compared to MOMENTS datasets). Examples from C1: Jun 04, Jul 04, Dec 04, Nov 05, Dec 05, Mar 06, Apr 06, Aug 06. PROPOSE TO CLOSE Detailed checks for all spacecraft and all delivered times were made at UKDC. Missing empty files have been generated and delivered to UKDC. Fill files should now propagate to CAA. Status of action items from Progress Meetings

20. MSSL PEA12-AI-05 to PEACE (due 15-12-2012): 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-06 to PEACE (due 15-12-2012): to check why PITCH_3DRL/H and 3DRL/H do not have the same coverage. Examples from C1: Feb 09, Mar 09 PROPOSE TO CLOSE For entire missing days see response for PEA12-AI-02. For gaps smaller than a day detailed checks have been made for the months listed above for C1 only. No regeneration of files yet. Detailed checks have been made for PITCH_3DRH/L and 3DRH/L for all units and dates using the tool developed in PEA13-AI-05 and the missing/incomplete files have been regenerated and redelivered Status of action items from Progress Meetings

21. MSSL PEA12-AI-07 to PEACE (due 15-12-2012): to check why OMSH/L are occasionally missing. Examples from C1: Mar 09 PROPOSE TO CLOSE For entire missing days see response for PEA12-AI-02. Lists of missing OMS, LER,NOI have been generated, validated and delivered. It seems that the CAA inventory plots do not always match the “list” info. PEA12-AI-08 to PEACE (due 15-12-2012): to investigate if the MODE dataset can be created for PEACE and what information is the most useful/relevant while searching PEACE in a given mode in a given region of space OPEN Has overlap with OR7-R3 & OR8-R14. PEA13-AI-01: to check why PITCH_3DR products contain fake records, for examples see e.g. C1-Jan 2001 when none of the other datasets contain anything. These records should be removed. Note that these records are not FILLVALs. PROPOSE TO CLOSE We have used the tool developed in PEA13-AI-05 to find problem dates and also which units have missing data. Regeneration has cured all problems dates. PITCH_3DR data for C1 Jan-2001 has been redelivered. PEA13-AI-02: to check why PITCH_3DRL is empty while 3DRL and PAD are not; for examples, see e.g. C1- Mar-Apr 2001 IN PROGRESS This is an extension of PEA12-AI-06 Status of action items from Progress Meetings

22. MSSL 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. PEA13-AI-04: to check why some of the units have empty files while some other units contain real data, for an example see e.g. 27 Jan 2001 PROPOSE TO CLOSE This type of problem has been addressed using the tool mentioned in PEA13-AI-05, e.g. when fixing the action item PEA13-AI-01. PEA13-AI-05: to develop a tool for checking that different units of the given product type have identical coverage. The existence of a file is not enough as the file may be empty PROPOSE TO CLOSE This has now been done by the PEACE team. Status of action items from Progress Meetings

23. MSSL PEA13-AI-06: 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 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 IN PROGRESS This is an extension of PEA12-AI-06 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

24. MSSL PEA13-AI-10: to clarify which coordinate system is used for 3DR products. Are they given in ISR2, SR2, or instrument coordinates? If the last, where is the sun direction? PROPOSE TO CLOSE This has been done in the new User Guide release (see Appendix E) PEA13-AI-11: to correct Sweep_Azimuth and their DeltaLower and DeltaUpper values in PITCH_FULL datasets PROPOSE TO CLOSE The bug in the production code has been identified and corrected. Regeneration validation and redelivery of the PITCH_FULL dataset is complete. PEA13-AI-12: to include both FGM GAPS and VALF datasets in the analysis of FGM data gaps PROPOSE TO CLOSE This is relevant to the Status_FGM flag. The codes have been updated to handle VALF. PEA13-AI-14: to update the UG, CR and ICD PROPOSE TO CLOSE The UM and the CR have been updated in May 2014. The ICD was not updated. Status of action items from Progress Meetings

25. MSSL Status of OR recommendations OR5-R16 to all teams: the board recommends delivery of observations from the commissioning stage particularly from January 2001 and December 2000 (also November 2000). PROPOSE TO CLOSE Scientifically useful data has been delivered for September through December 2000. MOMENTS have been also produced and delivered for select dates in Sep, Oct, Dec 2000 0after generating ‘dummy’ FGM PP data for dates that were not delivered to CSDS. This was achieved using FGM CoIi software and calibration files from dates closest to the missing dates with advice from the FGM team. 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.

26. MSSL Status of OR recommendations OR7-R2 to All: The board recommends that all teams ensure that they have provided detailed information to the CAA regarding the pointing of instrument sensors relative to the spacecraft reference frame (e.g. sun- sensor or spacecraft Y-axis). PROPOSE TO CLOSE This has been done in the new User Guide release (see Appendix E) 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. 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.

27. MSSL Status of OR recommendations 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-R1 to All: The board recommends that instrument teams ensure that all ancillary datasets are fully described in their ICDs. PROPOSE TO CLOSE See action item OR8-R13 OR8-R2 to All: All instrument teams should ensure that their user guides contain a detailed description and time-line of instrument operations and failures. PROPOSE TO CLOSE See action item OR8-R14 OR8-R3 to All: The board recommends that all teams investigate data quality at mode changes and instrument switch-on or switch-off. PROPOSE TO CLOSE See action item OR8-R15 OR8-R4 to PEACE: Add information regarding the pointing of the sun-sensor relative to PEACE on the pointing diagram in the PEACE user guide (see Steve Schwartz figure in QPEACE documentation). PROPOSE TO CLOSE See OR8-R19

28. MSSL Status of OR recommendations OR8-R13 to All: The board recommends that instrument teams ensure that all ancillary datasets are fully described in their ICDs. (See also CAA-OR8-R16 to CIS.). PROPOSE TO CLOSE The Ancilliary Datasets for PEACE are all described in the ICD. See 3.5.2 for PAD* and OMS. See 3.5.3 for LER and NOI. See 3.6.1 for CSDS PP data. OR8-R14 to All: All instrument teams should ensure that their user guides contain a detailed description and time-line of instrument operations and failures. PROPOSE TO CLOSE This is handled in User Guide Sections 3.3 and 3.4, but see also OR7-R3. OR8-R15 to All: The board recommends that all teams investigate data quality at mode changes and instrument switch-on or switch-off. (See also CAA-OR8-R20 to RAPID.) PROPOSE TO CLOSE 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. 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. There is a short interval (~30 sec) at the 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. OR8-R19 to PEACE: Add information regarding the pointing of the sun-sensor relative to PEACE on the pointing diagram in the PEACE user guide (see Steve Schwartz figure in QPEACE documentation). PROPOSE TO CLOSE This has been done in the new User Guide release (see Appendix E)

29. MSSL Status of OR recommendations OR9-R21 to PEACE: PEACE MOMENT dataset is often missing during burst mode periods. Examples include 19/02/2011, 22/02/2011, 28/02/2011, 21/04/2011 (C2,C1). The board recommends that priority is given to delivery of the missing intervals since BM intervals are among the most exploited data. IN PROGRESS The problem has been traced to a bug in the “peacemoments” software. We have sought assistance from Andrew Lahiff who wrote the software. (No results yet) OR9-R22 to PEACE: The board asks that PEACE consider delivering the PSD products in SR2. This involves only changing Depend metadata. OPEN …in every delivered file; this may be best handled at the time of a mass redelivery

30. MSSL Thank you for listening!