Differences

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

--- chara:trouble_shooting [2023/07/06 07:45]
gail_stargazer
+++ chara:trouble_shooting [2023/11/21 01:23]
charaobs [Can't find the star]
@@ Line 28: / Line 28: @@
   * Check the instrument alignment. Is flux getting through to the detector? How long has it been since the last NIRO camera alignment? Classic and CLIMB programs can run for about an hour before the light will drift from the central pixel. Use the Classic or CLIMB gui to view the light on the pixels by clicking the PICTURE tab and then the PIXEL AREA button. Turn the camera off with the STOP button. Is the right dither power turned on? CLIMB 1 and Classic use different dithers. If Classic or CLIMB fringes are found in a scan, but not when in recording mode, the dither powers are likely not on. Are the camera settings correct for the seeing conditions and flux levels?
   * There is a script that will display offsets for all scopes against Hour Angle to help find offsets when using MIRCX and MYSTIC. You'll need to log into the MIRCX spooler computer with the command ssh spooler@mircx, then use the command fringe_predictor. A window will pop up displaying the last five nights of offsets vs. HA.
+===== Can't find the star =====
+Sometimes the star does not appear on the ACQ camera and there are many reasons why this can happen. Here are some of those reasons.
+  * Did the telescope actually slew? If the powers are off or the scope is disabled, it will not slew.
+  * Did the telescope disable after slewing? Check the dome gui to see if it says it has disabled. Enable to get it going again.
+  * Are the M1 and M3 covers open? Check with the Telescope monitor or spycam 2 to see if the covers opened.
+  * Did the dome rotate with the scope? Check with Spycam 1 to see if it is blocking the telescope. Use Autodome On to get it in line with the telescope.
+  * Is the ACQ camera showing a live view. Hit ACQ or reopen to see a live view. If the server has quit, bootlaunch on the appropriate computer to restart the ACQ server. Sockman will tell which computer the server runs on. Should be wfs computer at each scope.
+  * Is the ACQ exposure appropriate for the star magnitude? Turn it up as needed to show the star.
+  * Has the default flat or last flat been loaded after a slew? A bad DM will distort dim stars and they will not be visible.
+  * Is the star too low or obstructed by a tree or dome? W1 and S2 have trees nearby that can obscure the star below 40 degrees. Refer to the horizon maps to see if they are the cause.
+  * E1 does not track past 218 degrees azimuth. The finder camera may be needed to find the star again. It will be off in azimuth, but should still show in the finder.
+  * If a telescope is lost and star does not appear in the finder either, such as after a dome server crash and restart, a bright star, the moon or Jupiter can be used to get the scope pointing correctly. Anything brighter than Vmag 1 will show on the Spycam 1 view and can be used to get the scope close enough to find it in the finder, then ACQ. It should be placed just below the top bar of the telescope, centered left to right using the telescope paddle. You may have to pan up and down to see it move through the finder view. Use the obsgtk ADJUST tab scope paddle and set a step of 3000 and go up and down after centering it in the SPY 1 view below the top telescope bar. When you get it centered in the finder, manually init the scope to the AZ and EL on the MANUAL tab of the dome gui to one decimal place. Use Stellarium online or any resource to get the current position. You should then be able to slew to a star and center it in the finder, then ACQ and init on the obsgtk to get the scope back to usual.
 ===== The new OPLE system =====
@@ Line 195: / Line 211: @@
 S2's acquisition server resides on "S2pi4" computer. Logging on to it (ssh s2pi4) and running bootlaunch will restart it
+==== Focusing the Telescope ====
+  - Fully align beacon to labao and TWFS, especially making sure the focus terms between the two agree very well.
+  - Open a secondary gui: mergurygtk W2_SECONDARY.
+  - Note the current M2 actuator positions and send them to Nic for the log.
+  - Turn off the beacons and lock the star on TWFS tiptilt.
+  - Turn the servo on in the mercurygtk gui.
+  - On the align tab of the wfsgtk there is a button for FOCUS SCOPE.
+  - Press the button.
+  - When done the focus term of starlight on the TWFS should be zero.
+  - Turn off the servo on the mercury_gtk gui.
+A couple of notes:
+  * If large moves of M2 are made, tiptilt tracking may be lost. Pay careful attention so that M2 doesn't get driven away crazily due to lost light.
+  * If it takes too long to start the autofocus procedure, the mercury_gtk servo will automatically turn off and nothing will happen. So just make sure the servo is on right before hitting the FOCUS SCOPE button.
 ===== Dome issue =====
@@ Line 229: / Line 262: @@
 ==== LabAO Shutters Not Working ====
-If the labao shutters are not working, the power button on each of the two red control boxes on the top of the table might need to be pressed. After that the other button needs to be pressed and held for 5 seconds so that the units can be controlled remotely. (Note: look for instructions on table.)
+<font 10.5pt font-family:/inherit;;#333333;;inherit>If the labao shutters are not working, the power button on each of the two red control boxes on the top of the table might need to be pressed. After that the other button needs to be pressed and held for 5 seconds so that the units can be controlled remotely. (Note: look for instructions on table.) A good way for this step is to manually set the shutter to the opposite state that it is in remotely, keep pressing the “enable” button until you hear a slight click. Release. The shutter should now change state.</font>
+<font 10.5pt font-family:/inherit;;#333333;;inherit>If this does not work, or the other CHARA shutters are not working then a reboot is required. The order of restart needs to be correct for all shutters to work again (not shutters on insturment tables which are controlled by instrument servers).</font>
+<font 10.5pt font-family:/inherit;;#333333;;inherit>Turn off electronics box for shutters (above the GPS computer). Reboot the gps computer. Check to see that the shutter server is running by typing bootlaunch_master on gps computer. If running, turn on shutter electronics box (you just rebooted gps computer so restart gps server).</font>
 ==== LabAO DM Electronics ====
@@ Line 251: / Line 288: @@
 ==== Homing carts ====
-  *
+  * To home the carts, turn off the [OL] and [MAN] buttons on each cart and it will automatically return to the front switch. If the cart has no issue, it will arrive at the target position of 0m and the home switch at the same time. The X in the OPLE server under the HM will indicate it has stopped on the home switch. If a cart does not reach the home switch when it returns to position 0m, it was lost and likely the cause of the difficulty in finding fringes. The X does not guarantee the cart has retained its home position. This home position can be checked by using the CHECK button on the ople gui or by typing the command “homechk S1” into the ople server. When the error value is displayed on the ople server, hit ESC to clear the display. Click on the [OL] and [MAN] buttons and hit [TRACK] to send the cart to the desired cart position.
-To home the carts, turn off the [OL] and [MAN] buttons on each cart and it will automatically return to the front switch. If the cart has no issue, it will arrive at the target position of 0m and the home switch at the same time. The X in the OPLE server under the HM will indicate it has stopped on the home switch. If a cart does not reach the home switch when it returns to position 0m, it was lost and likely the cause of the difficulty in finding fringes. The X does not guarantee the cart has retained its home position. This home position can be checked by using the CHECK button on the ople gui or by typing the command “homechk S1” into the ople server. When the error value is displayed on the ople server, hit ESC to clear the display. Click on the [OL] and [MAN] buttons and hit [TRACK] to send the cart to the desired cart position.
 ==== Metrology ====
-  *
+  * Good metrology signals are important to the proper positioning of the carts. Monitor the signal strength by running [RUN MULTIPLE] on the Metrology Monitor. Place the windows above the TV windows for each scope you are using. They should show white sine waves that are around the height of the window. Erratic, fluctuating waves indicate self-interference or a weak signal. This may cause the carts to lose their place as the signal strength falls too low. Red waves indicate that some displayed signal has gone too low and the carts will all need to be homed. A careful adjustment of the MET2 mirror can sometimes bring the signal back. Do not adjust the MET1 mirror
-Good metrology signals are important to the proper positioning of the carts. Monitor the signal strength by running [RUN MULTIPLE] on the Metrology Monitor. Place the windows above the TV windows for each scope you are using. They should show white sine waves that are around the height of the window. Erratic, fluctuating waves indicate self-interference or a weak signal. This may cause the carts to lose their place as the signal strength falls too low. Red waves indicate that some displayed signal has gone too low and the carts will all need to be homed. A careful adjustment of the MET2 mirror can sometimes bring the signal back. Do not adjust the MET1 mirror
 Steps for adjusting MET2:
@@ Line 452: / Line 485: @@
 Follow instructions in the [[:chara:mircx_monitors|linked page to display the MIRC-X wolverine2 monitors]] in the control room.
- \\
+==== No Power for Aperture Wheels ====
-Last updated 2023-02-09 by Norm Vargas END HERE
-==== Telescope is not receiving the commanded position for a target. ====
+To minimize heat sources in the lab, the power for the apwheels is turned off. If you need to use aperture wheels during the night, the operator will need to plug the power into the outlet next to the metrology table (see photo below). If there are any communication issues after plugging in the power, try restarting the server using bootlaunch on ctrscrut. It's probably a good idea to home the apwheels after turning on the power.
-Sometimes it happens that a telescope receives the wrong position for a target or does not receive the commanded position at all. The commanded position is listed on the telescope server in the first column under TCS Az/El; the second column lists the actual position of the telescope. Try entering the star designation directly into the telescope server, ie. hd 123456. If it does not accept the number, try closing and restarting the telescope server and hitting repoen on Cosmic Debris and the telescope gui. Try entering the star into the server again. If that does not work, it is possible that something is wrong with the dome server. To restart the dome server follow these steps above.
+{{:chara:d859af0efb2dab690d3a44526d7b8afc.png}}
-==== Telescope is tracking poorly, overshooting in slew, oscillating. ====
-This might mean that the gain for the tracking servo is wrong. Note that changing this gain can be dangerous, especially if you set it too high as that can cause the telescope to oscillated and damage the drives. Please only do this if you are very very sure that it is necessary. Symptoms of bad gain are: The scope over shoots the position while slewing. The star will be seen to move out of the window and may come back after a few seconds. This means the slewing gain is too low. The scope oscillates when tracking or after a slew. The star will be tracing an ellipse, figure eight or other looping shape. This means the tracking gain is too low. You can damp this out with the telescope or dome gui by disabling the scope, then re-enabling it. Adjust the gain upward and watch it on the next slew. In all cases if either gain is too high the scope will go into "Fog Horn" mode, which is bad. This can be seen during slews on the twfs or labao as vibrating spots, usually in one axis.
-You always want to use the lowest gain that still allows the scope to work as best as possible. If the tiptilt tells you the scope is oscillating slowly, the gain may be too low. If it is oscillating quickly it may be too high.
-The usual values for slewing gains are 4-7 and tracking gains are 7-10. Note that these values may change as the temperatures change rapidly. Gains are usually higher when cold and lower when warm. Be sure to set mode back to AUTO if changing the gains left it in Slewing or Tracking mode.
-==== How to Adjust CPUMotor Gains ====
  \\
-The GAIN controls the gain of the feedback between the encoder and the drive velocity. A high gain means a "stiffer" response, but can lead to oscillations or fog-horning if it's too high. \\  \\
+Last updated 2023-02-09 by Norm Vargas END HERE
-The Fn controls the maximum frequency of the servo response. A high Fn means higher frequencies are allowed through, which can mean correcting for faster problems but if too high can also lead to oscillations or fog-horning. \\  \\
-The software will not make changes to either of these quickly as that is a dangerous thing to do. There is NO POINT to clicking the up or down buttons more than once every few seconds. Indeed it is bad to do so as you will confuse the software. The change between slewing and tracking is also slow for similar reasons. This is why sometimes the "wrong" thing seems to change. It is a sign that you are trying to do things too quickly. \\  \\
-Slew and tracking mode work differently, mostly because the speeds are so different. \\  \\
-IN SLEWING MODE \\  \\
-- If the gain is too low you will overshoot the target. \\  \\
-- If the gain is too high it will fog-horn. \\  \\
-- If the Fn is too high it will also fog-horn, even at low gains. \\  \\
-You need to have the lowest possible gain and Fn in slew mode that doesn't overshoot the target. Fn in slew mode should almost never be higher than 4. If it is, please turn it back down to 4. If you think this is a problem please let Theo know, along with a detailed explanation of what happened. \\  \\
-IN TRACKING MODE \\  \\
-- If the gain is too low it will keep moving between slewing and tracking. \\  \\
-- If the gain is too high it will fog-horn. \\  \\
-- The same goes for Fn. \\  \\
-In tracking mode you want the highest gain and Fn that allows the telescope to track well without fog-horning. If it "oscillates", which you will see in the green dots of tiptilt oscillating, try turning up the gain, and also try turning down the Fn. \\  \\
-Some final remarks: \\  \\
-- The gain is temperature dependent, so when the temperature changes these things will change, but more so for tracking. \\  \\
-- The tiptilt system almost never causes oscillations, it almost always shows you that the scope is oscillating. If the white dots are centered on tiptilt and the green dots are moving the tiptilt is doing it's job and correcting for scope motion. \\  \\
-- If a drive gets disabled at the end of a slew, the gain is too low. At low gain and low velocity the encoder signal changes very slowly or doesn't change at all. After 5 secs the software interprets this as a stall and disables the drive. The tricky part is that increasing the gain to avoid this situation might make the telescope to oscillate during the next slew. So the gain should be low (4 or even 1) during slewing but higher 7 or 10 when the telescope is basically at the target position.
-==== E2 AOB Dichroic Recovery ====
-{{:chara:files:beaconrecoveryinstructions.pdf|E2 AOB Dichroic Recovery Document}}
-==== E1 Hut and Cooler Communications Recovery ====
-{{:chara:files:e1_hut_coms_recovery.pdf|E1 HuT and Cooler Communications Recovery}}
-==== S2 Acquisition Server Restart ====
-S2's acquisition server resides on "S2pi4" computer. Logging on to it (ssh s2pi4) and running bootlaunch will restart it
-===== Dome issue =====
-At times the domes do not rotate, open or close, or otherwise behave. Some problems are simple and others are more complex.
-==== Dome does not rotate ====
-Sometimes when observing, the dome will not follow the telescope during a slew. This can happen when the Autodome feature is not turned on. Click the ON button on the MAIN tab of the telescope gui to enable it. This may happen after a server restart so always check the dome position with the spycam during a slew after a server restart. Also make sure the target position of the dome matches the telescope's position. If not, it will insist on being in the wrong place. If it is not at the same AZ as the scope, manually move it until it is centered on the telescope in spycam 1. If the dome AZ does not read the same as the telescope AZ, enter the scope AZ in the position box of the DOME tab of appropriate dome server and hit the INIT POS button to tell it at what AZ it is. \\  \\
-If the dome does not turn at all, even with the manual controls on the telescope or dome guis, the control may be set to manual on the control box. This can happen if there was work done at the dome during the day. If the dome opens, but does not turn, check to see that control of the dome rotation is in the computer position and not manual on the dome rotation controller box just inside the door of the bunker. Sometimes the drive wheel jumps in the track and cannot turn the dome, even when the motor works. This will need to be fixed during the day.
-==== Dome does not open ====
-Is the SPYCAM on and updating? An old image may show the dome is closed, but it has actually started to open. If the dome won't open, try hitting the SLIT CLOSE button on the telescope gui first. It may be that there was a computer or server issue and the computer thinks the dome is open already and won't allow it to open again. Hit the SLIT OPEN button to see if it works now. If it still won't open, go to the bunker and look to see if the power switch is on to the dome. It will be up and red if on.
-Also look to see if the power cable is connected to the computer box. If it's connected up high to the manual dome controls, the cable needs to be brought back to the computer box connector. __Turn the power off first__  to the dome before disconnecting the power cable. Slide it onto the connector at the box and turn the collar to lock it in place. Turn the power back on and see if you can open the dome from the computer in the bunker.
-==== Dome does not close ====
-If a dome will not close after observing, it may need to be closed manually at the bunker. Turn the power to the dome off at the switch, disconnect the cable from the computer control box and connect it to the manual control switches above. Turn on the power to the dome after connecting the cable and use the two controls to close the dropout first, then the slit. The dropout must be fully closed and the slit closed over it to be shut properly. Inform the staff that the dome did not function properly so someone can look at it in the morning.
-===== HUT servers =====
-The HUT servers control functions such as beacon and dichroic movements, heater and dehumidifier usage, and various AO functions. An observer may find that the obsgtk is no longer controlling the beacon LED's, beacon flat or dichroic alignments. This happens on occasion with E2 and other scopes. The HUT server may be the cause if it has quit or lost connection or the AOB may be at fault. To see if it is the server, open the HUT gui for the desired telescope from the CHARA menu. If the alignments can be changed from the gui, then the HUT server is ok. You can use the hut gui to continue observing. If the hut gui gives move error messages, cycle the power on the AOB and open a new hut server to restore the connection to the obsgtk. On the POWER gui, turn off the power to the AOB for the offending telescope and turn it back on. Stop the hut server by logging into the appropriate telescope computer and identifying the PID with the bootlaunch_master command and killing the process with the kill -9 #### command. Start the new server via the bootlaunch_master command. Hit REOPEN on the obsgtk to reopen the connection to the HUT server and hit reopen on Cosmic Debris as well.
-If the server won't restart, a reboot of the power supply in the telescope bunker might be necessary. The power supply that controls the acquisition and finder cameras as well as their controllers is located on top of the computer rack in each bunker. The power supply has green readouts of volts and current. After turning the power off for 10 seconds and back on, try restarting the server from the computer in the bunker to see if it starts cleanly. If so, then restart the telescope server, reopen the connection to the telescope gui, and hit REOPEN on Cosmic Debris. Part of the HUT server also controls the AO table. If the AOB part of the HUT server doesn't work, then the power supply on the back of the AO table in the telescope dome might need recycling. This power supply controls the actuators at M2 and the AO table. The power supply box is a 6×9 inch aluminum box on the back of the AO table, behind the keyboard and monitor. Turn it off with the power button on the bottom edge of the box, wait 5 seconds and turn it back on. The HUT server should now restart cleanly. Restart the telescope server as well to make the connections to the telescope gui. Hit REOPEN in Cosmic Debris if you are observing to make all needed connections.
-===== Tiptilt Server. (These sections apply to the old lab tiptilt system retired in April 2021) =====
-[[:chara:old_lab_tiptilt_server|Instructions for the old lab tiptilit system are archived here.]]
-===== LabAO =====
-==== LabAO Shutters Not Working ====
-If the labao shutters are not working, the power button on each of the two red control boxes on the top of the table might need to be pressed. After that the other button needs to be pressed and held for 5 seconds so that the units can be controlled remotely. (Note: look for instructions on table.)
-==== LabAO DM Electronics ====
-If a labao server complains that it failed to find the EDAC40 device, try unplugging the power and ethernet cables for DM and then replugging in again.
-===== OPLE and Metrology =====
-==== OPLE Server doesn't open - complains about not finding run_ople ====
-This usually happens if someone runs a "make clean" in the cvs tree but doesn't follow up with a "make install" on ople. To generate the run_ople file, follow these steps:
-  * Open a terminal window and type "ople" to log onto the ople machine.
-  * Change to the appropriate directory under the CVS tree by typing "cd control/cliserv/ople"
-  * Update the CVS tree by typing "cvs update"
-  * Run the Makefile script by typing "make"
-  * Log on as root by typing "su" and entering password.
-  * Type "make install"
-  * This will install run_ople. Try opening the ople server again.
-==== Homing carts ====
-  * To home the carts, turn off the [OL] and [MAN] buttons on each cart and it will automatically return to the front switch. If the cart has no issue, it will arrive at the target position of 0m and the home switch at the same time. The X in the OPLE server under the HM will indicate it has stopped on the home switch. If a cart does not reach the home switch when it returns to position 0m, it was lost and likely the cause of the difficulty in finding fringes. The X does not guarantee the cart has retained its home position. This home position can be checked by using the CHECK button on the ople gui or by typing the command "homechk S1" into the ople server. When the error value is displayed on the ople server, hit ESC to clear the display. Click on the [OL] and [MAN] buttons and hit [TRACK] to send the cart to the desired cart position.
-==== Metrology ====
-  * Good metrology signals are important to the proper positioning of the carts. Monitor the signal strength by running [RUN MULTIPLE] on the Metrology Monitor. Place the windows above the TV windows for each scope you are using. They should show white sine waves that are around the height of the window. Erratic, fluctuating waves indicate self-interference or a weak signal. This may cause the carts to lose their place as the signal strength falls too low. Red waves indicate that some displayed signal has gone too low and the carts will all need to be homed. A careful adjustment of the MET2 mirror can sometimes bring the signal back. Do not adjust the MET1 mirror
-Steps for adjusting MET2:
-  - Looking at the met signal while the cart is at the back.
-  - Peak so that the beam is aligned as well as possible. Does not need to be perfect but not loose.
-  - All beams have a signal between 1-2 volts while at the back. Sometimes the signal strength can change for no apparent reasons.
-  - Using steps of 50, try moving 3 times in one direction. After each step, wait 5 seconds or so for things to update. If nothing then try the other way.
-  - Return to starting position.
-  - Repeat for the other axis.
-===== Beam Samplers =====
-==== Beam Samplers are not moving ====
-This happens most frequently with the E1 beam sampler. If you are doing alignments and are using E1, try to move it forward first to see if it dies. If it does, follow this procedure.
-  * Turn off power on Newport Universal Motion Controller/Driver for the Beam Samplers (on top of rack in computer area, labelled "BS")
-  * Then go behind the racks and locate the serial port for BS. Look for all of the blue ethernet cables coming out. BS is labelled in prt 2. Remove the ethernet cable for BS. The step stool is available to make it easier to reach the blue ethernet cable at the back of the BS controller box.
-  * Restart BS controller (press power button again). Wait for all axes to appear on screen.
-  * Plug the ethernet cable back in.
-  * Restart BS server on ctrscrut using commands in /etc/rc.local (see instructions below)
-  * Reopen Beam Sampler GUI. You will need to home each Beam Sampler one by one. You should be able to do this from the regular Beam Sampler GUI. If that doesn't work, try opening "espgtk BS" from the command line.
-==== Restarting the Beam Sampler Server ====
-The most common cause for getting multiple copies of a server is using the socket manage RESTART button, which is flaky at best. Don't do this. If you need to restart a server you should do it manually.
-. Make sure you are logged into the right machine: ssh ctrscrut
-. If you are not sure see if the socket manager will tell you. If it doesn't have a look in the file: /ctrscrut/chara/etc/sock_manager/socket_manager.list
-. See if there are any ghosts running
-ps aux | grep esp_server
-Yes, it's hard to know which one it is with the esp servers. You can work out which ones are ghosts by typing the command
-tsockman |grep ctrscrut
-which will give you a list of the servers running on the machine you are interested in. Checking for non-matching PIDs will tell you which processes you need to stop.
-. Stop those processes:
-kill -9 PID1 PID2 ….
-. Make sure there is no sign of it in the socket manager
-tsockman rm BS
-. Restart the beam sampler servers (this starts both beam sampler servers BS1 and BS2):
-bootlaunch_beamsamp
-==== "Failed to request position of S1" ====
-Cosmic Debris reports "Failed to request position of S1" when trying to set the beam order. This indicates that ople is no longer talking to the beam samplers. If the beam sampler server has been restarted recently, then the ople server will also need to be restarted to re-establish the connection. \\  \\
-The beam sample server runs on ctrscrut. The ople server tries to open a connection to the beam sampler when it starts. If the beam sampler is not there, or dies, \\
-you need to restart the ople server as there is no command to reopen that connection.
-===== Remote Observing =====
-==== VPN connection is not working ====
-To re-establish the VPN connection, follow these steps:
-  * Open VPN status page from the firefox web broswer. To do this, click on the "AROC VPN reconnect" icon on the zoot desktop. Alternatively, you can open the firefox web browser and go to 192.168.3.1/vpn_sta.htm
-  * The browser will prompt you for the admin user name and password. If these entries are not already filled in, then look for this information on the papers near the console.
-  * If the browser does not open, then check if there are other instances of firefox already running. To do this, open a terminal window, type "ps auxw | grep firefox", and kill the other instances of firefox so that you can open a new window.
-  * When the VPN connection is working, it will report "Phase 1: M-ESTABLISHED / Phase 2: ESTABLISHED" under the state column.
-  * If either Phase 1 or Phase 2 states say IDLE for a given VPN, then you need to re-establish the connection. To do this, click on the "DROP" button for that VPN. Then click on the "CONNECT" button and wait for the Phase 1 and Phase 2 connections to be established.
-  * Make sure to close Firefox by using CTRL-Q to quit the program and not just close the window.
-===== Network Problems =====
-==== User accounts not recognized ====
-The gps computer does the user authentication for the control side while ctrscrut provides the home directories. Yellowpages is gone, the new paradigm is LDAP (local directory access protocol). If you can't log on to computers on the control network, then make sure both ctscrut (michelson) and gps computers are running. If the login screen screen on ctrscrut says "Ubuntu Administrator" and has no user accounts, then check to make sure gps computer is on. If you restart gps, then you might have to reboot ctrscrut to get the user accounts. If ctrscrut was rebooted, you might have to reboot other control network computers if you can't log on.
-If gps computer does not start, check the power distribution unit (PDU) at the top of that rack. If any units show both "+" and "-" then you can use the arrow buttons to move through the units and cycle the units to on "+". That should automatically start the computer connected to those units.
-===== General Problems =====
-==== GUIs are frozen ====
-Check to see if Sockman is working. Click the [LIST] button on sockman. If the list doesn't come up, Sockman may be hung up. Follow the Sockman restart procedure in the text file on the desktop if it won't respond.
-Hit [REOPEN] on the gui to see if it reconnects with its server. if that does not fix it, the server may be dead. From the LIST on Sockman, select the server suspected of being frozen. Ping it and if it reports back as being dead, see [[:chara:trouble_shooting#server_is_frozen|Server is frozen]] section below.
-Telescope guis often freeze. Hit reopen on the gui to bring it back to life. Hitting [MOVE] on the telescope gui before the star has stopped moving can cause the gui to freeze. Avoid doing this. Close the dead one and open a new one to fix the problem.
-==== Server display is blank or filled with jibberish ====
-  * If the top of a server goes blank, try typing "sb" (start background) on the server command line.
-  * If the server screen fills with jibberish, try hitting CTRL-L in the server to clear it.
-  * If a server freezes, sometimes hitting CTRL-C and then N, for NO, will unfreeze it.
-==== Server is frozen ====
-Try quitting the server using CTRL-C and entering "Y". If that doesn't work, try the following:
-  * On Sockman, click [LIST] and select the appropriate server. It will give a PID number you can use to kill the server in a terminal. Open a terminal and follow the directions for Restarting Servers above.
-  * If a server window does not close, click the X in the upper right corner to close it, but only after getting the PID from Sockman.
-  * Click [REOPEN] on Cosmic Debris and relevant GUIs to re-initialize communication with the server after it is restarted.
-  * A folder is on the desktop that has the restart commands for CTRSCRUT servers and the Shutters server restart command running on OPLE. Use it to restart servers that will not reopen from the menu.
-  * if a telescope server does not close after using CTRL-C when restarting them after UT midnight and the Send ON button is green on the obsgtk, turn the Send ON to OFF and the server will close. Turn the Send ON button back on to resume the setup for the night.
-==== PAVO Server - Error communicating with IFW ====
-The following error message sometimes appears when starting the PAVO server: "Error communicating with IFW. Could not read from IFW. Is the filter wheel plugged in and on?" Most of the time, restarting the PAVO server will clear this error message and allow PAVO to communicate with the filter wheel. If restarting the server doesn't help, then check that the cables going into the small, black IFW box on the PAVO table and into the back of the PAVO computer are plugged in securely.
-==== Adding or Finding a Star in the CHARA Database ====
-The command "dbadd" can be used to look up the CHARA number for a star or to add a star to the CHARA database. To use dbadd, open a terminal window, and type "dbadd starname" where starname is the common name (e.g., Vega) or identifier of the star (e.g., IRC, HR, HD, SAO, FK5, HIP, GJ, or 2MASS designation). If the object is in the database, then it will return the CHARA number.
-You can also look up different identifiers for the star by using the SIMBAD database: [[http://simbad.u-strasbg.fr/simbad/sim-fbasic|http://simbad.u-strasbg.fr/simbad/sim-fbasic]]
-DBADD uses SIMBAD to look up the coordinates of the star and then searches to see if the star is already in the CHARA database. If the star is in the database, it will return the CHARA number. If the star is not in the CHARA database, it will ask if you want to add it and assign a CHARA number if you answer yes.
-If an object is not in SIMBAD (such as a recently discovered nova), then you must enter the object manually using the instructions below.
-**Finding a star in the CHARA database**
-Here is an example of how to find the CHARA number of a star, nova, or AGN that is already in the CHARA database:
-[ctrscrut:502] dbadd NGC 4151 \\
-Object "NGC 4151" found as CHARA number: 320263
-Note: If the target information stored in the CHARA database does not match SIMBAD, then dbadd will provide the coordinates and magnitudes listed in SIMBAD, and it will also list the CHARA numbers of objects in the database located within 10 arcsec. Please check these nearby entries before adding a new star to the database.
-**Targets that are not in the CHARA database**
-If an object is not in the CHARA database, then you can use dbadd to query SIMBAD and add the star to the CHARA database. This might need to be done for faint stars, novae, and AGN. If the object is found in SIMBAD, then dbadd will return the target's coordinates, magnitudes, and spectral type and ask if this it the object for which you are looking. If you answer yes, then dbadd will issue a CHARA number and add the object to the database. Please check the target coordinates to make sure that they are correct before adding a new star to the database.
-Here is an example of how to add an object to the CHARA database:
-[ctrscrut:534] dbadd BD 41 3807
-SIMBAD found this for "BD 41 3807":
-ID 2MASS_J20340850 4136592 \\
-CHARA 320414 \\
-.0 \\
-CAT8 2MASS_J20340850 4136592 \\
-RA 20 34 08.5148 \\
-DEC 41 36 59.408 \\
-PMRA -2.32 \\
-PMDEC -3.87 \\
-PAR 0.58 \\
-RVEL -27.50
-VMAG 10.03 \\
-HMAG 6.23 \\
-KMAG 5.99 \\
-SP O5.5Ifc \\
-END
-Is the above the object you are looking for? [y/n] y \\
-Added "BD 41 3807" to the database.
-In the example above, the object "BD 41 3807" has been added to the database as CHARA number 320414.
-**Targets that are not in SIMBAD**
-Some objects like recently discovered novae are not in SIMBAD. Entering dbadd <star designation> for a star not in the SIMBAD database returns the message "Simbad is unable to find an object matching <star designation>. Try using a different catalog designation, or use the "-m" switch to add the object manually."
-The command dbadd -m is used by entering the star name and coordinates in this format:
-Usage: dbadd -m <name> <RA> <Dec> \\  \\
-<name>: Object ID (no spaces) \\  \\
-<RA> : XXhXXmXX.X or XXhXX.X (no spaces) \\  \\
-<Dec> : XXdXXmXX.X or XXdXX.X (no spaces) \\  \\
-There are cases where an object is not in SIMBAD and doesn't return a result in dbadd, but is in fact in the CHARA database. Novae and AGN's are the likely objects that cause this result. At times, objects have multiple entries and several CHARA numbers since the names can be so unique. A system will be developed to find these entries without knowing or having a conventional database designation.
-**Binary stars**
-Some binary stars have a common HD number with an A or B after them. These can cause problems as Cosmic Debris does not accept non numerical entries when filling in star designation. These stars are likely in CHARA's database but need to be searched in dbadd or on SIMBAD to get the CHARA number or another designation.
-When a recognized identifier is entered, the HD number with A or B will usually display. Confirm that the coordinates, magnitudes and spectral type match the star desired. If they do not match, you may have the wrong star or the database may have the wrong info and the baseline solution will be affected. Offsets based on incorrect coordinates or misidentifications can move the fringes many thousands of microns away from the calculated position. This can happen when observing a dim companion (B) using the brighter (A) companion's coordinates. Inform the observers that noting and using the CHARA number will save time next time the target is observed.
-**Editing the database:**  If you find a mistake in the database, please send an email to Nils to have it corrected. Identify what you believe to be the error and what is the correct information.
-==== Adding an anchor to the wiki page ====
-To add an anchor to the wikipage, type the following where you want the anchor inserted (without the spaces between the symbols): \\
-[ [ #AnchorName ] ]
-Highlight the text you want to be a link to the anchor, click the link symbol above and select anchor. Select a page(such as Trouble Shooting) where the anchor is located and give the same name for the anchor.
-==== Displays for the MIRC-X wolverine2 monitors ====
-Follow instructions in the [[:chara:mircx_monitors|linked page to display the MIRC-X wolverine2 monitors]] in the control room.
- \\
-Last updated 2023-06-09 by Norm Vargas

The CHARA Array Wiki

User Tools

Site Tools

Differences

Page Tools