| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
|
I've modified the system to simplify by removing some confusing key names like viameTrainingExe. Instead of having that separate key for the training exe everything is reliant on the viame cli so I upated all places where it is reference and the documentation for this as well. |
Sorry, something went wrong.
There was a problem hiding this comment.
Approving after I made some changes to remove the training vs the viame cli. So now everything uses the viame cli instea dof having a separate kwiver and training executable
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
Summary
Use `viame runner` (a thin wrapper that pre-loads VIAME's environment) instead of bare `kwiver runner` for pipeline execution and ONNX export, matching the runner used by the rest of the desktop pipeline tooling.
Changes vs main
`viame runner` is identical to `kwiver runner` from a pipeline-execution standpoint but already sources the VIAME setup script and resolves binary paths against the VIAME install, which removes a class of "binary not found" / partially-loaded-environment failures we hit on Windows and on minimal Linux installs.