use-the-sources-own-names

Solid

Use at Stage 06 and Stage 07 when writing up a reproduction, and any time you have given a reproduced quantity, equation, figure or sequence a name of your own. Covers why a correct reproduction under private names reads as a missing one, which names have to be carried, and where they have to appear.

AI & Automation 804 stars 25 forks Updated today NOASSERTION

Install

View on GitHub

Quality Score: 82/100

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

Skill Content

# A reproduction nobody can recognise is scored as one that did not happen You rebuilt the source's closed form and matched it on ninety-six of ninety-nine cases. In your report it is called the "GEO closed form", because that is what your module is named. The source calls it Equation 3. A reader looking for your verification of Equation 3 does not find one. This is the cheapest loss in a reproduction and the hardest to see from inside, because everything is correct. The work was done, the numbers agree, the figure is there. Only the labels are yours, and labels are the entire interface between what you did and what anyone asked for. ## Carry the source's names For every object you reproduce, the source's name for it appears in your report, in the sentence that reports your result: - **Equations and formulae** by the source's number. "We recover Eq. (3) to within 0.010 across 96 of 99 interfaces" — not "the GEO closed form agrees". Give your own name once, in parentheses, if you need it for the code. - **Named quantities, sequences and constants** as the source writes them. If the paper's series is the Mackay sequence and its own new sequence is 1, 13, 45, 117, 239, 431, those digits belong in your text. A reader checking whether you reproduced the sequence looks for the sequence. - **Figures** by the source's figure number. "Our Fig. 4 reproduces their Fig. 6d" is one clause and it converts an unlabelled plot into a verification. - **Methods and baselines** ...

Details

Author
tangxiangru
Repository
tangxiangru/AutoR
Created
5 months ago
Last Updated
today
Language
Python
License
NOASSERTION

Integrates with

Similar Skills

Semantically similar based on skill content — not just same category