imagehub is constantly evolving. It is a "science project" that is part of a larger system to observe, monitor and optimize a small permaculture farm. It is part of a distributed computer vision and sensor network. Here is where I keep the list of the stuff I'm experimenting with but haven't pushed to GitHub yet. Feel free to open an issue and make suggestions or start a discussion about a potential change or new feature. The list below is not in any particular order; all of these are ongoing experiments on differing timelines.
Right now, the imagehub returns "OK" after every message tuple is sent. The reply could be a "command word" instead that would cause imagenode to take an action such as change the exposure_mode of the PiCamera. Or send a dozen "live frames" from the camera (even though no detector has activated). Command words look like this (format is: CommandWord value): - OK # that is the only one now and is sent back for every reply. - ReloadYaml # reload the yaml file to get a change in one of the options. - SendFrames 10 # Send some frames now, even if no detector is activated. - SetResolution (640,480) # set a new resolution value for the camera.
Command words would arrive from the Librarian and be sent to the specific imagenode that is mentioned in the command.
As an alternative to passing commands from the Librarian to the imagenode
in REP "command words", I am also testing an arrangement where the Librarian
issues commands directly to the imagenode by making changes to the
imagenode.yaml file on the imagenode directly. In current testing,
having the Librarian communicate directly with the imagenode rather than
use the imagehub for commands is simpler and faster. But testing of
alternatives is continuing.