Shane AO  

Welcome/Index | Architecture | Procedures | Problems | Features | Documents | Resources | Chronology  



Procedure: LGS Files

Task Schedule

Tasks should be accomplished in accordance with the latest version of the Laser Clearing House Reports Handbook:

LCH_Reports_Handbook_Change_8--USSF_2022-10-15.pdf
LCH normal hours are 08:00--17:00 PT Mo-Fr. (805) 605-4763 or (805) 606-7410. For emergency actions outside regular business hours the phone number is (805) 605-3514 to request on-call support. Hence, it is important to process PAM files promptly (by 16:00) so we can contact them during regular business hours

Quaterly Contact Laser Clearing House (LCH) to update projection of laser firings in the Laser Test Master (LTM) Schedule to cover the next 12 months.
Submit 2 weeks prior to the end of each quarter.
Template pending.
No later than 15th of each month (formerly 30 days prior to LGS Propagation) Contact LCH to provide an update on dates and times for laser firings and scenarios. This is achieve by submitting Master Test and Operations Schedule (MTOS) input forms. Coordinate with LCH on predictive avoidance runs to be performed, method of transmission of safe firing windows, frequency and timing of support plus points of contact (phone, fax and e-mail). Template
November 2017
September 2017
No later that 3 days prior to LGS Propagation Provide LCH with the laser operating parameters for the upcoming laser activity. The laser owner will transmit a P/A request message to LCH identifying the date and time of the test sequence, laser to be used, laser location, and the targets to be illuminated. The possible formats needed to specify target and laser locations are found in the Interface Control Document (ICD) to the LCH Deconfliction Spiral 3 system. Template; Example

Introduction

Communication of to-and-from USAF Space Command regarding LGS clearances and shutdowns is achieved by uploading Predictive Avoidance Request Message (PRM) files, and downloading Predictive Avoidance Authorization Message (PAM) files.

Both PRM and PAM files use the following specific naming conventions (as of January 2016):

PAM_LaserOwner_A_B_T+000_##Mon####_For_JDAY###_TargetType.txt

Where:

  • Fields A and B are should be unique to the program, laser, mission, etc.
  • Date ##Mon#### is date run by Space Command deconfliction software, DECON.
  • T-### is how many days from JDAY window requested by laser owner/operator.
  • Date For_JDAY### is date of activity.

Example:

PRM_Lick_589nm_13kHz_13Nov2018_For_JDAY326_RADEC.txt

PAM_Lick_589nm_15W_T-001_25JAN2016_For_JDAY026_AZEL.txt

PAM files are made available (typically 24 hours in advance of LGS operations). Notification of the availability of new PAM files may, or may not, also be sent via electronic mail to mh-laser@ucolick.org.

Extra notifications at short notice due to space events (e.g. unannounced/modified launches) may be transmitted by telephone to the Control Room, via electronic mail to mh-laser@ucolick.org, via the http://www.space-track.org service, or all of these methods. PRM, PRM and Laser Shutdown Monitor (LSM) procedures all require appropriately formatted files.

PRM Files

  • PRM files should be supplied to USAF Space Command at least 3 days in advance of the anticipated date of LGS propagation. This assumes that LCH is going to process PRM files only Mo--Fr 08:00--17:00. In practice, endeavour to provide them 4 days in advance (with rare exceptions), this should facilitate routine operations. PAM files for weekends should be processed before Friday 16:00, so if there is a problem (too many laser shutdowns, missing targets, mistakes on our side that were unrealized until too late, etc.), LCH can be contacted during their regular hours. . A few weeks before an AO run, contact the Principal Investigator/Observer(s) requesting submission of LGS target lists, e.g:
     
       Subject: UCO/Lick Observations: 20XX-XX-XX--20XX-XX-XX; Inst=Shane+ShaneAO+ShARCS; PI=; Prog=20XXN_SXXX [NNNN] 
        
       Dear Principal Investigator, 
        
       This communication is with respect to a forthcoming observing run using 
       UCO/Lick Observatory facilities on Mount Hamilton, as indicated in the 
       Telescope Schedule at the following URL: 
        
       http://www.ucolick.org/~mountain/sched/telA.html 
        
       OBSERVING RUN DETAILS: 
        
       Observer(s) .................... 
       Observing Date(s) .............. 20XX-XX-XX--20XX-XX-XX [N night(s)] 
       Instrument ..................... Shane+ShaneAO+ShARCS (LGS) 
       Principal Investigator .........  (UCXX) 
       Observing Program Identifier ... 20XXN_SXXX [NNNN] 
        
       It is necessary to provide target lists several days in advance of 
       LGS observations to enable processing of targets for submission to 
       USAF Space Command for authorization, creation of appropriate Predictive 
       Avoidance Authorization Message (shutdown) files and ingestion of 
       authorizations into the observatory's management system. 
        
       For details about target lists (which should include not only science 
       targets, but also PSF stars and 10th mag alignment stars near each 
       science target) and other issues related to AO (both NGS and LGS) 
       observing. please refer to the ShaneAO on-line manual at the following 
       URL: 
        
       http://mtham.ucolick.org/techdocs/instruments/ShaneAO/prep/ 
        
       Please provide LGS target list(s) for the forthcoming observations 
       on, or before, the following date: 
        
       Day XX Month 20XX 
        
       Please provide LGS target list(s) via electronic mail to the following 
       address: 
        
       sa@ucolick.org 
        
       Yours sincerely, 
       
  • The observer should submit a target list in the following format:
     
       TargetName  RA  Dec  Epoch lgs=1 
       
    For example,
     
       PKS0736+01 07:36:42.51 01:44:00.24 1950 lgs=1 
       M10 16 57 06.0 -04 06 00 2000 lgs=1 
       
    Important:
    • The <TargetName> should have no spaces.
    • Any target that does not include the lgs=1 key shall not be cleared.
    • The equinox must be of the form 2000 or 1950 (as opposed to 2000.0 or 1950.0).
    • The R.A. and Dec may be space or colon separated.
    Note that only one of the guide star-science target pair needs to be cleared (typically in Keck lists only the science target is cleared and the tip-tilt T star(s) are not, Lick lists will often have everything cleared).
  • It is necessary to modify the submitted target list:
    • Add header information.
    • Render the equinox into a convention compliant with USAF Space Command requirements (e.g. 2000, not 2000.0.
    • Truncate all lines following the lgs=1/lgs=1 descriptor.
    • The file should be (re-)named according to the following convention:
       
         LGStargetlist_YYYYMonDD.txt 
         
      where, YYYYMonDD is the anticipated PST date of LGS propagation, for example:
       
         LGStargetlist_2019Nov11.txt 
         
    These modifications can be achieved by invoking the following tool:

    user@shimmy.ucolick.org> /usr/local/lick/bin/targetListParse

    alt="Image">
    Figure of targetListParse.tcl interface.

    The resulting file should be located at:

    user@shimmy.ucolick.org > /u/user/observers/lgs/targetLists/

    The header and content should be of the following form:

     
       Observer's name:        Name 
       Observer's email:       E-mail 
       Observer's phone:       XXX-XXX-XXXX 
       Program name:           20XXN_SXXX [XXXX] 
       Date for which list applies:  DD Month YEAR 
       Comments: 
       Target list: 
       
    For example,
     
       Observer's name:        Mickey Mouse 
       Observer's email:       mickey@disney.com 
       Observer's phone:       408-XXX-XXXX 
       Program name:           2018B_S001 [4444] 
       Date for which list applies:  11 November 2019 
       Comments: 
       Target list: 
       PKS0736+01 07:36:42.51  01:44:00.24 1950 lgs=1 
       M10        16 57 06.0  -04 06 00    2000 lgs=1 
       

  • Render the information into files compliant with USAF Space Command PRM format:

    user@shimmy.ucolick.org > /usr/local/lick/bin/PRM /u/user/observers/lgs/targetLists/LGStargetlist_YYYYMonDD.txt

    For example:

    user@shimmy.ucolick.org > /usr/local/lick/bin/PRM /u/user/observers/lgs/targetLists/LGStargetlist_2018Nov19.txt

    This yields 3 new files at the following location:

    user@shimmy.ucolick.org > /u/user/observers/lgs/PRM/

    1. PRM_Lick_589nm_13kHz_DDMmmYYYY_For_JDayXXX_AZEL.txt where DDMmmYYYY is the date on which the files were produced, and JDayXXX is now the anticipated Julian Day of propagation.
    2. PRM_Lick_589nm_13kHz_DDMmmYYYY_For_JDayXXX_RADEC.txt where DDMmmYYYY is the date on which the files were produced, and JDayXXX is now the anticipated Julian Day of propagation.
    3. YYYYmmmDDUT.txt where YYYYmmmDD is the anticipated UT date of lasing, e.g. 2018Nov20UT.txt
  • Upload the PRM files to the following (password protected) URL: http://www.space-track.org.

    1. Log-in as mh-laser@ucolick.org
    2. Select FILES... UPLOAD...
    3. Select destination directory: zLCH/LICK/PRM/
    4. Select PRM files to upload
    5. Notify mh-laser@ucolick.org (including PRM files as attachements) that PRM files have been uploaded, e.g.
       
         Subject: PRM files for JDays 324-326 uploaded 
          
         Dear All, 
          
         PRM files for JDays 324-326 (Nov 19-21 PDT) have been uploaded to space-track.org. 
         
    If necessary due to problems, transmit the PRM files via electronic mail to USAF Space Command at: JSpOCSSAOps@vandenberg.af.mil and UDG_614AOCDet1_SSAOPS@us.af.mil. Copy mh-laser@ucolick.org. For example:
     
       Dear SBM, 
        
       Attached are PRM files for Lick Observatory Laser activities for UT 20XX November 20-22 (JDays 224-226). 
        
       Please email clearances to mh-laser@ucolick.org. 
       

Alignment Stars

Since Shane Telescope and the LGS launch telescope exhibit different flexures during telescope slews, it has been traditional to require observers to provide (9th/10th magnitude) alignment stars in the vicinity of each target.

However, some LGS programs (especially Galactic plane or ecliptic plane surveys) may not have 9th/10th magnitude alignment stars within a conveniently small Zenth Distance, which may force LGS image sharpening at high ZD to be compromised/impractical. The lack of cleared alignment stars conveniently near zenith can challenge the NGS to LGS switch-over operation.

Therefore, in August/September 2019 it was recommended to include a fixed set of 9th/10th magnitude stars with Declinations circa +37 degrees, spaced every circa 2 hrs of sidereal time along a celestial great arc, to provide a collection of stars to enable alignment checks to be performed conveniently close to meridian, especially in marginal conditions.

Alignment stars near zenith are automatically added by the program:

targetListParse.tcl

These 9th/10th magnitude alignment stars should always be listed first in PRM and PAM files and cleared for every LGS run by default.

The actual starlist file that can be loaded into the coords GUI is located at:

user@shimmy:/u/user/observers/lgs/targetLists/10thMagStarList.txt

Or, locally from the following URL:

10thMagStarList--EGates_2019-09-XX.txt

These all appear as single stars on the finder charts. However, if any are discovered to be unsuitable, notify and the unsuitable star shall be replaced by a different star. It is anticipated that use of these alignment stars will eventually supercede the need for observers to provide alignment stars for each of their science targets.

Identifier Identifier R.A. (2000) Dec. (2000) B R
1279-0000894 TYC 2781-534-1 00 02 11.37 37 57 20.06 12.31 10.09
1279-0037796 NGC 752 66 01 56 14.28 37 58 14.25 11.23 10.12
1272-0038442 TYC 2320-617-1 02 00 31.24 37 16 28.35 11.65 10.02
1272-0080731 BD+36 794 03 57 53.25 37 16 34.28 13.16 10.04
1284-0077324 TYC 2877-1375-1 04 01 46.74 38 24 37.46 12.79 10.22
1276-0147398 TYC 2912-1768-1 05 55 42.00 37 37 14.81 12.85 10.24
1271-0147913 Coordinates suspect 06 00 48.80 37 10 00.25 13.14 10.30
1272-0195390 TYC 2479-997-1 07 56 08.56 37 13 13.94 12.36 10.13
1287-0178910 TYC 2960-415-1 07 57 35.61 38 45 56.06 12.02 10.09
1287-0199907 TYC 2993-775-1 09 58 35.78 38 42 44.79 12.49 10.13
1272-0220038 TYC 2509-1160-1 10 02 22.09 37 12 20.05 12.13 10.04
1269-0218657 BD+37 2241 12 02 43.49 36 55 18.27 11.21 10.21
1283-0230546 TYC 3017-1448-1 12 01 28.19 38 20 20.22 12.07 10.16
1275-0265600 TYC 3027-1075-1 13 58 04.87 37 32 21.10 11.28 10.07
1263-0218081 TYC 2550-1212-1 13 58 17.12 36 23 32.90 11.67 10.01
1270-0281225 TYC 2579-683-1 16 01 42.54 37 03 52.23 11.58 10.03
1277-0308725 TYC 3054-1171-1 15 59 18.94 37 46 57.49 11.50 10.06
1275-0335124 TYC 3089-983-1 17 58 01.19 37 35 12.32 11.92 10.08
1266-0280617 TYC 2633-914-1 18 02 10.26 36 40 49.59 12.10 10.19
1275-0452356 BD+37 3694 19 57 38.75 37 31 33.10 12.05 10.00
1272-0462306 TYC 2682-900-1 19 59 44.18 37 13 39.30 11.87 10.14
1276-0595074 TYC 3185-1332-1 21 57 20.00 37 39 42.64 12.60 9.99
1265-0513802 TYC 2731-2381-1 22 01 08.04 36 30 27.57 11.89 9.98
1270-0614033 TYC 2780-442-1 23 57 45.21 37 03 46.04 12.79 9.98

PAM Files

  • It is important to process PAM files promptly (by 16:00) so in the event of misunderstanding or uncertainty, Laser Clearing House can be contacted during regular business hours. LCH normal hours are 08:00--17:00 PT Mo-Fr. 805-605-4763 or 805-606-7410. For emergency actions outside regular business hours the phone number is 805-605-3514 to request on-call support
  • USAF Space Command should provide PAM (Predictave Avoidance Authorization Message) files via electronic mail to mh-laser@ucolick.org. PAM files should also be placed in the appropriate (password protected) directory at the following URL:

    http://www.space-track.org

    Assign the PAM files descriptive names (e.g. 2018jday224azel.txt; 2018jday224radec.txt) and save/copy them to:

    user@shimmy.ucolick.org:/u/user/observers/lgs/lsm/

    Note: Both Julian date and UT date are listed in the PAM file in case of uncertainty regarding which date the files are for. References to JDAY should be understood to mean the day of year (DOY) that begins at 0000 UT.

    http://www.epochconverter.com/epoch/daynumbers.php

    There are 3 (updated March 2014) programs to process PAM files and create related files for the Laser Shutdown Monitor.

    1. Parse PAM files:

       
         user@shimmy.ucolick.org: /usr/local/lick/bin/lsmParse /u/user/observers/lgs/lsm/2018jdayXXXazel.txt 
         

       
         user@shimmy.ucolick.org: /usr/local/lick/bin/lsmParse /u/user/observers/lgs/lsm/2018jdayXXXradec.txt 
         
    2. Check UT date vs JDAY to ensure that every requested target was cleared (and lists targets cleared, but not requested):

       
         user@shimmy.ucolick.org: /usr/local/lick/bin/lsmCheck 2018MmmXXUT 
         
    3. Renames the .lsm file(s) according to the target names provided by the observer in their submitted LGS Target List file.

       
         user@shimmy.ucolick.org: /usr/local/lick/bin/lsm 2008Jan20UT 
         

Extra Shutdowns Due To Space Events

Occasionally, in advance of (or even during) Laser Guide Star (LGS) operations, USAF Space Command may notify of recent space events (e.g. previously unannounced launches). These events typically necessitate periods of extra, "blanket" LGS shutdowns in addition to those already permitted via Laser Shutdown (PAM) Files (which are normally received electronically 24 hours in advance of LGS operations). These additional notifications may be transmitted (less than 24 hours in advance of LGS operations) by telephone to the Control Room, via electronic mail to the mh-laser@ucolick.org distribution list, via the http://www.space-track.org service, or all of these methods. The additional notifications normally comprise of a list of UT time intervals between which all LGS operations must be suspended. Since there is the likelihood that the nighttime LGS and AO operators may not see whoever receives the phone message, the optimal method to communicate such phoned-in information is to send and e-mail to: mh-laser@ucolick.org specifying the additional shutdown intervals, e.g.
 
   UT05:18--UT05:29 
   UT06:55--UT07:03 
   
It cannot be overstated how much this type of coordination is needed to help avoid inadvertent LGS propagations and the overbearing paperwork (and space command potentially suspending LGS operations) that ensues. It is vitally important that the contents and output of LSM.tcl and lsmExtra.tcl are cross-checked to verify the contents match the blanket shutdowns provided by USAF Space Command. Otherwise, we could be in violation by propagating the laser out-of-constraints. The LGS operator and ShaneAO operators should pay attention to the extra, "blanket" shutdowns to ensure that no accidental propagation occurs, regardless of whether the software is functioning properly.

Post-2018-12-07 Procedure

It is necessary to only run LSM.tcl for each target, since a modification has been been applied to incorporate extra shutdowns into individual target lists. The format of the extra blanket shutdowns is typically:
 
   JDAY HHMM - HHMM 
   
where JDAY is the Julian day number (e.g. 227) and the first HHMM is the time at which the laser should be shuttered, and the second HHMM is the time at which laser propagation is again permitted. It is necessary to create a .lsm file that the Laser Shutdown Monitor, lsm.tcl can read. The core description of this procedure can be found at the following URL:
 
   http://mtham.ucolick.org/techdocs/techref/ShaneAO/LGStargetLists.html 
   
  1. Create a text file with a name such as the following: 2014jday227shutdowns.txt
  2. The text in the file must adopt the following example format:
     
       2014 Aug 15 (227) 0200 00  2014 Aug 15 (227) 0644 00 
       
    where the first item is the UT date (JDay) and the zulu (or UT) time of the beginning of the first open window for the laser in HHMM SS. The second item on the line, with the same format, is the time at which the laser must be shuttered for satellite avoidance.
    The first line should always start with the current UT/JDay of laser operations with propagation allowed starting at 0200. Operations cease no later than 1400, so the last line of the file should end with:

    YYYY MMM DD (JDy) 1400 00

  3. Save file at: user@shimmy:observers/lgs/extraShutdowns/
  4. As user on shimmy, execute the following command:
     
       user@shimmy.ucolick.org > /local/u/user/observers/lgs/bin/lsmParseExtras.tcl path/filename UTDate 
       
    This creates a file called extra.lsm in the following directory on shimmy:
     
       /data/lsm/YYYYMMDDUT/ 
       
  5. As user on shimmy, execute the following script to incorporate the extra shutdowns into the individual target shutdown files:
     
       user@shimmy.ucolick.org > observers/lgs/bin/lsmIncludeExtras.tcl UTDate 
       
    This script will copy the original files to the following directory:
     
       /data/lsm/YYYYMmmDDUT/named/ 
       
    and create new .lsm files with the same name incorporating all shutdowns.

Example

Today is 2014 Aug 14. USAF Space Command calls to notify of an additional shutdown tonight for a space event from 0644z to 0646z.
  • Determine the night's UT Date and JDay. The aotelcoc display will list the current UT Date and JDay. It may be necessary to add one if it is before 5 pm PDT (4 pm PST). In this example, tonight's UT date is 2014 Aug 15, JDay 227.
  • Log in to shimmy.ucolick.org as user:

    ssh user@shimmy

  • Change to the extraShutdowns directory:

    cd observers/lgs/extraShutdowns

  • Create a file for the new shutdowns using your favorite text editor, e.g.

    emacs 2014jday227shutdowns.txt

  • The first line of the file always starts with the UT Date of operations starting at 0200 and then ends with the start time of the first shutdown:
     
       2014 Aug 15 (227) 0200 00 2014 Aug 15 (227) 0644 00 
       
    Next line of the file will start the end time of the first shutdown, and ends with the start of the next shutdown. In this case, as there is only one shutdown, we use the final (end of night) shutdown, which always starts at 1400:
     
       2014 Aug 15 (227) 0646 00 2014 Aug 15 (227) 1400 00 
       
  • Save file.
  • Process the shutdown list to create the .lsm file. If in the extraShutdowns directory:
     
       user@shimmy.ucolick.org > ../bin/lsmParseExtras.tcl 2014jday227shutdowns.txt  2014Aug15UT 
       
    This creates a file called extra.lsm in the following directory on shimmy:
     
       /data/lsm/YYYYMMDDUT/ 
       
  • Process to insert the extra shutdown information into pre-existing (from normal LGS file preparations) .lsm files for individual targets. If in the extraShutdowns directory:
     
       user@shimmy.ucolick.org > ../bin/lsmIncludeExtras.tcl 2014Aug15UT 
       
    This creates new .lsm files for each target in the directory:
     
       /data/lsm/2014Aug15UT/. 
       
    and copies the original/pre-existing files to the following directory:
     
       /data/lsm/YYYYMmmDDUT/named/ 
       
The LSM.tcl and lsmExtra.tcl services have never played well together, with one sometimes allowing LGS propagation and the other disallowing LGS propagation.

Pre-2018-12-07 Procedure

As of 2018-12-06, it should no longer be necessary to run lsmExtra.tcl. However, it may be run as a backup in case something goes wrong with the lsmIncludeExtras.tcl script. The format of the extra blanket shutdowns is typically:
 
   JDAY HHMM - HHMM 
   
where JDAY is the Julian day number (e.g. 227) and the first HHMM is the time at which the laser should be shuttered, and the second HHMM is the time at which laser propagation is again permitted.
It is necessary to create a .lsm file that the Laser Shutdown Monitor, lsm.tcl can read.
  1. Create a text file with a name such as the following: 2014jday227shutdowns.txt
  2. The text in the file must adopt the following example format:
     
       2014 Aug 15 (227) 0300 00  2014 Aug 15 (227) 0644 00 
       
    where the first item is the UT date (JDay) and the zulu (or UT) time of the beginning of the first open window for the laser in HHMM SS. The second item on the line, with the same format, is the time at which the laser must be shuttered for satellite avoidance. The intervals must appear in the file in the correct time-sequential order.
    The first line should always start with the current UT/JDay of laser operations with propagation allowed starting at 0300. Operations cease no later than 1400, so the last line of the file should end with:

    YYYY MMM DD (JDy) 1400 00

  3. Save file at: user@shimmy.ucolick.org > observers/lgs/extraShutdowns/
  4. As user on shimmy, execute the following command:
     
       user@shimmy.ucolick.org > /local/u/user/observers/lgs/bin/lsmParseExtras.tcl path/filename UTDate 
       
    This creates a file called extra.lsm in the following directory on shimmy:
     
       /data/lsm/YYYYMMDDUT/ 
       
  5. Start (additional?) lsm.tcl and load in the extra.lsm file to get automatic shutdown of the laser and prevent accidental laser propagations.

Example

Today is 2014 Aug 14. USAF Space Command calls to notify of an additional shutdown tonight for a space event from 0644z to 0646z.
  • Determine the night's UT Date and JDay. The aotelcoc display will list the current UT Date and JDay. It may be necessary to add one if it is before 5 pm PDT (4 pm PST). In this example, tonight's UT date is 2014 Aug 15, JDay 227.
  • Log into user@shimmy:

    ssh user@shimmy

  • Change to the extraShutdowns directory:

    cd observers/lgs/extraShutdowns

  • Create a file for the new shutdowns using your favorite text editor, e.g.

    emacs 2014jday227shutdowns.txt

  • The first line of the file always starts with the UT Date of operations starting at 0300 and then ends with the start time of the first shutdown:
     
       2014 Aug 15 (227) 0300 00 2014 Aug 15 (227) 0644 00 
       
    Next line of the file will start the end time of the first shutdown, and ends with the start of the next shutdown. In this case, as there is only one shutdown, we use the final (end of night) shutdown, which always starts at 1400:
     
       2014 Aug 15 (227) 0646 00 2014 Aug 15 (227) 1400 00 
       
  • Save file.
  • Process the shutdown list to create the .lsm file (if you are still in the extraShutdowns directory):
     
       ../bin/lsmParseExtras.tcl 2014jday227shutdowns.txt  2014Aug15UT 
       
    This creates a file called extra.lsm in the directory:
     
       /data/lsm/2014Aug15/. 
       
  • Start lsm.tcl and load in the extra.lsm file to get automatic shutdown of the laser and prevent accidental laser propagations.

Reprocessing Extra Shutdowns Due To Space Events

On rare occasions, in advance of (or even during) Laser Guide Star (LGS) operations, USAF Space Command may notify of yet more recent space events (e.g. previously unannounced launches, orbit recalculations). These events typically necessitate periods of extra, "blanket" LGS shutdowns in addition to those extra shutdowns already received and those permitted via Laser Shutdown (PAM) Files (which are normally received electronically 24 hours in advance of LGS operations). In such cases, the pre-existing extra shutdowns file must be deleted and regenerated, incorporating the additional shutdown intervals:

Post-2018-12-07 Procedure

If USAF Space Command contacts you with additional or modified shutdowns, ensure the following procedure is undertaken during a safe period when there is no chance of needing to shutter the laser due to one of these blanket (or any other) shutdown(s). The core description of this procedure can be found at the following URL:
 
   http://mtham.ucolick.org/techdocs/techref/ShaneAO/LGStargetLists.html 
   
  • As user on shimmy, re-visit the file containing the extra shutdowns, e.g.
     
       ~/observers/lgs/extraShutdowns/2014jday227shutdowns.txt 
       
    Edit the shutdowns file appropriately to reflect the latest information from USAF Space Command in the correct time-sequential order.
  • Delete the pre-existing file extra.lsm in the appropriately-dated subdirectory:
     
       ~/data/lsm/YYYYMmmDDUT/extra.lsm 
       
  • If the script lsmIncludeExtras.tcl had been executed for this date, do the following:
    • Delete all the individual target .lsm files in the appropriately-dated subdirectory:
       
         ~/data/lsm/YYYYMmmDDUT 
         
    • Move the (original) .lsm files from:
       
         /data/lsm/YYYYMmmDDUT/named/ 
         
      to:
       
         /data/lsm/YYYYMmmDDUT/ 
         
  • As user on shimmy, execute the following command:
     
       user@shimmy.ucolick.org > /local/u/user/observers/lgs/bin/lsmParseExtras.tcl path/filename UTDate 
       
    This creates a file called extra.lsm in the following directory on shimmy:
     
       /data/lsm/YYYYMMDDUT/ 
       
  • Process to insert the extra shutdown information into pre-existing (from normal LGS file preparations) .lsm files for individual targets. If in the extraShutdowns directory:
     
       user@shimmy.ucolick.org > ../bin/lsmIncludeExtras.tcl YYYYMmmDDUT 
       
    For example,
     
       user@shimmy.ucolick.org > ../bin/lsmIncludeExtras.tcl 2014Aug15UT 
       
    This creates new .lsm files for each target in a date-stamped directory:
     
       /data/lsm/YYYYMmmDDUT/ 
       
    For example,
     
       /data/lsm/2014Aug15UT/ 
       
    and copies the original/pre-existing files to the following directory:
     
       /data/lsm/YYYYMmmDDUT/named/ 
       
  • Only perform this step if lsmIncludeExtras.tcl was NOT executed:
    Load the new extra.lsm into the lsmExtra.tcl program.

Pre-2018-12-07 Procedure

  1. Delete the appropriate file:

    /data/lsm/20YYMonXXUT/extra.lsm

  2. Edit the appropriate file to include the latest shutdown intervals in the correct time sequential order:

    user@shimmy.ucolick.org > /local/u/user/observers/lgs/extraShutdowns/20YYjdayXXXshutdowns.txt

  3. Run the command:

    user@shimmy.ucolick.org > /local/u/user/observers/lgs/bin/lsmParseExtras.tcl 20YYjdayXXXshutdowns.txt 20YYMonXXUT

  4. (Re-)start the lsmExtra.tcl GUI to ingest the correct, refreshed shutdown information.

Prepare 30 Day Monthly Lookout File

On or before the 15th day of each month, notify USAF Space Command of periods of intended LGS operation intended for the subsequent month:
  1. Download template or
  2. Copy/re-name file to appropriate month (e.g. LCH_MTOS_Input_Form--Lick_Observatory--Mon20XX.xlsx).
  3. Open and edit the copied/re-named file:
    • Edit MONTH and YEAR appropriately: MONTH 20XX
    • Edit/rename sheet appropriately: Mon XX
    • Enter LGS program name: Lick Observatory/Lick_589nm_13kHz
    • Highlight (e.g. in yellow) cells corresponding to dates of intended LGS operation. Note: US military use Zulu time (UTC). However, Lick Observatory telescope schedules use Pacific time (PST/PDT). Therefore, highlight all intended LGS operation dates, commencing with first date of intended LGS operation and then append one additional date at the end of each intended LGS run to accommodate any ambiguity between Pacific and Zulu times (e.g. for 2 LGS nights in March: March 12 and 13, highlight the 3 nights: March 12, 13 and 14 to accommodate any work load preceding the intended LGS run, and to ensure declaration encompassing the entire intended LGS run).
    • Annotate the highlighted region with Active 0200z to 1400z each day.
  4. Save updated (XLSX format) file.
  5. Preview and format content of relevant month/sheet.
  6. Save/export as a single page, US letter format, landscape orientation PDF format file (e.g. example (XLSX format) file. example (XLSX format) file. example (XLSX format) file. Note: For some editing software (e.g. LibreOffice) it may be necessary to delete all except the current month/sheet before the export as PDF function produces the desired result.
  7. Prepare an electronic mail message:
    • Subject of the following form:

      MTOS for Lick Observatory**

    • Attach the resulting PDF format file.
    • Message content of the following form:

       
         Dear Laser Clearing House, 
          
         Attached is the current version of the MTOS for Lick Observatory. 
         If you have any questions or concerns, please contact us. 
          
         Yours sincerely, 
          
         Staff Astronomer 
          
         Elinor Gates, Ph.D.   Office: 408-238-0652 / 408-238-9610 
         egates@ucolick.org    Cell:   408-202-1691 
          
         Paul Lynam, Ph.D      Office: 408-238-0652 / 408-238-9617 
         plynam@ucolick.org    Cell:   408-398-7526 
          
         Lick Observatory, Mount Hamilton, CA 95140 
         
    • Circulate including the following address:

      mh-laser@ucolick.org

    • Send to the following address:

      LaserClearinghouse@us.af.mil

Change Log:

2022-10-15: Updated: New procedures for LCH.
2022-05-06: Updated typographical error corrected.
2019-11-11: Updated (equinox format i.e. 2000 vs 2000.0).
2019-11-05: Updated.
2018-12-07: Updated: New procedures for Extra Shutdowns.
2018-11-12: Updated.
2018-10-29: Updated: Added Reprocessing Extra Shutdowns.
2017-10-06: Updated: Updated reporting form format.
2017-06-09: Updated: shimmy replaced shred.
2017-04-12: Updated.
2015-12-01: First version.

This document last updated (UTC): Tuesday 04 March 2025