DPC SGS-IR – ESTEC – January 2007 Anna Gregorio University of Trieste and INAF – Osservatorio Astronomico di Trieste On behalf of the Planck LFI DPC-IOT and Planck SCS DPC-IOT (Gianluca Morgante) LFI & SCS Operation Plan

DPC SGS-IR – ESTEC – January 2007 Overview  Operations Context  Data processing  Tele-commanding  Software maintenance, new software release, archive development  Nominal Operations  Routine Operations  Non-Routine Operations  Commissioning and CPV Operations See also Operation Plan PL-LFI-PST-PL-011 PL-LFI-PST-PL-011 ANNEX I

DPC SGS-IR – ESTEC – January 2007 Operation Context  Data Processing  LFI: SGS1 & SGS2  SCS: SGS1 only (SCS data are considered HK)  Tele-commanding  Maintenance TC (re-setting TM counter) + ad-hoc TC to enhance LFI performance or better monitor the LFI  Software maintenance, new software release, archive development  SGS1 (LFI and SCS) & SGS2 (LFI only)  Support to MOC when necessary

DPC SGS-IR – ESTEC – January 2007 DPC-IOT Nominal Operations  Routine Phase Operations  Daily Operations (LFI & SCS)  Weekly Operations (LFI & SCS)  Monthly Operations (LFI & SCS)  End of Survey (Map Production) (LFI)  Component separation and optimization  Inter-comparison and cross-check  Non Routine Operations  LFI:  Planet Scanning  Small Gap  Recovery Operations  SCS:  Recovery Operations (in case of contingencies, at MOC or at DPC)  SCS switch-over (baseline, it is planned in advance)  Regeneration (NOT baseline, if needed can be planned in advance)  Commissioning and CPV  The operation timeline depends on the synergetic interaction of several activities involving the S/C, both instruments and SCS, that need to be finalized

DPC SGS-IR – ESTEC – January 2007 Daily Operations: automatic 1.Download one observation day of consolidated data 2.Run SGS1 software: RTA, TQL, TMH 3.Check system health and performance:  LFI: Compute R and evaluate the knee frequency  SCS: compute heat lift and input power, evaluate high/low pressure and cold end T 4.Compare with HFI data (on demand) 5.Run the Time Series Analysis (TSA) – LIFE system: Trends, Data Quality, Flags 6. Compile the reports generated by LIFE into a Daily Quality Report (DQR) to be sent to PSO LFI & SCS

DPC SGS-IR – ESTEC – January 2007 Daily Operations: DPC/IOT 7.Check and transmit the information (DQR and uplink operations) towards the instrument and SCS: LFI Instrument procedure requests (maintenance TC & additional), calibration channel switching, small gap recovery requests, Instrument special procedure requests (REBA patching) (if needed) SCS LookUpTable update/upload (if needed) 8.Eventually provide support to the scientific team running the Quick-Alarm system for detection of flaring radio sources 9.First look for systematics, perform first-order calibration, cleaning, write processed “circles” 10.Comparison with HFI data when needed 11.Organize the daily meeting LFI & SCS

DPC SGS-IR – ESTEC – January 2007 Daily Quality Report (OD)  Period covered by the report, Date/Time of report generation, Software tools version, Issuer of the report, Any relevant warnings or comments  LFI  Threshold NET (Noise Equivalent Temperature)  Data records for quality analysis parameters (per pointing): Pointing Reference, Axis positioning information, Dwell period start and end times, Science observation time  Transfer status to DPC of TM collected per detector  Dipole/Galaxy Response per detector  NET per detector, NET bandwidth per channel  Temperature sensors report (average T, drift, noise power, fluctuations, out of limits)  State vector (voltage and current report)  SCS (DQR is annex to the LFI one)  TMU health & SCE health (all sensors: T, P, V, I)  Cooler Status (Cycle Time, GGA’s timing, number of cycles)  Contingencies & Events (Diagnostic TM, Event Reports TM(5,1))  SCS Primary (T, P, V, I) and Derived Performance Parameters vs requirements (Cold End T and PSD, Heat Lift, Mass Flow, Input Power)  Primary I/F’s status (Warm Radiator T, PC1, PC2, PC3abc T, HFI I/F T, LFI I/F T)  Any relevant warning or comment

DPC SGS-IR – ESTEC – January 2007 Delays in the timelines  Short Delays in DQR production  Glitches or Alarms  Limited in time, reprocessing of a chunk of data;  Bad sky subtraction  Reason to be understood, reprocessing of a chunk of data;  Bad point sources subtraction  Reason to be understood, reprocessing of a chunk of data  Additional Delays in the Operation Context (Data processing & TC)  Small Gap or a more general gap  Cause to be understood and then solved before implementing a correction;  Requiring a list of TC to be sent;  If not a trivial problem, it could be a long delay;  A minor problem or a required tuning  Requiring a list of TC to be sent;  HFI comparison  HFI data to be retrieved and then compared to LFI

DPC SGS-IR – ESTEC – January 2007 Weekly Operations 1.Read one week of consolidated raw LFI/SCS TOI from archive 2.Run TSA – LIFE for data checking and trend analysis 3.When needed, compare with HFI data 4.Perform initial “calibration” on data: LFI Iterative calibration of radiometers, 1-D evaluation of beam, Stray-light effects, Attitude reconstruction, Focal Plane reconstruction SCS Primary (T, P, Input Power) & derived (Heat Lift, Cold End T and PSD) parameters Hydrides degradation Possible LUT update evaluation 5.Map Making (temperature & polarization) 6.Compile the reports generated by TSA-LIFE trend analysis and daily reports into a Weekly Health Report (WHR) to be sent to PSO 7.Organize the weekly meeting

DPC SGS-IR – ESTEC – January 2007 Monthly Operations 1.Read one month of calibrated LFI/SCS TOI from archive 2.LFI: Build partial frequency maps and compare SCS: Run trend analysis (primary and derived parameters) Evaluate hydrides degradation Evaluate possible variations to SCS Operation baseline 3.Possibly, run Level 3: Component separation, Inter-frequency cross-checks on CMB maps, Component maps archive, Merge component maps 4.Cross-check LFI and HFI data Retrieve HFI maps/power spectra, Cross-check LFI - HFI data, LFI/HFI optimization on component maps 5.Compile monthly data processing reports to be sent to PSO 6.Organize the monthly meeting

DPC SGS-IR – ESTEC – January 2007 SGS1 SGS2 Timeline 1/4 SGS1 f ~ 10 hr SGS1 1 ~ 8 hr LIFE ~ 10 hr SGS2 1 ~ 20 hr SGS2 2 ~ 26 hr Operational Day (OD): 24 hr DTCP ~ 3 hr GS to MOC ~ 5 hr ~ 3 hr SGS1

DPC SGS-IR – ESTEC – January 2007 Timeline 2/4: Mid caseSGS2

DPC SGS-IR – ESTEC – January 2007 Timeline 3/4: Extreme Late caseSGS2

DPC SGS-IR – ESTEC – January 2007 Timeline 4/4: Extreme Early case SGS2 SGS2

DPC SGS-IR – ESTEC – January 2007 Conclusions  Effort to implement as much as possible the LFI/SCS operations in an automatic way  For operations requiring DPC/IOT intervention, a person will always be in place  For contingencies, gaps or more in general for any alarm, a DPC/IOT responsible will be automatically informed to react as soon as possible  Routine Operations  Operations and timelines are in place  Quality reports are being implemented