1 / 24

PACS SOVT-2 (SIMS) and CAPs development

MPIA. PACS SOVT-2 (SIMS) and CAPs development. PACS ICC Meeting #32 1 st – 3 rd April 2009, MPE Garching. Markus Nielbock (MPIA). Initial Remarks. worked on SOVT-2 (SIMS#1/#2) data of OD 63. mainly used ESAC/HSC data pool products.

briar-maldonado
Download Presentation

PACS SOVT-2 (SIMS) and CAPs development

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

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

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

  3. 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

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

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

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

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

  8. PACS PHOT Linearity in Flux • during PV phase: sequence of objects covering large flux range • standard PHOT dithered point source photometry AOT used • during SOVT-2: one AOR – tracking on SSO Ceres • full analysis still pending Results: • OOL product present but empty Markus Nielbock – PACS SOVT-2 Analysis / CAPs • TC history only available for SIMS#1, missing for SOVT-2 and SIMS#2 • 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.) ICC#32

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

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

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

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

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

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

  15. PACS PHOT Linearity in Flux 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

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

  17. PACS PHOT Linearity in Flux Markus Nielbock – PACS SOVT-2 Analysis / CAPs • after nodAvg(): first off frame produces third nod position? ICC#32

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

  19. Concluding remarks • 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? Markus Nielbock – PACS SOVT-2 Analysis / CAPs • How do we assure exchange of vital information on data processing? ICC#32

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

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

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

More Related