E-time 20160213 UT

Observers: DMiller, JHill (Tucson)
Telescope Operator: DHuerta (LBTO)
AO Support: DMiller
Telescope Support: KNewton (LBTO)
Software Support: SGroup (Tucson)
Instrument Support: JMorris (LBTO)
Engineering Support: MGusick

Summary

TCS Build 2016A was tested and released for science. The GCS patch for MODS changing filters is not being used.

We measured field aberrations on LFBG and RFBG and found that no binodal adjustments were needed on either side.

DougM was able to close the SX FLAO AO loop using the reconstructor measured on Tuesday.

Phil, Amali and Denis were able to close the DX LBTI AO loop using 400 modes with the recently measured reconstructor.

John and Marco verified that the sign of the Z11 correction on LBC-Blue is correct.

Preparation

00:30 Switch to TCS Build 2016A

cp MODS_L.cfg MODS_L_2x2.cfg and changed guidecambinning from 1 to 2. (similar for MODS_R)

vi /lbt/tcs/current/gcs/configuration/GCS/Instrument2AGW.cfg

Details

Open

00:55 Open to photometric sky and light winds. A few cirrus clouds are drifting across Cochise County. We love the Omega block high pressure! T=+5 degC, D=-25 degC.

TCS Testing of Build 2016A

01:21 ACQUIRE preset with MODS/MODS in pseudomono mode, but MODS wasn't ready.

01:41 ACTIVE preset with MODS/MODS in pseudomono mode (green dot in wrong place, but guiding OK)

01:xx repeating preset fixes the graphics

01:54 RADEC offset - OK

01:55 DETXY offset - OK

01:56 Authorize MODS1 monocular only

01:57 ACTIVE preset monocular - OK

01:58 DETXY offset - OK

01:59 RADEC offset - OK

02:00 Authorize MODS/MODS (full binocular)

02:04 ACTIVE preset (full binocular) on V808 Aur gs=0 on left, gs=1 on right (star not found)

02:05 resent ACTIVE right with gs=4 (Axel's comparison star) shell was ripped

Good guiding data starts about 02:10 UT (beware of the beam splitter on MODS1) with default exposure time.
These images are in: /Repository/20160213/GCS/

02:18 Change to 1 sec exposure time on both sides.
gcsclient setExpTime left -e 1000
gcsclient setExpTime right -e 1000

02:19 Change to B-BESSEL filter with MODS gui on both sides (stars are red, so this really cuts the flux, so we aren't guiding) (MODS doesn't have a V or R filter.)

02:21 Press the "Stop Guiding" button on GCS guis. Then use the command line to collect full frame guider images still in B-Bessel.

gcsclient readGuideCam left -e 1000 20 to get the achieve full frame rate without guiding overhead
gcsclient readGuideCam right -e 1000 20

These images are in:
/lbt/data/share/tcs/telescope.20160213/right_guider000002.fits up to and including 000021
/lbt/data/share/tcs/telescope.20160213/left_guider000002.fits
These images are taken in the B-BESSEL filter despite what the header says.

02:25 gcsclient selectAGW right MODS_R_2x2.cfg
gcsclient selectAGW leftt MODS_L_2x2.cfg
to test 2x2 binning
Acquisition was OK, but guiding failed miserably. GCS seems confused by the binning.
KS: It appears to be in the clipping - we likely need to change the code to divide the clipping window by the binning factor. Since it failed, it was centroiding on nothing?

2016-02-13T02:25:57.620490+00:00 tcs1 LBT_GCSR: CamImage: createSubImage: coordinate mismatch in (xm 40, width 51, ym 40, height 51)
2016-02-13T02:25:57.620810+00:00 tcs1 LBT_GCSR: CamImage: createSubImage: coordinate mismatch ac (xmin 15, xmax 66, ymin 15, ymax 66)
2016-02-13T02:25:57.621074+00:00 tcs1 LBT_GCSR: AGWCamera: clipImage: warning:createSubImage(XY: 40,40 WxH: 51,51) returned NULL, its center too close to image edge

02:29 back to regular binning=1
gcsclient selectAGW right MODS_R.cfg
gcsclient selectAGW leftt MODS_L.cfg

resend the presets - OK

02:34 changed filters to B-BESSEL

02:35 changed filters to F525LP

02:42 MODS-issued binocular preset to StoneE (right side missed the star off the bottom)

David bumps IE/CA.

02:46 Olga does "r" for retry to resend the right preset which now succeeds, but appears to have grabbed the wrong guide star. John, Olga, Doug, Kellee, Michele and Chris are witnesses to this first recovery of an instrument issued binocular preset.

Restart both GCSs to revert Michele's GCS patch.

ACQUIRE preset to reset pointing on the right side. This is the binocular inefficiency personified.

03:03 binocular preset to StoneE at PA=0 from MODS. Olga is working on aligning the two MODS StoneE masks.
  • acqBinoMODS mods.44.StoneE1f_f525lp.acq
  • some notes on the alignments:
    • MODS1: modsAlign mods.44.StoneE1f.mms mods1r.20160213.0003.fits mods1r.2010213.0004.fits
      • offsetpointing -0.0855 -3.327 -1.652 detxy rel
      • mods1r.20160213.0005.fits, thru-mask confirmatory image, looks good.
    • MODS2: modsAlign mods.44.StoneE1f.mms mods2r.20160213.0002.fits mods2r.20160213.0003.fits
      • offsetpointing 0.7526 -1.305 -1.751 (first modsAlign, based on 2 and 3)
      • mods2r.20160213.0004.fits, thru-mask confirmatory image, is not very good.
        • I tried modsAlign again, mistakenly on the same two images 2 and 3, so effectively I 'doubled-up' the offsets: offsetpointing 0.7560 -1.372 -1.951
      • mods2r.20160213.0007 is a second field image.
        • third modsAlign, based on 2 and 7, yielded offsetpointing 0.7807 0.688 3.614. The delta Y is what I expect, but not delta Y or delta theta.
    • For neither MODS was the automatic box detection that good - it was best at the bottom right corner. "r" to refine box positions helped but still the regions file drawing the boxes was not perfectly over the box images.

03:34 switching to LBC on both sides. Cirrus clouds are moving up from the south.

03:52 ACT0370

03:54 DOFPIA - Red side was intrafocal to start, but

04:05 dithered LBC images of this pointing field (but John forgot to check the Guiding box on fast OB.)

04:07 try again. - OK - Red images are crisp and round. Blue images have aberration

John ran the new command "lbc restart" as user telescope, and it worked as Kellee already knew it would.

LBC complained about filters power problem when I turned it off

04:20 Switch to LUCI on both sides

Problems getting the SX AdSec to set.

05:14 ACQUIRE preset for LUCI/LUCI binocular from IRAF. Did not find either star.

Next we have pointing problems on DX AGW2. Why is this pointing worse than MODS? Or is DX MODS also bad?

05:37 ACTIVE preset in pseudomono mode - left GCSGUI shows hotpot in a funny position, but right is OK.

from 05:40 we have r-band guider images on both sides of V808 Aur (default exposure time).

05:43 ACTIVE preset again - both hotspots look OK now. Pointing is drifting 2.5x more on the left than right.

Michele changed binning on GCSL from GUI, but it didn't work.
KS: This was due to it being done on-the-fly. The guide loop is initialized with a binning. When binning changes, the azcam camera is notified, but the guide loop was going. It didn't get re-init'ed and so it started getting images that didn't match its configuration:
2016-02-13T05:47:30.344541+00:00 tcs1 LBT_GCSL: GT: guide image received has incorrect dimensions (should be 105 x 105): is 210 x 210 width x height, ignoring image contents.
2016-02-13T05:47:33.514879+00:00 tcs1 LBT_GCSL: GT: guide image received has incorrect dimensions (should be 105 x 105): is 210 x 210 width x height, ignoring image contents.
...

05:49 binning wasn't retained on preset
KS: no - because GCS resets to "default" binning at the beginning of an acquisition - do we not want this behavior?

05:52 gcsclient selectAGW left LUCI_L_4x4.cfg for both sides

This does change the ACQ size, but guiding is goofy as it was for MODS.
KS: Again, this could be the clipping, see the complaints:

2016-02-13T05:53:14.756468+00:00 tcs1 LBT_GCSL: CamImage: createSubImage: coordinate mismatch in (xm 53, width 76, ym 53, height 76)
2016-02-13T05:53:14.759866+00:00 tcs1 LBT_GCSL: CamImage: createSubImage: coordinate mismatch ac (xmin 15, xmax 91, ymin 15, ymax 91)
2016-02-13T05:53:25.490501+00:00 tcs1 LBT_GCSL: CamImage: createSubImage: coordinate mismatch in (xm 53, width 76, ym 53, height 76)
2016-02-13T05:53:25.490771+00:00 tcs1 LBT_GCSL: CamImage: createSubImage: coordinate mismatch ac (xmin 15, xmax 91, ymin 15, ymax 91)
2016-02-13T05:53:35.380991+00:00 tcs1 LBT_GCSL: CamImage: createSubImage: coordinate mismatch in (xm 53, width 76, ym 53, height 76)
2016-02-13T05:53:35.384585+00:00 tcs1 LBT_GCSL: CamImage: createSubImage: coordinate mismatch ac (xmin 15, xmax 91, ymin 15, ymax 91)
2016-02-13T05:53:45.224998+00:00 tcs1 LBT_GCSL: CamImage: createSubImage: coordinate mismatch in (xm 53, width 76, ym 53, height 76)
2016-02-13T05:53:45.225296+00:00 tcs1 LBT_GCSL: CamImage: createSubImage: coordinate mismatch ac (xmin 15, xmax 91, ymin 15, ymax 91)

05:54 gcsclient selectAGW right LUCI_R_1x1.cfg for both sides

This does change the ACQ size, but guiding is goofy as it was for MODS.
KS: this also complained quietly in the log - the clipping is too small for where the HS is. The clipping created a 76x76 image centered at 53x53, but the HS was at 106,106.
2016-02-13T05:55:22.374025+00:00 tcs1 LBT_GCSR: GT: initial.HS: 275.0, 237.0 [pix] (abs.) guideWindowX/Y: 170.0, 132.0  guideWindowSize:210
2016-02-13T05:55:22.374290+00:00 tcs1 LBT_GCSR: GT: GuideCam setSubframe to guideWindow: x,y,w,h = 170,132,210,210
2016-02-13T05:55:22.374621+00:00 tcs1 LBT_GCSR: AzCam: send: 'SetROI 170 379 132 341 1 1'
2016-02-13T05:55:22.375820+00:00 tcs1 LBT_GCSR: AzCam: recv: 'OK'
2016-02-13T05:55:22.376096+00:00 tcs1 LBT_GCSR: AzCam: send: 'GetDetPars'
2016-02-13T05:55:22.377574+00:00 tcs1 LBT_GCSR: AzCam: recv: 'OK 210 210'
2016-02-13T05:55:22.377845+00:00 tcs1 LBT_GCSR: AGWCamera: setSubframe OK:  x 170..379  y 132..341
2016-02-13T05:55:22.378188+00:00 tcs1 LBT_GCSR: AzCam: fromAbsolutePixelToROI: CCD.abs: 275.0 237.0 [pix] ROI: 170,132 : 379,341 binX,Y: 1 1 ROI.pos 106.0 106.0 [pix] x2, y2 check
2016-02-13T05:55:22.378478+00:00 tcs1 LBT_GCSR: AzCam: fromAbsolutePixelToROI: if (106.0 <= 379) & (106.0 <= 341) & (106.0 >= 1.0) & (106.0 >= 1.0) return TRUE
2016-02-13T05:55:22.378730+00:00 tcs1 LBT_GCSR: AGWCam: fromRelativePixelToClipped: if (106.0 < 15) || (106.0 > 90) || (106.0 < 15) || (106.0 > 90) return FALSE
2016-02-13T05:55:22.378982+00:00 tcs1 LBT_GCSR: AGWCam: fromRelativePixelToClipped: relative.pos: 106.000 106.000 [pix] clipped.pos 0.000 6.000 [pix] unchanged
..
2016-02-13T05:55:25.756203+00:00 tcs1 LBT_GCSR: CamImage: createSubImage: center (XY: 53,53 WxH: 76 x 76) getFilename = /Repository/GCSfiles/dailyimages/right_acquire000023.fits
2016-02-13T05:55:25.857711+00:00 tcs1 LBT_GCSR: GT: sextractor found no star.

05:57 Back to 2x2 binning

05:49 RADEC offset in pseudomono mode

05:59 DETXY offset

TCS Build 2016A testing complete

DX Field Aberration Data

06:11 Preset to BS9134

mkdir /home/lbto/data/20160213_lfbg and /home/lbto/data/20160213_rfbg

IN SEPARATE IDL windows and directories do this:

06:18 iif_register, /right field_collect, limit=250 for BS9134

06:22 iif_register, /left field_collect, limit=250 for BS9134

06:32 Doug turns off DX AdSec LUT. So data for GS=17 is likely contaminated.

06:44 GS=2 is a binary with ~1 arcsec separation

06:52:xx another SX guide image which seems to have been taken before the probe/telescope was finished moving.

Seeing is fluctuating between 0.4 and 0.6 arcsec during this dataset.

Note jump in SX aberrations at 7.32 UT. What caused this?

Why is the on-axis aberration changing as we change position angle? Could we have pupil wobble?

RFBG Results

No change required or applied

 => Field Data Results
      Motion of the secondary needed to remove bi-nodal astigmatism
  
                  rfbg
              From residual Focus Measurement
                  On-Sky Arcseconds
         -------------------------------------------
          Tip =   9.7", Delta IE =  -9.7"
         Tilt = -10.1", Delta CA =  10.1"
  
   
 => Field Data Results
             Measured bi-nodal astigmatism
  
                  rfbg
              From 45 Astigmatism Measurement
                  On-Sky Arcseconds
         -------------------------------------------
          Tip =  -8.0", Delta IE =   8.0"
         Tilt = -12.0", Delta CA =  12.0"
  
  
                  rfbg
              From 0 Astigmatism Measurement
                  On-Sky Arcseconds
         -------------------------------------------
          Tip =   6.7", Delta IE =  -6.7"
         Tilt = -10.1", Delta CA =  10.1"
  
  
                  rfbg
              From both Astigmatisms Measurement
                  On-Sky Arcseconds
         -------------------------------------------
          Tip =   1.3", Delta IE =  -1.3"
         Tilt =  -7.9", Delta CA =   7.9"

LFBG Results

No change required or applied

  => Field Data Results
      Motion of the secondary needed to remove bi-nodal astigmatism
  
                  lfbg
              From residual Focus Measurement
                  On-Sky Arcseconds
         -------------------------------------------
          Tip =  15.7", Delta IE = -15.7"
         Tilt =  13.2", Delta CA = -13.2"
  
  
   
 => Field Data Results
             Measured bi-nodal astigmatism
  
                  lfbg
              From 45 Astigmatism Measurement
                  On-Sky Arcseconds
         -------------------------------------------
          Tip =   7.1", Delta IE =  -7.1"
         Tilt =   4.6", Delta CA =  -4.6"
  
  
                  lfbg
              From 0 Astigmatism Measurement
                  On-Sky Arcseconds
         -------------------------------------------
          Tip =  11.4", Delta IE = -11.4"
         Tilt =  12.5", Delta CA = -12.5"
  
  
                  lfbg
              From both Astigmatisms Measurement
                  On-Sky Arcseconds
         -------------------------------------------
          Tip =   2.7", Delta IE =  -2.7"
         Tilt =  10.8", Delta CA = -10.8"
  

SX FLAO Tests

During engineering time tonight, we had SX FLAO closed loop

We used the reconstructor measured on Tuesday, 20160209_195514

We had closed loop for a bout 10 minutes before we had to move on to the next task, but we did collect three sets of data. The gains were just set manually (no optimization). The closed loop was stable until the clouds got thicker (skip frame).

AO394 8.3 mag star

-> some clouds up to 3 mag thick during these tests

mag from CCD 39 = 9.6
gain 0.5 0.4 0.2
save file 20160213_081847

mag from CCD 39 = 10.2
save file 20160213_082218

mag from CCD 39 = 10.2
gain 0.65 0.55 0.35
save file 20160213_082330

LBTI AO Tests

As with RFBG, we needed to remove the -4 mm Zglobal offset that was put on for the DX Rigid Secondary.

The DX Gregorian Pointing model found the star in LBTI right away. We had trouble finding the SX LBTI star and had to add -500 Tip to SX M3 in order to get into copointing range.

The DX LBTI loop was able to close in good seeing with 400 modes using the reconstructor measured in the last two days.

WRS Tests with LBC-Blue

11:00 DOWRS on ACT0241

Marco Stangalini is connect by Skype from Rome.

Running OB, Iteration =        2
Waiting for OB to finish and data files to appear in /newdata
Waiting for file in /newdata/lbcb.20160213.??????.fits
2016-02-13
Processing: /newdata/lbcb.20160213.111310.fits
BLUE par file read
--------------------------------
WRS ver. 0.9.8
--------------------------------
2016Feb13_11:13:49
--------------------------------
RUNNING WRS IN SLOW MODE
% LOADCT: Loading table B-W LINEAR
% LOADCT: Loading table RAINBOW
% LOADCT: Loading table B-W LINEAR
% LOADCT: Loading table RAINBOW
% LOADCT: Loading table B-W LINEAR


===========================================================
===========================================================
===========================================================
If I am not wrong Z11 is very large, isn t it?
===========================================================
===========================================================
===========================================================
If you see large Sph, options 1 or 2 are suggested.
If you see coma larger than Sph than suggested option is 0
1 = Sph close to the obscuration
2 = Sph toward the edges of the pupil
0 = NO Sph first order correction (not suggested if large SpH present)
: 2
 Z         1       2       3       4       5       6       7       8       9      10      11
Cycle:        1  RMS=       92.2418 percent
 um    0.500   1.764   3.320  13.183   0.000   0.000   0.000  -0.000   0.000   0.000  -0.800
Computing the interaction matrix...
      11 singular values rejected in inversion
Cycle:        2  RMS=       92.2418 percent
 um    0.500   1.764   3.320  13.183   0.000   0.000   0.000   0.000   0.000   0.000  -0.800
Cycle:        3  RMS=       92.2418 percent
 um    0.500   1.764   3.320  13.183   0.000   0.000   0.000   0.000   0.000   0.000  -0.800
Computing the interaction matrix...
      10 singular values rejected in inversion
Cycle:        4  RMS=       72.7723 percent
 um    0.528   1.763   3.318  13.221  -0.001  -0.002  -0.015  -0.006   0.002   0.003  -0.696
Cycle:        5  RMS=       63.6567 percent
 um    0.544   1.763   3.317  13.242  -0.002  -0.003  -0.023  -0.009   0.002   0.005  -0.639
Computing the interaction matrix...
       8 singular values rejected in inversion
Fitting done!
***************** Zernike coeffs in mu starting from defocus **********************
      13.2422   0.00209972   0.00295149   -0.0225443  -0.00904714   0.00240656
   0.00535221    -0.638587
***********************************************************************************
Focus Offset = -0.50000000  Filter = V-BESSEL  Rotator = 39.127290
***************** Rotated Zernikes in nm starting from focus **********************
      49.6074     -1.96981     -2.12526      5.88974     -10.6224      1.09372
     -1.37955     -319.294
--------------------------------------------------------------------------
          Computed Aberrations (nm)              |   (arcsec)   | channel 
 Defoc   AstX   AstY   ComaY  ComaX   Sph        |  Est.   Est. |         
 (Z4)    (Z5)   (Z6)   (Z7)   (Z8)   (Z11)  (Z22)| seeing  WIQ  |         
--------------------------------------------------------------------------
    49     -1     -2      5    -10   -319      0   0.54   0.22    blue
--------------------------------------------------------------------------

--------------------------
TCS Send Wavefront program
--------------------------

Reading "lbciaCoeffs_blue.dat" file ... Sending data to TCS ... Success

Checking for Blue Convergence
Limits:    250.0   250.0   250.0   400.0   400.0   250.0    50.0
Red is not used,  Blue is analyzing

It appears that the sign of the Z11 correction is correct (JMH reversed it yesterday). We have been working on the gain and zeropoint of the coma correction.

12:22 lbcb.20160213.122242 is a 60 sec exposure taken after a good WRS convergence.

Now Marco is adjusting the sensitivity, but previous value seems better.

12:50 180 sec exposure with LBC-Blue in V-BESSEL stars are slightly elongated, but we are at EL=41.

12:53 dowrs, /redonly

13:05 120 sec exposure with LBC-Red in r-SLOAN after WRS convergence.

Close

13:10 Close for impending twilight.

-- %USERSIG{JohnHill - 2016-02-12}%

This topic: Commissioning > Main > WebHome > Com20160213
Topic revision: 10 Mar 2016, KelleeSummers
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