Manager doesn't Start or Stop ChimeraObjects properly

[GoogleCodeExporter]

I was working on a chimera-man script as a way of remotely loading and
unloading objects so that I could better restart the scheduler when I
encountered this bug. When calling Manager.stop({location}) followed by
Manager.start({location}), ChimeraObject referred to by {location} doesn't
restart.

Furthermore, {location}.getState() == State.RUNNING is always true, even
following Manager.stop({location}). That said, Manager.stop('/Dome/0') does
seem to stop the dome from being woken up to check tracking even though it
still claims State.RUNNING.

A work-around is to use Manager.remove({location}) and then
Manager.addLocation({location}), but this doesn't allow a ChimeraObject
(such as a scheduler) to be paused and resumed properly. (It must save
state to disk and not rely on memory.) Alternatively, a ChimeraObject may
implement alternative methods to start and stop itself.

Original issue reported on code.google.com by laughing...@gmail.com on 22 Jul 2008 at 4:12

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

Fixed in r266 -- Thanks, Paulo

Original comment by laughing...@gmail.com on 23 Jul 2008 at 4:46

• Changed state: Fixed