Science Operations

Quick Review

Quick review of setup and observing commands for binocular MODS observing:

  • Log into LBTO workstation using your partner account (INAF,LBTB,OSURC,AZ). Instructions for the older, 32-bit OS machines, obs2,obs3 and obs4, and the new 64-bit OS machines, obs5, obs6 and robs differ slightly and are indicated by grey/black text for the old and green text for the new. If you are observing from the remote room, open an x2go session into obs2, obs3, obs4, obs5, obs6 or robs with your partner account. Use a gnome session for obs2,3,4 and a MATE session for obs5, obs6 and robs.
  • Copy your scripts to the obs2, obs3, obs4, obs5, obs6 or robs machines. The partner home directories are cross-mounted on obs2, obs3, obs4, but they are local to obs5, obs6 and robs.

    • scp -r myscriptdir/ PARTNER@obs2.mountain.lbto.org:~/    will copy the entire directory myscriptdir/ to /home/PARTNER on obs2.
  • Open a terminal window and type mods1 status and mods2 status. Everything but the mods1 and mods2 guis (UI) should be running and owned by mods.
  • Open 2 terminal windows: in one type mods1 start gui and in the other type mods2 start gui. This should launch the MODS Control Panel.
    • Click GetDate on the right side of the Instrument Setup Screen to update the UT date in the image file names. Make sure it is the correct UT date for the night. If it is before 5pm (00h UT), you will need to edit the date to be the UT for the coming night. If you have taken data already with that UT date, click refresh and double check that the Blue and Red CCD filenames do not already exist. Once you’ve checked that the starting filenames are what you want, click Apply. 
    • Enter the Observer/Project Information on the left side:
      • Partner, PI and Project ID will be filled in by the scripts which you run and do not need to be entered at this time.
      • At this time, you need only enter:

        • Observer Names (can be separated by commas and spaces). This goes into headers as the value for the keyword, OBSERVER.
        • Support (SUPPORT), Telescope Operator (TELOPS) and a Comment describing the run.
      • Once all the necessary updates have been made, click Apply, then Save.
  • Wake up MODS:
    • cd ~modseng/modsScripts/Support (cd ~/modseng/modsScripts/Support on obs5, obs6 and robs)

      • On obs5,6 and robs, you may need to create a link under /home/<partner>: cd; ln -s /lbt/data/old_homes/modseng modsens better (31-May-2022: A better solution will be implemented soon.)
    • execBinoMODS mods1Wake.pro mods2Wake.pro
  • Open another 2 terminal windows: in one type modsDisp (modsDisp –mods1) and in the other type mods2Disp (modsDisp –mods2). This will launch two read-only ds9 windows per MODS to display the most recent Blue and Red images, while the terminal windows will display a table of the images as they arrive on the /newdata (/lbt/data/new) disk. You should keep the terminal windows visible, as you can copy/paste filenames from them into the modsAlign command line.
  • Take a set of test images:
    • execBinoMODS simSnap.pro
      • The simSnap.pro script is also in ~modseng/modsScripts/Support (~/modseng/modsScripts/Support)
      • 25-Feb-2021: Recommending to use simSnap.pro rather than sieveSnap.pro. simSnap takes an image through the sieve mask and then an image through the imaging mask, thus allowing us to monitor cleanliness of the optics.
  • put MODS into Observing Mode.

    • Click the “Observing” button near the top left of the Dashboard and,
    • once the calibration unit has finished moving, click Home to move the guide probe to its home position.
  • Open ancillary tools:
    • LBTplot: In a terminal window, type LBTplot to launch this tool.
    • GCSGUIs: In another terminal window, type GCSGUI left & and then GCSGUI right & to launch the GCSGUIs
  • Give the OSA the coordinates of your first target so he can check pointing and collimate.
  • Acquisition:

    • acqBinoMODS mymods1.acq.txt [mymods2.acq.txt]

      •  will launch two terminal windows and run acqMODS –mods1 mymods1.acq.txt in one and, in the other, acqMODS –mods2 mymods1.acq.txt (or mymods2.acq.txt in case two scripts are given on the command line).
    • run modsAlign (filenames and arguments/options can be in any order on the command line):

      • long-slit alignment to position target 11″ (MODS1) and 9″ (MODS2) above slit center:

        • MODS1: modsAlign -y 11 mods1slitimg.fits mods1fieldimg.fits
          • should put target at Y~617 on 1Kx1K mods1r image
        • MODS2: modsAlign -y 9 mods2slitimg.fits mods2fieldimg.fits
          • should put target at Y~590 on 1Kx1K mods2r image
      • MOS alignment:
        • modsAlign modsmaskimg.fits modsfieldimg.fits maskfile.mms
  • Observation:
    • execBinoMODS mymods1.obs.txt [mymods2.obs.txt]
      • will launch two terminal windows and run execMODS –mods1 mymods1.obs.txt in one and, in the other, execMODS –mods2 mymods1.obs.txt (or mymods2.obs.txt in case two scripts are given on the command line).
    • execBinoMODS is used for all spectroscopic observation, imaging and calibration scripts.
  • Calibrations:

    • Must be taken at zenith and with the dome dark (comparison lamp spectra are OK to do when there is light, though).
  • End of Night: put mods to sleep
    • cd ~modseng/modsScripts/Support (cd ~/modseng/modsScripts/Support)
    • execBinoMODS mods1Sleep.pro mods2Sleep.pro