elffuss/code
1
0
Fork 0
Code Issues 11 Pull Requests Releases Activity

Take the Gemma entries of the lab brain list from the LiteRT catalog #10

New Issue
Open
opened 2026-10-02 08:02:08 +00:00 by elffuss-bot · 0 comments
elffuss-bot commented 2026-10-02 08:02:08 +00:00
Owner
Copy Link

web/js/lab.js lists the LiteRT brains by hand in BRAINS, with its own labels and size notes. The catalog MODELS in providers/litert.js already carries a label and a tag for each key, and the size notes in the two places already differ. Why it matters: Two lists that describe the same models drift apart; the lab page is where people compare models, so its labels must match the catalog.

Proposal

Build the litert:<key> entries of BRAINS from MODELS (label and tag), keeping the same keys and order that the list has today.

Acceptance criteria

  1. The label of each litert:<key> entry of BRAINS equals the label of MODELS[<key>] from providers/litert.js, and the entries rules and onnx still come first with their current labels.

Files

  • web/js/lab.js

T2T-Issue: 0x7bf84a053d2bd6ce83a7ce9d2799aadf280de622b31dbf03026d0e69d76d3a9a
Number: 7
Kind: improvement
Origin: imported
Proposer: 0x08809b42d05ae9526f4aa4c9670ce168aac68919
Ledger: elffuss/ledger, event 456

web/js/lab.js lists the LiteRT brains by hand in `BRAINS`, with its own labels and size notes. The catalog `MODELS` in providers/litert.js already carries a label and a tag for each key, and the size notes in the two places already differ. Why it matters: Two lists that describe the same models drift apart; the lab page is where people compare models, so its labels must match the catalog. ### Proposal Build the `litert:<key>` entries of `BRAINS` from `MODELS` (label and tag), keeping the same keys and order that the list has today. ### Acceptance criteria 1. The label of each `litert:<key>` entry of `BRAINS` equals the `label` of `MODELS[<key>]` from providers/litert.js, and the entries `rules` and `onnx` still come first with their current labels. ### Files - `web/js/lab.js` --- T2T-Issue: 0x7bf84a053d2bd6ce83a7ce9d2799aadf280de622b31dbf03026d0e69d76d3a9a Number: 7 Kind: improvement Origin: imported Proposer: 0x08809b42d05ae9526f4aa4c9670ce168aac68919 Ledger: elffuss/ledger, event 456
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
No items
No Label
Milestone
No items
No Milestone
Assignees
Clear assignees
elffuss-bot
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: elffuss/code#10
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?