Give feedback

How would you rate this Learning Path?

Review frequently asked questions

AI-assisted

These FAQs were drafted with an approved AI-assisted workflow and reviewed by Arm contributors before publication. Human technical review remains part of the process so the final page reflects engineering rigor, accuracy, and Arm editorial standards.

Close
?
How do I know the Arm backend export path worked?
Run the PTQ example and check ./output/ for an exported .vgf artifact. Open the artifact in Model Explorer with the VGF adapter and inspect the graph.
Where should the exported .vgf files appear?
Find the PTQ export in ./output/ and the QAT export in ./output_qat/. Open the exported .vgf files from those directories for inspection.
How should I decide between PTQ and QAT for my model?
PTQ optimizes for speed of iteration, while QAT optimizes for quality and robustness. Export both, inspect the graphs in Model Explorer, and compare outputs to choose a strategy that fits your accuracy and development needs.
What changes do I make to use my own model and data?
First, run the CIFAR-10 example to verify your environment. Then, adapt the PTQ or QAT export structure in quantize_and_export_vgf.py for your FP32 model, inference input, and representative calibration data or QAT fine-tuning loop.
What should I look for when inspecting the graph in Model Explorer?
Check for unexpected layout conversions, operators that you didn’t intend to run on your GPU path, and model I/O shapes that don’t match your integration. Use these findings before you integrate the .vgf artifact into your runtime.

Share

Tell others about this Learning Path.

Back
Return to Mobile, Graphics, and Gaming