AGw Commissioning with IRTC - 13-14 November 2008 MST

Observers: J. Hill
Software Support: T. Sargent
Telescope Operator: W. Wack

Summary

Details

Some time at beginning was donated back to HBS work.

19:15 Open dome, T=+5 degC, D=-13 degC, scattered thin clouds, wind 10-15 m/sec.

19:40 pointto M5_0042 gs=0 TelM="ACQUIRE" - Adjust IE=1 CA=-7

20:00 pointto BS9188 gs=33 TelM="ACTIVE"

Nov 13 20:02:49 lbtmu107 LBT_left_GCS: transfer of initial correction to PCS failed.

20:09 pointto BS9188 gs=29 TelM="ACTIVE" (brighter guide star)

Nov 13 20:10:50 lbtmu107 LBT_left_GCS: transfer of initial correction to PCS failed.

Restart GCSL

Nov 13 20:13:25 lbtmu107 LBT_left_GCS: transfer of initial correction to PCS failed.

Restart PCS

Nov 13 20:16:58 lbtmu107 LBT_left_GCS: pcsClient.guider.updateGuideOrigin(0.286259,72.144296); Nov 13 20:17:19 lbtmu107 LBT_left_GCS: transfer of initial correction to PCS failed.

20:19 Rollback to GCS.08111301 which appears to be the previous version (47). Stop and restart GCSL

Nov 13 20:22:07 lbtmu107 LBT_left_GCS: transfer of initial correction to PCS failed.

20:29 pointto BS9188 gs=29 TelM="ACTIVE" works this time with Torsten on the phone, but nobody did anything dffierent.

20:32 Stop guiding. Stop and restart GCSL with the current version (48).

20:33 pointto BS9188 gs=29 TelM="ACTIVE" - succeeded again.

Tracking test -- closed loop

20:40 After a few iterations of active optics, the images are 0.6 arcsec on the guider.

20:43 focus 0

20:47 takeseq 2.0 Nimage=1000 take1+ - This sequence has guiding running with active optics. Seeing is varying between 0.5 and 1.3 arcsec (on timescales of seconds) as measured by the guider in 0.5 sec exposures. There is significant image motion, but it seems correlated with the bad patches of seeing, so I suppose it is atmospheric. Wavefront corrections vary between 120 and 280 nm rms (as reported on GCSGUI) with 15 sec exposures. Seeing explodes to 1.8 arcsec near frame 1600, but then good again a minute later. Why does it take 1 hour to collect 1000 x 2.0 sec images (because 2000 exposures were actually taken)? 081114_00093_cube.fit

21:58 offset 30 30

21:59 takeseq 2.0 Nimage=40 take1+ for blank sky

Tracking test -- open loop

offset 0 0; stopWFS; block Guiding in PCS. Seeing is still varying 0.5 to 0.9 arcsec, but focus is very stable compared to last night.

22:03 takeseq 2.0 Nimage=400 take1+ -- open loop tracking, with M1 collimation updated every 50 frames.

Field aberration measurements

22:19 pointto BS9107 gs=0 ACTIVE - Apparently the IIF crashed during this preset.

22:22 Restarted IIF

22:23 pointto BS9107 gs=0 ACTIVE - failed authorization.

22:24 pointto BS9107 gs=0 ACTIVE - succeeded

22:35 switching to IDL collimation.

22:43 checked Z22 focus compensation, everything working weel, very small residuals of Z4 in the noise level (<100 nm Z4) for -200 nm Z22 sent.

22:49 John observes that the new build of GCS has overwritten our recent changes lZernike coefficients. Need to get those "hardwired". Updating the configuration file for now.

22:50 Updated AIP_L_RM_sub11.cfg to replace the scale coefficients with the 9-Nov-2008 values for Z4-Z11 plus Z22 (with Z12-Z21 still zero). Set threshold for applying Z22 to 300 nm rms.

22:50 doing a quick test collimating on stars at right angles to each other in field and checking that the first iteration of each sequence isn't a big jump...

22:51 going to GS 8 in Guide mode. AGW_Data/081114w, wfsc 2-10

23:01 going to GS 70 wfsc 11-15 first number sent to active optics" z4 , 290, z5, 156, z6, 145, z7, 9, z8, 24, z9, 20, z10, 20, z11, 6

23:05 going to GS 106 didn't acquire star, but 106 is quite faint, trying for 91 nearby failed again ,sending preset in acquire mode to see if I can see a star, star visible, John's theory is that it is not far above background, checking in the full image in DS9

23:19 changed "guidecam_lowCounts" from 1000 to 500 in the GCS configuration file , still not guiding. Tried adjusting IE CA (-3 -65) to better center star and it starts guiding (TORSTEN, why wasn't it acquiring the star on the previous acquisition images?)

23:27 going back on-axis to re-set IE CA... (IE, CA -> -4 -69)

23:35 Updated default IE in pointing model irtc.2008112.ptmod to -4 arcsec.

23:40 collimated on GS 91 (last wfsc 24) now gone to GS 64 first numbers sent to active optics Z4-Z8 318, 75, -46, 145, -75 do a focsu zero and switch to M1 active final collimation wfsc 35 going to GS 11

23:52 first set of numbers sent to Active optics Z4-Z8 414, -235, -113, -17, 68, collimating last wfsc 40 , going to GS 35 didn't get star, resending prset in acquire mode...

00:00 see that the GS 35 is in the same part of the chip in which acquisition was failing before, this however is a very bright GS, so don't understand why it should not acquire... trying just resending the preset...failed again on GS 35, the brightest GS we ever use, and the GS is within 100 pixels of the hotspot. see acquisition image acquire 00000023.fits (taken at 00:05).

00:07 now at this high elevation will check the GCS collimation with Z22 correction switched on. /tmp wfsc 132-148 watching Z22 drive to zero (with no big focus jumps)...

00:22 Z22 converged nicely. and now makes up the bulk of the applied forces on the mirror. Total Correction -32 (on PSF GUI). Now trying new button on PSF WAVEFRONT GUI, "HOLD WFS CORRECTIONS". Intend to hold corrections until the guide camera image is noticably degraded, then focus zero and measure residual aberrations in IDL.

1:04 Jesper has rolled back to last version of his AGW configuration file, we will test to see if acquisition works better now... note that after coming down from Zenith to 80 degrees IE an dCA need to be readjusted from -4 -69 to 0 -66

1:10 sending active preset to GS 8 preset failed, examination of the acquisition image (acquire0000026.fits) shows the star to be in the exact same place that it was failing previously tonight. Torsten, Jespers changes seem to be eliminated, is this something to do with GCS/PCS?

1:20 sending active preset to GS 35 and failed again see acquire00027, sending active preset to GS 82 Not guiding AGAIN acquire 000028.fits

1:25 sending active preset to GS 96 failed again see acquire 000029, sending active preset to GS 104 didn't guide but failed but very faint compared to background so not surprised, sending new APS to GS 97, at first didn't appear in guide box but was close enough to be pulled in. see acquire 31. cconverging slowly (too fiant see wfsc 165-169).

1:33 sending active preset to GS 64 immediately acquired and collimating wfsc 170-177

1:45 now sending preset to GS 39, immediately acquired (acquire 33.fits) star and collimating wfsc 178- 181 initial correction Z4-Z8 -> 304, 71, 487, -58, -161

1:50 going to GS 11, couldn't get guide star though GS 11 is 1000+ counts above backgroud as seen in acquire 34.

1:52 sending preset to 9108 @ 58 degrees elevation and star just off chip on acquire 35 .fits rest IE CA to -16 -58, an 18" change from the immediately previous star that had been centered on the hotspot. Resending preset in active mode and collimating a bit. sending preset to GS 23, failed see acquire37.fits

2:30 Doug preparing GS map for new BS star better positioned than we have, Nancy doing quick test of Lucifer preset and offset series while we're getting set up. Nancy sending active preset as Lucifer to BS9108 GS 0. No joy, and now sending presets in IRTC goes to the wrong place because of the Lucifer pointing model.

3:05 adjusted IE CA for the Lucifer model to IE=6 CA = 12, sent to M5_0151 from Lucifer, Nancy testing offsets then back to field aberration

3:30 collimating on BS9126 GS 0, but realize that we want an M5 star for EF data....

3:36 preset to M5_0258 GS 4 active, acquired star, collimating wfsc 198-

3:41setting up to take EF data send an active preset and fail to acquire star, see aquire .fits. Star had moved about 5 " and now not acquiring though easily visible.

3:53. In fact this is interesting, I sent the preset to GS 4 which failed to find a guide star, even though the star was easily visible in the acquisition image and indeed closer to the hotspot than it had been on the last successful preset. So, noting that the parent star had drifted in pointing I PTMODIFied the star on the IRTC back down to the hotspot and suddenly the GS 4 appeared in the guide camera and the system started guiding. The implication to my mind is that the original preset failed to send the guide probe anywhere.

3:57 collimating on GS4, getting ready for taking EF data on M5_0258, seeing around 2-3" taken cubes EF 96 preset to GS 3 and repeat...

4:07 collimated on GS 3 wfsc 215 taking EF cube 97-98

4:18 back to GS 4 to repeat 'cause it didn't work EF 99-100 (final collimation wfsc 219)

4:21 going to GS 10 having trouble, end up killing GCS resend preset, now it works. Unexplained GCS hang at 4:28.

4:30 resent preset and now collimating on GS 10 wfsc 220-222 taking EF data EF 101-102

4:37 preset to GS 9 collimating wfsc 223-226, taking EF data 103-104

4:46 gone to GS 6 collimating wfsc 227-232, taking EF data 105-106

4:54 preset to GS 8 (PA=200.53) collimating wfsc 233-236, taking EF data 107-108

5:02 preset to GS 12 acquisition failed because AZ drive dropped out, Wayne checking ... we have HBS errors and not starting back up.

5:26 doing a preset for EF to get bacground images BG 109-110

5:33 HBS problem intractable , signing off.

Final IE CA -20 -62

-- JohnHill - 14 Nov 2008
Topic revision: r6 - 14 Nov 2008, DavidThompson
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