a-second-model-family-before-a-fifth-sample

Solid

Use at literature survey, study design, implementation and experimentation when the predictions come from running a pretrained checkpoint you picked off the shelf over each row — a language model that reads the text and answers, an encoder, any released artifact — rather than from fitting a model on the training rows, and especially when the next thing you planned is another sample, seed, temperature or voter from the checkpoint you already downloaded. Covers treating the set of checkpoints as an experimental axis with a deadline of its own, the best-single / oracle / best-vote measurement on your own labelled rows that decides whether to buy a better aggregator or a different model, and why a ceiling computed from your own predictions bounds your shortlist rather than the task.

AI & Automation 805 stars 25 forks Updated 2 weeks ago NOASSERTION

Install

View on GitHub

Quality Score: 82/100

Stars 20%
97
Recency 20%
90
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
80
License 10%
100
Description 5%
100

Skill Content

# Buy the second model family before the fifth sample of the first When a released checkpoint does the predicting rather than a model you fit, the largest single determinant of the score is which checkpoints are on disk *and how unlike each other they are*. This skill is about the set, not about picking the best single member of it. That decision usually gets made in the first ten minutes, from one search, before anything has been measured — and then it is never revisited, because every later hour goes on prompts, decoding and voting *inside* the set it created. Measured on one run of this shape: two checkpoints were on disk eight minutes in, and ten hours later they were still the whole pool — a 1.5B and a 7B of one released family. A second agent on the same task with the same clock kept adding checkpoints for two and a half hours, finished with six across five unrelated lineages, and beat it by 4.7 accuracy points. ## Another sample of the same checkpoint is not another candidate Decodes of one checkpoint at different seeds and temperatures fail on the same rows, so they add votes without adding information. On that run's own 200 labelled held-out rows, six decodes of its two checkpoints scored between 144 and 192; the best of all 63 subset votes was 194; the oracle over all six — count a row correct if *any* decode gets it — was 196. What that pool was actually worth is visible only afterwards, from the withheld labels, and it is the reason this skill exists: on the ...

Details

Author
tangxiangru
Repository
tangxiangru/AutoR
Created
6 months ago
Last Updated
2 weeks ago
Language
Python
License
NOASSERTION

Integrates with

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Solid

a-model-you-can-audit-is-not-a-model-that-scores

Use at study design and implementation when choosing between a method you can validate quickly and a stronger one you are not sure you can afford. Covers pricing the expensive method with a measurement instead of an impression, the go/no-go that has to be written before the clock is spent, and why the safe choice is only safe on the axes nobody is grading.

805 Updated 2 weeks ago
tangxiangru
AI & Automation Solid

a-combination-is-not-the-candidate-set

Use once more than one trained artifact exists on disk -- two checkpoints, two seeds, two architectures, a continuation run -- and something is deciding which of them, or which combination of them, writes the predictions file. Covers the ballot that lists every artifact as a submission on its own before any blend, re-running it whenever a training job finishes, the known-bad canary that tests the objective, and persisting a rejected candidate's predictions.

805 Updated 2 weeks ago
tangxiangru
AI & Automation Solid

a-throughput-number-belongs-to-the-runtime-not-the-model

Use at the survey, study design and implementation stages when the task needs a pretrained model, solver or library you must download and run on the machine you were given, and the first configuration you try is too slow to cover the split in the time you have. Covers why the seconds-per-item you just measured is a property of the runtime, the workload and the machine as much as of the component, which field to change before demoting it, re-asking the component question after you fix the runtime, and checking that your fallback still has the property you picked the original for.

805 Updated 2 weeks ago
tangxiangru