Expose selected decoder plugin and backend per decoded sample

Abierto
  • ¿Algo no está bien?
#64 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
38/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
cpp, python
Área
backend-api-design

Línea de trabajo

Start by reading the generic decoder API around nvimgcodecDecoderDecode, nvimgcodecFutureGetProcessingStatus, and nvimgcodecExecutionParams_t, then compare the Python get_decoder_ids() API and the cuCIM workaround described in the issue. Define how per-sample plugin and backend provenance, fallback information, and results after completion should fit the C and Python APIs. Done means callers can query those details for successful and failed samples while preserving generic per-sample dispatch.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

Request

Please expose the decoder plugin identifier and backend kind that actually handled each sample submitted through the generic decoder API.

Motivation

Applications that audit heterogeneous decode pipelines need to distinguish GPU-only, hybrid CPU/GPU, and CPU fallback execution without inferring it from the codec, output buffer, or installed extensions. The generic decoder can fall through registered implementations in priority order, and a batch can contain per-sample choices.

Current API boundary

With nvImageCodec 0.9, nvimgcodecDecoderDecode plus nvimgcodecFutureGetProcessingStatus reports only processing status. nvimgcodecExecutionParams_t::backends can constrain backend kinds, but the selected nvimgcodecDecoderDesc_t::id and backend_kind are not returned.

Current documentation also provides plugin enumeration/selection (get_decoder_ids() in Python and plugin selections/framework queries in the newer C API), which is useful for configuration but still does not identify the implementation selected after generic fallback.

Suggested shape

A future/result query returning, for each submitted sample:

  • selected decoder plugin ID;
  • selected backend kind;
  • whether fallback occurred (and optionally rejected candidates/statuses).

The query should remain valid after the decode completes and should work for both success and failure. An equivalent Python result/property would be useful.

Workaround and limitation

cuCIM can create separate generic decoders restricted to one backend kind and probe/decode in an explicit order. That provides truthful backend provenance but changes selection to a caller policy, cannot identify the plugin within that backend, and cannot preserve arbitrary per-sample mixed-backend dispatch in a single batch.

Lenguaje dominante
Jupyter Notebook
Estrellas
164
Forks
26
Merge medio
27 min
PR fusionados (30 d)
1

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de NVIDIA/nvImageCodec

Todos los issues de NVIDIA/nvImageCodec

Issues similares

Más issues de Backend & API Design

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.