Report should be standardized and versioned and classifiers should produce it...
@aroyphillips is already working on this.
Since Nov 26, 2025.
Assessment
This issue has not been assessed yet.
Description
Roy agreed to do this; he may have done it by the time this is assigned to him.
We want to define a JSON output for the "report" which comes out of each executtion of a classifier. The fields should be:
- Report Version: Semantic version string like "0.1.0"
- Classifier Name: One of fixed set of Classifer names
- Score/Class: text
- Confidence: floating point
- Image ID
- Dominant language
- Python
- Stars
- 3
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from PubInv/librecorder
-
[General] Review of paper 3May be free again @aroyphillips claimed this 298 days ago, and no pull request is open. Open
PubInv/librecorder#42 · 1 assignee ·
-
Make "dark_light" classifer product report in proper formatMay be free again @aroyphillips claimed this 318 days ago, and no pull request is open. Open
PubInv/librecorder#41 · 1 assignee ·
-
Make GUI use "sample Type" and "Classifier" registry....May be free again @Nipul12 claimed this 318 days ago, and no pull request is open. Open
PubInv/librecorder#39 · 1 assignee ·
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
PubInv/librecorder#38 ·
-
[GENERAL] Verison 0.1 of model report formatMay be free again @aroyphillips claimed this 319 days ago, and no pull request is open. Open
PubInv/librecorder#37 · 3 comments · 1 assignee ·
All issues in PubInv/librecorder
Similar issues
-
enhancement good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
python-version
Difficulty 1/5 Under an hour Newbie friendliness 88/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
Maintainers usually reply within 1 day
-
bug javascript P2-medium python release:v3.1
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
adrirubio/claude-deck#546 ·
Maintainers usually reply within 1 day
-
area: desktop area: website priority: P2 type: feature
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
appandflow/stim#3411 · 1 comment ·
Maintainers usually reply within 1 day