wiki:HetProcedures/RA/overview

Overview of the basic afternoon & night time procedures

Who to call

Person Home Cell
Steven J x679 419 721-8193
Sergey x656 432-755-2081
Steve O x660 432 386-0090
Justen x677 See List
Jim 432 426-2313 432 249-0043
Herman x674 432 386-5815

URLs for critical tools/pages in operations


Afternoon checkout

suggested order of OPS procedure, seasonally

  • before TO restarts servers and tests cameras, RA can:
    • accept new targets/allocations, run daily calcs/highpri
    • check zeus/vdas/lrs2 system health (disks, sounds, processes)
    • check LRS2/VIRUS pressures/temperatures, but do not adjust any until asking Jim or Herman
  • after TO restarts servers and tests cameras, RA can: (many of these can be done simultaneously)
    • turn off IP/VG on LRS2/VIRUS
    • run ACQ camera mirror insertion test (best to do first while TO does their walkaround)
    • take LRS2 * VIRUS test cals
      • evaluate for flux and TCS comms
      • evaluate VIRUS bias for any vreload needs
    • restart HPF tims client, take HPF LFC cal, evaluate
    • test probe moves
  • after all checks are successful
    • turn off dome lights
    • start HPF Part A cals running (include A+C if possible to finish before sunset on weekends - always run A+C on weekdays)
    • schedule LRS2/VIRUS cals to run (as "at" job on astronomer@vdas)
    • send the OPS email report

NOTE when in remote operations mode, all tasks involving the on-site day ops staff member are prioritized, to minimize their time spent on-site:

  • TO starts with restarting servers and doing structure/tracker move tests
  • TO alerts the RA when it is safe to begin instrument/PFIP tests
  • TO alerts the RA when it is safe to do the ACQ camera mirror insertion test (commands tracker to center)

NOTE during winter OPS in on-site operations mode, timing is tighter:

  • RA need to run the ACQ camera mirror insertion test at the beginning while the TO does their walk around in the dome.

Detailed steps before TO has finished restarting servers

  • Setup scripts can be helpful to get windows open and configured. I recommend considering these as examples: 
    /data1/archive/users/stevenj/setup/setup_zeus.sh
/data1/archive/users/stevenj/setup/move_zeus.sh
  • Recommend starting autodisplay at this time by running autodisplay in a terminal
  • The order of the following steps is fairly flexible, depending on individual preferences and any problems that arise. These steps have been updated to include the new RA OPS webpage tools as well as the manual commands
    • check LRS2/VIRUS temperatures/pressures but do not adjust
      • Display temperatures/pressures for LRS2/VIRUS with buttons on RA OPS page
        • manual mode: run getSpectTemperatures -p TROUBLE command with --virus or --lrs2. You may instead use the RA Launcher, click "Operations" and "Display LRS2 Temperatures" and "Display Virus Temperatures". Save a copy of this initial temperature readout for your OPS report email
      • LRS2:
        • Cryo Press should be a few x 10E-7 mB
        • Cryo Temps should be around -160 to -190 C
        • Left & Right CCD amplifier Temps (columns 10 & 11, L & R on LRS2-B & LRS2-R) should all be -110 C
        • Left & Right CCD heater power should be between 10-90% -- if outside, see below for instructions
      • VIRUS:
        • As of June 2020, cryo pressure is not populated (until new hardware arrives)
        • Cryo Temps should be around -160 to -190 C
        • Left & Right CCD amplifier Temps (columns 10 & 11) can be set to -100, -105, or -110 C, and should match their set point
        • Left & Right CCD heater power should be between 10-90% -- if outside, see below
      • NOTE do NOT adjust temperatures without talking to Jim or Herman
      • Determining temperature set points: (-p TROUBLE flag helps a lot)
        • If power < 10%, ask HK/JF if they want to raise set point temperature by 5 C, but no warmer than -100 C.
        • If power > 90%, ask HK/JF if they want to lower set point temperature by 5 C, but no colder than -110 C.
        • If you cannot reach HK or JF, do not adjust the temperatures but note it in your OPS report.
      • Report temperature adjustments in your OPS email report, by clicking the "Compare set temps" button
  • accept new targets into the queue, run daily calcs, run highpri
    • Log in to the HETqueue-RA interface on nossy in a Firefox browser at nossy/noss/RA/interface
    • Check the QueueTool tab for new allocations, new targets, or target updates. Verify and accept those.
      • See this page for detailed instructions, especially when accepting new allocations
    • After all targets and allocations are accepted, click the appropriate checkboxes in the RA OPS webpage, then click "Run daily queue updates" and after that finishes, "Run highpri" buttons.
      • manual option: in htopx nossy/noss/htopx3/ click "Tools", "Daily Calcs", and "OK" to run daily synoptic calculations for any new targets
    • If you accept targets later during OPS, it is necessary to re-run these daily calcs and then also re-run highpri
    • highpri will make a list of that night's expected OCD schedule and any high-priority or highly-constrained targets in the queue, and this output should be included in your OPS report.
  • check zeus computer health (disks, sounds) , in MISC section on RA OPS page
    • Check the filesystem state on zeus - make sure the / partition is not alarmingly full.
    • Check that sounds are working normally by copying the play command to a terminal on zeus. If sounds are not working, follow troubleshooting procedures here
    • Check the HET Operations calendar for any important notices about work done today or upcoming changes.
    • Check that DIMM data are mounted (if not, contact Sergey)
  • check lrs2 health (disks, processes), in LRS2 section on RA OPS page
    • Check uptime with the "uptime" button, or run manually: getUptime --lrs2
    • Check that the RAMdisk has no data on it with the "RAMDISK" button, or use the following: ssh -q lrs2 "df -h /mnt/camra_ramdisk"
      • If residual data remain (and an exposure has not been taken in the past ~minute), there may be a problem with pivot (see steps below to fix)
    • Check that the LRS2 proxy/servers/transfers are running correctly. Click the "Operational processes" button or run: ssh -q lrs2 "ps ax|egrep 'lrs2_server|proxy|dt_local_nfs'|egrep -v 'tail|grep'"
      • There should be 3 tasks: tcs_proxy, lrs2_server, and dt_local_nfs
        • if proxy (tcs_proxy) is missing then run ssh -q astronomer@lrs2 sudo /sbin/service lrs2Pivot restart
        • if LRS2 server (lrs2_server) is missing then run ssh -q astronomer@lrs2 sudo /sbin/service lrs2Server restart
        • if data transfer (dt_local_nfs) is missing then run ssh -q astronomer@lrs2 sudo /sbin/service lrs2DataTransfer restart
  • check vdas/VIRUS health (disks processes), in VIRUS section on RA OPS page
    • Check uptime with the "uptime" button, or run manually: getUptime --vdas
    • Check that the RAMdisk has no data on it with "RAMDISK" button or by running: ssh -q vdas "df -h /mnt/camra_ramdisk"
      • If residual data remain (and an exposure has not been taken in the past ~minute), there may be a problem with pivot (see steps below to fix)
    • Check that the VIRUS proxy/servers/transfers are running correctly with "Operational processes" button or by running: ssh -q vdas "ps ax|egrep 'virus_server|proxy|dt_'|egrep -v 'tail|grep'"
      • There should be 4 tasks: tcs_proxy, virus_server, dt_local_nfs, dt_tacc
      • if proxy (tcs_proxy) is missing then run ssh -q vdas sudo /sbin/service virusPivot restart
      • if VIRUS server (virus_server) is missing then run ssh -q vdas sudo /sbin/service virusServer restart
      • if data transfer (dt_local_nfs) is missing then run ssh -q vdas sudo /sbin/service virusDataTransfer.local restart
      • if data transfer (dt_tacc) is missing then run ssh -q vdas sudo /sbin/service virusDataTransfer.tacc restart
    • Contact Sergey if pivot or data transfer problems cannot be solved with these steps.
      • Some help may be found here, although some of that information is out-dated
    • You may also try to log in to vdas as user: hetdex, and run dt_fix virus to remove left-over data on the RAM disk


Detailed steps after the TO has restarted servers, tested cameras, and says that it is OK to use PFIP

Note: Use only observation numbers from 9900-9999 for afternoon OPS work

  • Once it is safe to use hardware, click the "HET has been released for OPS" button in the RA OPS webpage
  • Turn off the Ion Pumps (IP) and Vacuum Gauges (VG) with "Turn off IP/VG" buttons, or manually turn off the LRS2 IP/VG and the -V means to turn off the VIRUS V309 IP as well: ipvg off
    • This can be manually accomplished by carefully clicking the appropriate icons in the APC Status/Control tab of the TCS GUI.
    • Include the time you turned off the IP/VG in your OPS email report (is now automated!)
  • run ACQ camera mirror insertion test (takes ~10 minutes, not during test cals)
    • Verify with the TO that the tracker is at center and it is OK to run the ACQ camera mirror insertion test
      • The structure should not be moved during this test
    • Verify that the current time is not between 23:50 and 23:59 UT (test will fail if run across two UT dates)
    • Click the "ACQ stability test" button, or manually run: stability_test.py acq
    • This will insert and retract the mirror 10 times, storing an image each time, and analyze those at the end
    • More information about the stability test is on the wiki
    • Include the result in your OPS email report, like: 
      averages on 9 comparisons:
-------------------------------
 dx =  0.0021 +/- 0.0024 [pixels]
 dy = -0.0000 +/- 0.0001 [pixels]
-------------------------------
    • If the standard deviations are >0.1 pixels, this may be cause for concern; try re-running the test.
  • take VIRUS + LRS2 test cals using command string from "Calibration commands" in RA OPS webpage. Currently we use opscals.sh, see opscals.sh -h for help.
  • check VIRUS test cals:
    • Check for TCS communications with "TCS Comm" button. If values are not populated then see this page for troubleshooting help, but it will probably require restarting the VIRUS server.
    • Display data with autodisplay (or manually in the data folders). Evaluate the line and continuum lamps for appropriate flux; report any issues with any lamps
    • Enter the current UT date and bias Obs num into the boxes at the top of the VIRUS section of the RA OPS page, then click on "VHC report" to see the viruserr report. If acceptable, click "Generate bias image" button (or run vjpg manually), and then after that, at the top, click the "Check VIRUS bias" button to see it.
    • Evaluate the bias frame (usually Observation #9901) carefully, also decide whether any units need to be vreloaded. Bias should show:
      • roughly ~1000 or ~2000 count bias levels
      • no strange patterns, shapes, features, missing data, etc
      • If new units appear black/blank/bad, try running vreload by following these suggestions, then take another LDLS and bias exposure afterward
    • Click the checkbox after evaluating the VIRUS test cals
  • check LRS2 test cals
    • Check for TCS communications with "TCS Comm" button. If values are not populated then see this page for troubleshooting help, but it will probably require restarting the LRS2 server.
    • Display data with autodisplay (or manually in the data folders). Evaluate the line and continuum lamps for appropriate flux; report any issues with any lamps
    • Evaluate the bias frame (usually Observation #9900) carefully. Bias should show:
      • roughly ~1000 or ~2000 count bias levels
      • no strange patterns, shapes, features, missing data, etc
    • Click the checkbox after evaluating the LRS2 test cals
  • Daily HPF restarts (can be done any time) and test LFC (internal, can be done with other cals running):
    • Click the "HPF obs number" to get the current observation number, or manually: in the scripts window (help page on HPF Screens), run the following and record the output in your OPS report: tims detect pyhxrg:GetObsnum
    • Restart the HPF TCS Client by clicking the "TCS client restart" button, and verify that you get two messages and the second confirms that "timshet started". Manual option:
      • Monitor the HPF HET client window (currently screen 7)
      • In the scripts window, run: tims het shutdown
        • Verify that the client shuts down successfully
      • In the HPF HET client window, restart the client by running: timshet
        • Verify that the client starts successfully
    • When no other exposures of calibration lamps will be taken, verify that the HPF exposures have header keywords from TCS:
      • Take an LFC HR cal exposure by clicking "Run HPF cal" or with cal hpf -l 1 or manually run it in the HPF Scripts screen with: ./hpf_takeLFCHRCalExposure.sh 1
      • Allow autodisplay to show you the data, or run showhpfspec or ds9h on hpf@hpf window to display the data after at least 3 frames are finished
      • Click "HPF TCS Comm" to verify communications (can look manually at the header)
      • If TCS data is not present in the header, follow the HPF-specific instructions on this page which have worked well in the past
      • Verify that the fiber scrambler sounds normal during this exposure, click checkbox
  • test probe motions: (can be done any time) in PFIP section of RA OPS page
    • These tests can be done while other exposures/tests are running
    • Verify that all probes are green/normal in the Probe Assembly GUI in the TCS GUI before proceeding, report and discrepancies
    • Click the "Before" button, or manually run the following to get the current positions of each probe, and save that in your OPS email report shoprobes
    • Click the "home5" button or manually run the following command to send the probes to roughly the centers of their ranges, save the output in your OPS email report: home5
      • Watch the Probe Assembly GUI to verify that the colors/motion are as expected (yellow while moving, green when on target)


Detailed steps after all OPS checks have succeeded

  • verify dome lights are off
    • in normal mode the TO usually turns them off after their trajectory tests are complete
    • in remote operations mode, the Day Ops staff person will turn them off before they leave the site
  • start HPF Part A cals running (include A+C if possible to finish before sunset on weekends - always run A+C on weekdays)
    • Part A cals take 43 minutes to run, require a dark dome, and are absolutely essential to run every night, even if they must go 5-6 minutes past sunset
    • Part C cals take 45 minutes to run, can be run during twilight or while other cals are running, and can be skipped occasionally if no time
    • If you have at least 43 minutes before sunset, run Part A cals in the HPF scripts window with: 
      /home/hpf/Scripts/InstConfig/CalScripts/hpf_evening_cals_PartA.sh
    • If you have at least 88 minutes before sunset (or it is a weekday), run Part A+C cals in the HPF scripts window with: 
      /home/hpf/Scripts/InstConfig/CalScripts/hpf_evening_cals_PartAC.sh
      • If running Part A+C cals will extend past sunset on a weekend, it is not worth doing A+C. Instead, run Part A only and let the night RA to decide when/if to run Part C so they can observe a twilight.
    • Include the start and end times of Part A (and Part C, if applicable) in your OPS email report. This is accomplished by clicking in the time boxes on the RA OPS webpage and it should do the calculation for you.
    • Verify that the initial FCU moves have completed successfully and you hear the fiber agitator running during the first cal exposure
  • schedule LRS2/VIRUS cals to run as astronomer@vdas
    • If there will be time after HPF Part A finishes and before sunset, it is very useful to schedule nightly calibrations to run with "at"
    • New way of scheduling VL cals
      • Click in the time boxes for all required VL cals which you can fit before sunset
      • Press the "Schedule VL cals" button. This will create "at" job and display the result
      • The "at" job will send an email to astronomer@het.as.utexas.edu with the output from its run.
      • The RA OPS webpage has a useful tool for calculating the start/end times of these cals. If you have not scheduled all cals for that night, click on the names of the missing cals and they will appear in the "Still needed cals" area.
      • After you schedule the "at" job, click "Check at state" button in RA OPS page to update that in the report
  • Old way to set "at" job manually. In this case you do should NOT press the "Schedule VL cals" button. Provide all cals times in comment section.
    • Use "at" to start V/L cals after HPF Part A finishes, like this in a terminal as astronomer@vdas: 
      $ at 23:10
at> cal lrs2 -pb -b 11 -B
at> cal lrs2 -pd -de 360 -d 3 -B
at> [ctrl-D]
  • Fill in the NOTES section at the top of the page with any issues, or else say that everything was normal/ok.
  • send the OPS email report
    • click "Generate Report" button and address any errors/issues it complains about
    • proof-read over the webpage/report to make sure it contains all of the necessary information
    • Clicking "send email" will send the OPS email to het-ra-reports@het.as.utexas.edu
    • close out of all windows and log out of Zeus when finished.
  • monitor the emails generated by your scheduled "at" job(s); monitor for any problems as well
    • If problems arise after the OPS checks are finished and before the night RA comes on duty at sunset, it is the responsibility of the OPS RA to troubleshoot them or call for help if needed. The OPS TO should call the OPS RA if they notice anything strange with the telescope/instrument state after the daily checks are finished, even if the OPS RA has already left.



Start of the Night

  • Plan to arrive in control room (or connect remotely) at least 10 minutes before sunset to get set up for the night.
  • Run your setup script or manually configure the windows/screens in your preferred format
    • Examples of setup/window-moving scripts: /data1/archive/users/stevenj/setup/setup_zeus.sh and /data1/archive/users/stevenj/setup/move_zeus.sh
    • It is recommended to start running autodisplay at this time
    • It is also recommended to run mboard on to turn on the count-down clock in the control room
  • Start an RA log named YYYYMMDD_RAlog.txt (can do it in /data1/mcs/guider/YYYYMMDD/ or else copy it there at the end of the night)
    • Template file for night RA log is available here: (<- yes that works, click it)
  • Check for any new target submissions in the QueueTool interface and accept them into the queue. Run Daily Calcs afterward using the link in htopx (Tools --> Daily Calcs). Note that htopx will provide audio alerts when new target submissions are received, so we don't have to manually check this anymore.
  • Run highpri to get the most updated list of high-priority targets for tonight; include them in your observing plan for the night.
  • Check your emails for any relevant updates; check OPS email to see if additional calibration data are required for the night or for other information
    • If necessary, check the temperatures of the instruments (via RA Launcher-->Operations), be sure that IP/VG are turned off
    • If necessary, check latest commissioning plan located here or Science plan located here
  • Ask the TO to start opening the dome about 6 minutes before sunset (takes 2-3min to open), if weather is safe. (Consider opening earlier if calibrations are finished and temperatures would benefit from an open dome - ask the TO for advice.)
  • Verify the telescope is correctly configured for twilights:
    • structure and dome pointed north (Az=0)
    • dome louvers closed
    • dome shutter open
    • tracker at center
  • Take HPF twilight if possible (try hard on weekends, but not required every night), only if the sky is fully clear (bright clouds can saturate HPF; dark clouds give low SNR):
    • execute htwi 3min before sunset (Updated 2022 - was 1-2min before sunset, but 3min before gives better results now)
    • after 3rd frame, run ds9h as hpf@hpf to monitor for saturation. Saturation occurs at 65k, and should be avoided.
    • OR use the old manual procedure...
      • on the hpf machine execute tims detect pyhxrg:SetObstype:Cal
      • open the PFIP shutter, make sure ACAM and FCU head are retracted
      • 2 minutes after sunset, run hpframp twilight 28 1
      • close the PFIP shutter
      • tims detect pyhxrg:SetObstype:Sci
      • this should produce nice twilight flats for HPF, but may eliminate your chance of getting LRS2 sky flats that night
  • Take LRS2/VIRUS twilights (ok even with clouds)
    • Starting in early 2023, consider using the new automatic twilight script: autotwi
    • Move probes to 'home5' position to prepare for twilights
    • Set GC2 to filter 'B', set exposure time to 0.1s, cycle time to 1s, check "store images"
      • Optional: set GC1 to filter 'r', set exposure time to 0.01, cycle time to 1s, check "store images"
    • In TCS GUI, Guider 2 tab
      • Click "Start Camera Pipeline" to start pipeline (N.B., starting the metrology Loop can cause unexpected crashes)
      • Select "Raw" under the "View Extension" drop-down box
    • Monitor counts under cursor near (but not at) center of the image
    • When GC2 counts are at 36k, run lsky to start LRS2 twilights (use 35k during cloudy conditions)
      • This will take 6 exposures with LRS2 (7/10/13/16/22/30s), which should take ~5 minutes
      • Evaluate the images to be sure they are not saturated
    • When GC2 counts are at 6.6k, run vsky to start VIRUS twilights
      • This will take 5 exposures with VIRUS (7s/10s/14s/18s/26s), which should take ~6 minutes
      • Evaluate the images to be sure they are not saturated
      • Warn the TO when you start these so they know when to expect you to ask them to start stacking
    • Verify that the twilight script has turned off the GC2 pipeline.

  • After twilight spectra are complete:
    • Ask the TO to start stacking the primary mirror, and to let you know when they start the final measurement (approx 7-8 minute warning to be ready to go on sky)
    • Run additional nightly calibrations if required; a stack typically takes 25-35 minutes. Plan your first few targets of the night.
  • When the TO lets you know that the stack is complete and they are ready for a target, send a target in the usual way. Further instructions are here.
    • When you send a target, verbally notify the TO of the instrument in use and the setup method requested
  • Keep at least 1 or 2 targets planned in advance, using these rough overhead/time estimates: (see here for more details about choosing targets based on their optimal times)
    • HPF:
      • HPFACAM setup = 7.5min
      • DirectACAM setup = 6.5min
      • overheads: 40s per exposure, 60s per observation
      • for example, a 3x300s observation would take 60s + 3x300s + 3x40s or 1080s = 18 minutes
    • LRS2
      • directACAM setup = 6.5min
      • ACAMblind setup = 5.5min
      • overheads: ~60s per exposure
      • for example, a 1800s exposure would take 60s + 1800s or 1860s = 31 minutes
    • VIRUS
      • directGuider setup = 4min
      • ACAMblind setup = 5min
      • overheads: ~60s per exposure
      • for example, a 3x360s exposure would take 3x60s + 3x360s or 1260s = 21 minutes
  • If you are idle for poor weather:
    • run HPF LFC cals every few hours to improve drift calculation with cal hpf -l 3 or in the HPF scripts window
    • check the Long Cals page to see if any weekly/monthly cals are required and run those



End of the Night

  • After the last science/engineering target is finished, perform the usual end-of-night (EON) tasks by running eon_tasks. It will:
    • acquire ACQ camera bias images (takes ~1 minutes)
      • It should run automatically, but if needed you can see more details on Steve's project to use daily ACQ camera biases here)
    • take end-of-night VIRUS bias, save an image with the following command and attach it to your EON email bias_20200827am.jpg (can run manually with vjpg)
      • You will need to run viruserr to get the Virus Health Check output for the bias, and include that in your EON email as well
      • possibly using the obs argument like: viruserr -obs 17 for the correct observation
    • copies DIMM (primary and secondary) data to /hetdata/data/ImageQuality/
    • takes Cd-A and Hg lamp cals for Gary (labels them with ENGYY-T-002 program ID), which we also run manually with gcals
    • turns on LRS2 ion pump and VG, and V309 IP, could run manually with ipvg on
    • displays LRS2 temperatures and pressures (please include LRS2 temps/pressures in your night report)
      • if VIRUS has been in use recently, temperatures may be unstable and should not be adjusted or reported.
    • moves probes to "home4" position
  • If no morning twilights or additional cals are required, start HPF morning calibrations like normal, and include start/end times in your report
    • Note that the times when the cals complete can be found in /home/mcs/astronomer/Desktop/morning.txt and can be copied into your end of night email/report (e.g., for normal morning cals): 
      12:10 UT: HPF morning cals started
13:22 UT:    HPF finished with dark dome
14:07 UT:    HPF finished with PFIP shutter
  • If morning twilight sky spectra are required on LRS2 or VIRUS:
    • Ask the TO to set up the telescope for twilights - north with louvers closed tracker at center
    • Be sure the probes are at their home5 position
    • If IP/VG are powered on, be sure to turn them off before attempting these, using ipvg off
    • Set GC2 to 'B' filter, 0.1s exposure, view 'raw' extension in TCS
    • At ~3k counts, run vsky-morning to take 3 VIRUS twilight flats
    • At ~12k counts, run lsky-morning to take 3 LRS2 twilight flats
      • suggestion: run lsky-morning -stop to take 3 LRS2 twilight flats then turn off the guider pipelines, so you don't have to remember to turn them off yourself
    • After finishing these, turn the IP/VG back on with ipvg on
    • Put the probes back to their home4 position, as is standard for end of night
  • If additional morning cals are required on VIRUS/LRS2, schedule them to run during the "PFIP shutter closed" portion of the HPF morning calibrations:
    • Run HPF morning cals with leave_signs_on argument to leave the cal signs on outside the dome: 
      [hpf@hpfserver CalScripts] ./hpf_morning_cals.sh leave_signs_on
    • As astronomer@vdas schedule necessary cals with "at", including IP/VG commands, and using the -eon flag to turn off the signs and turn on the IPVG at the end.
      • For example, if you start the HPF morning cals at 11:00 (with leave_signs_on, the dark-dome portion finishes at 12:00 so you could run the following to take the LRS2/VIRUS parallel biases appropriately: 
        [astronomer@vdas setup]$ at 12:01
at> ipvg off
at> cal lrs2 -pb -b 11 -B -eon
at> <EOT>
    • Copy and paste the "at" information about these cals in your log text file and in the EON email
  • Send end of night RA email to het-ra-reports@…
    • Subject line should be RA log for night of YYYYMMDD UT (note that that will be the same as the current civil date when you send it in the morning)
    • Attach the JPEG screenshot of the EON VIRUS bias
    • Attach your observing log text file
  • If you did not already create it there, move the RA night report text file into the Guider nightly working directory /data1/mcs/guider/YYYYMMDD/
  • Log out of Zeus.


Last modified 8 months ago Last modified on Aug 28, 2023 4:17:49 PM

Attachments (3)

Download all attachments as: .zip