Hailo compilation fails with BackendAllocatorException / concat14 Agent infeasible on ONNX detection model

General Discussion
, ,
1

Hi,

I am trying to compile an ONNX object detection model with Hailo, and I am stuck at the compilation stage.

Environment

  • Hailo environment: hailodfc

  • ONNX exported from MMDetection / RTMDet-style model

Current status

  • ONNX parsing works

  • DFL optimization also succeeds

  • Failure happens during compilation / mapping

Error

[info] Successfully built optimization options - 7s 239ms
[error] Mapping Failed (allocation time: 7s)
No successful assignments: concat14 errors:
        Agent infeasible

[error] Failed to produce compiled graph
[error] BackendAllocatorException: Compilation failed: No successful assignments: concat14 errors:
        Agent infeasible

Important detail

In my ONNX graph, I do not see a node literally named concat14.

The ONNX concat nodes are named like:

  • /Concat_4

  • /Concat_6

  • etc.

So I assume concat14 is an internal Hailo-translated node name rather than the original ONNX node name.

What I already checked

  • Parsing issue is resolved

  • End nodes were corrected to match the ONNX node names

  • DFL optimization runs successfully

  • The problem only appears at compilation/mapping stage

My question

What does Agent infeasible on concat14 usually mean in practice?

I would like to know:

  1. How to identify which original ONNX concat corresponds to Hailo internal concat14

  2. Whether this usually indicates:

    • too large input resolution

    • too many channels at a concat

    • problematic neck/head structure

    • unsupported topology for mapping

  3. What is the recommended way to fix it:

    • reducing input size

    • changing end nodes

    • simplifying the ONNX graph

    • changing export settings

    • modifying the model architecture

2

Hi @gje_gje,

“Agent infeasible” means the Hailo compiler couldn’t map that concat layer onto the hardware - typically because the tensor dimensions at that point exceed what the HW can handle in a single operation.

To identify the node: Open the .har file’s model visualization (or run hailo profiler) - concat14 is the internal name assigned during parsing. It usually corresponds to the 14th concat encountered in graph traversal order.

Common causes might be input resolution too high or too many channels at the concat.

Thanks,