fix(kv260): make PaDiM XMODEL compilation compatible with KV260` This is accurate and avoids claiming hardware validation that you haven't performed.

[DeepKnowledge1]

🔗 Related Issue

Fixes #

📝 Description

• Fixed PaDiM KV260 quantization and XMODEL generation.
• Isolated the PaDiM backbone to generate a KV260-compatible DPU subgraph.
• Removed unsupported graph operations that caused vai_c_xir to crash with a segmentation fault.
• Successfully compiled the generated XMODEL for the DPUCZDX8G_ISA1_B4096 KV260 architecture.

🔄 Type of Change

• 🐛 Bug fix (non-breaking change which fixes an issue)
• 🚀 New feature (non-breaking change which adds functionality)
• 💥 Breaking change (fix or feature that would cause existing functionality to not work as expected)
• 📖 Documentation update
• 🏗️ Infrastructure / CI/CD update

🧪 Hardware & Matrix Testing

Vitis AI / KV260:

• PaDiM quantization calibration
• XMODEL generation
• vai_c_xir compilation
• KV260 hardware runtime test (hardware not available)

Compilation result:

• Target: DPUCZDX8G_ISA1_B4096
• Input: [1, 224, 224, 3] xint8
• DPU output: [1, 56, 56, 64] xint8
• DPU subgraphs: 1
• Compilation: Successful

Host OS used for testing:

• Linux / Ubuntu
• Windows (Native or WSL2)
• macOS

✅ Developer Checklist

• My code follows the core style guidelines of this project (Ruff/Black formatting).
• I have run uv run pytest and all unit tests pass locally.
• Lockfile Guard: No dependency changes.
• I have added tests that prove my fix is effective or that my feature works.
• I have updated the documentation accordingly (if applicable).

📸 Screenshots / Visual Proof (Optional)

Vitis AI compilation

[UNILOG][INFO] Compile mode: dpu
[UNILOG][INFO] Target architecture: DPUCZDX8G_ISA1_B4096
[UNILOG][INFO] Graph name: PadimKV260, with op num: 43
[UNILOG][INFO] Total device subgraph number 3, DPU subgraph number 1
[UNILOG][INFO] Compile done.
[UNILOG][INFO] The compiled xmodel is saved to:
compiled_padim_kv260/compiled/PadimKV260.xmodel