2017 February - Revision history

Dgary at 11:13, 2 April 2017

2017-04-02T11:13:11Z

← Older revision		Revision as of 11:13, 2 April 2017
Line 1:		Line 1:
			[http://www.ovsa.njit.edu/wiki/index.php/Expanded_Owens_Valley_Solar_Array#Observing_Log Back to Observing Log]

	= Feb 01 =		= Feb 01 =
	'''11:27 UT''' Started another interferometric pointing run (CALPNT), which has been running since 08:16 UT without error. The wind is low, and Ant 14 is working well.		'''11:27 UT''' Started another interferometric pointing run (CALPNT), which has been running since 08:16 UT without error. The wind is low, and Ant 14 is working well.

Dgary: /* Feb 25 */

2017-02-26T13:05:48Z

Feb 25

← Older revision		Revision as of 13:05, 26 February 2017
Line 85:		Line 85:
	'''23:26 UT''' I updated the delays, and am going back to 3C84 to check them.		'''23:26 UT''' I updated the delays, and am going back to 3C84 to check them.

	= Feb 25 =		= Feb 26 =
	'''02:28 UT''' Doh. I just checked, and the delays were put in with the wrong sign. I just updated the delays once more, and the new file is starting 02:28 UT.		'''02:28 UT''' Doh. I just checked, and the delays were put in with the wrong sign. I just updated the delays once more, and the new file is starting 02:28 UT.

			'''13:03 UT''' I found this morning that Ant 14 stopped tracking at 04:28 UT (possible came to the +51 HA limit). I had also set up the schedule to observe two sources (3C273 and 3C286) all night, but it had a cable tension alarm on the first source, so none of those observations are good. Also, Ant 14 cannot be used until it is fixed, hopefully tomorrow.

Dgary: /* Feb 25 */

2017-02-26T02:29:38Z

Feb 25

← Older revision		Revision as of 02:29, 26 February 2017
Line 84:		Line 84:

	'''23:26 UT''' I updated the delays, and am going back to 3C84 to check them.		'''23:26 UT''' I updated the delays, and am going back to 3C84 to check them.

			= Feb 25 =
			'''02:28 UT''' Doh. I just checked, and the delays were put in with the wrong sign. I just updated the delays once more, and the new file is starting 02:28 UT.

Dgary: /* Feb 25 */

2017-02-25T23:30:17Z

Feb 25

← Older revision		Revision as of 23:30, 25 February 2017
Line 82:		Line 82:

	'''22:52 UT''' Now everything looks fine, so apparently the reload of the roaches did the trick. I will get the delays and apply them.		'''22:52 UT''' Now everything looks fine, so apparently the reload of the roaches did the trick. I will get the delays and apply them.

			'''23:26 UT''' I updated the delays, and am going back to 3C84 to check them.

Dgary: /* Feb 25 */

2017-02-25T22:53:01Z

Feb 25

← Older revision		Revision as of 22:53, 25 February 2017
Line 80:		Line 80:

	'''22:10 UT''' The solar data are "okay" except that now ant 8 is showing no coherence, and the pattern of data looks strange, as if baseline order was messed up. I decided to reboot the roaches again, and while I was at it I measured and updated X vs. Y delays. We are on the Sun again, but I am thinking about taking some 3C84 data to see if the earlier problem has been affected by the reboot.		'''22:10 UT''' The solar data are "okay" except that now ant 8 is showing no coherence, and the pattern of data looks strange, as if baseline order was messed up. I decided to reboot the roaches again, and while I was at it I measured and updated X vs. Y delays. We are on the Sun again, but I am thinking about taking some 3C84 data to see if the earlier problem has been affected by the reboot.

			'''22:52 UT''' Now everything looks fine, so apparently the reload of the roaches did the trick. I will get the delays and apply them.

Dgary: /* Feb 25 */

2017-02-25T22:12:31Z

Feb 25

← Older revision		Revision as of 22:12, 25 February 2017
Line 78:		Line 78:

	'''14:38 UT''' Same problem on 3C84. I have rebooted the ACC, which is the last option I have. I am not sure how the ACC could cause the problem I am seeing, but it is the last system not otherwise restarted. Now 3C286 is unreachable, so again I'll wait for the Sun.		'''14:38 UT''' Same problem on 3C84. I have rebooted the ACC, which is the last option I have. I am not sure how the ACC could cause the problem I am seeing, but it is the last system not otherwise restarted. Now 3C286 is unreachable, so again I'll wait for the Sun.

			'''22:10 UT''' The solar data are "okay" except that now ant 8 is showing no coherence, and the pattern of data looks strange, as if baseline order was messed up. I decided to reboot the roaches again, and while I was at it I measured and updated X vs. Y delays. We are on the Sun again, but I am thinking about taking some 3C84 data to see if the earlier problem has been affected by the reboot.

Dgary: /* Feb 25 */

2017-02-25T14:40:32Z

Feb 25

← Older revision		Revision as of 14:40, 25 February 2017
Line 76:		Line 76:

	'''13:58 UT''' I checked last night's 3C84 data, and they do not show the problem, so I decided to kill and restart dppxmp. Possibly it could cause the problem, although I am not sure how. I am going to 3C286 (on source at 14:05 UT), to see if that restart makes any difference. This is using band14.fsq to maximize SNR.		'''13:58 UT''' I checked last night's 3C84 data, and they do not show the problem, so I decided to kill and restart dppxmp. Possibly it could cause the problem, although I am not sure how. I am going to 3C286 (on source at 14:05 UT), to see if that restart makes any difference. This is using band14.fsq to maximize SNR.

			'''14:38 UT''' Same problem on 3C84. I have rebooted the ACC, which is the last option I have. I am not sure how the ACC could cause the problem I am seeing, but it is the last system not otherwise restarted. Now 3C286 is unreachable, so again I'll wait for the Sun.

Dgary: /* Feb 25 */

2017-02-25T14:06:07Z

Feb 25

← Older revision		Revision as of 14:06, 25 February 2017
Line 74:		Line 74:

	'''13:30 UT''' Well, rebooting the LO1-A did not change anything, and 3C273 is now set, so I cannot do more tests. However, I also looked at some solar data from yesterday, and it looks fine, so it does not seem that dppxmp is at fault. I am stymied for now. Further tests will likely have to wait until we are on the Sun.		'''13:30 UT''' Well, rebooting the LO1-A did not change anything, and 3C273 is now set, so I cannot do more tests. However, I also looked at some solar data from yesterday, and it looks fine, so it does not seem that dppxmp is at fault. I am stymied for now. Further tests will likely have to wait until we are on the Sun.

			'''13:58 UT''' I checked last night's 3C84 data, and they do not show the problem, so I decided to kill and restart dppxmp. Possibly it could cause the problem, although I am not sure how. I am going to 3C286 (on source at 14:05 UT), to see if that restart makes any difference. This is using band14.fsq to maximize SNR.

Dgary: /* Feb 25 */

2017-02-25T13:33:47Z

Feb 25

← Older revision		Revision as of 13:33, 25 February 2017
Line 73:		Line 73:
	'''13:07 UT''' I see the same pattern after restarting the schedule. All baselines are bad except ant 8 with 14. In desperation, I rebooted the LO1-A (tunable LO) to see if that is the problem. Another possibility is that Jim's latest update to dppxmp has a problem.		'''13:07 UT''' I see the same pattern after restarting the schedule. All baselines are bad except ant 8 with 14. In desperation, I rebooted the LO1-A (tunable LO) to see if that is the problem. Another possibility is that Jim's latest update to dppxmp has a problem.

	'''13:30 UT''' Well, ~~3C273 is now set, and~~ rebooting the LO1-A did not change anything. However, I also looked at some solar data from yesterday, and it looks fine, so it does not seem that dppxmp is at fault. I am stymied for now.		'''13:30 UT''' Well, rebooting the LO1-A did not change anything, and 3C273 is now set, so I cannot do more tests. However, I also looked at some solar data from yesterday, and it looks fine, so it does not seem that dppxmp is at fault. I am stymied for now. Further tests will likely have to wait until we are on the Sun.

Dgary: /* Feb 25 */

2017-02-25T13:32:23Z

Feb 25

← Older revision		Revision as of 13:32, 25 February 2017
Line 72:		Line 72:

	'''13:07 UT''' I see the same pattern after restarting the schedule. All baselines are bad except ant 8 with 14. In desperation, I rebooted the LO1-A (tunable LO) to see if that is the problem. Another possibility is that Jim's latest update to dppxmp has a problem.		'''13:07 UT''' I see the same pattern after restarting the schedule. All baselines are bad except ant 8 with 14. In desperation, I rebooted the LO1-A (tunable LO) to see if that is the problem. Another possibility is that Jim's latest update to dppxmp has a problem.

			'''13:30 UT''' Well, 3C273 is now set, and rebooting the LO1-A did not change anything. However, I also looked at some solar data from yesterday, and it looks fine, so it does not seem that dppxmp is at fault. I am stymied for now.