Difference between revisions of "Startup"
(Created page with 'All the telescopes run a server that handles communication with the mounting, telescope components, camera, guider, and dome. Starting the observatory from a total shutdown woul…') |
|||
| Line 2: | Line 2: | ||
1. Turn on power to the computer and wait for it to boot up. | 1. Turn on power to the computer and wait for it to boot up. | ||
2. Turn on power to the video server, telescope field of view camera, guider, and dome interior surveillance camera. | 2. Turn on power to the video server, telescope field of view camera, guider, and dome interior surveillance camera. | ||
3. Turn on power to the telescope science camera. | 3. Turn on power to the telescope science camera. | ||
4. Turn on power to the telescope mount. | 4. Turn on power to the telescope mount. | ||
5. Assure that dome power is on to maintain charge on the solar powered battery supply. | 5. Assure that dome power is on to maintain charge on the solar powered battery supply. | ||
6. Log onto the dome computer and check network connection with a ping offsite if you are running locally. | 6. Log onto the dome computer and check network connection with a ping offsite if you are running locally. | ||
8. Check network time to be sure it is synchronized with NTP to an atomic clock standard. | 8. Check network time to be sure it is synchronized with NTP to an atomic clock standard. | ||
7. Create a directory for the daily data: /data/observations/2010mmdd where mm is a two-digit month 01 to 12, and dd is a two-digit day. By convention, this is the local date for sunset at the telescope, not UT. | 7. Create a directory for the daily data: /data/observations/2010mmdd where mm is a two-digit month 01 to 12, and dd is a two-digit day. By convention, this is the local date for sunset at the telescope, not UT. | ||
8. cd /data/observations/2010mmdd/ | 8. cd /data/observations/2010mmdd/ | ||
9. ps -e ; look for monitordome which should be in the computer's startup script. If it is not there, then as root "monitordome&". | 9. ps -e ; look for monitordome which should be in the computer's startup script. If it is not there, then as root "monitordome&". | ||
10. indiserver dome tel ccd guider & ; as the observing user, from the data directory | 10. indiserver dome tel ccd guider & ; as the observing user, from the data directory | ||
11. xephem | 11. xephem | ||
Revision as of 17:04, 2 June 2010
All the telescopes run a server that handles communication with the mounting, telescope components, camera, guider, and dome. Starting the observatory from a total shutdown would follow this sequence:
1. Turn on power to the computer and wait for it to boot up.
2. Turn on power to the video server, telescope field of view camera, guider, and dome interior surveillance camera.
3. Turn on power to the telescope science camera.
4. Turn on power to the telescope mount.
5. Assure that dome power is on to maintain charge on the solar powered battery supply.
6. Log onto the dome computer and check network connection with a ping offsite if you are running locally.
8. Check network time to be sure it is synchronized with NTP to an atomic clock standard.
7. Create a directory for the daily data: /data/observations/2010mmdd where mm is a two-digit month 01 to 12, and dd is a two-digit day. By convention, this is the local date for sunset at the telescope, not UT.
8. cd /data/observations/2010mmdd/
9. ps -e ; look for monitordome which should be in the computer's startup script. If it is not there, then as root "monitordome&".
10. indiserver dome tel ccd guider & ; as the observing user, from the data directory
11. xephem