Test and analysis teams

1. Test and analysis teams Frank Helmich

2. Overview • History • Planning this year • Test teams - organigram • Data Processing for ILT Training sessions • Further training • Outlook AIV/Calibration meeting

3. History • Already in calibration review of 2004 a closer interaction between calibration group and AIV/ILT team was requested • This led in the following 1.5 year to • Improvements in documentation • A few calibration group members actively participated in the DM/QM tests • The start of a series of meetings: Strategic AIV • Both sides AIV-team and calibration-team hoped for more combined work, but we all agreed that it was best to wait for the full FM for more action • This year we will have the full FM for testing, calibration and characterization -> Joint meeting AIV/Calibration meeting

4. Planning this year • From AIV/ILT side there has been QM analysis and DM2 testing • (Tests have been done on S/S level) • Integration and functional tests have been performed • For reviews: we have seen the start of the Science Verification Review and the Test Readiness Review • In calibration there has been a new draft of the PV plan • A workshop on planetary atmospheres and Mars will be held in October • Observations with APEX on CO lines in AGB stars have been requested • Real integration with the AIV team has started and will be in place for ILT-FM3 AIV/Calibration meeting

5. Test & analysis teams • Of the main conclusions of many HIFI reviews: • The AIV team is too small • The data analysis is often delayed until after the tests such that the testers lack immediate feedback • Combine the qualities of AIV and calibration teams • Intimate knowledge of HIFI with all its sub-systems • Skills in data analysis • Form test and analysis teams for: • Preparation of the tests • Performing the tests • Immediate feedback from planned analyses • Reporting in a stream-lined fashion • The best preparation for Performance Verification (PV) in orbit AIV/Calibration meeting

6. Organigram AIV/Calibration meeting

7. Data Processing training for ILT • Data processing for Herschel is a joint project of the three instruments, ESA and the NHSC • Herschel Common Science System contains all of it • There are still problems to be solved before all of it can be used • Test engineers need to know how it works and start using it • Test and analysis teams need to be familiar with the software just like with their usual analysis packages • The system is evolving, and thus contains bugs at all times • Over the last half year many analyses were done using DP • Some analyses were outside the whole system, especially when no data was generated for the data base (e.g beam) AIV/Calibration meeting

8. Data processing use – test engineers & teams • All the test engineers know the HCSS by now • Two training sessions were held over the last months • 7 & 8 June • 4 & 5 September • These were given by Tony, Russ & Volker (June) and Tony & Volker (September) • The first session generated an enormous boost in the system, due to all complaints • The number of people able to work with HIFI data increased tremendously • Hardly any of these people found him/herself capable in the whole system • The second session was better structured, had less people, but still revealed software problems, especially in installer set-up and connecting to the data bases AIV/Calibration meeting

9. Evolving system • The HCSS is an evolving system • This has both advantages and disadvantages • Advantages: • The system is already large and is still extended • The system has an error/change-reporting system • The effort is well coordinated • Disadvantages • The system can be very complex • SxRs are not always solved on the spot • The users will be regularly updated • At the Test Readiness Review the board recommended a frozen version to be used in the test room • Outside the test room newer versions can be used AIV/Calibration meeting

10. Test & analysis teams - tasks • Preparing the tests based on experience with DM. QM and functional tests and taking into account in-orbit needs • Up-date the operational procedures for the tests • Writing the up-link scripts in the Common Uplink System (CUS) • Executing the tests (only trained personnel) • Performing the Quick Look Analysis using QLA software • Divide the test results Obsid’s amongst the test team • Analyse the data • Write reports and put these on the ILT wiki • Feed results back to the ILT-teams AIV/Calibration meeting

11. Further training • We had planned exercises to be done by all the test team members • This turned out to be difficult due to software problems and the holiday period • Therefore training needed to be done within the separate test teams • Stability team is having regular telecons • Radiometry team has spent one entire day discussing and exercising • More teams will follow this month • We hope to extract several exercises from these training days AIV/Calibration meeting

12. Real testing • When all scripts are exercised and hardware is in • It is expected that team members are present in Groningen when their tests are due • Test teams can (TBC) use the separate cabin in room 50 for immediate evaluation of the data. • Data will be transported to the outside system approximately once a day • Analysis can be performed from the second floor rooms or from outside SRON after data base export • Reports, performance- and calibration parameters can later be generated • So, we are ready to start AIV/Calibration meeting