PACS SOVT-2 (SIMS) and CAPs development MPIA PACS ICC Meeting #32 1 st – 3 rd April 2009, MPE Garching Markus Nielbock (MPIA)

Markus Nielbock – PACS SOVT-2 Analysis / CAPs Initial Remarks ICC#32 worked on SOVT-2 (SIMS#1/#2) data of OD 63 mainly used ESAC/HSC data pool products re-processing done at HSC many times analysis results subject to change with each iteration my first acquaintance with data pool product analysis (tutorials and exchange of experience needed) inconsistencies found between SOVT-2, SIMS#1 and SIMS#2

PACS Chopper Angular Calibration (CAPs) ground calibration needs to be redone in orbit (zero gravity) measure mechanical zero point offset open-loop measurement (SFT) used for static/dynamical properties new CAPs available, based on previous versions (JIDE & IDL by UK, JS) ‐ had to be split into two CAPs (Jython error: too many code lines) Markus Nielbock – PACS SOVT-2 Analysis / CAPs ICC#32

PACS Chopper Characterisation (CAPs) Markus Nielbock – PACS SOVT-2 Analysis / CAPs ICC#32

PACS Chopper Characterisation (CAPs) Markus Nielbock – PACS SOVT-2 Analysis / CAPs ICC#32

PACS PHOT Linearity in Flux standard PHOT dithered point source photometry AOT used during PV phase: sequence of objects covering large flux range during SOVT-2: one AOR – tracking on SSO Ceres full analysis still pending (no flux analysis) Markus Nielbock – PACS SOVT-2 Analysis / CAPs ICC#32 OOL product present but empty TC history only available for SIMS#1, missing for SOVT-2 and SIMS#2 Results (based on dp-pacs 361):

PACS PHOT Linearity in Flux Markus Nielbock – PACS SOVT-2 Analysis / CAPs ICC#32 SOVT-2SIMS#1 SIMS#2

PACS PHOT Linearity in Flux standard PHOT dithered point source photometry AOT used during PV phase: sequence of objects covering large flux range during SOVT-2: one AOR – tracking on SSO Ceres full analysis still pending Markus Nielbock – PACS SOVT-2 Analysis / CAPs ICC#32 OOL product present but empty TC history only available for SIMS#1, missing for SOVT-2 and SIMS#2 Results: labelling of CS 1 and 2 swapped in Status product (PACS SPR 1052) pointing check for moving object confusing: What is the correct coordinate of Ceres for the date of observing? How were the coordinates simulated for the SOVT-2 data? 3 different results (HSPOT, JPL webtool, HIPE: ephemerides, horizons) 5” discrepancy between JPL and HIPE (PACS SPR 1347, aberration corr.)

PACS PHOT Linearity in Flux Markus Nielbock – PACS SOVT-2 Analysis / CAPs ICC#32

PACS PHOT Linearity in Flux Markus Nielbock – PACS SOVT-2 Analysis / CAPs ICC#32 used prototype ExtractCS task to separate calibration block both arrays agree well two frames do not align (cf. presentation of MS yesterday)

PACS PHOT Linearity in Flux Markus Nielbock – PACS SOVT-2 Analysis / CAPs ICC#32 CS1CS2

PACS PHOT Linearity in Flux Markus Nielbock – PACS SOVT-2 Analysis / CAPs ICC#32 CS1CS2 indication for improper flagging of chopper transitions

PACS PHOT Linearity in Flux Markus Nielbock – PACS SOVT-2 Analysis / CAPs ICC#32 first target frame is not on the correct position (still slewing) positions of first frame in blue/green and red data differ (Why? Timing?) issue of applying masks correctly or even findBlocks task? invalidates subsequent processing steps

PACS PHOT Linearity in Flux ICC#32 Markus Nielbock – PACS SOVT-2 Analysis / CAPs target frame 155 affected by nodding transition is this taken care of?

PACS PHOT Linearity in Flux ICC#32 Markus Nielbock – PACS SOVT-2 Analysis / CAPs last two blue/green target frames: no chopping total number of target frames differ between blue/green and red

ICC#32 Markus Nielbock – PACS SOVT-2 Analysis / CAPs after dithAvg() : first off frame determines coordinate of first average PACS PHOT Linearity in Flux

ICC#32 Markus Nielbock – PACS SOVT-2 Analysis / CAPs after nodAvg() : first off frame produces third nod position?

PACS PHOT Linearity in Flux ICC#32 Markus Nielbock – PACS SOVT-2 Analysis / CAPs tried to produce level 2 data products and FITS files do not contain WCS information (PACS SPR 1392) blue exposure map red exposure map

Concluding remarks ICC#32 Markus Nielbock – PACS SOVT-2 Analysis / CAPs still seems some work necessary pointing/tracking seems to be (approximately) correct final confirmation only possible after elimination of 5” offset When will the various issues/SPRs be followed up? How do we assure exchange of vital information on data processing?

PACS Chopper automatic PID tuning iteration on small modifications around four PID parameters BBIDs “abused” for parameter set indexing originally designed for Commissioning Phase  15 following observations lost (SPEC) – “NACK” in event log detected  PV phase clone will be changed accordingly if needed  chopper was switched off during SOVT-2 at end of measurement Markus Nielbock – PACS SOVT-2 Analysis / CAPs ICC#32 OOL product present but empty TC history only available for SIMS#1, missing for SOVT-2 and SIMS#2 (cf. PICC-MA-TN-002, PICC-MA-TR-076)

PACS Chopper automatic PID tuning Markus Nielbock – PACS SOVT-2 Analysis / CAPs ICC#32 SOVT-2SIMS#1 SIMS#2

PACS Chopper automatic PID tuning SOVT-2 data did not contain diagnostic HK SPEC HK indicates observation was fully executed Markus Nielbock – PACS SOVT-2 Analysis / CAPs ICC#32 only present in latest re-processing during SIMS#2

PACS Chopper automatic PID tuning CAP (Jeroen Bouwman) based on manual PID tuning analysis Markus Nielbock – PACS SOVT-2 Analysis / CAPs ICC#32 fully tested with SOVT-2 and FS-ILT data PID coding via BBIDs done properly observation executed successfully