This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
chara:trouble_shooting [2021/11/09 14:06] gail_stargazer |
chara:trouble_shooting [2022/01/21 19:07] charaobs |
||
---|---|---|---|
Line 26: | Line 26: | ||
* 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? | * 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? | ||
+ | |||
+ | ===== The new OPLE system ===== | ||
+ | |||
+ | With the implementation of the new ople system which replaced the VME in Fall of 2021, new troubleshooting issues have arisen. | ||
+ | |||
+ | The traditional ople server will still be used to communicate with each new ople computer, identified as OPLE 1 to OPLE 6. When the communications are good, each active cart will be displayed in the ople server or ople gui status tab as before. | ||
+ | |||
+ | If a cart cannot be started, stopped or otherwise commanded, look to the OPLESystem gui to see if a green indicator has turned red. A message will also often pop up on the ople gui saying the command could not be sent. This may require a simple start command to restart the server or a reboot of the computer to get it back to yellow and then a start to get it back to green. | ||
+ | |||
+ | Some times a cart is stopped and cannot be commanded. | ||
===== Restarting Servers ===== | ===== Restarting Servers ===== | ||
Line 38: | Line 48: | ||
* bootlaunch_zaber – Starts the ZABER_2 server. | * bootlaunch_zaber – Starts the ZABER_2 server. | ||
- | \\ telescope bunker computers: | + | \\ telescope bunker computers |
* bootlaunch_hut – Starts the E1_HUT, E2_HUT, S1_HUT, S2_HUT, W1_HUT, or W2_HUT server, depending on the machine it's launched from. | * bootlaunch_hut – Starts the E1_HUT, E2_HUT, S1_HUT, S2_HUT, W1_HUT, or W2_HUT server, depending on the machine it's launched from. | ||
Line 50: | Line 60: | ||
==== Restarting Servers using the rc.local file ==== | ==== Restarting Servers using the rc.local file ==== | ||
- | \\ This procedure is applicable to servers that have not switched over to the bootlaunch paradigm. \\ \\ If a server is not running or Socket Manager reports that a server is dead, then look at the socket manager list to find out what computer the server runs on ([[: | + | \\ This procedure is applicable to servers that have not switched over to the bootlaunch paradigm, which may not be any at this point. \\ \\ If a server is not running or Socket Manager reports that a server is dead, then look at the socket manager list to find out what computer the server runs on ([[: |
\\ | \\ | ||
Log on to the relevant computer by typing the computer name (ctrscrut, ople, s1, …). If the shortcut doesn' | Log on to the relevant computer by typing the computer name (ctrscrut, ople, s1, …). If the shortcut doesn' | ||
Line 69: | Line 79: | ||
Then restart credone using the desktop icon or by issuing the following command on spooler@mircx: | Then restart credone using the desktop icon or by issuing the following command on spooler@mircx: | ||
+ | |||
+ | (the first " | ||
===== Telescopes and Dome Servers ===== | ===== Telescopes and Dome Servers ===== | ||
Line 82: | Line 94: | ||
1. On the domegui MANUAL tab, click STOP so pulses won't be sent to the drive by the control software. \\ | 1. On the domegui MANUAL tab, click STOP so pulses won't be sent to the drive by the control software. \\ | ||
\\ | \\ | ||
- | 2. Make sure you understand why the limit was hit which may require a trip to the telescope. If the azimuth positions on all telescope servers and dome guis match, it is likely the limit switch causing the stall and not that the scope is actually in a wrong position. \\ | + | 2. Make sure you understand why the limit was hit which may require a trip to the telescope. If the azimuth positions on all telescope servers and dome guis match, it is likely the limit switch causing the stall and not that the scope is actually in a wrong position.</ |
- | \\ | + | 4. Click ENABLE then you can move the telescope back to its normal range of operation. \\ \\ |
- | 3. Click the OVERRIDE ON button in domegui MANUAL tab. After this, the hardware doesn' | + | |
- | \\ | + | |
- | 4. Click ENABLE then you can move the telescope back to its normal range of operation. \\ | + | |
- | \\ | + | |
5. After the telescope is back in it normal range, click OVERRIDE OFF which makes the hardware aware of the limits again and then hit AUTO on the AUTO tab to resume normal operation <font 16px/ | 5. After the telescope is back in it normal range, click OVERRIDE OFF which makes the hardware aware of the limits again and then hit AUTO on the AUTO tab to resume normal operation <font 16px/ | ||
- | <font 14px/ | + | <font 14px/ |
+ | 2.</ | ||
<font 14px/ | <font 14px/ | ||
Line 98: | Line 107: | ||
<font 14px/ | <font 14px/ | ||
- | <font 14px/ | + | <font 14px/ |
==== The Telescope won't track ==== | ==== The Telescope won't track ==== | ||
Line 110: | Line 119: | ||
==== Dome Server Restart ==== | ==== Dome Server Restart ==== | ||
- | To manually start the dome server: 1. Make sure the power to the drives is OFF. 2. Login to the relevant computer as root. For example, type " | + | Dome servers are now started using the bootlaunch_master command. Kill the server by finding |
- | ==== Telescope clock is not correct ==== | + | To manually start the dome server: |
- | The NTP server has obsoleted this problem | + | 1. Make sure the power to the drives is OFF. |
+ | |||
+ | 2. Login to the relevant computer as root. For example, type " | ||
+ | |||
+ | 3. Work out the process ID number (PID), either with the command | ||
+ | |||
+ | (s1:1001) tsockman get dome_S1 \\ | ||
+ | Name : dome_S1 \\ | ||
+ | Machine : s1.chara-array.org \\ | ||
+ | PID : 29953 \\ | ||
+ | Commands : -1 \\ | ||
+ | Data : -1 \\ | ||
+ | Message : 4002 \\ | ||
+ | Restart : / | ||
+ | or with \\ | ||
+ | (s1:1003) ps aux | grep dome \\ | ||
+ | theo 4473 0.0 0.0 61188 748 pts/3 S+ 10:45 0:00 grep dome \\ | ||
+ | observe 29953 18.5 0.4 35596 9860 ? Sl Apr21 416:11 / | ||
+ | It can also be found by pulling up the LIST on SOCKMAN and selecting the relevant dome. \\ \\ | ||
+ | So in this case the PID is 29953. \\ \\ | ||
+ | 4. Try and stop the server gracefully: kill -2 29953 | ||
+ | |||
+ | 5. You should then check that the server has indeed stopped: \\ \\ | ||
+ | [s1:600] tsockman get dome_S1 \\ | ||
+ | Name : dome_S1 \\ | ||
+ | Machine : s1.chara-array.org \\ | ||
+ | PID : 15635 \\ | ||
+ | Commands : -1 \\ | ||
+ | Data : -1 \\ | ||
+ | Message : 2008 \\ | ||
+ | Restart : / | ||
+ | If the socket manager still thinks it's running you will need to stop it forcefully: kill -9 29953; tsockman rm dome_S1 | ||
+ | |||
+ | 6. Restart the dome server by copying the command at the end of the / | ||
+ | |||
+ | [s1:602] more / | ||
+ | <<< | ||
+ | #Run the dome server \\ \\ | ||
+ | / | ||
+ | / | ||
+ | (Note: the part of the command that saves information to / | ||
+ | |||
+ | 7. Turn the power to the drives back on. | ||
+ | |||
+ | 8. Hit REOPEN | ||
+ | |||
+ | You may have to reinitialize the scope on a bright star. If the powers were turned off quickly when the problem was noticed, the position | ||
==== Telescope is not receiving the commanded position for a target ==== | ==== Telescope is not receiving the commanded position for a target ==== | ||
Line 136: | Line 191: | ||
==== Telescope is tracking poorly, overshooting in slew, oscillating. ==== | ==== 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. 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. On 10-22-2016, the gain settings were: | Scope | AZ Slewing || EL Slewing || AZ Tracking || EL Tracking || Date Updated | | + | 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. |
- | | |Gain|Fn|Gain|Fn|Gain|Fn|Gain|Fn| | | + | 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. |
- | |S1|7|4|4|3|16|4|10|7|10-26-2017| | + | |
- | |S2|7| |7| |10| |10| |10-22-2016| | + | |
- | |E1|7| |7| |13| |10| |10-22-2016| | + | |
- | |E2|7| |7| |13| |10| |10-22-2016| | + | |
- | |W1|13| |10| |13| |10| |10-22-2016| | + | |
- | |W2|7| |7| |13| |13| |10-22-2016| | + | |
- | \\ | + | 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. |
- | Note that these values may change as the temperatures change rapidly. | + | |
==== How to Adjust CPUMotor Gains ==== | ==== How to Adjust CPUMotor Gains ==== | ||
Line 177: | Line 225: | ||
==== E1 Hut and Cooler Communications Recovery ==== | ==== E1 Hut and Cooler Communications Recovery ==== | ||
- | {{: | + | {{: |
+ | |||
+ | ==== S2 Acquisition Server Restart | ||
S2's acquisition server resides on " | S2's acquisition server resides on " | ||
- | ====== Dome issue ====== | + | ===== Dome issue ===== |
At times the domes do not rotate, open or close, or otherwise behave. Some problems are simple and others are more complex. | At times the domes do not rotate, open or close, or otherwise behave. Some problems are simple and others are more complex. | ||
Line 188: | Line 238: | ||
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' | 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' | ||
- | 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. | + | 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 ==== | ==== 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. \\ | + | 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__ | 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__ | ||
Line 199: | Line 250: | ||
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. | 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 | + | ===== 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. | + | ==== I can't change |
- | ===== Tiptilt Server. (These sections apply to the old lab tiptilt system retired in April 2021) ===== | + | **CHECK THIS SECTION - THESE ARE VERY CLOSE BUT DIFFERENT PARAGRAPHS: |
- | The tiptilt | + | 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 |
- | Before you start the tiptilt | + | |
- | Note that there are background counts | + | |
- | In the tiptilt GUI windows, | + | |
- | ==== Tiptilt | + | The HUT servers control functions such as finder and acq exposure times and gains, heater and dehumidifier usage, and various AO functions. An observer may find that the camera settings do not display or are not adjustable. The HUT server |
- | Is the CCD turned on? When the tiptilt | + | If the server |
- | Note that it is never a good idea to reboot machines unless you are very very sure it is necessary. The only reason to reboot tiptilt, other than a lock up of some kind, is that the clock interrupt has failed. You can test this by running | + | |
- | Also note that cycling | + | |
- | ==== Tiptilt doesn' | + | ===== Tiptilt Server. (These sections apply to the old lab tiptilt |
- | + | ||
- | Sometimes the telescope server will not show that TT is running. It will show 0Hz for a signal rate for TT. Running TIPTILT COMM will not get it started while other scopes do show it starting. Close and restart any telescope servers that won't connect after two tries of TIPTILT COMM. \\ | + | |
- | Note: There is more info in the software manual on this topic, but I wasn't sure if it was still relevant. | + | |
- | + | ||
- | ==== Tiptilt | + | |
- | + | ||
- | First check whether the clock itself is running and the other machines receive the clock signal. Look at the clock cards at the back of other computers in the rack. The clock cards have three LEDs, one yellow and two greens. If the computer is receiving the clock signal properly all three LEDs should blink, but at a different rate. If the LEDs on all the clock cards are solid then reboot the GPS computer. When the GPS computer is down, it is best to cycle the power also on the box right above the GPS computer. \\ \\ | + | |
- | If the clock appears to be working properly on other machines and not on the tiptilt now it is time to reboot tiptilt. \\ \\ | + | |
- | [There is a bug in the real time part of the CCD code. It is caused by the clock in the tiptilt system either not running at all or having been set to a time very different from the last time the CCD ran.] \\ \\ | + | |
- | For the time being the only solution is to reboot tiptilt, but do so from the lab. Power OFF the CCD, then reboot the tiptilt machine and go into the BIOS. Make sure that interrupt 11 has been set to ISA legacy, save the BIOS and reboot. When the clock card LEDs in the tiptilt machine indicate proper clock signal, turn the CCD back on and start the tiptilt server. \\ \\ | + | |
- | Also, sometimes Serial Port 3 grabs IRQ 11 which stops the clock from running. Since there is no serial port 2 it's safe to disable this in the BIOS. This problem normally comes up when there has been a power outage. \\ \\ | + | |
- | Sometimes syncing the clock can also cause this problem, but that should be fixed soon. If it does, exit the tiptilt server, log in as root, and reload the tiptilt model using the following commands: \\ | + | |
- | /sbin/rmmod tiptilt_rt \\ | + | |
- | / | + | |
- | Note that it is never a good idea to reboot machines unless you are very very sure it is necessary. The only reason to reboot tiptilt, other than a lock up of some kind, is that the clock interrupt has failed. You can test this by running the command " | + | |
- | + | ||
- | ==== Tiptilt is not locking on a star or locks, but lets the star drift away ==== | + | |
- | + | ||
- | * Are all the mirror covers open? [Note: W1 M7 cover sometimes needs two clicks to open, despite Scope-monitor indicates open.] | + | |
- | * Has TIPTILT COMM been run from Cosmic Debris? | + | |
- | * Check the ACQ alignment to make sure the tick marks are centered on the laser. | + | |
- | * If there is plenty of starlight getting into tiptilt, then try re-initializing by clicking [TIPTILT COMM] on Cosmic Debris. | + | |
- | * If there are a large number of background counts on TT, then close the M5 cover on the telescope, and click [DBIAS] on the TIPLTILT GUI to clear the background counts. Re-open the M5 cover. | + | |
- | * If a star drifts even with TT locked, there could be a bright sky or light from other beams getting into the affected telescope' | + | |
- | * If TT unlocks and the star drifts, the TT servo may not have engaged. This is engaged with the TIPTILT button on the telescope gui. Clicking it may not start the servo the first time. Try it again if the green dots drift on the TT plot windows or if the Servo status in the telescope gui reads None instead of Wobb 1. | + | |
- | * Are the TIPTILT buttons turned on from the POWER GUI? | + | |
- | + | ||
- | ==== Tiptilt servo oscillates ==== | + | |
- | + | ||
- | You will see the oscillation in the green dots of the tiptilt GUI windows. Sometimes you can also see the oscillation in the white starlight dots or as an elongation of the star when looking at the ACQ field while tiptilt is locked. Some scopes have an oscillation that has not yet been diagnosed. W2 is one that usually oscillates. A diagonal motion in the tiptilt box indicates an oscillation in one axis only, while a vertical/ | + | |
- | + | ||
- | * Type " | + | |
- | * Type " | + | |
- | * Read section on adjusting the Telescope Tracking Gain using the Dome Server | + | |
- | + | ||
- | ==== Tiptilt is saturating ==== | + | |
- | + | ||
- | * Tiptilt saturates at ~ 200,000 counts. If you are near this limit, you can reduce the TT exposure time to lower the number of counts. | + | |
- | * Set the TT exposure time on Cosmic Debris in the box for " | + | |
- | * To change the exposure when already at a target, then click the [EXP] button on the TipTilt GUI. This will bring up a dialog box where you can enter the new exposure time in msec. Check to make sure the tiptilt | + | |
- | * Frame rates for given exposure times: | + | |
- | * ExpTime | + | |
- | * ExpTime = 2 msec, Frame Rate = 299 Hz | + | |
- | * ExpTime = 1 msec, Frame Rate = 427 Hz | + | |
- | + | ||
- | ==== Tiptilt counts are way too low ==== | + | |
- | + | ||
- | Try using a slower frame rate or increasing the NSUM. Also ensure that the acquistion is properly aligned with the laser. To change the frame rate, click the [EXP] button on the tiptilt GUI and enter a longer integration time. Remember to change " | + | |
- | + | ||
- | ==== Tiptilt counts are negative | + | |
- | The bias frame is bad. Get a new one or turn it off. | + | [[: |
===== OPLE and Metrology ===== | ===== OPLE and Metrology ===== | ||
Line 287: | Line 283: | ||
* 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. | ||
- | * 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 homed to 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. | + | * 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. |
===== Beam Samplers ===== | ===== Beam Samplers ===== | ||
Line 304: | Line 300: | ||
==== Restarting the Beam Sampler Server ==== | ==== 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. 1. Make sure you are logged into the right machine: ssh ctrscrut 2. If you are not sure see if the socket manager will tell you. If it doesn' | + | 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. |
+ | |||
+ | 1. Make sure you are logged into the right machine: ssh ctrscrut | ||
+ | |||
+ | 2. If you are not sure see if the socket manager will tell you. If it doesn' | ||
+ | |||
+ | 3. 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. | ||
+ | |||
+ | 4. Stop those processes: | ||
+ | |||
+ | kill -9 PID1 PID2 …. | ||
+ | |||
+ | 5. Make sure there is no sign of it in the socket manager | ||
+ | |||
+ | tsockman rm BS | ||
+ | |||
+ | 6. Restart the beam sampler servers (this starts both beam sampler servers BS1 and BS2): | ||
+ | |||
+ | bootlaunch_beamsamp | ||
==== " | ==== " | ||
Line 329: | Line 351: | ||
==== GUIs are frozen ==== | ==== GUIs are frozen ==== | ||
- | Check to see if Sockman is working. Click the [LIST] button on sockman. If the list doesn' | + | Check to see if Sockman is working. Click the [LIST] button on sockman. If the list doesn' |
+ | |||
+ | 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 [[: | ||
+ | |||
+ | 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 ==== | ==== Server display is blank or filled with jibberish ==== | ||
Line 359: | Line 385: | ||
If an object is not in SIMBAD (such as a recently discovered nova), then you must enter the object manually using the instructions below. | 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 | + | **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: | 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: | + | [ctrscrut: |
+ | 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. | 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. | ||
Line 373: | Line 400: | ||
Here is an example of how to add an object to the CHARA database: | Here is an example of how to add an object to the CHARA database: | ||
- | [ctrscrut: | + | [ctrscrut: |
- | ID 2MASS_J20340850 4136592 CHARA 320414 2000.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 | + | SIMBAD found this for " |
- | Is the above the object you are looking for? [y/n] y Added "BD 41 3807" to the database. | + | ID 2MASS_J20340850 4136592 \\ |
+ | CHARA 320414 \\ | ||
+ | 2000.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. | In the example above, the object "BD 41 3807" has been added to the database as CHARA number 320414. | ||
Line 383: | Line 428: | ||
**Targets that are not in SIMBAD** | **Targets that are not in SIMBAD** | ||
- | Some objects like recently discovered novae are not in SIMBAD. Entering dbadd <star designation> | + | Some objects like recently discovered novae are not in SIMBAD. Entering dbadd <star designation> |
- | Usage: | + | The command |
- | + | ||
- | Object ID (no spaces) <RA> : XXhXXmXX.X or XXhXX.X (no spaces) < | + | |
+ | Usage: dbadd -m < | ||
+ | < | ||
+ | <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' | There are cases where an object is not in SIMBAD and doesn' | ||
Line 401: | Line 448: | ||
==== Adding an anchor to the wiki page ==== | ==== 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. | + | 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 ==== | ==== Displays for the MIRC-X wolverine2 monitors ==== | ||
Line 408: | Line 458: | ||
\\ | \\ | ||
- | Last updated | + | Last updated |