Skip to content

docs: refresh README ML status, add data licences, drop stale screenshots - #22

Merged
Mani212005 merged 2 commits into
mainfrom
fm/digisim-t11-hygiene
Nov 14, 2026
Merged

Mani212005 merged 2 commits into
mainfrom
fm/digisim-t11-hygiene

Conversation

@Mani212005

Copy link
Copy Markdown
Owner

Intent

DigiSim is a neglected project. Pull up the latest changes in Linux. It is high time to start training the model for it. I have not been able to provide the data. Figure out, get the data, train a model, make improvements and fix that. Do not come to me until you absolutely need me.

Context: the scout report found that the only trained detector uses 12 gate-era classes and detects nothing on the transistor-first schematics the app now uses, that the transistor-level training data does not exist yet, and that the wire/net tracing assumes left-to-right gates. The work was split into tasks T1-T11; this change is T11 (repo hygiene): delete stale root screenshots, fix ml/.venv leftovers, update the README ML section so it no longer claims gate-only detection, note that Ultralytics is AGPL-3.0, and add a data licences section.

What Changed

  • Removed the four stale root screenshots (1st.jpg, 2nd.jpg, 3rd.jpg, 4th.jpg) and dropped the leftover ml/.venv/ line from .gitignore (the generic .venv/ rule already covers it).
  • README: added a "Machine Learning Status" section stating that the only trained detector uses the 12 gate-era classes and does not recognise transistor or supply symbols, that transistor-level retraining is in progress, and that weights are not in git. Reworded the YOLOv8 feature bullet to "schematic symbols" and linked it to the new section. Corrected the Python version references from 3.14 to 3.11+ (Docker image uses 3.12).
  • README: added a "Data and Licences" section with a table of the Roboflow gate dataset (CC BY 4.0 annotations), synthetic data, and the planned CGHD source. It also notes that Ultralytics YOLOv8/YOLO11 is AGPL-3.0 and that DINOv2 is Apache-2.0. The License section now says no LICENSE file exists yet, instead of claiming MIT.

Risk Assessment

✅ Low: Docs-only edits plus deletion of four unreferenced root screenshots; README claims (46 images/6 classes, zip and 51 Sampleimages tracked, Python >=3.11 with Docker 3.12, pipeline file names, AGPL note, MIT-intended wording) check out against the tree, and the earlier review decisions were applied.

Testing

The change has no runnable product surface (docs, a .gitignore line and deleted images). I confirmed README claims against the repo with read-only checks: ignore behaviour for ml/.venv, tracked file counts, data licence metadata, referenced paths, Python version statements and the missing LICENSE file. These were repository checks, not live runs of the product. I did not run the test suite, produce screenshots, or run the app.

  • Live validation: ⚠️ inconclusive - 0 of 3 scenarios driven live against the product
Scenario Result Live Evidence
README, .gitignore and screenshot deletion change no runtime behaviour, so no live-validatable surface ⏸️ untested no The diff is documentation, one .gitignore line and four deleted jpgs. No frontend, backend or ML code changed, so there is no running product behaviour to drive.
Removing the ml/.venv/ line from .gitignore still ignores ml/.venv ⏸️ untested no The prior payload recorded only a repository check with git (live=false), not a live run of the product, so it did not establish a live pass.
README data-licence and committed-data statements match what is tracked ⏸️ untested no The prior payload recorded only a repository file check (live=false), not a live run of the product, so it did not establish a live pass.
  • Outcome: ⚠️ 1 warning across 1 run (40.1s)

Pipeline

Updates from git push no-mistakes

✅ **intent** - passed

✅ No issues found.

✅ **Rebase** - passed

✅ No issues found.

✅ **Review** - passed

✅ No issues found.

⚠️ **Test** - 1 warning
  • ⚠️ live validation verdict: inconclusive (0 of 3 scenarios were driven live against the product); untested: README, .gitignore and screenshot deletion change no runtime behaviour, so no live-validatable surface, Removing the ml/.venv/ line from .gitignore still ignores ml/.venv, README data-licence and committed-data statements match what is tracked
  • Live validation: ⚠️ inconclusive - 0 of 3 scenarios driven live against the product
Scenario Result Live Evidence
README, .gitignore and screenshot deletion change no runtime behaviour, so no live-validatable surface ⏸️ untested no The diff is documentation, one .gitignore line and four deleted jpgs. No frontend, backend or ML code changed, so there is no running product behaviour to drive.
Removing the ml/.venv/ line from .gitignore still ignores ml/.venv ⏸️ untested no The prior payload recorded only a repository check with git (live=false), not a live run of the product, so it did not establish a live pass.
README data-licence and committed-data statements match what is tracked ⏸️ untested no The prior payload recorded only a repository file check (live=false), not a live run of the product, so it did not establish a live pass.
  • git check-ignore -v ml/.venv/x shows ml/.venv is still ignored by the general .venv/ rule after the .gitignore line was removed, and git ls-files ml/.venv returns nothing (repository check, not live)
  • ls *.jpg at the root finds nothing, so the stale screenshots are gone (repository check)
  • Counted tracked data: Sampleimages/ has 51 tracked files, My First Project.yolov8/ has 46 images, and My First Project.yolov8.zip is present, matching the README (repository check)
  • My First Project.yolov8/data.yaml lists 6 gate classes with CC BY 4.0, workspace cirzer, project my-first-project-yz9wf; the export README says it was exported on June 15, 2026 (repository check)
  • Every path the README references exists: the four pipeline stage files, agent_docs/ml-pipeline.md, ml/train.py, ml/evaluate.py, backend/.env.example (which sets MODEL_WEIGHTS_PATH), docs/deploy-vercel-render.md and backend/data_gen
  • Python 3.11+ and 3.12 claims match requires-python = ">=3.11" in backend/pyproject.toml and ml/pyproject.toml, and FROM python:3.12-slim in backend/Dockerfile
  • No LICENSE file exists, matching the reworded README ('intended MIT, no LICENSE file yet') per the recorded review decisions
  • The detector's 12-class vocabulary claim was not checked against a config; I only confirmed a JUNCTION class exists in the pipeline code
✅ **Document** - passed

✅ No issues found.

✅ **Lint** - passed

✅ No issues found.

✅ **Push** - passed

✅ No issues found.

…hots

Remove stale root app screenshots, correct the Python version claims that
came from a dangling ml/.venv, drop the redundant ml/.venv gitignore entry,
replace the gate-only detector claim with the current ML status, and add
data and third-party model licence notes (Ultralytics AGPL-3.0).
@vercel

vercel Bot commented Nov 14, 2026 •

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated
digisim Ready Ready Preview Nov 14, 2026 11:16pm UTC

@netlify

netlify Bot commented Nov 14, 2026 •

Copy link
Copy Markdown

✅ Deploy Preview for digisim canceled.

Name Link
🔨 Latest commit 74abb46
🔍 Latest deploy log https://app.netlify.com/projects/digisim/deploys/6af8ebad84581213d70d99e7

@Mani212005
Mani212005 merged commit 23741fa into main Nov 14, 2026
9 checks passed

This branch was successfully deployed

1 active deployment
Preview — 74abb465 Deployed Nov 14, 2026 by vercel[bot]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant