chemistry-accuracy-and-cost-for-every-module-you-swap-in

Solid

Use at study design, through experimentation and again at analysis when the method under test is a drop-in replacement for a standard layer — a different basis, kernel, activation family or transform — and the source claims the replacement is both more accurate and cheaper. Covers giving every alternative module a cell in the accuracy column and in the cost column, fixing one matching convention across both, and dividing the runtime by the invariant already sitting in your own results file before you publish a contradiction of the source's ratio.

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

Install

View on GitHub

Quality Score: 85/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

# A module you only timed is half an arm When a study's contribution is a module swapped into an existing architecture, its claim is almost always joint: the replacement is *more expressive* and it is *cheaper*. That is one claim with two columns, and it is answered by one table in which every module the source compares — the proposed one, each alternative it is compared against, and the conventional layer being replaced — carries a value in both. An arm that appears only in the timing table cannot answer the accuracy half. It is also the cheapest number in the whole study: the arm is already implemented, the graphs are already featurised, and it is one training run from a score. Build it once, then run it through the same loop, the same split and the same estimator as the proposed module, and give it its row. `rebuild-the-sources-headline-table-row-for-row` owns which columns have to exist at all. This is about what has to be inside each of them once they do. ## One matching convention, stated, across both columns Equal width and equal parameter count are different experiments. A basis that holds 2K coefficients where a linear layer holds one is, at equal width, a bigger model; at equal parameters it is a narrower one. Decide which match the comparison is made at, write it in the caption, and use the same match on both sides of the joint claim. A run that compares accuracy at matched parameters and cost at matched width has measured two different comparisons and answered...

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

chemistry-a-cut-variant-takes-its-analyses-with-it

Use at literature survey, at study design, at every descope decision and again at writing, when the source's method is a family — the same module dropped into two or more backbones, or one architecture published in several named variants — and you are about to run only one of them. Covers listing which of the source's downstream analyses were produced from which variant before any of them is cut, shrinking a variant rather than deleting it, and what a saliency map, case study or ablation computed on the surviving variant is and is not evidence for.

805 Updated 2 weeks ago
tangxiangru
AI & Automation Solid

a-comparison-you-never-run-defaults-to-your-preference

Use at hypothesis drafting, study design and implementation when the task could plausibly be attacked by more than one family of method - hand-built features fed to a fitted model, a network trained on the raw structure or sequence, a pretrained backbone, retrieval - and your hypothesis list mostly compares variants inside one of them. Covers separating the hypotheses that would change what you build from the ones that would change an argument, requiring code on both sides of a family claim, running the comparison at a budget you actually have and reading each side's slope rather than its level, and demoting a comparison you will not run into a priced assumption.

805 Updated 2 weeks ago
tangxiangru
AI & Automation Listed

math-equal-effort-baselines-and-knob-sweeps

Use at study design when the source names competing algorithms and they are about to become a related-work paragraph instead of arms. Covers running every named baseline at equal tuning effort, and sweeping the parameter you claim credit for.

805 Updated 2 weeks ago
tangxiangru