[Motmot] getting started with MotMot

[Andrew Straw]

Jacobson, Gilad wrote:
> Hi Andrew,
>
> I upgraded the camiface and executed ran /usr/lib/libcam_iface/example/simple-dc1394. Results attached.
>
> The interesting things are in coriander. The Controls contain the same parameters as reported by the above executable, in the same order. The value right after IRIS, where motmot failed, is temperature. This control (both current and target temperature) appear gray in coriander and cannot be modified, so this must be where motmot tries to write a value that cannot be written. Trigger delay and frame rate are then controllable, but then pan and tilt are not.
>
> I would guess that the good thing is that coriander KNOWS which variables are writable, which means that it should be possible to make motmot's initial parameter setting conditional no the parameters being available for writing. Would that seem reasonable?
>   
Hi Gilad,

OK, I believe I found and fixed the problem. Basically, each camera
feature (e.g. shutter speed, gain, temperature,...) has the attributes
"is_present" and "is_available". I was not checking "is_available". My
guess is that the temperature attribute is present, but not available,
on your camera. I've added support for checking these attributes in
libcamiface and then done so in FView. I've made new releases with this
in it for Ubuntu Hardy and Karmic. A normal update should download
these. The package versions with the updates are:

libcamiface 0.5.7
python-motmot-camiface 0.4.8
python-motmot-fview 0.6.0

Please let me know if this resolves the issue or whether you still have it.

Thanks,
Andrew

-- 
Andrew D. Straw, Ph.D.
California Institute of Technology
http://www.its.caltech.edu/~astraw/