During the Oct technical time, we tested the 2.3 version of DIMM on-sky. However, we never did a measurement for a long time (30 minutes+). When they used version 2.3 on-sky, it would periodically core dump (see IT 4327)

Added mutex to protect the attributes of the DimmImageHandler class - used by the camera thread and the server thread. Steve let us test on-sky when they couldn't get going due to other problems on 1-Nov-2012. These are notes from daytime and nighttime testing.

Focuser

On the night of 1-Nov-2012, played around with the focuser.

Found that focuser control is weird. Don't use the type-the-value-in-the-box; don't use the move in or move out options on the GUI. Use the slider, and very carefully - it's very sensitive.
add this info to operations somewhere

Few error messages:
Error: Focuser internal error on a "move out" command
Error: Bad file descriptor
Error: Bad file descriptor between close and initialize ...

Focus control causes the distance between the stars to change - lower spreads the stars further apart, higher values bring the stars closer together, even crossing.

677 is where we left it - looked good. In fact, JH noted he's never seen DIMM record less than 0.6 seeing before this night!

Need to change the GUI to keep the range much, much smaller than the whole focuser range - we saw values like 1300, but it should really stay something like 300 to 800.

  • don't have to be on-source for DIMM to measure

  • dropped frames on the GUI are the seeing.problemCount value in the server process

  • stars too close to the border message do NOT stop the camera thread

  • camera thread seems to run as fast as it can - there's no sleep; can be as fast as 20Hz, down to 5Hz it seems

  • mount thread has configurable 800 millisec sleep

  • does guiding stay on sometimes? sometimes the GUI had guiding available to turn on, but we WERE guiding...

  • tested two sets of source for the locking -- using tryLock and lock
    daytime looked at how long between log messages in calculateSeeing - both ways was about 0.5 sec
    used the tryLock version so we won't ever deadlock
    grepped through the output from when Steve started up through the whole rest of the night (04:10 through last measurement ~13:36)
    219 complaints in 9.5 hours - mostly on "set seeing", then findStars - only one on calculateSeeing

from 2-Nov log after I left:
11/02/2012 04:12:30.337 - update: LBT is on-source.
DimmImageHandler::findStars couldn't get lock
.....
11/02/2012 04:12:52.424 - update: LBT is on-source.
11/02/2012 04:12:53.172 -       Seeing value: 0.812 at el 70.80 az 206.73,   LBT el 76.44  az 214.10
DimmImageHandler::calculateSeeing couldn't acquire lock to set seeing
....
11/02/2012 04:14:43.105 -       Seeing value: 0.803 at el 70.63 az 207.96,   LBT el 76.22  az 215.65
DimmImageHandler::calculateSeeing couldn't acquire lock to set seeing
...
11/02/2012 04:16:39.006 - update: LBT is on-source.
DimmImageHandler::calculateSeeing couldn't acquire lock to set seeing
....
11/02/2012 04:20:06.705 - update: LBT is on-source.
DimmImageHandler::findStars couldn't get lock

11/02/2012 04:22:00.209 - update: LBT is on-source.
DimmImageHandler::calculateSeeing couldn't acquire lock to set seeing

11/02/2012 04:27:10.165 -       Seeing value: 0.774 at el 69.24 az 215.76,   LBT el 74.51  az 224.99
DimmImageHandler::calculateSeeing couldn't acquire lock to set seeing
...
11/02/2012 04:27:42.028 - update: LBT is on-source.
DimmImageHandler::calculateSeeing couldn't acquire lock to set seeing

11/02/2012 04:29:30.211 -       Seeing value: 0.712 at el 68.94 az 217.11,   LBT el 74.16  az 226.52
DimmImageHandler::calculateSeeing couldn't acquire lock to set seeing

11/02/2012 04:29:55.856 - update: LBT is on-source.
DimmImageHandler::calculateSeeing couldn't acquire lock to set seeing

11/02/2012 04:32:24.430 - Warning: Stars close to the edge minX:99.79 maxX:150.56 minY:73.20 maxY:75.33
DimmImageHandler::calculateSeeing couldn't acquire lock to set seeing

11/02/2012 04:33:38.180 - update: LBT is on-source.
DimmImageHandler::calculateSeeing couldn't acquire lock to set seeing
11/02/2012 04:33:40.414 - update: LBT is on-source.
DimmImageHandler::calculateSeeing couldn't acquire lock to set seeing


11/02/2012 04:34:22.142 -       Seeing value: 0.926 at el 68.31 az 219.81,   LBT el 73.40  az 229.53
DimmImageHandler::calculateSeeing couldn't acquire lock to set seeing

11/02/2012 04:35:03.069 - update: LBT is on-source.
DimmImageHandler::calculateSeeing couldn't acquire lock to set seeing

11/02/2012 04:35:09.897 - update: LBT is on-source.
DimmImageHandler::findStars couldn't get lock

  • can we get an unhandled exception from spiral search?

  • we get 0.0 seeing measurement the first print out - why?

  • guiding didn't perform great, in fact, while at zenith we couldn't hold very well at all - better to have guiding off?
    it may be that the gain on the Y-axis (on the image preview) is about 2x too much on guide corrections - but not always, sometimes a similar move didn't change anything on the preview -- still need to go through the logs for this
    I watched this for awhile and it certainly doesn't stay around 100,100

Performance

full-frame camera preview, client takes ~55% cpu, server ~21%

server measuring, no preview, server 21%

Add to an operations page about testing:
on-sky checkout should include looking at DD entries on env GUI or via DD browser or viewer
Topic revision: r3 - 09 May 2014, KelleeSummers
This site is powered by FoswikiCopyright © by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding Foswiki? Send feedback