Propsero Data System Issues

Tuesday, August 16, 2016 9:14 AM

Problem(s) Encountered:

The data-taking system had problems.  First, during a series of biases the machine started claiming that the file it was writing to already existed - it claimed to be trying to write to 157, but the file number had already incremented beyond that, and in any case it made up a string of characters and saved the data.  To cure this we followed the instructions in  Duplicate Files Generated by Prospero (CCDS)  which involved quitting prospero, quitting caliban, quitting the IC, powering down the IC and the caliban disk, and starting back up.  The first time we did this prospero would not ''startup'', so we did it again, and it worked.  However, when we tried to take data we got


TELESCOPE CONTROLLER NOT RESPONDING ACQTAG=OSMOS


even though tcstatus gave normal results.  Telescope information was evidently not written to the headers.  We ended up quitting from all four of the control programs, powering down the IC and caliban, and bringing everything back up from scratch.  Things appear to be working now, but weirdly the Prospero Status window is not painting completely -- it doesn''t

have the nice ledger lines and so on.  I''m not sure what information is missing, if any.  


It sure would be nice if this system were simplified.


Solutions:

I believe you did the correct procedure for resolving the data-taking issue.  Not sure why it balked on the telescope controller, or really even what that refers to.  Incidentally, I did find that “Num Lock” on the keyboard had been shut off.  This leads to issues with key-mapping that can affect interaction with the TCS GUI.  I turned it back on and am consulting with David Will on steps to take to disable this undesired consequence of Input Methods.  As for the Prospero status window:  I performed a status clear in the Prospero command window and that resolved the display issues.  Interestingly, simply typing status returns some of the display to the window, but not all of it, leaving it in a configuration as you described in the trouble report.