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/07/08 11:50] gail_stargazer [MIRC-X CredoneImAcq Server] |
chara:trouble_shooting [2021/11/04 18:07] charaobs [The Telescope won't move or stopped moving] |
||
---|---|---|---|
Line 8: | Line 8: | ||
This is a list of simple things to check if you can't find fringes: | This is a list of simple things to check if you can't find fringes: | ||
- | * 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. |
* 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. The proper star can also 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. The proper star can also be entered by typing hd #### into the OPLE server and hitting ENTER. | ||
* Are the PoP's correct? After a PoP change, the PoP's are sometimes not updated in CD or ople. | * Are the PoP's correct? After a PoP change, the PoP's are sometimes not updated in CD or ople. | ||
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 after a few seconds to avoid crashing NIRO. 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 after a few seconds to avoid crashing NIRO. 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? | ||
+ | |||
===== Restarting Servers ===== | ===== Restarting Servers ===== | ||
Line 62: | Line 63: | ||
The MIRC-X CredoneImAcq server and GUI can be opened using the " | The MIRC-X CredoneImAcq server and GUI can be opened using the " | ||
- | From a terminal window, log on to mircx (old observe password): | + | From a terminal window, log on to mircx (old observe password): \\ ssh -X spooler@mircx |
- | ssh -X spooler@mircx | + | |
- | Look up credone process:\\ | + | Look up credone process: \\ ps aux | grep credone |
- | ps aux | grep credone | + | |
Kill all credone processes (including the ones for the error messages) using "kill -9 PID" where PID is the process number. Note that credone can't be restarted if there are any error processes in the list. Check "ps aux | grep credone" | Kill all credone processes (including the ones for the error messages) using "kill -9 PID" where PID is the process number. Note that credone can't be restarted if there are any error processes in the list. Check "ps aux | grep credone" | ||
- | 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: |
- | credoneImAcq –no-display | + | |
+ | (the first " | ||
===== Telescopes and Dome Servers ===== | ===== Telescopes and Dome Servers ===== | ||
Line 80: | Line 79: | ||
==== The Telescope won't move or stopped moving ==== | ==== The Telescope won't move or stopped moving ==== | ||
- | \\ Have the powers been turned on to the drives? Are the scopes disabled? The usual state of the telescopes is disabled until enabled. This is due to the stall function of the scopes which eventually disables the scopes when they are stowed. Enable the scopes by hitting [ENABLE] on the dome gui or in the telescope gui control tab. If a scope disables itself during a slew, it may be just an overcautious stall function. Hit ENABLE and the scope should continue to slew. If it disables again without moving, there may be something wrong at the scope, ie. a hatch left open, a ladder not put away, a tool on the floor, or something else physically impeding the motion of the scope. You will need to go to the dome to see what it is. The computer in the dome will give you control of the scope to turn it away from the problem. \\ \\ Sometimes the dome guis get hung up and can cause erratic motion or no motion of the scopes. Check them for current times and continuous updates of numbers. If they are not updating, try to REOPEN them first. If that does not work, close the gui and open a new one. If a new one does not open, the dome server may be dead or Sockman lost track of it. See **Dome Server Restart** | + | \\ |
+ | Have the powers been turned on to the drives? Are the scopes disabled? The usual state of the telescopes is disabled until enabled. This is due to the stall function of the scopes which eventually disables the scopes when they are stowed. Enable the scopes by hitting [ENABLE] on the dome gui or in the telescope gui control tab. If a scope disables itself during a slew, it may be just an overcautious stall function. Hit ENABLE and the scope should continue to slew. If it disables again without moving, there may be something wrong at the scope, ie. a hatch left open, a ladder not put away, a tool on the floor, or something else physically impeding the motion of the scope. You will need to go to the dome to see what it is. The computer in the dome will give you control of the scope to turn it away from the problem.\\ | ||
+ | \\ | ||
+ | Sometimes the dome guis get hung up and can cause erratic motion or no motion of the scopes. Check them for current times and continuous updates of numbers. If they are not updating, try to REOPEN them first. If that does not work, close the gui and open a new one. If a new one does not open, the dome server may be dead or Sockman lost track of it. See **Dome Server Restart** below.\\ | ||
+ | \\ | ||
+ | **Azimuth Limit Switches** \\ | ||
+ | \\ | ||
+ | <font 14px/ | ||
+ | \\ | ||
+ | 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.\\ | ||
+ | \\ | ||
+ | 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</ | ||
+ | |||
+ | <font 16px/ | ||
+ | |||
+ | <font 14px/ | ||
+ | \\ | ||
+ | <font inherit/ | ||
+ | \\ | ||
+ | <font inherit/ | ||
+ | |||
+ | <font 14px/ | ||
+ | |||
+ | <font 14px/ | ||
+ | |||
+ | <font 14px/ | ||
+ | |||
+ | <font 14px/ | ||
==== The Telescope won't track ==== | ==== The Telescope won't track ==== | ||
Line 139: | Line 172: | ||
==== How to Adjust CPUMotor Gains ==== | ==== 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 " | + | \\ The GAIN controls the gain of the feedback between the encoder and the drive velocity. A high gain means a " |
- | ====== Dome issues ====== | + | ==== E2 AOB Dichroic Recovery |
- | \\ At times the domes do not rotate, open or close, or otherwise behave. Some problems are simple and others are more complex. | + | {{: |
+ | |||
+ | ==== E1 Hut and Cooler Communications Recovery ==== | ||
+ | |||
+ | {{: | ||
+ | \\ | ||
+ | <font 16px/ | ||
+ | |||
+ | S2's acquisition server resides on " | ||
+ | |||
+ | ====== 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 ==== | ==== 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' | + | \\ |
+ | 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. | ||
==== Dome does not open ==== | ==== Dome does not 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__ | + | \\ |
+ | 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__ | ||
==== Dome does not close ==== | ==== 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. | + | \\ |
+ | 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 ====== | ||
Line 161: | Line 212: | ||
==== I can't change the camera settings on the TV ==== | ==== I can't change the camera settings on the TV ==== | ||
- | \\ 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 may be the cause if it has quit. To see if it is the server, open the HUT gui for the desired telescope from the CHARA menu. If the camera settings are displayed and the settings can be changed from the gui, then the HUT server is ok. Restart the telescope server to reopen the connection to the HUT server and hit reopen on Cosmic Debris as well. If the gui is not functioning, | + | \\ |
+ | 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 may be the cause if it has quit. To see if it is the server, open the HUT gui for the desired telescope from the CHARA menu. If the camera settings are displayed and the settings can be changed from the gui, then the HUT server is ok. Restart the telescope server to reopen the connection to the HUT server and hit reopen on Cosmic Debris as well. If the gui is not functioning, | ||
===== Tiptilt Server ===== | ===== Tiptilt Server ===== | ||
- | \\ The tiptilt server controls the CCD based tiptilt detection system. \\ \\ Before you start the tiptilt server, you must ensure that the power to the cooling system and the CCD iteslf is on. It is extremely important that the cooler be running before you turn on the CCD and is only turned off if you are sure the CCD is NOT running. You can start the server from the X windows menu or with the command xtiptilt. \\ \\ Note that there are background counts and read noise to deal with. Whenever you change the frame rate, please ensure that the bias frame is OK. The server will attempt to load an old bias frame that should work, but if things are not working, try making a new bias frame by ensuring that the detector is in the dark and typing " | + | \\ |
+ | The tiptilt server controls the CCD based tiptilt detection system. \\ \\ | ||
+ | Before you start the tiptilt server, you must ensure that the power to the cooling system and the CCD iteslf is on. It is extremely important that the cooler be running before you turn on the CCD and is only turned off if you are sure the CCD is NOT running. You can start the server from the X windows menu or with the command xtiptilt. \\ \\ | ||
+ | Note that there are background counts and read noise to deal with. Whenever you change the frame rate, please ensure that the bias frame is OK. The server will attempt to load an old bias frame that should work, but if things are not working, try making a new bias frame by ensuring that the detector is in the dark and typing " | ||
+ | In the tiptilt GUI windows, the white dots represent the starlight while the green dots represent the motion applied to telescope' | ||
==== Tiptilt server complains about the CCD ==== | ==== Tiptilt server complains about the CCD ==== | ||
- | \\ Is the CCD turned on? When the tiptilt server starts up it tries no more than five times to communicate with the CCD. If they all fail, it will give up. If this happens, try cycling the power to the CCD and try again. If this fails, connect to the tiptilt machine and type the command rtccdAPIDemo, | + | \\ |
+ | Is the CCD turned on? When the tiptilt server starts up it tries no more than five times to communicate with the CCD. If they all fail, it will give up. If this happens, try cycling the power to the CCD and try again. If this fails, connect to the tiptilt machine and type the command rtccdAPIDemo, | ||
+ | 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 " | ||
+ | Also note that cycling the power on the CCD can cause harm so be sure you need to do it before trying it. Also, it is important to wait for at least 20 seconds after turning off the power before turning it on again. | ||
==== Tiptilt doesn' | ==== Tiptilt doesn' | ||
- | \\ 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. | + | \\ |
+ | 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 server says the clock isn't running ==== | ==== Tiptilt server says the clock isn't running ==== | ||
- | \\ 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 \\ / | + | \\ |
+ | 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 ==== | ==== Tiptilt is not locking on a star or locks, but lets the star drift away ==== | ||
Line 250: | Line 320: | ||
==== 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 \\ \\ | ||
+ | 5. Restart the beam sampler servers (this starts both beam sampler servers BS1 and BS2): \\ \\ | ||
+ | bootlaunch_beamsamp | ||
==== " | ==== " | ||
- | \\ Cosmic Debris reports " | + | \\ |
+ | Cosmic Debris reports " | ||
+ | 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 ===== | ===== Remote Observing ===== | ||
Line 273: | Line 361: | ||
==== 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. | 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. | ||
Line 292: | Line 381: | ||
==== 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 ==== | ||
Line 298: | Line 389: | ||
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:// |
- | \\ | + | |
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. | 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. | ||
Line 308: | Line 398: | ||
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. | ||
- | \\ __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' | + | \\ __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' | ||
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: |
+ | SIMBAD found this for "BD+41 3807": | ||
- | 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 | + | 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. | + | 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. | ||
- | \\ __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 SIMBAD__ \\ \\ |
+ | Some objects like recently discovered novae are not in SIMBAD. Entering dbadd <star designation> | ||
+ | The command dbadd -m is used by entering the star name and coordinates in this format: \\ \\ | ||
+ | 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' | ||
+ | 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' | ||
- | When a recognized identifier is entered, the HD number with A or B will usually display. Confirm that the coordinates, | + | When a recognized identifier is entered, the HD number with A or B will usually display. Confirm that the coordinates, |
+ | 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 ==== | ==== 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 336: | Line 455: | ||
Follow instructions in the [[: | Follow instructions in the [[: | ||
- | \\ Last updated 2017-04-12 | + | \\ |
+ | Last updated 2017-04-12 | ||