This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
chara:remote_observing [2020/07/24 15:09] jones |
chara:remote_observing [2023/02/13 16:59] charaobs |
||
---|---|---|---|
Line 1: | Line 1: | ||
====== Remote Observing ====== | ====== Remote Observing ====== | ||
- | Note: As of June 2018, we are using a new remote observing procedure. Details can be found here: [[http:// | + | Note: As of June 2018, we are using a new remote observing procedure. Details can be found here: [[http:// |
+ | |||
+ | Last updated 2-13-2023 by Norm | ||
__**Remote Observing**__ \\ | __**Remote Observing**__ \\ | ||
Line 18: | Line 20: | ||
**__Modes of Operation__ ** \\ | **__Modes of Operation__ ** \\ | ||
\\ | \\ | ||
- | Since several beam combiners can run simultaneously at CHARA, it is important that the remote observers follow the observing procedures correctly and maintain good communication with the Array Operator (or Observing Specialist). The Array Operator will determine the priority and order in which to address problems that arise. Sometimes the Array Operator may be quite busy. If a serious situation | + | Since several beam combiners can run simultaneously at CHARA, it is important that the remote observers follow the observing procedures correctly and maintain good communication with the Array Operator (or Observing Specialist). The Array Operator will determine the priority and order in which to address problems that arise. Sometimes the Array Operator may be quite busy. If something wrong occurs with the OPLE carts, cameras |
\\ | \\ | ||
\\ | \\ | ||
__**Pre-Observing Communications**__ \\ | __**Pre-Observing Communications**__ \\ | ||
\\ | \\ | ||
- | Please | + | Please |
- | * Date of program start and number of nights. Please specify | + | * Date of program start and number of nights. Please specify |
* Program PI and designation | * Program PI and designation | ||
* Beam Combiner(s) | * Beam Combiner(s) | ||
- | * Telescopes used in first configuration and back up scopes or configurations. Please | + | * Telescopes used in first configuration and back up scopes or configurations. Please |
* Beam order (if you have a preference) | * Beam order (if you have a preference) | ||
* PoP combination to start and PoP changes during the night | * PoP combination to start and PoP changes during the night | ||
* First target (or designated check star for first target) so operator can init scopes and align beacons in the proper part of the sky | * First target (or designated check star for first target) so operator can init scopes and align beacons in the proper part of the sky | ||
- | * Filter | + | * Filter |
- | * Any special requirements you might have (LDCs in or out, CLIMB for fringe finding/ | + | * Any special requirements you might have (LDCs in or out, CLIMB for fringe finding/ |
- | * Skype or phone contact if remote (in case we do not already have it). Skype is the preferred means of communicating so please create an account if you do not have one. | + | * Discord |
- | \\ 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 | + | \\ 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 |
+ | |||
+ | \\ 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. | ||
\\ | \\ | ||
\\ | \\ | ||
- | **__Pre-Run Assessments__ | + | **__Pre-Run Assessments__ |
- | \\ | + | |
+ | HPWREN cameras on the 150 foot Solar Tower [[http://hpwren.ucsd.edu/cameras/wilson.html|http://hpwren.ucsd.edu/cameras/wilson.html ]] 360 degree | ||
Caltech Millikan Library Camera ([[http:// | Caltech Millikan Library Camera ([[http:// | ||
\\ | \\ | ||
National Weather Service ([[http:// | National Weather Service ([[http:// | ||
\\ | \\ | ||
- | CHARA telescopes spy cams and weather graph ([[http:// | + | IR satellite loop ([[https://www.star.nesdis.noaa.gov/GOES/sector_band.php?sat=G17§or=wus& |
- | \\ | + | |
- | Aerospace Corporation weather station ([[http:// | + | |
- | \\ | + | |
- | Jet stream forecast ([[http:// | + | |
- | \\ | + | |
- | IR satellite loop ([[http://www.wrh.noaa.gov/lox/scripts/ | + | |
- | \\ | + | |
- | California Regional Weather Server ([[http:// | + | |
- | \\ | + | |
- | Clear Sky Clock ([[http:// | + | |
\\ | \\ | ||
+ | Clear Sky Clock ([[http:// | ||
+ | |||
+ | CHARA telescopes spy cams and weather graph ([[http:// | ||
\\ | \\ | ||
- | **__Remote Observing Setup__ | + | **__Remote Observing Setup__ |
- | * 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/ | * CLASSIC/ | ||
- | * Visible programs | + | * PAVO and SPICA will also use the LDC's |
+ | * MIRCX/ | ||
- | \\ 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 GUI has a STATUS | + | \\ 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 |
* OPLE | * OPLE | ||
- | | + | * CLASSIC or CLIMB |
- | * The TELESCOPES | + | |
- | * GPS | + | |
- | | + | |
\\ **__Cosmic Debris - The Sequencer__ | \\ **__Cosmic Debris - The Sequencer__ | ||
Line 88: | 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. | ||
- | \\ **TIPTILT Comms** \\ \\ • Check the TIPTILT STATUS GUI. If it reads that the selected beams are correct for the combiner you’re using, then all is well. \\ • If not, notify the Observing Specialist so that they can run the TIPTILT COMM sequence again. [TIPTILT COMM] is a button on Cosmic Debris. When selected, Cosmic Debris will put 7 items in the job queue and then run them. If the communication is established there will be messages in the status window of the Cosmic Debris indicating signal rates for tiptilt for the chosen telescopes. | + | |
- | + | ||
- | * Find a bright star near your first target to initialize the telescopes. The [FIND STAR] button on the Telescope Control Tab can be useful in finding a suitable, bright star. | + | |
- | * Enter the HD number | + | |
- | * Check to make sure that EL/AZ reported by Cosmic Debris are correct (never point below 15-20 degrees elevation). It is recommended to initialize | + | |
- | * Slew to the target by clicking [OBJECT], [CHECK STAR], [CALIBRATOR 1], or [CALIBRATOR 2] on Cosmic Debris (depending on which field you entered | + | |
- | * Verify that the telescopes are moving by checking the azimuth | + | |
- | | + | |
- | * Enter the ideal reference cart position | + | |
- | * When the telescope slew finishes, check the spy cameras to make sure that the domes are aligned with the telescope. | + | |
- | * Click [FIND] | + | |
- | * Switch to the ACQ window | + | |
- | + | ||
- | \\ Acquisition Laser Alignment | + | |
- | + | ||
- | * Check availability of VISBEAMS with Observing specialist. | + | |
- | * Put the Neutral Density Filter on ND 3.0 using the Laser_Filters GUI. | + | |
- | * Using the SHUTTERS GUI, open the laser shutter | + | |
- | * Put the corner cubes in with the [CC IN] button | + | |
- | * You will see the star and reflection and the laser and reflection in the ACQ field of view. | + | |
- | * Use the " | + | |
- | | + | |
- | | + | |
- | | + | |
- | * You may need to redo the ACQ laser alignment during the night, especially if slewing far in azimuth. | + | |
- | + | ||
- | \\ Locking Tiptilt | + | |
- | + | ||
- | * With the star aligned with the acquisition ticks, check to make sure there are counts on the TipTilt server or white plots in the TT windows. | + | |
- | * On the Tiptilt Servo Control GUI, turn tiptilt [ON] for that telescope. | + | |
- | * On the Main Tab of the Telescope GUI, click [TIPTILT] under the Pointing Servo menu. If this button is not pressed, the telescope will not be guided by the TT servo and TT will lose the star as the pointing model takes the star out of the range of the TT mirror. It can be seen by the green dots drifting to one side on the tiptilt windows. | + | |
- | + | ||
- | \\ Finishing the slew sequence | + | |
- | + | ||
- | * If the Job Queue was stopped | + | |
- | * Click [Star Acquired] on the Control Tab on Cosmic Debris to update the target information listed at the top of the Cosmic Debris window. | + | |
- | * You can now point to your first science target/ | + | |
- | | + | __**PoP changes during the night**__ |
- | | + | **__Monitoring MIRCX/MYSTIC observing__ |
- | | + | |
- | | + | |
- | | + | |
- | \\ **__6.8 OPLE Cart Operation__ | + | When running MIRCX/ |