Technical Observing at Bent Gregorian with IRTC - 08-09 May 2009 MST

Observers: J. Hill (mtn)
Telescope Operator: W. Wack
Software Support:
Telescope Support: J. Little

An Interlude in DG Commissioning before we move IRTC to the Direct Gregorian Focus

Summary

AGW transformation worked tonight. So we took lots of additional AGW transform data. We also took some dice5 offset test data. And we took some 1 millisec vibration data with IRTC at the end.

Sky was photometric all night long, seeing varied from 0.5 to 1 arcsec, with one well-placed bad patch that allowed for night-lunch.

Telescope problems were quite minor. Hardly any time was lost. We spent a few minutes bumping against the +Y limit of M1 at high elevation and +9 degC temps.

The plan for tomorrow is to move IRTC to direct gregorian and continue there.

Details

Open

18:55 Open early so we can be ready to take some post-sunset photos of LBT in photometric skies. T==11.5 degC, D=-6 degC. Wind 6 m/sec.

19:41 pointto M5_1246 Tel="ACQUIRE" gs=0 PAM- =- star was only off by ~6 arcsec in elevation! Adjust IE=-90 CA=-9 and some Zglobal to focus.

19:47 pointto M5_1246 Tel="ACTIVEE" gs=1 PAM+ PA=INDEF - didn't find the guide star (of course, I have no idea how bright gs=1 is)

19:48 pointto M5_1246 Tel="ACTIVEE" gs=2 PAM+ PA=INDEF - still too much twilight sky gradient in the acquisition image.

19:50 pointto M5_1246 Tel="ACQUIRE" gs=0 PAM+ PA=0 - star is off by 10 arcsec from where we centered a few minutes ago.

Clear all active optics and M2 offloads, which didn't change much.

19:52 pointto M5_1246 Tel="ACQUIRE" gs=0 PAM- why has the azimuth pointing shifted by 10-12 arcsec in 10 minutes? (and same thing has happened two nights in a row) Adjust *IE=-95 CA=-7 * We also have a bit of Z7. Open-loop tracking is not drifting nearly enough to explain this.

19:58 pointto M5_1246 Tel="ACTIVE" gs=2 PAM+ PA=INDEF - hit this star dead on, although it is still a bit lost in twilight

20:01 stop Guiding, selectAGW AIP_IRTC_L.cfg, startGuiding (just to be sure)

20:03 Press startGuiding and then startWFSing on GCSGUI. This works as expected but IIF does not escalate to ACTIVE mode. This could be a new feature to add to IIF someday.

20:10 focus 0 to force an offload of the coma.

20:11 pointto M5_1246 Tel="ACQUIRE" gs=0 PAM- star is centered within 1-1.5 arcsec

20:14 pointto BS9145 Tel="ACTIVE" gs=8 PAM+ PA=0 funny light gradient in the field - was it a bad CCD readout?

20:21 pointto BS9145 Tel="ACQUIREE" (which translates as ACTIVE) gs=8 PAM+ PA=0 - found star OK. Seeing varies 1.0 to 1.5 arcsec takeseq 2.0 20 irtc.20090509.032732.fits getdat0

20:29 pointto BS9145 Tel="ACTIVE" PAM+ PA=0 gs=6 - funny gradient of light in acquisition image, but also a star which sextractor identified. But preset failed because guiding not stable.

20:33 pointto BS9145 Tel="ACTIVE" PAM+ PA=0 gs=6 - succeeded with a normal looking acq image. WFS images show all kinds of scattered light. We've sent Wayne to investigate. Moonlight reflections? irtc.20090509.033617.fits getdat0

Closed both side vent doors without seeing much change in the stray light.

20:37 pointto BS9145 Tel="ACTIVE" PAM+ PA=0 gs=9 irtc.20090509.033936.fits getdat0

20:42 pointto BS9145 Tel="ACTIVE" PAM+ PA=0 gs=16 irtc.20090509.034424.fits getdat0

It is already clear that whatever was broken with the transformation at the end of last night is not broken tonight. All these off-axis stars are putting central star within 1 arcsec of the same place. What is different? We restarted oacserver at the end of last night. We are authorized as IRTC instead of LUCIFER.

20:57 takeseq 2.0 1000 - Closed loop guiding test (or excuse to go and have a cup of tea) while waiting for the seeing to improve before we take serious transform data. Seeing is in the range 0.6 to 0.9 arcsec on the guider during this test - call it median conditions. irtc.20090509.035758.fits cube 0054. Guider was taking 2100 ms exposures at a rate of 0.3 Hz with scaling factor 0.9.

Offset Tests with Dice5 pattern

21:36 dice5 off1=7.5 off2=4.5 coord ="DETXY" exptime=2.0 Nexpo=20 loopN=10 - seeing is running 0.5 to 0.7 arcsec at the start.

21:40 Hit collimation limit and lost the guide star. Probably this means we need to implement a temperature dependent Y-translation in both M1 and M2 together. I need to review the winter history of this collimation model.

The first run of dice5 got through cube 0057 before it was interrupted.

21:42 The guider recovers the guide star on its own when Wayne shifts M1 and M2 by a millimeter!

21:43 dice5 off1=7.5 off2=4.5 coord ="DETXY" exptime=2.0 Nexpo=20 loopN=10 - starting with irtc.20090509.044420.fits and cube 0058, and ending with irtc.20090509.054109.fits and cube 0106.

For this dataset, DThompson finds the following:
  • Central position is at SFP/PCS coordinates x=-82.325 y=40.866 mm
  • Assuming previous scale/rotation as before, rms = 0.426 and 0.236 pixels = 43 x 24 mas.
  • RMS improves only slightly (~5% or less) if I allow scale/rotation to float.

21:56 Seeing degrades to 0.9 - 1.2 arcsec.

21:58 Seeing back to 0.5 to 0.6 arcsec, although there is significant motion on timescales longer than the 2 sec guider images.

Stone L field - Transformation Data at low El (starting at 45 deg)

22:45 pointto StoneLagw Tel="ACQUIRE" PAM- gs=0 - Adjust IE=-105 CA=-10

22:51 pointto StoneLagw Tel="ACTIVE" PAM+ gs=31 - sextractor grabbed a warm pixel at the edge of the field instead of the actual star. Does sextractor have a parameter for minimum star width? This is probably one of the present limiting factors on how faint we can guide.

22:55 pointto StoneLagw Tel="ACTIVE" PAM+ gs=31 PA=xx - succeeded with 0.5 to 0.6 arcsec guider images. irtc.20090509.055816.fits cube 0107 getdat0

22:59 pointto StoneLagw Tel="ACTIVE" PAM+ gs=35 PA=69.7 irtc.20090509.060157.fits cube 0108

23:03 pointto StoneLagw Tel="ACTIVE" PAM+ gs=35 PA=0 irtc.20090509.060433.fits cube 0109 seeing degraded

23:05 pointto StoneLagw Tel="ACTIVE" PAM+ gs=31 PA=0 - failed - grabbed the warm pixel

23:06 pointto StoneLagw Tel="ACTIVE" PAM+ gs=31 PA=0 irtc.20090509.061024.fits cube 0110

23:11 pointto StoneLagw Tel="ACTIVE" PAM+ gs=21 PA=0 irtc.20090509.061249.fits cube 0111

23:14 pointto StoneLagw Tel="ACTIVE" PAM+ gs=19 PA=0 irtc.20090509.061545.fits cube 0112

23:17 pointto StoneLagw Tel="ACTIVE" PAM+ gs=15 PA=0 irtc.20090509.061802.fits cube 0113 lots of stray light on the edge of the WFS image

23:19 pointto StoneLagw Tel="ACTIVE" PAM+ gs=13 PA=0 irtc.20090509.062058.fits cube 0114

23:22 pointto StoneLagw Tel="ACTIVE" PAM+ gs=9 PA=0 irtc.20090509.062324.fits cube 0115

23:25 pointto StoneLagw Tel="ACTIVE" PAM+ gs=6 PA=0 irtc.20090509.062610.fits cube 0116

23:27 pointto StoneLagw Tel="ACTIVE" PAM+ gs=5 PA=0 irtc.20090509.062816.fits cube 0117

23:29 pointto StoneLagw Tel="ACTIVE" PAM+ gs=10 PA=0 irtc.20090509.063109.fits cube 0118

23:32 pointto StoneLagw Tel="ACTIVE" PAM+ gs=24 PA=0 irtc.20090509.063349.fits cube 0119

23:35 pointto StoneLagw Tel="ACTIVE" PAM+ gs=30 PA=0 irtc.20090509.063646.fits cube 0120

The off-axis star on the acquisition image seems to be circling the hotspot. What can make such a pattern? It seems a peculiar pattern for the telescope pointing to drift.

23:38 pointto StoneLagw Tel="ACTIVE" PAM+ gs=36 PA=0 irtc.20090509.063915.fits cube 0121

23:40 pointto StoneLagw Tel="ACTIVE" PAM+ gs=42 PA=0 irtc.20090509.064207.fits cube 0122

23:43 pointto StoneLagw Tel="ACTIVE" PAM+ gs=35 PA=0 irtc.20090509.064458.fits cube 0123

23:46 pointto StoneLagw Tel="ACTIVE" PAM+ gs=21 PA=0 irtc.20090509.064736.fits cube 0124

23:48 pointto StoneLagw Tel="ACTIVE" PAM+ gs=35 PA=0 irtc.20090509.065030.fit cube 0125

23:52 pointto StoneLagw Tel="ACTIVE" PAM+ gs=21 PA=0 irtc.20090509.065319.fits cube 0126

23:55 pointto StoneLagw Tel="ACTIVE" PAM+ gs=35 PA=0 irtc.20090509.065522.fits cube 0127

Changing PA moves the position of the off-axis star relative to the hotspot. Could this be some residual DETXY issue leftover from dice5? No, it is only the changing rotator angle along with a quasi-linear drift in pointing.

23:57 pointto StoneLagw Tel="ACTIVE" PAM+ PA=240 gs=22 irtc.20090509.065940.fits cube 0128

00:01 pointto StoneLagw Tel="ACTIVE" PAM+ PA=240 gs=26 irtc.20090509.070200.fits cube 0129 - faint star

00:03 pointto StoneLagw Tel="ACTIVE" PAM+ PA=240 gs=34 irtc.20090509.070504.fits cube 0130 - bright star

Changed DETECT_MINAREA from 5 to 9 in gcs_sx.sex

00:07 pointto StoneLagw Tel="ACTIVE" PAM+ PA=240 gs=33 irtc.20090509.070941.fits cube 0131

00:10 pointto StoneLagw Tel="ACTIVE" PAM+ PA=240 gs=29 irtc.20090509.071207.fits cube 0132

00:13 pointto StoneLagw Tel="ACTIVE" PAM+ PA=240 gs=27 irtc.20090509.071438.fits cube 0133

00:16 pointto StoneLagw Tel="ACTIVE" PAM+ PA=240 gs=28 irtc.20090509.071654.fits cube 0134

00:18 pointto StoneLagw Tel="ACTIVE" PAM+ PA=240 gs=23 irtc.20090509.071906.fits cube 0135

00:20 pointto StoneLagw Tel="ACTIVE" PAM+ PA=240 gs=20 irtc.20090509.072110.fits cube 0136

00:22 pointto StoneLagw Tel="ACTIVE" PAM+ PA=240 gs=18 irtc.20090509.072313.fits cube 0137

00:25 pointto StoneLagw Tel="ACTIVE" PAM+ PA=240 gs=16 irtc.20090509.072527.fits cube 0138

Adjust IE=-110 (wrong way)

00:27 pointto StoneLagw Tel="ACTIVE" PAM+ PA=240 gs=14 irtc.20090509.072755.fits cube 0139

Adjust IE=-95 (not precisely centered)

00:29 pointto StoneLagw Tel="ACTIVE" PAM+ PA=240 gs=8 irtc.20090509.073025.fits cube 0140 -pupil vignetted

Adjust CA=-2

00:32 pointto StoneLagw Tel="ACTIVE" PAM+ PA=240 gs=17 irtc.20090509.073324.fits cube 0141

Adjust IE=-97 CA=+1

00:34 pointto StoneLagw Tel="ACTIVE" PAM+ PA=240 gs=7 irtc.20090509.073541.fits cube 0142

00:36 pointto StoneLagw Tel="ACTIVE" PAM+ PA=240 gs=12 irtc.20090509.073751.fits cube 0143

00:39 pointto StoneLagw Tel="ACTIVE" PAM+ PA=240 gs=3 irtc.20090509.074000.fits cube 0144

00:41 pointto StoneLagw Tel="ACTIVE" PAM+ PA=240 gs=15 irtc.20090509.074222.fits cube 0145

00:43 pointto StoneLagw Tel="ACTIVE" PAM+ PA=240 gs=13 irtc.20090509.074428.fits cube 0146

00:45 pointto StoneLagw Tel="ACTIVE" PAM+ PA=240 gs=9 irtc.20090509.074633.fits cube 0147

00:47 pointto StoneLagw Tel="ACTIVE" PAM+ PA=240 gs=6 irtc.20090509.074837.fits cube 0148

00:49 pointto StoneLagw Tel="ACTIVE" PAM+ PA=240 gs=22 irtc.20090509.075138.fits cube 0149 - bad seeing

00:53 pointto StoneLagw Tel="ACTIVE" PAM+ PA=240 gs=34 irtc.20090509.075452.fits cube 0150 - bad seeing

00:56 pointto StoneLagw Tel="ACTIVE" PAM+ PA=0 gs=35 irtc.20090509.075754.fits cube 0151 - bad seeing

This brings us to the 1AM bad seeing break in our program.

01:22 Stop and restart GCSL to be sure that we picked up the new sextractor parameters.

01:23 pointto StoneLagw Tel="ACTIVE" PAM+ PA=0 gs=35 - GCS crashed. Restart it.

May  9 01:23:18 lbtmu107 LBT_left_GCS: waiting for handle block:1:1 0 1
May  9 01:23:18 lbtmu107 LBT_left_GCS: GuideStar set to RA/DEC: 4.19313, 0.0253219
May  9 01:23:18 lbtmu107 LBT_left_GCS: PROFILING: moveProbeOnGuideStar entered.
May  9 01:23:18 lbtmu107 LBT_left_GCS: PROFILING: calling  pcs.guider.adjustGSCoordinates()...
May  9 01:23:18 lbtmu107 LBT_left_GCS: PROFILING: pcs.guider.adjustGSCoordinates() returned.
May  9 01:23:22 lbtmu107 LBT_networkserver: GCSL died unexpectedly
May  9 01:23:22 lbtmu107 LBT_networkserver: GCSL is not active
May  9 01:23:22 lbtmu107 LBT_networkserver: dropping GCSL

GCS dies this way multiple times. Probably it was because we forgot to selectAGW.

01:28 Start GCSL. Then selectAGW AIP_IRTC_DG_L.cfg

01:29 pointto StoneLagw Tel="ACTIVE" PAM+ PA=0 gs=35 - succeeds, but seeing still bouncing between 1 and 1.7 arcsec.

01:34 Turn off left mirror ventilation to verify that Chris' patch of PSF puts the Command at Glass-0.9. It does.

More transformation data on the meridian

01:50 pointto StoneLagw Tel="ACTIVE" PAM+ PA=0 gs=6 irtc.20090509.085321.fits cube 0152

01:54 pointto StoneLagw Tel="ACTIVE" PAM+ PA=0 gs=35 irtc.20090509.085611.fits cube 0153

01:57 pointto StoneLagw Tel="ACTIVE" PAM+ PA=0 gs=21 irtc.20090509.085820.fits cube 0154

01:59 pointto StoneLagw Tel="ACTIVE" PAM+ PA=0 gs=19 irtc.20090509.090019.fits cube 0155

02:01 pointto StoneLagw Tel="ACTIVE" PAM+ PA=0 gs=15 irtc.20090509.090308.fits cube 0156 - bad seeing

02:04 pointto StoneLagw Tel="ACTIVE" PAM+ PA=0 gs=13 irtc.20090509.090605.fits cube 0157

02:07 pointto StoneLagw Tel="ACTIVE" PAM+ PA=0 gs=9 irtc.20090509.090813.fits cube 0158

02:09 pointto StoneLagw Tel="ACTIVE" PAM+ PA=0 gs=6 irtc.20090509.091036.fits cube 0159

CA=+3

02:11 pointto StoneLagw Tel="ACTIVE" PAM+ PA=0 gs=5 irtc.20090509.091257.fits cube 0160

I suppose it is rather late to notice this now, but it looks like IRTC is not in focus.

IE=-94 (wrong way)

02:14 pointto StoneLagw Tel="ACTIVE" PAM+ PA=0 gs=10 irtc.20090509.091513.fits cube 0161

IE=-104

02:16 pointto StoneLagw Tel="ACTIVE" PAM+ PA=0 gs=24 irtc.20090509.091720.fits cube 0162

02:18 pointto StoneLagw Tel="ACTIVE" PAM+ PA=0 gs=30 irtc.20090509.091950.fits cube 0163

02:21 pointto StoneLagw Tel="ACTIVE" PAM+ PA=0 gs=36 irtc.20090509.092205.fits cube 0164

02:23 pointto StoneLagw Tel="ACTIVE" PAM+ PA=0 gs=42 irtc.20090509.092411.fits cube 0165

02:25 pointto StoneLagw Tel="ACTIVE" PAM+ PA=0 gs=39 irtc.20090509.092620.fits cube 0166

02:27 pointto StoneLagw Tel="ACTIVE" PAM+ PA=0 gs=21 irtc.20090509.092853.fits cube 0167

02:30 pointto StoneLagw Tel="ACTIVE" PAM+ PA=0 gs=35 irtc.20090509.093106.fits cube 0168

Move to Stone M field

02:32 pointto StoneMagw Tel="ACTIVE" PAM+ PA=90 gs=55 irtc.20090509.093809.fits cube 0169 0.5 x 80

02:39 pointto StoneMagw Tel="ACTIVE" PAM+ PA=90 gs=53 irtc.20090509.094053.fits cube 0170

02:41 offset 0 60 - blank sky cube 0.5 x 80 irtc.20090509.094229.fits cube 0171

02:43 pointto StoneMagw Tel="ACTIVE" PAM+ PA=90 gs=56 irtc.20090509.094516.fits cube 0172 - binary - bad coords (did getdat0 twice)

02:46 pointto StoneMagw Tel="ACTIVE" PAM+ PA=90 gs=62 irtc.20090509.094751.fits cube 0173

02:49 pointto StoneMagw Tel="ACTIVE" PAM+ PA=90 gs=64 irtc.20090509.095005.fits cube 0174

02:51 pointto StoneMagw Tel="ACTIVE" PAM+ PA=90 gs=69 irtc.20090509.095211.fits cube 0175

02:53 pointto StoneMagw Tel="ACTIVE" PAM+ PA=90 gs=51 irtc.20090509.095434.fits cube 0176

02:56 pointto StoneMagw Tel="ACTIVE" PAM+ PA=90 gs=58 irtc.20090509.095726.fits cube 0177

02:58 pointto StoneMagw Tel="ACTIVE" PAM+ PA=90 gs=68 irtc.20090509.095938.fits cube 0178

03:01 pointto StoneMagw Tel="ACTIVE" PAM+ PA=90 gs=72 irtc.20090509.100230.fits cube 0179

03:03 pointto StoneMagw Tel="ACTIVE" PAM+ PA=90 gs=85 irtc.20090509.100448.fits cube 0180

03:06 pointto StoneMagw Tel="ACTIVE" PAM+ PA=90 gs=83 irtc.20090509.100730.fits cube 0181

03:09 pointto StoneMagw Tel="ACTIVE" PAM+ PA=90 gs=76 irtc.20090509.100952.fits cube 0182

03:11 pointto StoneMagw Tel="ACTIVE" PAM+ PA=90 gs=79 irtc.20090509.101200.fits cube 0183

03:13 pointto StoneMagw Tel="ACTIVE" PAM+ PA=90 gs=67 irtc.20090509.101441.fits cube 0184

03:16 pointto StoneMagw Tel="ACTIVE" PAM+ PA=90 gs=70 irtc.20090509.101703.fits cube 0185

03:18 pointto StoneMagw Tel="ACTIVE" PAM+ PA=90 gs=78 irtc.20090509.101927.fits cube 0186

03:21 pointto StoneMagw Tel="ACTIVE" PAM+ PA=90 gs=74 irtc.20090509.102138.fits cube 0187

03:23 pointto StoneMagw Tel="ACTIVE" PAM+ PA=90 gs=66 irtc.20090509.102406.fits cube 0188

03:25 pointto StoneMagw Tel="ACTIVE" PAM+ PA=90 gs=60 irtc.20090509.102715.fits cube 0189

03:28 pointto StoneMagw Tel="ACTIVE" PAM+ PA=90 gs=63 irtc.20090509.102944.fits cube 0190

03:31 pointto StoneMagw Tel="ACTIVE" PAM+ PA=90 gs=61 irtc.20090509.103147.fits cube 0191

03:33 pointto StoneMagw Tel="ACTIVE" PAM+ PA=90 gs=54 irtc.20090509.103358.fits cube 0192

03:35 pointto StoneMagw Tel="ACTIVE" PAM+ PA=90 gs=49 irtc.20090509.103620.fits cube 0193

03:37 pointto StoneMagw Tel="ACTIVE" PAM+ PA=90 gs=59 irtc.20090509.103827.fits cube 0194

03:39 pointto StoneMagw Tel="ACTIVE" PAM+ PA=90 gs=50 irtc.20090509.104057.fits cube 0195

03:42 pointto StoneMagw Tel="ACTIVE" PAM+ PA=90 gs=55 irtc.20090509.104305.fits cube 0196

03:44 pointto StoneMagw Tel="ACTIVE" PAM+ PA=90 gs=55 irtc.20090509.104508.fits cube 0197

03:46 pointto StoneMagw Tel="ACTIVE" PAM+ PA=90 gs=55 irtc.20090509.104710.fits cube 0198

03:48 pointto StoneMagw Tel="ACTIVE" PAM+ PA=90 gs=76 irtc.20090509.104918.fits cube 0199

03:50 pointto StoneMagw Tel="ACTIVE" PAM+ PA=90 gs=55 irtc.20090509.105135.fits cube 0200

03:52 pointto StoneMagw Tel="ACTIVE" PAM+ PA=90 gs=55 irtc.20090509.105400.fits cube 0201

03:56 Longer frame to characterize image motion - closed-loop guiding takeseq 0.5 2000 irtc.20090509.105533.fits cube 0202

Vibration data

04:21 pointto M5_0713 Tel="ACTIVE" PAM+ PA=90 gs=4 - failed Hit the +Y limit of M1 at this high elevation. Add a second -1 mm to M1 and M2, and that still wasn't enough. Clear M2 Offload

04:26 pointto M5_0713 Tel="ACQUIRE" PAM- gs=0 - Adjust IE=-104 CA=-15

04:28 pointto M5_0713 Tel="ACTIVE" PAM+ PA=90 gs=4

-3 mm M1 and M2

04:33 offset -12 -5 (DETXY) Why did I have to apply this correction to center the star?

Change to medium FOV on IRTC

Change to wide FOV on IRTC

04:43 takeseq 0.001 3000 irtc.20090509.114350.fits with 48 x 50 sub-frame (don't ask how it got to be 48) cube 0203 Seeing on guider is 0.7-0.8 arcsec while this was taken.

04:52 takeseq 0.001 3000 irtc.20090509.115206.fits with 48 x 50 sub-frame cube 0204 Seeing on the guider was 0.6 to 0.7 while this was taken. Guider was running with 2.0 sec exposures at an effective guide rate of 0.2 Hz, so there could have been a guide update in one of these cubes.

05:00 takeseq 0.001 3000 irtc.20090509.120040.fits with 48 x 50 sub-frame cube 0205 Seeing on the guider was 0.9 - 1.0 arcsec.

irtc.20090509.120853.fits and cube 0206 is one of these fast cubes without the star.

A similar cube with the same sub-frame readout ran at 617 Hz while a full-frame readout would have gone at 65 Hz.

Close

05:05 Close for impending dawn T=9.4 degC, photometric. wind ~10 m/sec.

-- JohnHill - 09 May 2009
Topic revision: r8 - 10 Jun 2009, DougMiller
This site is powered by FoswikiCopyright © by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding Foswiki? Send feedback