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 [2018/09/25 16:04] 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 ==== | ||
- | \\ 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 " | + | 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 ([[: |
+ | |||
+ | To restart a server, log on to the machine that runs the server and type " | ||
* bootlaunch_beamsamp – Starts the beam sampler servers, BS1 and BS2. | * bootlaunch_beamsamp – Starts the beam sampler servers, BS1 and BS2. | ||
Line 45: | Line 50: | ||
==== 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. \\ \\ 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 269: | Line 274: | ||
==== PAVO Server - Error communicating with IFW ==== | ==== 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' | + | 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' |
==== Adding or Finding a Star in the CHARA Database ==== | ==== Adding or Finding a Star in the CHARA Database ==== | ||
- | The command " | + | The command " |
You can also look up different identifiers for the star by using the SIMBAD database: [[http:// | You can also look up different identifiers for the star by using the SIMBAD database: [[http:// | ||
Line 299: | Line 304: | ||
Is the above the object you are looking for? [y/n] y \\ Added "BD+41 3807" to the database. | Is the above the object you are looking for? [y/n] y \\ Added "BD+41 3807" to the database. | ||
- | 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. |
+ | |||
+ | \\ __Targets that are not in SIMBAD__ \\ \\ Some objects like recently discovered novae are not in SIMBAD. Entering dbadd <star designation> | ||
- | \\ __Targets that are not in the CHARA database or in SIMBAD__ \\ \\ Some objects like recently discovered novae are not in SIMBAD. Entering dbadd <star designation> | + | When a recognized identifier is entered, the HD number with A or B will usually display. Confirm that the coordinates, |
==== Adding an anchor to the wiki page ==== | ==== Adding an anchor to the wiki page ==== |