Extract standalone pyro_predictor package#331
Open
MateoLostanlen wants to merge 8 commits intodevelopfrom
Open
Extract standalone pyro_predictor package#331MateoLostanlen wants to merge 8 commits intodevelopfrom
MateoLostanlen wants to merge 8 commits intodevelopfrom
Conversation
f6c519a to
d2ac0f5
Compare
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## develop #331 +/- ##
===========================================
- Coverage 80.19% 72.59% -7.61%
===========================================
Files 7 7
Lines 828 602 -226
===========================================
- Hits 664 437 -227
- Misses 164 165 +1
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The detection core (YOLO inference + temporal sliding-window state) was tightly coupled inside pyroengine, which depends on pyroclient, requests, and other
API-related libraries. This made it impossible to use the predictor in external code (evaluation scripts, custom pipelines, CI benchmarks) without pulling
in the full engine stack.
Changes
New package: pyro-predictor/
A self-contained Python package with minimal dependencies (numpy, pillow, onnxruntime, ncnn, opencv, tqdm — no pyroclient, no requests):
Both Predictor and Classifier accept a verbose=False parameter to suppress all log output (the package uses a named logger pyro_predictor.* instead of
configuring the root logger, following library best practice).