Differences

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

--- chara:remote_observing [2022/02/09 19:43]
charaobs
+++ chara:remote_observing [2022/02/10 18:52] (current)
charaobs
@@ Line 84: / Line 84: @@
  \\  \\ **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 ﬁeld 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 carefully. Don’t forget to check the CHARA Array Control Software Manual or in the worst case scenario call the CHARA Control Room.
-__**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 change. Failure 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. \\  \\  \\ __**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.
+__**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 change. Failure 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__ **
+When running MIRCX/MYSTIC, the operator may want to have the windows open to follow the fiber mapping, scanning for fringes and data recording.  The 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 open.  Close what you don't 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.

The CHARA Array Wiki

User Tools

Site Tools

Differences

Page Tools