User Tools

Site Tools


chara:remote_observing

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
chara:remote_observing [2022/02/09 14:40]
charaobs
chara:remote_observing [2023/02/13 16:59] (current)
charaobs
Line 3: Line 3:
 Note: As of June 2018, we are using a new remote observing procedure. Details can be found here: [[http://www.chara.gsu.edu/observers/remote-observing|http://www.chara.gsu.edu/observers/remote-observing]] and a full description of the remote observing system can be found here: [[http://chara.gsu.edu/files/chara_technical_reports/tr102.pdf|http://chara.gsu.edu/files/chara_technical_reports/tr102.pdf]] Note: As of June 2018, we are using a new remote observing procedure. Details can be found here: [[http://www.chara.gsu.edu/observers/remote-observing|http://www.chara.gsu.edu/observers/remote-observing]] and a full description of the remote observing system can be found here: [[http://chara.gsu.edu/files/chara_technical_reports/tr102.pdf|http://chara.gsu.edu/files/chara_technical_reports/tr102.pdf]]
  
-Last updated 1-10-2021 by Norm+Last updated 2-13-2023 by Norm
  
 __**Remote Observing**__ \\ __**Remote Observing**__ \\
Line 36: Line 36:
   * Filter or prism desired if using MIRCX/MYSTIC. H, K or J for CLASSIC/CLIMB   * Filter or prism desired if using MIRCX/MYSTIC. H, K or J for CLASSIC/CLIMB
   * Any special requirements you might have (LDCs in or out, CLIMB for fringe finding/tracking, scope dichroic, lab tiptilt, etc)   * Any special requirements you might have (LDCs in or out, CLIMB for fringe finding/tracking, scope dichroic, lab tiptilt, etc)
-  * Discord or phone contact if remote (in case we do not already have it). Discord is the preferred means of communicating so please create an account if you do not have one or ask for an invitation to the CHARA Discord group.+  * Discord or phone contact if remote (in case we do not already have it). Discord is the preferred means of communicating so please create an account if you do not have one or ask for an invitation to the CHARA Discord group. We use night-time operations as the channel for remote observers.
  
- \\ Understand that this email is used to align the lab, set the configuration and get you on sky as efficiently as possible. \\ It goes to all staff who do alignments and who operate. You do not need to send it to individual staff members. \\ Failure to provide all of this info can cause a delay in getting on sky so please be thorough when submitting request. Also, be clear about dates when submitting requests for subsequent observing nights. Your nights or days may not match ours and giving local dates will help avoid confusion. \\ CHARA now uses Discord for communication between remote PI's and operators. Be sure to ask for an invitaion or create an account before your night. On the first night of your run, please contact the appropriate Array Operator via Discord at least half an hour before sunset if you are observing remotely. The observer work schedule is posted in the [[http://www.chara.gsu.edu/observers/observing-schedule|Online Observing Schedule]]. The operator can provide an update on the status of the array, current weather conditions, and whether there is a need to go on stand-by status. \\+ \\ Understand that this email is used to align the lab, set the configuration and get you on sky as efficiently as possible. \\ It goes to all staff who do alignments and who operate. You do not need to send it to individual staff members. \\ Failure to provide all of this info can cause a delay in getting on sky so please be thorough when submitting request. Also, be clear about dates when submitting requests for subsequent observing nights. Your nights or days may not match ours and giving local dates will help avoid confusion. Please advise the staff if the configuration is not decided upon before the evening so they don't align to an incorrect setup. 
 + 
 + \\ CHARA now uses Discord for communication between remote PI's and operators. Be sure to ask for an invitaion or create an account before your night. On the first night of your run, please contact the Array Operator via Discord in the night-time operations channel at least half an hour before sunset if you are observing remotely. Those needing to align MIRCX/MYSTIC or use STS can message in earlier to see when the lab is available for STS use. The observer work schedule is posted in the [[http://www.chara.gsu.edu/observers/observing-schedule|Online Observing Schedule]]. The operator can provide an update on the status of the array, current weather conditions, and whether there is a need to go on stand-by status. \\
  \\  \\
  \\  \\
-**__Pre-Run Assessments__  ** \\  \\ Due to the nature of remote observing, it is beneficial to assess a few things before the evening’s run. First would be the weather. Everything from the Weather Service page, The Clear Sky Clock and the Jet Stream can be checked to have an idea of what kind of night is ahead. Although the Observing Specialist on Mount Wilson will be responsible for these assessments, it's a good idea to check anyway. During the day, maintenance or upgrades may have taken place with the Array so look for updates via email and the Array status from the observing specialist and/or CHARA staff on Mount Wilson. Use the links below \\  \\  \\ __**Essential Observing Links**__+**__Pre-Run Assessments__  ** \\  \\ Due to the nature of remote observing, it is beneficial to assess a few things before the evening’s run. First would be the weather. Everything from the Weather Service page, The Clear Sky Clock and the Jet Stream can be checked to have an idea of what kind of night is ahead. Although the Observing Specialist on Mount Wilson will be responsible for these assessments, it's a good idea to check anyway. Your observing success may depend on how the weather is cooperating so have back ups for clouds, wind/poor seeing, etc. During the day, maintenance or upgrades may have taken place with the Array so look for updates via email and the Array status from the observing specialist and/or CHARA staff on Mount Wilson. Use the links below \\  \\  \\ __**Essential Observing Links**__
  
 HPWREN cameras on the 150 foot Solar Tower [[http://hpwren.ucsd.edu/cameras/wilson.html|http://hpwren.ucsd.edu/cameras/wilson.html ]] 360 degree view around the mountain HPWREN cameras on the 150 foot Solar Tower [[http://hpwren.ucsd.edu/cameras/wilson.html|http://hpwren.ucsd.edu/cameras/wilson.html ]] 360 degree view around the mountain
Line 48: Line 50:
  \\  \\
 National Weather Service ([[http://forecast.weather.gov/MapClick.php?site=lox&textField1=34.2231&textField2=-118.0587&smap=1#.VKsuq2TF8rO|http://forecast.weather.gov]]) Mount Wilson weather and 5 day forecast \\ National Weather Service ([[http://forecast.weather.gov/MapClick.php?site=lox&textField1=34.2231&textField2=-118.0587&smap=1#.VKsuq2TF8rO|http://forecast.weather.gov]]) Mount Wilson weather and 5 day forecast \\
- \\ 
-CHARA telescopes spy cams and weather graph ([[http://astro.gsu.edu/~weather/chara_scopes.html|http://www.astro.gsu.edu]]) Not updated. \\ 
  \\  \\
 IR satellite loop ([[https://www.star.nesdis.noaa.gov/GOES/sector_band.php?sat=G17&sector=wus&band=GEOCOLOR&length=12|http://www.noaa.gov]]) Keeps an eye on storms and clouds coming in \\ IR satellite loop ([[https://www.star.nesdis.noaa.gov/GOES/sector_band.php?sat=G17&sector=wus&band=GEOCOLOR&length=12|http://www.noaa.gov]]) Keeps an eye on storms and clouds coming in \\
  \\  \\
-California Regional Weather Server ([[http://squall.sfsu.edu/|http://squall.sfsu.edu/]]) A variety of weather links \\ +Clear Sky Clock ([[http://cleardarksky.com/c/MtWilsonOBCAkey.html|http://cleardarksky.com/c/MtWilsonOBCAkey.html]]) a forecasting tool, but be aware that the humidity forecast is often incorrect on this site as it incorporates the marine layer forecast for the valley below, which does not affect us 80-90% of the time 
- \\ + 
-Clear Sky Clock ([[http://cleardarksky.com/c/MtWilsonOBCAkey.html|http://cleardarksky.com/c/MtWilsonOBCAkey.html]]) a forecasting tool, but be aware that the humidity forecast is often incorrect on this site as it incorporates the marine layer forecast for the valley below, which does not affect us 80-90% of the time \\ +CHARA telescopes spy cams and weather graph ([[http://astro.gsu.edu/~weather/chara_scopes.html|http://www.astro.gsu.edu]]) Not updated. \\
- \\+
  \\  \\
-**__Remote Observing Setup__  ** \\  \\ The observing specialist on Mount Wilson will run all the servers locally. Before setting up, contact the mountain observing specialist to make sure the Array is stable and ready. At this time nothing by the Remote Observer should ever be turned on unless an "All Clear" has been given by the observing specialist. The first order is to set up the remote observing station monitors and or control panel. This is done with a background click to bring up the menu options and drop down choices for the various clients and GUI’S that will be used for the night's observing session. \\  \\ The clients that we will use are:+**__Remote Observing Setup__  ** \\  \\ The observing specialist on Mount Wilson will run all the servers locally. Before setting up, contact the mountain observing specialist to make sure the Array is stable and ready. The first order is to set up the remote observing station monitors and or control panel. This is done with a background click to bring up the menu options and drop down choices for the various clients and GUI’S that will be used for the night's observing session. Also, the remote observer will need to establish a connection to the array with a vnc.  You should have the info provided by Jeremy Jones. \\  \\ The clients that we will use are:
  
-  * TELESCOPE GUI’s 
   * OPLE PRIMARY or OPLE SECONDARY GTK (Dependent on Observing Schedule – Ask the Observing Specialist)   * OPLE PRIMARY or OPLE SECONDARY GTK (Dependent on Observing Schedule – Ask the Observing Specialist)
-  * TIPTILT GTK 
-  * GPS GUI 
   * SHUTTERS   * SHUTTERS
-  * VISBEAMS 
-  * LASER FILTER WHEEL 
-  * POWER 
-  * SOCKET MANAGER 
   * WEATHER   * WEATHER
   * CLASSIC/CLIMB GTK (Dependent on beam combiner use)   * CLASSIC/CLIMB GTK (Dependent on beam combiner use)
   * PAVO and SPICA will also use the LDC's   * PAVO and SPICA will also use the LDC's
 +  * MIRCX/MYSTIC
  
  \\ NOTE: If a Client does not appear this means that the server is not yet running. Ask the Observing Specialist or standby for more information. \\  \\ Each server GUI has a STATUS tab. The Status gives the observer information about the current status of that particular system and displays the same info as the server. Since the servers are all run from the Mountain, the status display can be run on the following systems that have a STATUS GUI option to use.  \\ NOTE: If a Client does not appear this means that the server is not yet running. Ask the Observing Specialist or standby for more information. \\  \\ Each server GUI has a STATUS tab. The Status gives the observer information about the current status of that particular system and displays the same info as the server. Since the servers are all run from the Mountain, the status display can be run on the following systems that have a STATUS GUI option to use.
Line 85: Line 78:
   * On the CONTROL Tab of Cosmic Debris, choose the beam combiner by checking the proper box for the instrument you will use for the evening’s observing session. If using Classic or CLIMB, also choose the filter.   * On the CONTROL Tab of Cosmic Debris, choose the beam combiner by checking the proper box for the instrument you will use for the evening’s observing session. If using Classic or CLIMB, also choose the filter.
  
- \\  \\ **Synchronizing the Clocks** \\  \\ Will be done by the observing specialist at start up using [SYNC CLOCKS] function on Cosmic Debris. \\  \\ __**System Check**__  \\  \\ The observing specialist on the mountain will have opened up the telescope enclosures, dome slits, and optics covers, as well as have things powered up. Set up can be continued as beacon alignments and sky flats are performed. \\  \\  \\ **__OPLE Cart Operation__  ** \\ While operating the OPLE carts, the remote observer should keep an eye on the delay lines as much as possible. Do not change the direction of the carts too quickly. When moving them, click STOP, wait, and then restart them. Also watch for warnings on the OPLE server STATUS display. If the FH= Front Hard or BH = Back Hard lights up it means the hard limit switch has been contacted by the cart, and the observer needs to notify the Observing Specialist and turn the carts OFF. If you suspect that the carts aren’t moving, or are stuck, or are not moving at the correct speed, IMMEDIATELY stop and notify the observer. \\  \\ **Checking the Cart Positions** \\ • The reference cart is stationary. Astrolib will give a TARGET position of where the Ref cart should be. When this position is set the other cart should come into range leaving plenty of delay space to slew through. If not, recheck or reset the REF position. \\ • For example, Astrolib gives a TARGET position of 30 Meters. The reference cart should be set to that position give or take. The moving cart then needs to be placed to allow room for it to slew between 0-44m. If the moving cart is out of this range, change the reference cart position to accommodate the moving cart. \\ • On Cosmic Debris, type in the reference position in the empty field next to the ‘REF’ input. The empty space next to this is for controlling the speed of reference cart, which we shall leave alone for now. \\ • The position that was just set will register in about 10 seconds on the OPLE server STATUS display under ‘Target’. \\ • Once the REF position has registered, the carts can go into place by clicking TRACK on the OPLE GUI. \\ • Once each cart has reached its position and the ERRORS are low, everything is set. \\ • Also once the carts are tracking, click the ‘MAN’ and ‘OL’ buttons for the moving carts and the OL button for the ref cart. \\  \\ __**Routine Observing**__  \\  \\ It is at this time that you can settle down to the standard, and sometimes mundane, part of observing. Not to be taken for granted, data means WINNING!!! As soon as the scopes are locked on the stars and carts are tracking, the Remote Observer can start fiber mapping, camera aligning, searching for fringes and taking data. Remember the Array is made up of many systems and at anytime one could falter. If problems occur, notify the observer. When trouble arises proceed slowly and carefullyDon’t forget to check the CHARA Array Control Software Manual or in the worst case scenario call the CHARA Control Room.+ \\  \\ **Synchronizing the Clocks** \\  \\ Will be done by the observing specialist at start up using [SYNC CLOCKS] function on Cosmic Debris. \\  \\ __**System Check**__  \\  \\ The observing specialist on the mountain will have opened up the telescope enclosures, dome slits, and optics covers, as well as have things powered up. Set up can be continued as beacon alignments and sky flats are performed. \\  \\  \\ **__OPLE Cart Operation__  ** \\ While operating the OPLE carts, the remote observer should keep an eye on the delay lines as much as possible. Do not change the direction of the carts too quickly. When moving them, click STOP, wait, and then restart them. Also watch for warnings on the OPLE server STATUS display. If the FH= Front Hard or BH = Back Hard lights up it means the hard limit switch has been contacted by the cart, and the observer needs to notify the Observing Specialist and turn the carts OFF. If you suspect that the carts aren’t moving, or are stuck, or are not moving at the correct speed, notify the observer. \\  \\ **Checking the Cart Positions** \\ • The reference cart is stationary. Astrolib will give a TARGET position of where the Ref cart should be. When this position is set the other cart should come into range leaving plenty of delay space to track through. If not, recheck or reset the REF position. \\ • For example, Astrolib gives a TARGET position of 30 Meters. The reference cart should be set to that position give or take. The moving cart/s then need to be placed to allow room for them to track between 0-44m. If the moving cart is out of this range, change the reference cart position to accommodate the moving cart/s or check if the pops are set correctly if no delay is available on any delay line. \\ • On Cosmic Debris, type in the reference position in the empty field next to the ‘REF’ input. The empty space next to this is for controlling the speed of reference cart, which we shall leave alone for now. \\ • The position that was just set will register in about seconds on the OPLE server STATUS display under ‘Target’. \\ • Once the REF position has registered, the carts can go into place by clicking TRACK on the OPLE GUI. \\ • Once each cart has reached its position and the ERRORS are low, everything is set. \\ • Also once the carts are tracking, click the ‘MAN’ and ‘OL’ buttons for the moving carts and the OL button for the ref cart for the CLASSIC, CLIMB, PAVO, and JOUFLU programs.  MIRCX/MYSIC now use the FT buttons fro fringe tracking. \\  \\ __**Routine Observing**__  \\  \\ It is at this time that you can settle down to the standard, and sometimes mundane, part of observing. Not to be taken for granted, data means WINNING!!! As soon as the scopes are locked on the stars and carts are tracking, the Remote Observer can start fiber mapping, camera aligning, searching for fringes and taking data. If problems occur, notify the observer. 
 + 
 +__**PoP changes during the night**__  \\  \\ It is proper protocol for the PI's or remote observers to announce any PoP changes 10 minutes before needed. Please give the PoP's for only the telescopes that need changing. Use this format: E1-1, E2-2, W1-3, etc. Give only the final PoP. \\  \\ **__Configuration changes during the night__  ** \\  \\ It is also proper protocol for the PI's or remote observers to announce any configuration changes 30 minutes before needed so the operator can open telescope domes and have the scopes ready for the changeFailure to announce changes causes observing time to be lost. Please also include additional configurations in your set up request. If a scope runs out of delay, please inform the operator if you want the star to be locked on subsequent slews or if the scope can be put away for the night. 
 + 
 +**__Monitoring MIRCX/MYSTIC observing__  **
  
-__**PoP changes during the night**__  \\  \\ It is proper protocol for the PI's or remote observers to announce any PoP changes 10 minutes before needed. Please give the PoP'for only the telescopes that need changingUse this format: E1-1, E2-2, W1-3, etc. Give only the final PoP\\  \\ **__Configuration changes during the night__  ** \\  \\ It is also proper protocol for the PI's or remote observers to announce any configuration changes 30 minutes before needed so the operator can open telescope domes and have the scopes ready for the change. Failure to announce changes causes observing time to be lostPlease also include additional configurations in your set up request. If a scope runs out of delay, please inform the operator if you want the star to be locked on subsequent slews or if the scope can be put away for the night. \\  \\  \\ __**Nightly Observing Report**__  \\  \\ The Observing Report is automatically generated by Cosmic Debris at the end of the observing. Check the report for completeness and accuracy and inform your observing specialist if there are notes which you would like to have added to the report.+When running MIRCX/MYSTIC, the operator may want to have the windows open to follow the fiber mapping, scanning for fringes and data recordingThe windows can be opened with the command mircx_launch_all_guis on a desktop terminal. It will open 5 windows for each combiner, but they do not need to all be openClose what you don'want to monitor. The fiberexplorer, gdt, rtd, and super_gtk windows are most helpful. \\  \\  \\ __**Nightly Observing Report**__  \\  \\ The Observing Report is automatically generated by Cosmic Debris at the end of the observing. Check the report for completeness and accuracy and inform your observing specialist if there are notes which you would like to have added to the report.
  
  
chara/remote_observing.1644435657.txt.gz · Last modified: 2022/02/09 14:40 by charaobs