chara:trouble_shooting
Differences
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 [2019/05/24 19:31] gail_stargazer |
chara:trouble_shooting [2020/01/28 03:02] charaobs |
||
|---|---|---|---|
| Line 9: | Line 9: | ||
| * Were the clocks synced? Make sure the [SYNC CLOCKS] button on Cosmic Debris has been pushed to start the night. If the OPLE server does not display the correct CHARA time and the errors don't read (0) or (1), the clocks were not synced. As the VME runs on its own clock and does not use the NTP server, it can drift over the course of the night and cause problems with finding fringes, even if it was synced at the start of the night. Syncing the clocks multiple time during the night may help to avoid this hidden clock problem. | * Were the clocks synced? Make sure the [SYNC CLOCKS] button on Cosmic Debris has been pushed to start the night. If the OPLE server does not display the correct CHARA time and the errors don't read (0) or (1), the clocks were not synced. As the VME runs on its own clock and does not use the NTP server, it can drift over the course of the night and cause problems with finding fringes, even if it was synced at the start of the night. Syncing the clocks multiple time during the night may help to avoid this hidden clock problem. | ||
| - | * Did the Astrolib update on OPLE? If the job queue is stopped too soon after slewing on Cosmic Debris, the correct calculations for the carts will not be done by OPLE and you may be searching for fringes with the wrong star data. The proper star can be entered by typing hd …. into the OPLE server and hitting ENTER. | + | * Did the Astrolib update on OPLE? If the job queue is stopped too soon after slewing on Cosmic Debris, the correct calculations for the carts will not be done by OPLE and you may be searching for fringes with the wrong star data. Hit STAR ACQUIRED on CD to update ople. |
| + | * Are the PoP's correct? | ||
| + | * Are the carts behaving or are there vibrations or jumps of 100 or more microns every 3-6 seconds? | ||
| * Is the target a high proper motion star? Red dwarfs are close stars and can have high proper motions. Scan a wider range to see if it is outside of the usual calculated scan range. Binaries can also have very high offsets from the expected position due to mistakenly using astromod calculations from the companion star. | * Is the target a high proper motion star? Red dwarfs are close stars and can have high proper motions. Scan a wider range to see if it is outside of the usual calculated scan range. Binaries can also have very high offsets from the expected position due to mistakenly using astromod calculations from the companion star. | ||
| + | * Do you have enough flux from each telescope or on each baseline? | ||
| * Did you get the same star in each telescope? Sometimes a busy star field and poor pointing of the telescopes can lead to the wrong star being acquired and locked by tiptilt. View the stars in the finder window to see if all the stars match. | * Did you get the same star in each telescope? Sometimes a busy star field and poor pointing of the telescopes can lead to the wrong star being acquired and locked by tiptilt. View the stars in the finder window to see if all the stars match. | ||
| * Check the CHARA time on the GPS server. The " | * Check the CHARA time on the GPS server. The " | ||
| Line 28: | Line 31: | ||
| ==== Restarting Servers using the bootlaunch paradigm ==== | ==== Restarting Servers using 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 ([[: | + | 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 ([[: |
| - | \\ | + | |
| - | A number of servers use an interim bootlaunch paradigm to restart. This is confined to servers that run on ubuntu machines, namely the telescope bunker computers and gps. The basic syntax is " | + | To restart a server, log on to the machine that runs the server and type " |
| - | \\ | + | |
| - | One thing of note about the output of the bootlaunch scripts, they call a number of other programs which themselves have output that may be misleading in the context of bootlaunch. Chief among these is the output of " | + | |
| - | \\ | + | |
| - | Here are the available bootlaunch scripts as of June 2017: \\ | + | |
| - | \\ | + | |
| - | gps computer: | + | |
| * bootlaunch_beamsamp – Starts the beam sampler servers, BS1 and BS2. | * bootlaunch_beamsamp – Starts the beam sampler servers, BS1 and BS2. | ||
chara/trouble_shooting.txt · Last modified: 2023/11/21 01:42 by charaobs
Page Tools
Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Share Alike 4.0 International
