Missing Camera Parameters

[daxatino]

Description:
The documentation page states:

Isaac ROS Argus Camera provides with several sensor capture and processing features, including AWB (auto-white-balance), AE (auto-exposure), and noise reduction.

However, in practice only the following parameters are visible/usable in the nvidia::isaac::ArgusCamera component:

- type: nvidia::isaac::ArgusCamera
  parameters:
    allocator: allocator
    left_camera_output: left_camera_output
    right_camera_output: left_camera_output
    camera_id: 0
    module_id: -1
    mode: 0
    framerate: 30
    fsync_type: 1
    camera_type: 0
    output_format: 0
    use_hw_timestamp: false
    camera_provider: global_camera_provider/global_camera_provider
    analog_gain_1: 1.0
    analog_gain_2: 1.0
    compute_brightness: false
    exposure_mode: auto
    exposure_time_1: 15000000
    exposure_time_2: 20000000
    isp_digital_gain: 10
    use_average_map: true
    cuda_stream_pool: stream

Problem:

• There is no clear documentation on how to configure AWB and noise reduction. These are accessible via nvarguscamerasrc.
• It is unclear whether these parameters are supported but undocumented, or not yet exposed in the Argus Camera GXF extension.

Request:

• Clarify how to tune AWB and noise reduction, as these are not visible in the current parameter set.
• If these features are not yet supported, could they be added in future releases?

[lucasreljic]

I am encountering the same issue, I need AWB (auto-white-balance), AE (auto-exposure), and noise reduction but they seem to not be exposed to the Argus Camera GXF extension.

Is there any updates to this issue or alternative solutions? I need to use Nitros because of downstream Isaac ros convert, resize and rectify nodes along with some custom Nitros nodes. Is the temporary solution to use nvarguscamerasrc and create a gscam2 like node with Nitros support?

[jaiveersinghNV]

Hi @lucasreljic ,

We don't have any updates to isaac_ros_argus_camera to share at this time.

Your proposal about writing a custom NITROS node sounds like a good solution for your use case. We'll continue our work to identify a better long-term solution in parallel.