Hi, and thnx for your response.
Ok watch:
For Windows:
Hailortcli (HailoRT)
Windows Ubuntu WSL:
Hailo compiler
Hailo model zoo
Driving on:
I5 13e gen
7900xtx with the ROCm install.
Hailo-8 (wich goes on a raspberry pi is now in my PCIe board with a NVMe port m.2).
It installs and shows up in my pc not as a stranger but as the the driver says.
I made the scanners for data on Windows, wich does this:
Data samples for 20 minutes, and that goes for
It spits out in data model. After that i train it as a Network.h5, GPU.h5, CPU.h5.
After that i made from those 3 a combined model to h5.
Then i realized onnx and h5 could be a thingy so i made the h5 a .Keras.
Then i made the keras .onnx.
So what i dit is i putted that in the shared Ubuntu folder because Ubuntu and windows with the HAILO applications dont talk well bad pipelines.
Once done i tryed to make a has and from has to hef so that that i can script that the HAILO can interfere with my gpu and cpu like a captain on a ship telling them whats best for them to get their full potential.
I am stuck of making that kinda hef, i have made it once but that was on a hosted program from hailo in the suite but the suite is a very big bottleneck an needs his own OS that would be beautiful to throw that on WSL.
But for starters how the hell can i make a hef file with the compiler or model zoo i tryed endless options but none of them work very very annoying. I will show you one:
This is in Ubuntu WSL (II):
hailo optimize
–ckpt ~/hailo_env/combined_model.onnx
–model-script ~/hailo_env/model_script.alls
–output-har-path ~/hailo_env/optimized_model.har
–calib-set-path ~/hailo_env/calibration_data
–hw-arch hailo8l
–optimization-level 2
–compression-level 1
And this is a clean one:
hailo parser onnx /home/kevin/hailo_env/combined_model.onnx --output-har /home/kevin/hailo_env/combined_model.har --hw-arch hailo8l
One of the problems is that WSL cannot onder whatever conditions communicate, Windows with Ubuntu WSL. Why is that a problem? The compiler and model zoo cannot see the HAILO m.2 because it is in Windows…