UT 11 Sep 2021



Night Staff:

OSA: D.G. Huerta

ISp: Mtn Staff

ISA/Observers: O. Kuhn. D. Thompson and Engin Keles (PEPSI PI) are online as well.

Technical Wizard: J. Hill (Tucson)

Mtn Manager: M. Wagner

Sunset: 18:37

Twlight Ends: 19:55

Twilght Starts: 04:37

Sunrise: 05:56

Starting Config: PEPSI

Handover from PEPSI to LBTO: UT 06:43 or 11:43 local time

Night Log:

00:48 David is checking pointing and collimating

Twilight observation of RS Oph

Started PETs observation.

02:30 UT - Ilya noted that the spectra obtained on SX/DX sides differ - are we pointing to the same star on both sides?

Dave, Ilya and I discussing pointing model data collection: Use BS6 to reflect all light to guide camera (but it probably doesn't make much difference so long as the same BS is used throughout). Use iraf task PtStars with input list /home/lbto/POINTING/PtStars_10m/PtStars_10m.dat (the format of /home/lbto/POINTING/AllStars10.dat is different - AllStars is an old list). Run PtStars on PtStars _10m.dat to generate a list for a given LST. It will generate a list that is sorted by AZ. Start at an extreme in AZ (-90 or +450) and select stars about 3 stars clustered about that AZ but at different elevations. Re-run PtStars for a new LST every 3-4 stars, and examine the output. Try to select stars to work your way from the starting to the ending extreme in AZ and zig-zaging in elevation, and try not to observe the same star more than once (since it could introduce some systematics(?))

02:38 After checking pointing, sent the preset again. Pointing was about 15" off. Now the fluxes on the back-reflected image are closer - before they were different by a factor of 10 and the spectra were different.

03:22 Noting that the Seeing Plot has a lot of spikes. LBT plot flux also has some spikes. Looking at the guide images (e.g. ds9 left_guiderimage0007*.fits), we see some images where the central core is saturated though in most images the peak is only about half-saturation, 30k. The spikes do not seem to appear randomly (look at LBTplot) and, when saturated, there are several pixels in the core that have 65k counts, that this doesn't seem to be just seeing variations. Background levels are not changing this much. We're wondering whether this is evidence of an electronic problem - an instability in the gain.

03:36 Both sides suddenly drifted off hotspot, but it was worse on the right side. Ilya resent the preset. happened during 037 (r) and 040 (b) - happened just at ingress. HA = -00:24

03:41 DX jumped off hotspot and then returned. HA = -00:19

04:12 DX off again. David will preset on the DX side only. HA = +00:11

04:13 DX back on-target

04:19 DX jumped again,David sent a DX_only preset to recover. Critical IT 8470 HA=+00:19

04:26 Ilya is rebooting the azcams, David restarting both GCSs.

04:29 DX jumped again. Recovered, but wrong star on the DX side. 00:28

04:38 Ilya change the binning from 4 to 2 (the FWHM excursions are smaller, but still seeing "flashes"). Immediately afterwards, SX side jumped.

04:38 Another SX jump seen on guide and WFS images. HA=00:37

Wind speed is low, ~4 m/s and steady.

04:53 SX WFS image shows jump. Recovered by itself. HA=00:52

05:24 Now we have bin 2 and we are still seeing the "flashes". We have not seen the jumps off the HS for a while --- were they only happening as the object crossed the meridian? Object RA, DEC = 20:01:39.99, 22:46:18.9.

Pointing model data collection

PtLog started - it will be written to /lbt/data/share/PointingLogs/20210911_[S|D]X.log

02:46 David is slewing to PT10m093 in acquire mode- he centered in the star on the pinhole and then sent an active preset.

02:51 BS1 is in place, though we put in BS6 to see. Worry that we could pick up different stars on each side without knowing it, but it does not sem that BS5 will help.

Images numbers in parenthesis were added after the fact, based on timestamp. In all cases after BS1 remained in place, the last guider image before the slew to the next field was collimated. The image numbers noted here are usually before the last one (due to overheads in recording and selecting and slewing to the next star). For star 81 where we switched to BS6 after the star was collimated with BS1, there the guider image number is chosen based on the time stamp, which is only to minute resolution, so there is some ambiguity (one has to examine the guider image to see if the pinhole is seen, in which case, BS1 is in, or not).

star UT left_guider right_guider AZ EL Comments
93 06:53 3335 2228 340 59 BS1 star landed on hs
82 06:56 3346 2249 330 40 BS1
94 07:02 3374 2274 297 72 BS1
81 07:0x         spot in SX WFS image is double - 2 different stars? David going into acquire mode to check - it seems to be a ghost
81 07:13 (3414)   289 32 BS1 still and collimated (index numbers filled in after the fact, switch to BS6 makes it so I rely on UT I noted)
81 07:15 3434 2315     BS6 is in place to check/compare
89 07:22 3483 2363     BS6, collimation was off, esp on DX, it needed a few cycles to converge
89 07:26 3520 2394 275 51 BS1, We are going to stick with BS1
84 07:30 3544 2422 268 31 BS1, very low, el 31 deg, star landed on HS
91 07:33 3565 2439     BS1 (do not use...still star 84 I see no record for this star RA/DEC in the guider headers)
95 07:38 3592 2458 241 64 BS1, collimation is far off on both sides, worse on DX, WFE >3000 at start
100 07:47 3655 2501 242 83 BS1, high elevation, 83 deg, no star found on DX - David went into acquire mode to pull in star from top 03:44
96 07:52 3679 2517 220 46 BS1
102 07:55         BS1, failed to find star on DX, 70 deg elev, David going to acquire mode to pull the star in from the right by about 12"
102 07:59 2536 3717 188 70 BS1
003 08:         BS1 (all below BS1 unless noted), SX side failed to find star, 40 deg elevation
003 08:09 3746 2616 176 41 David pulled star in on SX, but star on DX disappeared, resent preset after which both sides found star
002 08:13 3758 2634 177 57 el 56 star fell near HS
010 08:22 3812 2684 150 31 el 30, star relatively faint on both sides - collimation took a few iterations -
005 08:32 3864 2745 152 78 el 77, no GS found on SX side, there were a couple of stars and uncertainty. take data point and come back
014 08:38 3883 2779 112 52 51 deg
011 08:43 3915 2804 97 70 70 deg, landed near HS
012 08:47 3930 2818 142 50 50 deg, landed near HS
016 08:52 3957 2838 133 33 32 deg, landed near HS
019 08:56 3975 2856 90 50 50 deg, landed near HS
025 08:59 3989 2870 75 37 36 deg, landed near HS
015 09:03 4002 2888 52 62 62 deg, landed near HS, initial collim on DX not very good
005 09:10 4034 2913 195 79 79 deg, now after transit, landed near HS
008 09:17 4059 2939 355 77 77 deg and just after transit, landed near HS
024 09:28 4125 2995 412 46 44 deg, landed near HS - did it pick the right one?
017 09:33 4149 xxxx 381 52 51 deg,
034 09:39 4171 3045 368 32 32 deg, this one is a double but picked brighter of the two, unambiguous
032 09:44 4200 3065 402 32 31 deg, landed near HS
024 09:48 4226 3092 412 49 48 deg, landed near HS
011 09:59 4274 3110 144 85 83 deg, in E, failed to find star on DX side, David pulled star in by ~20"
101 10:05 4290 3127 311 56 56 deg, landed field
102 10:10 4309 3141 247 52 52 deg, found star this time
Some observations:
  • The star was not found much more often on DX than on SX
  • One high el star 005 was not found when E of meridian but found after it transited
  • Sometimes, the initial collimation was quite poor, WFE ~ 2000-3000
  • NB in the above table "landed near HS" should say just "star was found" ... "near" is loosely used, although for the first few stars, they really did land close to the HS.

10:13 Reconfiguring to LUCI1

M31 Test:

In the test script in LUCI_2021_Restart_V1.40.xml, the TPE shows that the guide star is at the very edge of the patrol field and it is indicated by a red dot even at the initial offset. This is not the case for the LaBarbera OT - one difference is that it is a fraternal OB and this one is LUCI1 only.

10:44 Send LUCI1 script, M31_test. It found the guide star and is taking acq images. The star was close to the HS and there are not other stars in the acq field of view. WFS images are vignetted at left and right, mostly right edge.

L1: 1 & 2, 3 --> offset sent was -4.156", 0.2815". --> 4. Tweaking it to the right by 0.15" --> 5

10:55 Continuing: 0 10 offset is fine. The script will do 4 offsets on slit and then make a large offset to sky where it will again do 4 offsets, but this time with no guiding. Then it will return to the target. luci1 images 6-9

11:00 Large offset made to sky - guiding paused 10-13

11:06 Made the large offset back to the target/guide star fine. 14-17

11:11 Again to sky 18-21

11:17 Back to object with no problem 22-25

Again to sky 26-29

NS long slit spec with dithers test:

11:29 Slewing to Comet 67/P Churyumov-Gerasimenko

11:35 acquisition images: 30 & 31, slit is 32. I don't see anything. Updated ndit from 1 to 20, now exptimes 2.51 x 20. Still nothing. We're at Ks - trying z.

At z, slit 36 and field 37 and 38. I may see it at 1427 1264 on the subtraction 38-37

While I was looking for the target, we lost the guide star.

12:07 Resending preset (oops - sent telescope to wrong object).

12:10 Now to comet. I had to change guide star.

12:19 finally sending an acq to the comet. z 5x20 acquisition (oops - meant 12 dits). It is getting bright but we'll see.

12:20 In the first field image, 40, the guide star trails are not smooth, there are two blobs. Rates are high: 2000

I cannot see a comet or anything that is not trailed.

In the images, there is a lot of structure in z - a bright crescent (see 40 and 41) at the bottom

12:27 Going to blank field for sky flats. K: 43-47

12:33 J 48-52,

K 53-57 5500 counts (was mistake but may serve as low illum flats)

z 58-62 (too bright)

J 63- (too bright)

H too bright

Ks 66-70 13,000 counts

K 71-75 30,000 counts - too bright

12:49 David is closing up.

I've put in the blind filters and turned off flexure compensation as the script I was running to take the dithered set of flats did not seem to do that (?).


Proposed Plan of Action:

  • If PEPSI is unavailable at twilight
    • LUCI-1 Dual BLR target - twilight until 08:45 local time
      • Take Telluric first as soon as AGW-1 can wave-front sense
    • MODS (Wagner)
      • 18:57:30 +16:53:39 - 30deg limit at 00:15hr
      • 17:50:13 -06:42:28 - 30deg limit at 22hr
  • PEPSI Pointing Model - depending on conditions and transform completion by D. Miller
  • If Transforms ready proceed to appropriate instrument to collect Transform Confirmatory data
  • Otherwise stay with PEPSI for Pointing Model
    • PtStarrs
    • Need 28 stars
    • Remove retro-reflecting dichroic (to give full FOV)
    • Take images with PFU (Active mode) -not a requirement, images come "free"
    • Turn on PCS logging
  • Configure to LUCI-Bino
    • LUCI-1 M31 observation check - up to 1hr
      • Conditions - Any
      • Bulge Coordinates 00:42:44.570 41:16:05.70
      • Center slit on bulge, verify GS can be found in crowded field.
      • Offset 20' to a sky frame and verify return can place slit on original position and find the original guidestar
      • This is a test for an upcoming INAF program.
      • Location: in V1.39 (or later if Barry keeps updating the OT like an OCD maniac) of the LUCI OT Restart Script
      • The original scripts need to be fixed, there are some mistakes in the setup - B. Rothberg has made (reasonable) corrections to the script for testing.
    • LUCI-1 NS Longslit
      • Conditions - Any
      • Comet 69 CG - scripts based on UT times - earlies is 01hr local time
        • Enter '90000693' in the NSIGUI (this is the JPL ID Horizon and NSIGUI will work with correctly)
        • IF NSIGUI issues persist, there is a 90000693 txt file in /lbt/ephemeris on ROBS for every UT data through end of restart that can be used
        • dither along the slit +/-45" zJHKspec G200
    • AGW-1/2 Transform Confirmatory Data - 1.5hr - Highest Priority
      • Fields:
      • <a href='https://wiki.lbto.org/bin/edit/Commissioning/StoneO?topicparent=Commissioning.Com20210906' rel='nofollow' title='Create this topic'> StoneO </a> 21 37 31 +00 31 55 Stone_O_m12.list
      • <a href='https://wiki.lbto.org/bin/edit/Commissioning/StoneP?topicparent=Commissioning.Com20210906' rel='nofollow' title='Create this topic'> StoneP </a> 22 35 49 +01 31 33 Stone_P1.list
      • <a href='https://wiki.lbto.org/bin/edit/Commissioning/StoneA?topicparent=Commissioning.Com20210906' rel='nofollow' title='Create this topic'> StoneA </a> 00 54 02 -00 32 34 Stone_A3.list
    • Photometric Standards (clear any seeing)
  • Configure to MODS-Bino (lower priority unless transform and/or clear)
    • Confirmatory AGW Transform - 1.5hr - Highest Priority
    • Spectrophotometric stars (if clear any seeing)
    • Standard Stars (if clear any seeing)
    • Pointing Model (poor weather and poor seeing)
  • LBC (after LUCI tests)
    • Photometric Standards (clear any seeing)
    • Spectrophotometric stars (clear any seeing)
    • Pointing Model LBC (poor seeing, clouds)
      • Turn on PCS logging


Current Status

  • LBCs
    • LBC-Blue - available
    • LBC-Red - available
  • MODS
    • MODS-1 - issues with M1RC headers & filenumbers short 1 digit
      • Imaging OK both sides, spectroscopy blue only for acquisition
      • AGW-5 - available
    • MODS-2 - available
      • AGW-6 - available
  • LUCI-1 - available
    • AGW-1 available
  • LUCI-2 offline
    • AGW-2 available
  • PEPSI - available
    • AGW-7/8 available


Closed Dome Activities

  • MODS-1 Full set of Cals
    • Biases
      • 1x1
      • 1x2
      • 2x2
    • Grating
      • Dual
      • Red
      • Blue
    • Imaging
      • Dual
      • Red
      • Blue
    • Prism
      • Dual
      • Red
      • Blue
  • MODS-2 Cals
    • Bias
      • 1x2
      • 2x2
    • Prism
      • Dual
      • Red
      • Blue
  • LUCI-1 Cals
    • Imaging N375 Flats
      • Narrow, medium-band filters
      • Broad zJHKKs and HeI completed
    • N1.8 G210 CWL=2.3 K-band 0.5" cals
    • N1.8 G200 CWL=1.93 HKspec 0.5" cals
  • ARGOS Cal-Unit test for M3 alignment and pupil wobble checkout (alternate to on-sky method)
  • LUCI-1 Only Calibrations
    • Flexure data for G150
      • /home/dthomspons/Luci/FlexureCompensation
      • README - Calib15 - 2hrs
      • Ks filter, Argon lamp, optical sieve mask
      • take dark frame
      • Manual Control MCSGUI for elevations
    • Wavelength data for G150
      • G150 Ks, Argon, take image through slit, then put in grating, line should show up where the slit is located (within a few pixels of the image of the slit)
      • Check a few lines (2 or 3)

-- BarryRothberg - 09 Sep 2021
Topic revision: r8 - 16 Sep 2021, OlgaKuhn
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