pacs sovt-2 and caps development mpia pacs icc meeting #31 12 th – 13 th january 2009, vienna (a)...

13
PACS SOVT-2 and CAPs development MPIA PACS ICC Meeting #31 12 th – 13 th January 2009, Vienna (A) Markus Nielbock (MPIA)

Upload: fay-marshall

Post on 03-Jan-2016

217 views

Category:

Documents


1 download

TRANSCRIPT

PACS SOVT-2and

CAPs developmentMPIA

PACS ICC Meeting #3112th – 13th January 2009, Vienna (A)

Markus Nielbock (MPIA)

Marku

s Nie

lbock – P

AC

S S

OV

T-2

Wash

Up / C

APs

Initial Remarks

ICC#31, 13th Jan 2009

• worked on SOVT-2 data from OD 63

• late arrival due to database problems at HSC and propagation to MPE

• tried working on ESAC/MPE data pool products and TM files (thx to EW)

• first useful data available on Friday, more on Sunday

• used dp-pacs on pacs-ds2 (MPE) remotely – plotting a nightmare

• my first experience with SPG product analysis (tutorials needed)

Marku

s Nie

lbock – P

AC

S S

OV

T-2

Wash

Up / C

APs

PACS Chopper Angular Calibration (CAPs)

ICC#31, 13th Jan 2009

• 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)

‐ had to be split into two CAPs (Jython error: too many code lines)

Marku

s Nie

lbock – P

AC

S S

OV

T-2

Wash

Up / C

APs

PACS Chopper Characterisation (CAPs)

ICC#31, 13th Jan 2009

Marku

s Nie

lbock – P

AC

S S

OV

T-2

Wash

Up / C

APs

PACS Chopper Characterisation (CAPs)

ICC#31, 13th Jan 2009

Marku

s Nie

lbock – P

AC

S S

OV

T-2

Wash

Up / C

APs

PACS Chopper automatic PID characterisation

ICC#31, 13th Jan 2009

• iteration on small modifications around five 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

• SOVT-2 data did not contain diagnostic HK (necessary for performance analysis)‐ neither in pool products nor in TM file

‐ no telecommand history available

• SPEC HK indicates observation was fully executed

• CAPs (Jeroen Bouwman) based on manual PID tuning analysis – fully tested

chopper was switched off during SOVT-2 at end of measurement

Marku

s Nie

lbock – P

AC

S S

OV

T-2

Wash

Up / C

APs

PACS Chopper automatic PID characterisation

ICC#31, 13th Jan 2009

Marku

s Nie

lbock – P

AC

S S

OV

T-2

Wash

Up / C

APs

PACS PHOT Linearity in Flux

ICC#31, 13th Jan 2009

• standard PHOT dithered point source photometry AOT used

• during PV phase: sequence of objects covering large flux range (low + high gain)

• during SOVT-2: one AOR – tracking on SSO Ceres

• full analysis still pending (late delivery of SPG products – Level 0 only)• Level 2 processing with SPG script successful (error message: no SIAM available) pointing offset due to missing FPG

Marku

s Nie

lbock – P

AC

S S

OV

T-2

Wash

Up / C

APs

PACS PHOT Linearity in Flux

ICC#31, 13th Jan 2009

• footprint of blue PHOT array

• pointing information available

• detector PA corresponds to roll angle• relative positions correct?

cal sources

blue PHOT array

Marku

s Nie

lbock – P

AC

S S

OV

T-2

Wash

Up / C

APs

PACS PHOT Linearity in Flux

ICC#31, 13th Jan 2009

• footprint of blue PHOT array pixels

Marku

s Nie

lbock – P

AC

S S

OV

T-2

Wash

Up / C

APs

PACS PHOT Linearity

ICC#31, 13th Jan 2009

• offset due to missing SIAM

• and source coordinates (earth vs. L2)• PA corresponds to roll angle

Marku

s Nie

lbock – P

AC

S S

OV

T-2

Wash

Up / C

APs

PACS PHOT Linearity

ICC#31, 13th Jan 2009

• consistency check (aligned to coordinate mean values)

• relative propagation of coordinates in time (RA and Dec separately)• added pointing of individual raw frames

Ceres

raw frames

final frames

• trend of telescope tracking seems correct

Marku

s Nie

lbock – P

AC

S S

OV

T-2

Wash

Up / C

APs

Conclusions

ICC#31, 13th Jan 2009

• OD 63 data very late for ICC meeting analysis due to database problems• pointing checks impossible SIAM not applied

• diagnostic HK data missing?

• PHOT dithered Point Source AOT + tracking SSO executed (successful?)• CAPs for chopper characterisation ready and tested

• strong plead for tutorials on data product handling (How to …), help function no help• exercise useful for data handling practice