Subject: Re: [sdss3-25mlog 817] Re: 2.5m obslog 20120915 (MJD 56186)
From: Elena Malanushenko
Date: Sun, 16 Sep 2012 10:35:04 -0600
In log fun I do read motor position values from boss keywords.
"Move" is my variable which I calculate as a difference between
previous position and current new one.
If something not ok with boss keywords, so my difference is
suffering and you see the problem.
I check with archiver and see some spike in values:
2012-09-16T09:57:56.473580	22340	22641	22567	31800	32111	32589
2012-09-16T09:57:09.715900	22340	22641	22567	31800	32111	32589
2012-09-16T09:56:39.978220	-1	-1	-1	-1	-1	-1
2012-09-16T09:44:39.222030	22340	22641	22567	31800	32111	32589
2012-09-16T09:43:20.838710	22340	22641	22567	31800	32111	32589
I also echo this differences and original position values to stui local log
(by echo of logFun script output)  in file with name
/Users//Documents/stuilog2012-09-16:02:56:51.txt
You might grep "motorPos" and see your values.
This log is not for long time. I do not remember but STUI is
keeping some reasonable amount on disk and delete old ones.
Elena
On 09 /16/ 12, at 8:32 AM, Kaike Pan wrote:
>> Although there are messages about huge piston move:
>> 09:57:18 motorPos.sp1.move: -22341,  -22642,  -22568;
>> 09:57:18 motorPos.sp2.move: -31801,  -32112,  -32590;
>> 09:57:44 motorPos.sp1.move:  22341,   22642,   22568;
>> 09:57:44 motorPos.sp2.move:  31801,   32112,   32590;
>> we checked it and found that the moves are not real.
>