Startup - Revision history

WikiSysop: A brief outline of command line operation without scripts describes the use of xmtel, xmccd, and xpa-based servers.

2015-08-15T23:16:42Z

A brief outline of command line operation without scripts describes the use of xmtel, xmccd, and xpa-based servers.

John at 04:15, 15 June 2010

2010-06-15T04:15:41Z

← Older revision		Revision as of 04:15, 15 June 2010
Line 43:		Line 43:
	8. Use "date" to be sure the local computer time is synchronized by NTP to an atomic clock standard.		8. Use "date" to be sure the local computer time is synchronized by 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 with "mkdir /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. Run subsequent commands from the new directory after "cd /data/observations/2010mmdd/".

			9. Copy your observation queue into this directory. Your images and log file will be created here.

	9. Run "ps -e" and look for the monitordome process which should be already have been started by the computer's startup script. If it is not there, then as root "monitordome &" will start it.		10. Run "ps -e" and look for the monitordome process which should be already have been started by the computer's startup script. If it is not there, then as root "monitordome &" will start it.

	10. If you are not running as "observer", then remove stale tmp files should they exist: "rm /tmp/telcoords".		11. If you are not running as "observer", then remove stale tmp files should they exist: "rm /tmp/telcoords".

	11. Run "indiserver dome tel ccd guider &" as the observing user, from the data directory.		12. Run "indiserver dome tel ccd guider &" as the observing user, from the data directory.

	12. Run "xephem &" as needed for the telescope operator and the observer.		13. Run "xephem &" as needed for the telescope operator and the observer.

	13. Run "xmtel &" only for the observer.		14. Run "xmtel &" only for the observer.

	13. Run "xmccd &" only for the observer.		15. Run "xmccd &" only for the observer.

John at 04:13, 15 June 2010

2010-06-15T04:13:00Z

← Older revision		Revision as of 04:13, 15 June 2010
Line 55:		Line 55:
	12. Run "xephem &" as needed for the telescope operator and the observer.		12. Run "xephem &" as needed for the telescope operator and the observer.

	13. xmtel & ; for the observer ~~only~~		13. Run "xmtel &" only for the observer.

	13. xmccd & ; for the observer ~~only~~		13. Run "xmccd &" only for the observer.

John: Sequence of operations to start an observing session.

2010-06-15T04:10:52Z

Sequence of operations to start an observing session.

← Older revision		Revision as of 04:10, 15 June 2010
Line 41:		Line 41:
	6. Log onto the dome computer and check the network connection with a ping offsite if you are running locally.		6. Log onto the dome computer and check the 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. Use "date" to be sure the local computer time is synchronized by 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. Run "ps -e" and look for the monitordome process which should be already have been started by the computer's startup script. If it is not there, then as root "monitordome &" will start it.

	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. If you are not running as "observer", then remove stale tmp files should they exist: "rm /tmp/telcoords".

	10. indiserver dome tel ccd guider & ; as the observing user, from the data directory		11. Run "indiserver dome tel ccd guider &" as the observing user, from the data directory.

	11. xephem & ; for the telescope operator and the observer		12. Run "xephem &" as needed for the telescope operator and the observer.

	12. xmtel & ; for the observer only		13. xmtel & ; for the observer only

	13. xmccd & ; for the observer only		13. xmccd & ; for the observer only

John at 03:07, 4 June 2010

2010-06-04T03:07:50Z

← Older revision		Revision as of 03:07, 4 June 2010
Line 39:		Line 39:
	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 the 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.

John at 03:04, 4 June 2010

2010-06-04T03:04:15Z

@@ Line 1: / Line 1: @@
-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:
+The remotely operated telescopes run a server that handles communication with the mounting, telescope components, camera, guider, and dome.
 .  Turn on power to the computer and wait for it to boot up.
@@ Line 30: / Line 58: @@
-[[File:Xephem_video_screenshot.jpg|600px|thumb|left|XEphem with indiserver tel and a video server.]]
+[[File:Xephem_video_screenshot.jpg|600px|thumb|left|XEphem with indiserver tel and the video server. The video server also allows the operator to see the finder field.]]

John at 02:59, 4 June 2010

2010-06-04T02:59:56Z

← Older revision		Revision as of 02:59, 4 June 2010
Line 30:		Line 30:


	[[File:Xephem_video_screenshot.jpg\|600px\|thumb\|left\|XEphem with ~~xmtel~~ and a video server.]]		[[File:Xephem_video_screenshot.jpg\|600px\|thumb\|left\|XEphem with indiserver tel and a video server.]]

John at 02:58, 4 June 2010

2010-06-04T02:58:04Z

← Older revision		Revision as of 02:58, 4 June 2010
Line 28:		Line 28:

	13. xmccd & ; for the observer only		13. xmccd & ; for the observer only


			[[File:Xephem_video_screenshot.jpg\|600px\|thumb\|left\|XEphem with xmtel and a video server.]]



























			----

John at 03:46, 3 June 2010

2010-06-03T03:46:39Z

← Older revision		Revision as of 03:46, 3 June 2010
Line 35:		Line 35:
	The observer may be logged directly into the telescope computer if the network connection is fast (>> 1 Mbits/sec) with low latency. Otherwise the observer should run software locally and set up tunneling through ssh.		The observer may be logged directly into the telescope computer if the network connection is fast (>> 1 Mbits/sec) with low latency. Otherwise the observer should run software locally and set up tunneling through ssh.

	For some testing purposes the ~~harware~~ may be operated with directly connected software that does not go through INDI. For control of the telescope, camera, dome, and guider these programs are		For some testing purposes the hardware may be operated with directly connected software that does not go through INDI. For control of the telescope, camera, dome, and guider these programs are

	xmtel1, xmccd1, xmdome1, and xmguide1		xmtel1, xmccd1, xmdome1, and xmguide1

John at 17:11, 2 June 2010

2010-06-02T17:11:48Z

← Older revision		Revision as of 17:11, 2 June 2010
Line 30:		Line 30:


	Notes		'''Notes'''

← Older revision		Revision as of 23:16, 15 August 2015
Line 1:		Line 1:
	The remotely operated telescopes run ~~a server~~ that ~~handles~~ communication with the mounting, telescope components, camera, guider, and dome.		The remotely operated telescopes run local servers that handle communication with the mounting, telescope components, camera, guider, and dome.


	[[File:Xephem_power_screenshot.jpg\|600px\|thumb\|left\|XEphem with ~~indiserver tel~~ and the power switch server.]]		[[File:Xephem_power_screenshot.jpg\|600px\|thumb\|left\|XEphem with an XPA telescope and the power switch server.]]


Line 29:		Line 29:
	Starting the observatory from a total shutdown would follow this sequence:		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.		1. If it is not on, 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, and dome interior camera.

	3. Turn on power to the telescope science camera.		3. Turn on power to the telescope science camera.
Line 37:		Line 37:
	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 backup battery supply in the case of the Sirius domes.

	6. Log onto the dome computer and check the network connection with a ping offsite if you are running locally.		6. Log onto the dome computer and check the network connection with a ping offsite if you are running locally.
Line 43:		Line 43:
	8. Use "date" to be sure the local computer time is synchronized by NTP to an atomic clock standard.		8. Use "date" to be sure the local computer time is synchronized by NTP to an atomic clock standard.

	7. Create a directory for the daily data with "mkdir /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 with "mkdir /data/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. Run subsequent commands from the new directory after "cd /data/observations/~~2010mmdd~~/".		8. Run subsequent commands from the new directory after "cd /data/observations/2015mmdd/".

	9. Copy your observation queue into this directory. Your images and log file will be created here.		9. Copy your observation queue into this directory. Your images and log file will be created here.
Line 53:		Line 53:
	11. If you are not running as "observer", then remove stale tmp files should they exist: "rm /tmp/telcoords".		11. If you are not running as "observer", then remove stale tmp files should they exist: "rm /tmp/telcoords".

	12. Run "~~indiserver dome tel ccd guider~~ &" as the observing user, from the data directory.		12. Run "xpatel and xpaccd &" as the observing user, from the data directory.

	13. Run "xephem &" ~~as needed~~ for ~~the telescope operator and~~ the observer.		13. Run "xephem &" for the observer.

	14. Run "xmtel &" only for the observer.		14. Run "xmtel &" only for the observer.
Line 96:		Line 96:


	The observer may be logged directly into the telescope computer if the network connection is fast (>> 1 Mbits/sec) with low latency. Otherwise the observer should run ~~software locally and set up~~ tunneling through ssh.		The observer may be logged directly into the telescope computer if the network connection is fast (>> 1 Mbits/sec) with low latency. Otherwise the observer should run a VNC session with tunneling through ssh. Alternatively, for low bandwidth situations or for operation by observers outside a secure network, use the web interface to the control system.

	For some testing purposes the hardware may be operated with directly connected software that does not go through ~~INDI~~. ~~For control of the telescope, camera, dome, and guider these~~ programs are		For some testing purposes the hardware may be operated with directly connected software that does not go through XPA. These programs are

	xmtel1, xmccd1~~, xmdome1, and xmguide1~~		xmtel1 and xmccd1

	They should not be running concurrently with the ~~indiserver versions~~.		They should not be running concurrently with the xpa servers for the same hardware.

	When the server is running the instruments are also open to scripted operation.		When the server is running the instruments are also open to scripted operation through xpaget and xpaset, as well as the web interface which communicates with the servers by means of node.js.