Closed jkbhagatio closed 5 months ago
@aspaNeuro @jkbhagatio @Dario55 Is this visualizer supposed to be running all the time? This will increase our camera memory bandwidth and compute pressure by 9x. Is there a reason for having all cameras open at all times?
I couldn't understand the discussion fully during the meeting, but here is my interpretation of it and counter-arguments:
If this is for pre-experimental checks, then my suggestion is that we simply make a separate workflow just for this, adapted from the camera calibration workflow, which already displays all cameras.
If this is for pre-experimental checks, then my suggestion is that we simply make a separate workflow just for this
Sure @glopesdev, for me fine to just do this, @aspaNeuro ?
This workflow is only to display the cameras or is there anything else you guys want to include? Also let me note that this workflow cannot run at the same time has the social workflow. Will implement tomorrow morning whatever you guys decide.
Sure, I guess a workflow just to display and log all cameras is good.
Closing this as we're going with approach in #494
As a camera view sanity check.
In future, something similar could be done for other devices (e.g. a workflow just to view patches, microphones, etc.)