Closed jaydcarlson closed 2 months ago
Hi @jaydcarlson , thank you for reporting this issue. Could you please confirm the version of Holoscan Sensor Bridge that you are using for reference?
From discussion with @AndreasHeumann , the rank check here is consistent with other tensor handling in Holoscan such as in Holoviz. Please consider the following workarounds:
Update: Corrected Holoscan SDK version compatibility for Holoscan Sensor Bridge 1.0.
Thank @jaydcarlson. I agree that it is confusing that a 3rd dimension (which I think must be size 1) is required. I can open an issue to update the operator to also accept 2D input in future releases (and still allow 3D as long the channels dimension is size 1)
Addressed in Holoscan SDK v2.4.0.
In holoscan SDK 2.1.0, code was added in to ensure the input image has rank 3:
But this makes no sense. The input to a demosaic operator is a single-channel bayer image (rank 2).
Consequently, this check breaks the entirety of Holoscan Sensor Bridge, which relies on the demosaic operator in every example.