# created by CALDBaxafcal/hetg/software/ddidl/xrcf/aciss_chip_offsets.pro
# Wed Jul 28 14:13:07 1999
# 
# These offset values are to be added to the TDETX
# and TDETY coordinates to produce more physically
# accurate event locations.  Generally this would happen
# during the input randomization of the TDET coordinates, e.g.:
#   X_value = FLOAT(TDETX) + tdetx_offset + RANDOMU(S) - 0.5
# where RANDOMU(S) is a uniform random value between 0.0 and 1.0
# The non-zero values are currently based on the attached e-mail.
#
# Note:  CCD_ID = 0 - 3 are chips i0 to i3
#        CCD_ID = 4 - 9 are chips s0 to s5
#
# - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
# Date: Mon, 5 Jul 1999 14:38:27 -0400 (EDT)
# From: "Herman L. Marshall" <hermanm>
# To: mwb
# Subject: ACIS-S chip positions
# Cc: dd, nss
# 
# I have completed my estimates of the chip location deviations.
# Relative to zeroth order and to the nominal positions of column
# zero in tiled coordinates (which are: 792, 1834, 2876, 3918, 
# 4960, 6002 in the Penn St event processing code), I find the
# following deviations:
# 
# (3.4, 2.5, 1.9, 0.0, 0.3, 0.6)
# 
# in units of pixels.  These values are subtracted from the tiled
# pixel coordinates for each event, according to its chip number,
# which is the same thing as subtracting from the column0 coordinates.
# The measurements are probably good to about 0.1-0.2 pix.  There
# is no apparent trend in the data that would indicate significant
# rotations of the chips, which would appear mainly in data for S0
# and S5, which some difference in the average row number between
# the HEG and MEG spectra.
# 
# I'll write up the analysis in my report concerning the grating
# observations of the continuum sources (C, Cu) at XRCF.  There
# were many lines to use, especially in the C anode tests and
# I could use high order lines as well.
# 
# I have not examined the information you sent to Dan regarding lab
# measurements of the chip locations.  I have handed it to Norbert
# to see if he can wade through it better than I can.
# 
# Herman
# - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
# 
# rdb parameter file ("rpf") format
# 
name	datatype	scalarvalue	unit	error	stringvalue	description
S	S	N	S	N	S	S
rpf_creation_time	StringValue	0.0000000		0.0000000	Wed Jul 28 14:13:07 1999	
tdetx_offset_id0	ScalarValue	0.0000000	pixel	0.0000000		
tdetx_offset_id1	ScalarValue	0.0000000	pixel	0.0000000		
tdetx_offset_id2	ScalarValue	0.0000000	pixel	0.0000000		
tdetx_offset_id3	ScalarValue	0.0000000	pixel	0.0000000		
tdetx_offset_id4	ScalarValue	-3.4000001	pixel	0.20000000		
tdetx_offset_id5	ScalarValue	-2.5000000	pixel	0.20000000		
tdetx_offset_id6	ScalarValue	-1.9000000	pixel	0.20000000		
tdetx_offset_id7	ScalarValue	0.0000000	pixel	0.20000000		
tdetx_offset_id8	ScalarValue	-0.30000001	pixel	0.20000000		
tdetx_offset_id9	ScalarValue	-0.60000002	pixel	0.20000000		
tdety_offset_id0	ScalarValue	0.0000000	pixel	0.0000000		
tdety_offset_id1	ScalarValue	0.0000000	pixel	0.0000000		
tdety_offset_id2	ScalarValue	0.0000000	pixel	0.0000000		
tdety_offset_id3	ScalarValue	0.0000000	pixel	0.0000000		
tdety_offset_id4	ScalarValue	0.0000000	pixel	0.0000000		
tdety_offset_id5	ScalarValue	0.0000000	pixel	0.0000000		
tdety_offset_id6	ScalarValue	0.0000000	pixel	0.0000000		
tdety_offset_id7	ScalarValue	0.0000000	pixel	0.0000000		
tdety_offset_id8	ScalarValue	0.0000000	pixel	0.0000000		
tdety_offset_id9	ScalarValue	0.0000000	pixel	0.0000000