Voyager Wingman

Sharing a measurement in case it saves someone else the confusion, and because it changes how you would size a deployment.Setup: Metis M.2 (metis-0:3:0, firmware 1.7.0, bc 7.4, 800 MHz), Voyager SDK 1.7.0, driver metis-dkms 1.5.5, yolov8n-coco-onnx, --aipu-cores 4 --pipe gst, Ubuntu 24.04.┌─────────────────────────────────────────────┬───────────┬───────────┐│ │ 1080p │ 4K │├─────────────────────────────────────────────┼───────────┼───────────┤│ inference.py … --output out.mp4 (16 clips) │ 34–61 FPS │ 13–16 FPS │├─────────────────────────────────────────────┼───────────┼───────────┤│ Headless app on create_inference_stream() │ 740 FPS │ 238 FPS │├─────────────────────────────────────────────┼───────────┼───────────┤│ SDK stage table, Metis element (both cases) │ ~840 FPS │ ~840 FPS │└─────────────────────────────────────────────┴───────────┴───────────┘The headless 1080p figure (740) sits just under the AIPU stage rate (~8

I was watching the new Wingman walkthrough from our agentic coding whisperer ​@Abhilash and I was expecting a "build from a prompt" demo, and while there is plenty of that in there, but the bit that realy leapt out at me is about porting.If you've already got a computer vision project running on NVIDIA or Hailo or similar, you don't actually have to rebuild it from scratch to move it over. You open the Wingman app, hit "Port to Axelera", and it takes over from there. Wingman creates the Voyager pipeline, adapts your existing application logic, compiles it, runs it, validates it on the hardware, and bakes a celebration cake for you afterwards.What started life as a project on another platform is suddenly running on Axelera, with the result sitting on the dashboard ready to inspect and refine. One click.For anyone who's ever done a hardware migration by hand, you know why that's a big deal. Usually that's the part that eats weeks. Rewriting the pipeline, chasing model compatibility, re-t

Hi Axelera Community After some prompts in the Axelera Wingman browser version, I wanted to test on the Metis M.2 hardware installed in an IPC on my desk.After downloading and installing the Linux amd64 client (version 1.4.0), logging in is required. Where the browser version supports logging in with an Axelera Community account or with Axelera SSO, the desktop client only seems to show the Axelera SSO option, which is not possible for me of course. Am I missing anything here? How should a non Axelera employee login to the desktop app? Kind regardsRobbe

Did you know that wingman learns from your preferences and projects?   What’s your favourite feature?