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 15:20] gail_stargazer |
chara:trouble_shooting [2018/09/25 16:08] gail_stargazer |
||
---|---|---|---|
Line 2: | Line 2: | ||
\\ | \\ | ||
- | This document describes how to solve common problems that sometimes arise at the array.\\ | + | This document describes how to solve common problems that sometimes arise at the array. |
- | \\ | + | |
===== Can't find fringes ===== | ===== Can't find fringes ===== | ||
Line 28: | Line 28: | ||
==== 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 " | + | \\ 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 " |
* bootlaunch_beamsamp – Starts the beam sampler servers, BS1 and BS2. | * bootlaunch_beamsamp – Starts the beam sampler servers, BS1 and BS2. | ||
* 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 41: | Line 41: | ||
* bootlaunch_upper – Starts the E1_Upper, E2_Upper, S1_Upper, S2_Upper, W1_Upper, or W2_Upper server, depending on the machine it's launched from. | * bootlaunch_upper – Starts the E1_Upper, E2_Upper, S1_Upper, S2_Upper, W1_Upper, or W2_Upper server, depending on the machine it's launched from. | ||
- | \\ Note: The bootlaunch scripts will not start a new server if there is an existing process running. Therefore, type "ps aux | grep // | + | \\ Note: The bootlaunch scripts will not start a new server if there is an existing process running. Therefore, type "ps aux | grep // |
==== Restarting Servers using the rc.local file ==== | ==== Restarting Servers using the rc.local file ==== | ||
Line 47: | Line 47: | ||
\\ 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' |
==== Shutters Server ==== | ==== Shutters Server ==== | ||
Line 55: | Line 55: | ||
===== Telescopes and Dome Servers ===== | ===== Telescopes and Dome Servers ===== | ||
- | \\ Here we discuss things that can go wrong with the telescopes. | + | \\ Here we discuss things that can go wrong with the telescopes. |
==== 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** |
==== The Telescope won't track ==== | ==== The Telescope won't track ==== | ||
- | \\ If a bright star is manually found and not slewed to by number, (usually after the scope has gotten lost), the telescope will not track as it does not know it has gone to a star. When you init the EL and AZ position of the scope to the star's position, you must enable the tracking by going to the dome gui, selecting the RA/DEC tab and hitting the [GO RA/DEC] button. The scope will track, but the pointing model may still be off. Try slewing to the same star and initing on it after it is locked in Tiptilt. This can be done in the dome with the computer at the telescope. | + | \\ If a bright star is manually found and not slewed to by number, (usually after the scope has gotten lost), the telescope will not track as it does not know it has gone to a star. When you init the EL and AZ position of the scope to the star's position, you must enable the tracking by going to the dome gui, selecting the RA/DEC tab and hitting the [GO RA/DEC] button. The scope will track, but the pointing model may still be off. Try slewing to the same star and initing on it after it is locked in Tiptilt. This can be done in the dome with the computer at the telescope. |
==== The Telescope won't stop moving or moves beyond the commanded position ==== | ==== The Telescope won't stop moving or moves beyond the commanded position ==== | ||
- | \\ Disable the scope whenever its motion is outside of what it is supposed to do. Turn the powers off to the axes as well on the Power gui. The dome server is usually to blame and will need to be restarted. | + | \\ Disable the scope whenever its motion is outside of what it is supposed to do. Turn the powers off to the axes as well on the Power gui. The dome server is usually to blame and will need to be restarted. |
==== 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 " | + | \\ 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 " |
==== Telescope clock is not correct ==== | ==== Telescope clock is not correct ==== | ||
- | \\ The NTP server has obsoleted this problem and fix as of 2014. \\ | + | \\ The NTP server has obsoleted this problem and fix as of 2014. |
==== Telescope is not receiving the commanded position for a target ==== | ==== Telescope is not receiving the commanded position for a target ==== | ||
Line 95: | Line 95: | ||
* Restart commands for the dome servers are also listed on the desktop in a text file. | * Restart commands for the dome servers are also listed on the desktop in a text file. | ||
- | \\ | + | < |
- | + | \ | |
- | ==== 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 | ||
+ | </ | ||
| |Gain|Fn|Gain|Fn|Gain|Fn|Gain|Fn| | | | |Gain|Fn|Gain|Fn|Gain|Fn|Gain|Fn| | | ||
Line 109: | Line 112: | ||
|W2|7| |7| |13| |13| |10-22-2016| | |W2|7| |7| |13| |13| |10-22-2016| | ||
- | \\ Note that these values may change as the temperatures change rapidly. These are still being adjusted so this is by no means final. Be sure to set mode back to AUTO if changing the gains left it in Slewing or Tracking mode. \\ | + | \\ Note that these values may change as the temperatures change rapidly. These are still being adjusted so this is by no means final. Be sure to set mode back to AUTO if changing the gains left it in Slewing or Tracking mode. |
==== How to Adjust CPUMotor Gains ==== | ==== How to Adjust CPUMotor Gains ==== | ||
Line 117: | Line 120: | ||
====== Dome issues ====== | ====== Dome issues ====== | ||
- | \\ 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. |
==== 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' |
==== 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 135: | Line 138: | ||
==== 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 " |
==== 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, |
==== 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 \\ / |
==== 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 185: | Line 187: | ||
==== Tiptilt counts are way too low ==== | ==== 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 " | + | 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 ==== | ==== Tiptilt counts are negative ==== | ||
Line 225: | Line 227: | ||
==== 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' |
==== " | ==== " | ||
Line 249: | Line 251: | ||
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' | ||
- | 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. |
==== Server display is blank or filled with jibberish ==== | ==== Server display is blank or filled with jibberish ==== | ||
Line 267: | Line 269: | ||
==== 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 ==== | ||
- | DBADD is a 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:// | ||
\\ | \\ | ||
- | SIMBAD will show many identifiers for the star, and often will show one of the database identifiers that Cosmic Debris recognizes. | + | 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 | + | If an object is not in SIMBAD (such as a recently discovered nova), then you must enter the object manually |
\\ __Finding a star in the CHARA database__ | \\ __Finding a star in the CHARA database__ | ||
Line 285: | Line 287: | ||
[ctrscrut: | [ctrscrut: | ||
- | 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. | + | 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' | ||
+ | |||
+ | Here is an example of how to add an object to the CHARA database: | ||
+ | |||
+ | [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 | ||
+ | |||
+ | Is the above the object you are looking for? [y/n] y \\ Added "BD+41 3807" | ||
- | \\ __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. If the object is found in SIMBAD, then dbadd will return the target' | + | In the example above, the object "BD+41 3807" has been added to the database |
- | If a star, nova, or AGN is not in the CHARA database, dbadd will query the SIMBAD database to see if it can be found there. If it returns a result, the target' | + | \\ __Targets that are not in the CHARA database or in SIMBAD__ \\ \\ Some objects like recently discovered |
==== Adding an anchor to the wiki page ==== | ==== Adding an anchor to the wiki page ==== |