MDM Trouble Report for 2016 May 01

Telescope: 2.4m
Observer(s): Carroll, Wei (Dartmouth)
Instrument: OSMOS

Problem(s) Encountered:
The previous team had changed the guiding setup, which I set back to the 
default settings listed here
http://mdm.kpno.noao.edu/Manuals/guiderdoc/autoguiding.html#startup
The only thing I didn't change was the  minimum move  which was set to 0.01.
The startup guide says it should be set to 0.00. I wasn't sure if there was 
perhaps a reason for this so I left it. Just wanted to let you know before I wake 
up. 

Ok now the real problem.

This isn't a telescope problem as much as the software. We use osctrtask to 
position the object on the slit, but it was not working like it normally does. It 
normally pops up and asks to mark the target  a,  slit  x,  and then quit, giving
you the dx,dy coordinates. The setup was different. 

First, it took a long time to load. Then it wouldn't automate the procedure. I can label the 
slit with 'x' and then quit 'q', but the target cannot be labelled with 'a.' Instead, 
it asks me to manually record the X,Y position of the target, which I enter to receive 
the dx,dy offsets. osctrtask is now also creating  scratch#.fits,   acqimage.fits,  and 
 slitimage.fits  files along other similarly named files. I don't remember this 
happening before.

I also noticed that in the osctrtask guide, the file reads  Package = RVSAO  while on 
my screen it reads  Package = Bias.  At some point while running pyexecute, it gave 
me and error that read  Warning, 'bias.osctrtask' is a task redefinition.' I looked 
for any files that might be conflicting but I did not find any. I'm not sure if this 
has anything to do with the problem. 
 
The loss of hours is really a result from me trying to troubleshoot the issue with 
the archived trouble reports. Once I realized I could actually manually input 
the target X,Y I proceeded with that.

------------------------------

Submitted on 2016 May 2 [5:22:23]