Venus Transit program for 8 June 2004; technical details


The images below show the approximate transit track. The ingress and egress diagrams show the track for the center of Venus as a solid curve, the disks for the approximate contact times as solid circles, and as dotted circles the Venus disk with an extra ring of 16.5 arcseconds


**********************************************

The program, as run on Wednesday, April 28:

For re-pointings every 130 arcsec of Venus' movement, moving them
off contact times and special-mode runs:

Date Time X (arcsec) Y (arcsec)
2004/06/08 03:27:01 -1162 -601
2004/06/08 03:59:25 -1032 -604
2004/06/08 04:31:49 -902 -607
2004/06/08 05:04:14 -772 -609
2004/06/08 05:36:38 -642 -612
2004/06/08 06:09:02 -512 -614
2004/06/08 06:41:26 -382 -617
2004/06/08 07:13:51 -252 -620
2004/06/08 07:46:15 -122 -622
2004/06/08 08:18:39 8 -625
2004/06/08 08:51:04 138 -627
2004/06/08 09:23:28 268 -630
2004/06/08 09:55:52 398 -632
2004/06/08 10:28:16 527 -635
2004/06/08 11:00:41 657 -638
2004/06/08 11:33:05 787 -640
2004/06/08 12:05:29 917 -643
2004/06/08 12:37:53 1047 -645
2004/06/08 13:10:18 1177 -648
2004/06/08 13:42:42 1307 -651
2004/06/08 14:15:06 1437 -653
2004/06/08 14:47:3 1567 -656

03:30 UT Start of program

171A (fixed 7.5s exp., 2x2 summed; movement of 1 pix/exp),

Register values:
$g2[=18]=18[171 2x2 at AEC+2]
$g1[=17]=40[2s delay]

04:48 UT Start of first limb transit phase (allow 4 min. extra buffer window,

starting with Venus at least 12000. km above the WL limb, plus an
extra 15 minutes for a full Venus diameter - as requested by Glenn
Schneider)

N.B. Too early for GBO from Canary islands

171A (fixed 8.2s exp., 2x2 summed; movement of 1 pix/exp),
1600A (fixed 0.9s), and 1216A (fixed 2.4s), WL (fixed 0.016s -
4 times standard to increase dynamic range - lossless and/or Q0)
Cycle appr. 8.2 [exp] +0.9 [exp] +2.4 [exp] +0.0 [exp] +
4*2 [readout/transfer] ~ 20 s cadence, or 1.3 TRACE resolution elements between exposures at a given wavelength.

Test run shows: 30s cadence. Why is there an extra 10s overhead?
Because of the 2s delay between frames. Lower to 0 ticks.

Register values:
$g2[=18]=18[171 2x2 at AEC+2]
$g16=3[top3 for shorter EUV exposures]
$g5[=21]=1[1600]+16[1216, standard]+256[context]*8[wl]=2065
$g9[=25]=3[wide frame]+256[context]*14[WL, 0.016s,JPEG0]=3587
$g1[=17]=0[no delay] ; was 40[2s delay] in test run 1.
$ga[=26]=2[context cycles; value cannot be 1]

05:41 UT End of first limb transit phase (allow 2 min. extra buffer window)

171A (fixed 15s exp.; movement of 1 pix/exp), WL & 1600, net cadence of about 20s, or 2.7 pixels between exposures at a given wavelength
Register values:
$g2[=18]=4[171 Q0 AEC]
$g5[=21]=1[1600]+8[wl, standard]=9
$g1[=17]=40[2s delay]

06:10-06:30 high cadence observations in WL (near limb for faculae)

08:19-08:39 high cadence observations in 1600 (partial frames?)

09:24-09:54 high cadence observations in EUV

10:58 UT Start of second limb transit phase (allow 2 min. extra buffer window)

N.B. Likely GBO support from Canary islands
WL (fixed 0.0128s = 4 times standard to increase dynamic range) &
1600, at <7.5 s cadence (1 pix/exp), LOSLESS compression,
If possible, run at max. cadence of ~5s for full frame, or ~2.5s
for central half of detector, or ~1.5s if only at 1600 and half
of the detector (0.1 arcsec occultor resolution).
Register values:
$g2[=18]=0[no 171]
$g5[=21]=1[1600]+8[wl, standard]+256[context]*8[wl]=2057
$g9[=25]=3[wide frame]+256[context]*15[WL, 0.016s,uncompr.]=3843
or
$g9[=25]=3[wide frame]+256[context]*14[WL, 0.016s,JPEG0]=3587
$g1[=17]=40[2s delay]
$ga[=26]=5[context cycles]

11:51 UT End of second limb transit phase (allow 4 min. extra buffer window,

which brings Venus at least 12000. km above the WL limb, plus an
extra 15 minutes for a full Venus diameter - as requested by Glenn
Schneider)
171A (fixed 7.5s exp., 2x2 summed; movement of 1 pix/exp),
Register values:
$g2[=18]=18[171 2x2 at AEC+2]
$g1[=17]=40[2s delay]

14:45 UT End of program

****************************************************

Last Updated: Wednesday, 26-May-2004

Content Contact Person: Dawn Myers