Since Crappy 2.0.0, the Camera Block never outputs messages to downstream Blocks. That is because the acquisition, display, and recording of the images are all managed from within the Camera Block. However, as pointed out in #98, there is currently no way for other Blocks to know when an image is saved. This feature could be useful when performing image analysis in post-processing, in case actions need to be performed during the test, to synchronize with the timestamps of the saved images.
With this PR, the Camera Block now sends messages containing the timestamp and metadata of each recorded image. It does so in case all these conditions are true:
the image recording is enabled
no image-processing is performed
the Camera Block has at least one output Link
The timestamp and metadata are respectively sent over the labels 't(s)' and 'meta'. A new example was added to demonstrate the new behavior, and the documentation was updated.
Since Crappy
2.0.0, theCameraBlock never outputs messages to downstream Blocks. That is because the acquisition, display, and recording of the images are all managed from within theCameraBlock. However, as pointed out in #98, there is currently no way for other Blocks to know when an image is saved. This feature could be useful when performing image analysis in post-processing, in case actions need to be performed during the test, to synchronize with the timestamps of the saved images.With this PR, the
CameraBlock now sends messages containing the timestamp and metadata of each recorded image. It does so in case all these conditions are true:CameraBlock has at least one output LinkThe timestamp and metadata are respectively sent over the labels
't(s)'and'meta'. A new example was added to demonstrate the new behavior, and the documentation was updated.