wiki:PublicPages/MayallZbandLegacy/NotesforObservers

Version 33 (modified by Arjun Dey, 8 years ago) (diff)

--

OBSERVING INSTRUCTIONS FOR MzLS

Still need to incorporate the following instructions:

  • Pointing the telescope, and re-zeroing the pointing using the numbers reported by MOSSTAT
  • Focusing the camera
  • Running the guiding loop (or choosing not to)
  • Instructions for converting the JSON files into the ones that the telescope can read (what are these called?)
  • Instructions for checking in the updated tile file (probably also need to add this to the DECam observing instructions)
  • Coverage plots, which we've not yet ported from the DECam version

These are instructions for using the MzLS planning scripts for the nightly program. To see the Mosaic observing manual, go here: http://www.noao.edu/kpno/mosaic/manual.

Log on to the mzls account on the mayall-idl.kpno.noao.edu machine (which can only be done from within the KPNO network or using a VPN):

Username : mzls
Password : Ask Arjun, David, or previous observers

These environment variables define the locations of data and code:

$MOS3_DATA= -- This is where our raw data files are written
$MOS3_OBS=$HOME/mosaic3 -- This contains the observing product with code and versioned log files.
$PS1CAT_DIR=$HOME/ps1/chunks-qz-star-v2 -- Pan-STARRS1 catalogs used by the IDL DECSTAT routine for computing astrometric offsets and photometry

These path names are set in the .bashrc file, or can be set for example with "export MOS3_DATA=/mosaic3/data2/observer". The $MOS3_DATA directory must be updated to point to the current night's data.

Other directories in the home directory are:

data/ -- Link to the top-level data directory, where each night is stored in subdirectories like "20151213"
exec/ -- Cross-mount to mosaic.kpno.noao.edu:/home/observer/exec
products/ -- Code checked out from the SDSS and the DESI svn repositories

Documentation for the IDL scripts can be printed from the IDL prompt with the DOC_LIBRARY command, for example:

      IDL> doc_library,'mosstat'

Date convention

All dates in log files are set to the local date of the beginning of the night. For example, any data taken during the night of December 13/14, 2015 will be written as 2015-12-13. This is consistent with how the NOAO Science Archive timestamps and saves the raw data files.

Official Nightly Strategy

Detailed instructions for NightlyStrategy?

Creating an almanac file with the observations for the night

At the end of the night, an almanac file should be generated for the night and checked into svn.

cd products/mosaic3/logs
idl
   almanac, <START-EXPOSURE>, <END-EXPOSURE>
   exit
svn add Almanac*
svn commit Almanac*

For example, for the night of March 26/27, 2015, this is done with:

cd products/mosaic3/logs
idl
   almanac, 424978, 425143
   exit
svn add Almanac_2015-03-26.*
svn commit Almanac_2015-03-26.*

There are actually two versions of this file, one that is an ASCII file (with .txt extension) and one that is a FITS file (with .fits extension).

Writing the human logs

THE FOLLOWING NOT YET UPDATED FOR MOSAIC-3

Please write about what happened during your night: weather conditions, which pass you observed, and telescope problems. Follow the example on the pages at DecamLegacy/ObservingLogs.

Catastrophically bad frames (such as saturated frames, or where the telescope moved) are recorded and svn-checked-in to products/mosaic3/logs/bad_expid.txt.

In case of technical difficulties

We have in the past encountered technical difficulties that have restricted where we can observe to a specific range in RA/Dec.

If this happens during your run, you have several options:

  1. First, try running mosaicstrategy.py with an appropriate --airmass-limit and/or --moon-sep-limit to try to keep to the required range of tiles.
  2. Shorten your observing period (using --start-date,--start-time and --end-date,--end-time) such that it's scheduling fewer tiles.
  3. Increase the assumed seeing such that it schedules longer exposures.

For reference, the tiles we’d be observing with MOSAIC3 in z-band are:

IN_DESI = 1 DEC > 30 88 < RA < 301 PASS <= 3

That’s 48760 tiles.


Example run-through for a given night


Update everything

Log into the mzls account on the mayall-idl machine.

Update the code, log files and most importantly the tile file:

cd ~/products/mosaic3
svn up
cd ~/products/observing
svn up

Set the paths

The data path must be changed to point to the current night's data. Edit the entry for MOS3_DATA ~/.bashrc file, for example if the start of the night is 13 Dec 2015 change this to

export MOS3_DATA=/mosaic3/data2/observer/20151213

Create nightly plan

Create the nightly plan from the available tiles. This will read the tile file to see which ones are already completed.

cd ~/products/mosaic3/json
python py/mosaicstrategy.py -t obstatus/mosaic-tiles_obstatus.fits -d *UT date at ''start'' of night* -p *portion of night* -pass *pass number*
python ./py/jnox.py --in *JSON input file --out *Output shell script
scp *output shell script to the /home/observer/exec area on mosaic3

Start up mosaic control software

On mayall-2, double click on the MOSAIC3 icon, which brings up the MOSAIC3 Menu on the left edge of the screen.

  1. Start the camera control program by pressing the yellow "Start Cameras" button. Wait for this to finish, then dismiss the screen by typing any key as instructed
  2. Start the MOSAIC3 NOCS software by pressing the blue "Start MOSAIC" button. This launches a blue xterm. Move it out of the way and watch all the windows come up
  3. Rearrange the desktop as needed.

If, for some reason, the buttons do not work, you can start up the software on a command line as follows: On mayall-2 open a terminal window and:

ssh -XY observer@mosaic3
nocs start ccp (this is equivalent to the "Start Cameras" button on the MOSAIC3 Menu)
nocs start all (this is equivalent to the "Start MOSAIC" button on the MOSAIC3 Menu)

Once nocs is up and running, rearrange windows as desired, and check the status of the system by typing the following in a nocs terminal window:

nocs status all
nocs fullstatus ccp

Set the PROP-ID and Project Info

On the NGUI window, press the "Set Project" button and fill out the relevant information. For example,

Principal Investigator: Arjun Dey
PIs Email Address: dey@noao.edu
Actual Observers: Tristram Shandy, Bertram Wooster
Observing Assistant: Karen Butler
OA's Email Address: 4meter@noao.edu
Proposal Identifier: 2016A-0453
Telescope System: KPNO Mayall 4m
Science Instrument: Mosaic 3

Please ensure the Proposal Identifier number is correct''

Then, in one of the NOCS xterm windows, type: "nocs set project"

Take a test image to ensure everything is working

Check that all is well by taking a test zero exposure. On the IRAF window, check the image statistics by cd-ing to the correct directory and typing "mscstat <filename>"

Take dome flats and zeros

During the afternoon (after 4pm), take dome flats with the telescope pointed at the white spot.

  1. Check that telescope is pointed to the white spot with mirror cover open
  2. Take 10 zero exposures
  3. Turn on low dome flat field lamps at 100% intensity (~50V)
  4. Create a dome flat script using the NGUI interface. Exposure times as follows:

z-band : 20 sec
r-band : 25 sec
g-band : 20 sec

Take 11 flats in z-band every night; only take flats in other bands if you intend to use them. Counts should be ~18-20k adu.

  1. Take 20 zero exposures
  2. Go eat dinner

Start the automated script for updating the tile file

From a terminal on the mayall-idl compute, in the mzls account, start this running:

idl
   muptiles

From another terminal in the mzls account, start this running:

idl
   mosstat_continuous

This will run mosstat on each frame as it shows up and display the results on the screen.

Observe - start of night

  1. No on-sky observations are permitted before 12 deg twilight.
  1. At start of night, check telescope pointing and zero the telescope coordinates using a bright star placed on the telescope boresight (defined as the center of the mosaic3 focal plane).
  1. Move to the beginning of the first MzLS tile position
  1. Focus the telescope

- create a focus script using the NGUI
 - run the focus script from the /home/observer/exec directory 
 - analyze the focus image using mscstarfocus 
    - edit the mscfoc.cl script to correct the name of the image that needs to be analyzed 
    - mark about 10 stars around the image; mark the top star in each sequence using "m"; "q" to quit 
 - log the Truss temperature 
 - set the telescope focus  
 - focus the guiders; this way you can use the guider images to monitor focus drifts

Observe - all night long!

Execute mzls*sh script

In a nocs terminal window (on the mosaic3 computer): Go to /home/observer/exec, and execute the mzls*.sh script.

Monitor focus by checking the image quality on each frame. Keep track of the truss temperature variation and modify the focus as needed. The Mayall has astigmatism, so one can tell from the shape of the images which way to move the focus.

need a figure here

If conditions change compared to assumptions for the script, re-run strategy.

End of night

No on-sky observations are permitted with MOSAIC3 before 10 deg twilight or after 10 deg dawn. No twilight flats are allowed.

At the end of night, shut down the software.

  1. Ensure that the "Shutter" and "ready" are both in the "Dark" position on the MCCD gui
  2. Press the red "Stop MOSAIC" button on the MOSAIC Menu gui. Wait for this to finish.
  3. Then press the yellow "Stop Cameras" button on the MOSAIC Menu gui.

If the buttons do now work, then go to one of the NOCS xterm windows and type:

nocs stop all (equivalent to pressing the "Stop MOSAIC" button)

Once nocs is shut down, type

nocs stop ccp (equivalent to pressing the "Stop Cameras" button)

Once this is done, type

nocs status all nocs fullstatus ccp

and make sure everything is shut down. Only when this is done, is it safe for the OAs to put on the lights in the dome.

Create the Almanac and Almanac plot files

At the end of the night, create the Almanac files and check them into svn.

- cd products/mosaic3/logs
- idl
- almanac,<first exp num>
- plotalmanac,'Almanac_date.fits',ps='plot_Almanac_date'
- exit
- svn add *Almanac_date*
- svn commit

Create a log file

THE FOLLOWING NOT YET UPDATED FOR MOSAIC-3

Generating a Coverage Map

The code pro/coverage_plot.pro will generate coverage maps for a given date range using the info in mosaic-tiles_obstatus.fits. To run it, login as ??@?? and start IDL:

IDL>.com coverage_plot

To produce the plot for a single night use, for example:

IDL> coverage_plot, datemin='2015-04-07', datemax='2015-04-07'

To produce a plot for a range of nights use:

IDL> coverage_plot, datemin='date-start', datemax='date-end'

To produce a plot for all nights to date use:

IDL> coverage_plot

All plots will be put in $??_OBS/obstatus/Plots. The default is to output a PDF but there are flags to output other formats.

The code pro/coverage_plot_alldates.pro will produce a set of cumulative coverage plots (one per day) over a date range. Within IDL when logged in as ??@?? you enter:

IDL> .com coverage_plot_alldates
IDL> coverage_plot_alldates, datemin='date-start', datemax='date-end'

All plots, consecutively numbered, will be put in $??_OBS/obstatus/Plots/PDFs and can be combined into a movie, e.g with the free graphicconverter http://www.lemkesoft.de/en/image-editing-slideshow-browser-batch-conversion-metadata-and-more-on-your-mac/ program on Macs.

Ben Weaver would prefer that we do not upload any plots to SVN but rather just the code. So feel free to mail plots around but there is no need to check them in.

Thank the OA and go to bed


Pages linking to PublicPages/MayallZbandLegacy/NotesforObservers:

Attachments (2)

Download all attachments as: .zip