Zain Dana Harper Map

Elements Swatches Studies Site index

Findings F308 Computing and mathematics, Method and statistics found 2026-10-31

Checking 213 OEIS recurrence conjectures against their b-files finds one failure, already known

We tested a random sample of conjectured recurrences in the On-Line Encyclopedia of Integer Sequences against the long term lists stored beside them. One of 213 failed, and the entry itself had recorded that failure in 2016, so the sweep produced no new counterexample.

Tier
D, honest null
Outcome
honest null
Rung
hypothesis
Verdicts
2 passed, 1 failed
Standing
narrowed in part: sampling and control, F422
Corrections
2, latest 2026-11-09
Version
v2, 2026-11-09
Redo it
Reproduce

Download PDF 486 KB BuildTeX source F308.bld

What this means for a reader

When an OEIS entry says "Conjecture" in front of a simple recurrence, the line has usually held far past the terms it was fitted on. In our sample, 212 of 213 such lines held for a median of 967 further terms, and the one that failed had already been marked false by a later contributor. Read such a line as a well-tested guess. It still has no proof behind it, and holding for a thousand more terms does not supply one.

Objection

The lines were fitted to data, so passing is what a correct fit does, and a high-order fit can pass by construction when the b-file is short relative to its order. A passing line stays a conjecture with more range.

What would change the call. Our publication register records no condition that would raise or overturn this call.

From the paper's first stated limitation; our register records no separate objection.

Abstract

Many entries in the On-Line Encyclopedia of Integer Sequences carry a line such as "Conjecture: a(n) = 3*a(n-1) - 3*a(n-2) + a(n-3)". Most such lines were found by fitting the terms known at the time, and the b-file stored beside the entry often lists hundreds or thousands more. We asked how often these conjectures fail on their own b-files and whether the failures are data errors or counterexamples. From the public OEIS data, 23,883 entries mention a conjecture and 1,179 have a line our parser accepts; we drew a random 500 and tested every line that its b-file extends by at least 30 terms. One of 213 tested conjecture lines failed on its b-file, 0.47 percent, with a 95 percent Wilson interval of 0.08 to 2.6 percent. The one failure, A031740, holds for 64 indices and fails at n = 65, and the entry has recorded the conjecture as false since 2016, so the sweep found no new counterexample. Planted errors were caught in 212 of 212 passing lines, and equations applied to other entries' terms passed at a mean rate of 0.005. The sampling frame changed after the preregistered route failed, and the change is recorded. The result says the check is cheap and, on this kind of line, low in yield.

c1 observed, evidence for claim 1
The numbers in claim 1
213; 0.47; 95; 0.08; 2.6 matches the result file, 2026-11-09
Chart 3
Share of tested conjecture lines that failed on their own b-file.
Basis
observed: measured in this study, with a result file
c2 observed, evidence for claim 2
The numbers in claim 2
031740; 64; 65; 2016 matches the result file, 2026-11-09
Chart 1
From every entry that mentions a conjecture down to the one line that failed.
Basis
observed: measured in this study, with a result file
c3 observed, evidence for claim 3
The numbers in claim 3
212; 0.005 matches the result file, 2026-11-09
Chart 2
Can the check tell a right equation from a wrong one?
Basis
observed: measured in this study, with a result file

Introduction

The OEISDefinition: OEIS mathematics (reference databases) The On-Line Encyclopedia of Integer Sequences, a public database of number sequences in which each entry carries the first terms, formulas, comments and links contributed by many people. Excludes a peer-reviewed journal; a line in an entry is a contribution, and a conjecture line in it carries no proof. full definition is a public database of integer sequences, online since 1995 and holding over 300,000 entries when Sloane described its recent history in 2018 [2]. Each entry lists the first terms of a sequence in a short data section, with formulas, comments and references contributed by many people. Beside most entries sits a b-fileDefinition: b-file the OEIS A text file stored beside an OEIS entry that lists the sequence's index and term pairs much further than the entry's own data section, often to thousands of terms. Excludes the entry's data section, which holds only the first few dozen terms. full definition, a plain list of index and term pairs that often runs to thousands of terms.

Some entries carry a conjecture lineDefinition: conjecture line the OEIS, our usage A comment or formula line in an OEIS entry that states an equation for the sequence and labels it a conjecture. Most were found by fitting the terms then known. Excludes a line marked as proved, and a statement with no equation. full definition: an equation for the sequence, offered without proof. Many are a linear recurrenceDefinition: linear recurrence mathematics (combinatorics) An equation that gives each term of a sequence as a fixed weighted sum of a set number of earlier terms, possibly with terms in n. Here with integer coefficients. Excludes an equation with a product of earlier terms, and an equation with coefficients that are not integers. full definition with integer coefficients, found by fitting the terms then listed. Fitting of this kind is a standard method in computer algebra. Kauers and Koutschan [3] describe guessing a recurrence from finitely many terms by linear algebra, note that the overdetermination of the linear system is one source of trust in a guess, and show how to guess from fewer terms by restricting the coefficients. In a later search across the OEIS [4] they found conjectured recurrences for sequences not previously known to satisfy one, proved some, and showed that a recurrence exists for others without proving the guessed one.

Our question was smaller. The b-files already hold the data a mechanical check needs. We asked what share of conjecture lines fail on their own b-files, and whether each failure is a data error or a true counterexampleDefinition: counterexample mathematics (logic) A single case where a general statement is false. One is enough to refute a conjecture. Excludes a term that disagrees because the data are wrong. full definition. The decision it informed was whether such lines are worth a routine check as a cheap source of counterexamples, and how to read one when it appears in our own work. Our searches found the guessing literature above and no published sweep of this exact kind; that is what the searches returned, and it does not show that none exists.

Preregistration and design

The preregistrationDefinition: preregistration research method (metascience) A dated written plan for a study, fixed and hash-locked before any result is seen: the question, the data, the statistic, the controls, the forecasts and the kill conditions. Excludes a plan revised after looking at the outcome, and a protocol written only for the record after the run. full definition was written and hash-locked on 31 October 2026, before any entry was sampled beyond one probe request that returned an unrelated entry. It names the sampling route, the parser rules, the definition of tested and of failed, the planted errors, the control, the forecasts and the kill conditions.

Kill conditions, without discretion:

  • The run is voidDefinition: void research method (our usage) The verdict of a run whose planted check failed or whose sample fell below its stated minimum. It says nothing for or against the claim. Excludes a null result, which comes from a working instrument. full definition if fewer than 99 percent of planted errors are caught, if fewer than 100 lines are tested, or if the real pass rate is at or below the control's 95th percentile.
  • A failure counts only after a second check that the failing term is not a known b-file error.
  • Nothing here proves the passing recurrences; a passing line stays a conjecture with more range.

Each kill conditionDefinition: kill condition research method (our usage, after Popper's falsification) A rule written in the preregistration that, when met, decides against the claim with no room for judgement after the run. Excludes reasons found after the run for setting a result aside. full definition and forecast became a rule set whose pass or fail is a verdictDefinition: verdict research method (our usage) The pass or fail of one preregistered rule set against the run's numbers, read off by code. Excludes an interpretation written after reading the numbers. full definition read off by code.

The locked plan sampled entries through the OEIS search pages at random offsets. That route returned only 10 entries, because the site asks for a sign-in past the first 100 search results, and we did not work around it. The first run tested 2 lines and was void under the first kill condition. Having seen only those 2 lines, both passing, we changed the sampling frameDefinition: sampling frame survey statistics The list from which a sample is drawn. A result describes the frame, so a change of frame changes what the result is about. Excludes the sample itself. full definition: the public OEIS data repository, every entry with a parsable conjecture line, then a seeded random 500. The change is recorded as a deviationDefinition: deviation research method (metascience) A dated, recorded change from the preregistered plan, stated with its reason and with what had been seen when it was made. Excludes a change made silently, and a change made after seeing the outcome it would affect without saying so. full definition with its reason and what had been seen. The new frame is wider than the locked one, and the second run used the same locked plan, rules and forecasts.

Data and provenance

The data are the OEIS entries from the public oeis/oeisdata repository and the b-files from oeis.org [1], retrieved on 31 October 2026. OEIS content is licensed CC BY-SA 4.0 under the OEIS End-User License Agreement. We used it as data for checks; this paper reports counts and quotes one entry's conjecture and comment lines with attribution.

Of all entries, 23,883 mention a conjecture and 1,179 have a conjecture line our parser accepts. The seeded random 500 entries held 531 lines that mention a conjecture and a term a(n), and 512 of those parsed. Only about 5 percent of the entries that mention a conjecture had a line our parser accepts: 1,179 of 23,883. The result therefore describes simple linear recurrences, not OEIS conjectures in general.

c4 observed, evidence for claim 4
The numbers in claim 4
5; 1,179; 23,883 matches the result file, 2026-11-09
Chart 1
From every entry that mentions a conjecture down to the one line that failed.
Basis
observed: measured in this study, with a result file
Diagram 1. From every entry that mentions a conjecture down to the one line that failed. 1,179 of 23,883 entries (4.9 percent) had a line the parser accepts; 213 lines from a random 500 were tested and 1 failed.
  1. data23,883 entries mention a conjectureCounted in the public OEIS data repository.
  2. measurement1,179 have a parsable line4.9 percent. The parser accepts an equation in n and earlier terms with integer coefficients, so the result describes simple linear recurrences.
  3. data500 entries drawn at randomSeeded draw. They held 531 conjecture lines, and 512 parsed.
  4. measurement213 lines testedTested means the b-file (the entry's long list of terms) runs at least 30 indices past the entry's data section. Median reach: 967 terms past it.
  5. planted check212 of 212 planted errors caughtEach passing equation had its first integer coefficient raised by one and was run again.
  6. controlWrong-entry equations pass at 0.005Each equation applied to another entry's terms, 200 draws of 30. This is the chance level of the test.
  7. already known1 line failed: A031740Held for 64 indices, failed at n = 65. The entry has recorded the conjecture as false since 2016.
n
23,883 entries that mention a conjecture
Supports
claim 4, claim 2

Read from frame_counts.json. SHA-256 of the run's file 06094824e262954032a7586b66fae734f69e910908b0a53fcafbce4261290941, published unchanged.

Read from result.json, run 20261031T223144Z. SHA-256 of the run's file d2b554ef618721f326ca8652c7db757b6bda7fa4e3a2cde013ace093c17929ea and of the published copy efbeff7d747ce414a6903fa2f6fe813b55873f265ef350236cc81a9f19d60d6b. In the copy, file paths are cut to the file name and the layout (indentation, line endings) may differ; every value is the same.

Methods

Parsing

A line was parsed only if it states an equation in n and earlier terms a(n−k) with integer coefficients. A pattern match finds the candidate equation, and a parser whitelistDefinition: parser whitelist computer science (parsing) A rule that turns each line into a syntax tree and accepts it only if every part is on a fixed list: integers, n, the terms a(n-k), addition, subtraction, multiplication and powers. Excludes any line that needs division, sums, named functions or words to state. full definition accepts it only if every part of its syntax tree is an integer, n, a term a(n−k), addition, subtraction, multiplication or a power. Anything else was skipped and counted.

Testing

For each sampled entry, the first conjecture line that parsed and qualified was tested; at most one line per entry was tested. A line qualified when the b-file holds at least 30 more terms than the entry's data section and the equation can be evaluated at 10 or more indices. The equation was evaluated at every index in the b-file's range where all the terms it needs exist. A line fails if its two sides differ at any such index; the first failing index and the number of indices it held for were recorded. This left 213 tested lines, with a median of 967 b-file terms beyond the data section.

The failure rate

With k failures among N tested lines, the failure rate is f=k/N. Its Wilson intervalDefinition: Wilson interval statistics A 95 percent interval for a proportion, found by inverting the score test. It stays inside 0 to 1 and behaves well when the count is small or near zero. Excludes the simple interval of the proportion plus or minus 1.96 standard errors, which fails near zero. full definition [5] at z = 1.96 has centre c and half-width w:

D=1+z2N(1)
c=1D(f+z22N)(2)
w=zDf(1−f)N+z24N2(3)

Controls and planted checks

The planted checkDefinition: planted check research method; called a positive control in experimental science Data built so that the right answer is known, run through the same analysis before the real data, to show that the analysis can see the effect when it is there. Excludes any check made on the real data, which cannot show what the analysis misses. full definition raised the first integer coefficient of each passing equation by one and ran the check again. A planted line should fail. Of the 213 tested lines, 212 passed, so 212 planted versions were built. All 212 were caught.

Chart 2. Can the check tell a right equation from a wrong one? Real lines pass at 0.995 and every planted error is caught, while equations run on another entry's terms pass at 0.005: the check separates right from wrong.
Real lines that pass on their own b-file
0.995 (212 of 213)
Equations that pass on another entry's terms
mean 0.005; draws 0 to 0.033
Planted errors caught
1.00 (212 of 212)

share of lines (0 to 1)

  • Real conjecture lines
  • Cross-entry control
  • Planted errors
n
213 tested lines; 212 planted versions of the passing lines; 200 control draws of 30 equations
Units
share of lines, 0 to 1
Interval
Whisker on the control row: 5th to 95th percentile of the draws. The other two rows are single counts.
Baseline or control
Cross-entry control: each equation applied to a different, randomly chosen entry's terms
Set in advance
Planted errors caught at least 0.99; real pass rate above the control's 95th percentile (0.033)
Planted check
Held: 212 of 212 caught
Supports
claim 3
Data behind chart 2 7 rows
QuantityValue
Real pass rate0.9953
Planted errors caught212 of 212
Control mean pass rate0.0048
Control 5th percentile0.000
Control 95th percentile0.033
Control draws200
p from draws0.005

Read from result.json, run 20261031T223144Z. SHA-256 of the run's file d2b554ef618721f326ca8652c7db757b6bda7fa4e3a2cde013ace093c17929ea and of the published copy efbeff7d747ce414a6903fa2f6fe813b55873f265ef350236cc81a9f19d60d6b. In the copy, file paths are cut to the file name and the layout (indentation, line endings) may differ; every value is the same.

The cross-entry controlDefinition: control statistics and experimental design A version of the data with the structure under test removed (for example shuffled or pooled), scored the same way as the real data, so the real score has something to beat. Excludes a comparison with a different dataset or with a published number. full definition applied each equation to a different, randomly chosen entry's terms, up to index 200. One draw takes 30 equations at random, applies each to another entry's terms, and records the share that pass. This share is the pass rate of an equation on a sequence it was not written for, the chance level of the test. Over 200 draws the mean share was 0.0048, and the 95th percentile of this null distributionDefinition: null distribution statistics The spread of scores a control gives over many random draws. Its 95th percentile is the bar a real score must clear. Excludes a theoretical distribution assumed rather than drawn from the data. full definition was 0.033, one equation in 30.

The real pass rate, 0.995, was above every draw. The p value from drawsDefinition: p value (from draws) statistics The share of control draws scoring at or above the real score, with one added to the count and to the number of draws, so it is never zero. Excludes a p value from a textbook formula that assumes a distribution. full definition is

p=k+1n+1(4)

with k the number of draws at or above the real pass rate and n the number of draws. Here k = 0 and n = 200, so p = 0.005, the smallest value 200 draws can give.

Results

Figure 1 follows the counts from the whole corpus to the one failure.

One of 213 tested conjecture lines failed on its b-file, 0.47 percent, with a 95 percent Wilson interval of 0.08 to 2.6 percent. Figure 2 places the rate against the forecast of 4 percent and the preregistered 1 percent rule.

Chart 3. Share of tested conjecture lines that failed on their own b-file. 1 of 213 lines failed, 0.47 percent (interval 0.08 to 2.6), below the forecast of 4 percent; the interval spans the 1 percent rule.
Lines that failed
0.47 percent; 0.08 to 2.6

percent of tested lines that failed (lower is fewer wrong conjectures)

  • 95 percent Wilson interval (a range for a share that stays valid when the count is small)
  • rule set in advance, 1 percent
  • forecast, 4 percent
n
213 tested conjecture lines from 500 sampled entries
Units
percent of tested lines whose equation is false at some index of the b-file; lower means fewer wrong conjectures
Interval
95 percent Wilson interval (a range for a share that stays valid when the count is small)
Baseline or control
Forecast written before the run: 4 percent
Set in advance
Failure rate above 1 percent, set in advance; not met, since the rate is 0.47 percent
Planted check
Held: 212 of 212 planted errors caught
Ruled out
A failure rate above 2.6 percent among simple linear recurrence conjectures of this kind (upper end of the interval)
Supports
claim 1
Data behind chart 3 7 rows
QuantityValue
Lines tested213
Lines that failed1
Failure rate0.47 percent
Wilson interval, lower end0.08 percent
Wilson interval, upper end2.61 percent
Rule set in advanceabove 1 percent
Forecast4 percent

Read from result.json, run 20261031T223144Z. SHA-256 of the run's file d2b554ef618721f326ca8652c7db757b6bda7fa4e3a2cde013ace093c17929ea and of the published copy efbeff7d747ce414a6903fa2f6fe813b55873f265ef350236cc81a9f19d60d6b. In the copy, file paths are cut to the file name and the layout (indentation, line endings) may differ; every value is the same.

The failing line is in entry A031740. Its conjecture, contributed by Colin Barker on 30 September 2012, reads:

a(n)=n(961n+1)(5)
a(n)=3a(n−1)−3a(n−2)+a(n−3)(6)

The entry's data section has 32 terms and its b-file 10,000. The one failure, A031740, holds for 64 indices and fails at n = 65, and the entry has recorded the conjecture as false since 2016, so the sweep found no new counterexample. The stored copy of the entry carries a comment by Chai Wah Wu dated 19 June 2016: the conjecture is false, and 3940288 is a term not of the form m(961m+1). The preregistration asked for a second code path before a failure counts; the result file records no such rerun. The check by hand was reading this comment, which confirms the failure is a true counterexample and not a b-file error.

Table 1 gives the counts and rates.

Table 2 sets the forecasts written before the run against the outcomes.

Discussion

The sweep shows that a mechanical check of OEIS conjecture lines is cheap: the analysis took about 6 seconds once the data were stored. On simple linear recurrences it is also low in yield. The lines held at a rate of 99.5 percent, the failure rate came in an order of magnitude under the forecast, and the single failure had been caught by a contributor four years after it was posted.

Two features of the lines explain much of this. They were fitted to data, so passing on further terms is what a correct fit does. And a recurrence of order d fitted to a few more than d terms is close to determined by them, so the guess is either right or wrong in a way that shows quickly; A031740's conjecture failed just past twice the length of its data section. Kauers and Koutschan [3] point to the same property, overdetermination, as a source of trust in a guessed recurrence. Our pass rate is a measurement of how well that trust held on one class of OEIS line.

The more interesting conjectures are the ones our parser skipped: 95 percent of the entries that mention a conjecture state something our whitelist cannot read; we did not classify what those lines say. A sweep of those would need a different checker for each kind of line.

Limitations

  • The lines were fitted to data, so passing is what a correct fit does, and a high-order fit can pass by construction when the b-file is short relative to its order. A passing line stays a conjecture with more range.
  • Only about 5 percent of conjecture entries parse under our rules, so the rate describes simple linear recurrences with integer coefficients.
  • Many lines come from a few contributors, so the rate also describes their habits.
  • The sampling frame changed after the locked route failed. A later review of our ledger marked this as narrowing the claim. The new frame was chosen after seeing 2 lines, both passing.
  • The preregistered second code path for a failure was not recorded; the single failure was confirmed by the entry's own comment.
  • Scoring was by our own code and was not blind.

Evidence

Honest null. One failure in 213 tested lines, 0.47 percent; the 95 percent Wilson interval runs to 2.6 percent, so failure rates above that are ruled out for lines of this kind.

Figures

These are the paper's own figures, numbered as in the PDF, and each "Figure" reference in the text points here. The charts on this page redraw the same results from the result files and carry their own numbers.

Seven horizontal bars on a log scale falling from 23,883 entries to one failed line
Figure 1. From the whole OEIS corpus to the one failing line. The first two counts are from the frame count file; the rest are from the run's result file.
A diamond at 0.47 percent on a bar from 0.08 to 2.6 percent, with dashed lines at 1 and 4 percent
Figure 2. Failure rate with its 95 percent Wilson interval, against the 1 percent rule and the preregistered forecast of 4 percent. Drawn from the run's result file and the preregistration.

Tables

Table 1. Counts and rates from the run.
QuantityValue
Entries mentioning a conjecture23,883
Entries with a parsable conjecture line1,179
Entries sampled500
Conjecture lines in the sample, parsed531, 512
Lines tested213
Median b-file terms beyond the data section967
Lines that failed1 (A031740, first failure at n = 65)
Failure rate, 95% Wilson interval0.47 percent, 0.08 to 2.6 percent
Planted errors caught212 of 212
Cross-entry pass rate, mean and 95th percentile0.0048, 0.033
Real pass rate, p from 200 draws0.995, 0.005
Table 2. Forecasts fixed in the preregistration against what the run gave.
QuantityForecastOutcome
Lines parsed300512
Lines tested150213
Failure rate0.040.0047
Pass rate0.960.995
Planted errors caught1.01.0
Cross-entry pass rate0.001mean 0.0048, 95th percentile 0.033
Share of failures from data errors0.50 of 1
At least one failure not from a data errorprobability 0.5one, already recorded in the entry; none new

Appendix A. The preregistered verdicts

Each verdict is a set of rules written before the run. A verdict passes only when every rule holds. Values are read from the run's result file. The first three rules are shared by all three verdicts.

Table 3. Preregistered verdicts and the rules that decided each one.
VerdictDeciding ruleValueHolds
Instrument works (not void)planted errors caught at least 0.99; at least 100 lines tested; pass rate above the control's 95th percentile (0.033)1.0; 213; 0.995yes
Any failurethe three rules above, and at least one failure1yes
Failure rate above 1 percentthe three rules above, and failure rate above 0.010.0047no
First run, search-page framethe instrument rules2 lines testedno (void)

What lowers it

  • scoring Scored by code and by the agent that ran it; self-graded. from our publication register, on who scored it
  • blinding Not blind, as the paper's limitations state. from the paper's Limitations
  • imprecision One failure in 213 tested lines, 0.47 percent; the 95 percent Wilson interval runs to 2.6 percent, so failure rates above that are ruled out for lines of this kind. from the bound stated under Evidence
  • depth of reading The cited literature was read at the level of abstracts, arXiv pages and search summaries; full texts were not read. from the Verified section

What holds it up

  • preregistration Preregistered and hash-locked before the run (sha256 9736ef8a). from the Reproduce section

Where the claim stands

  1. lead
  2. hypothesis
  3. thesis
  4. conjecture
  5. theorem
  6. law candidate
  7. killed

A preregistration with pass-or-fail rules is on file, which this rung needs. The next rung needs a named rival reading beaten by a decisive observation, and none is on file. Tier D: A low-cost sweep that mostly confirms the entries it tested.

Trail

Versions

  1. v2 2026-11-09, paper version 1.0, first published PDF sha256 1cd38685d6935293
  2. v1 2026-10-31, entered in the findings ledger

Corrections

  1. 2026-11-09 wording found by the publication pass

    The cross-entry control is described here as the code runs it, 30 equations per draw, each applied to another entry's terms; an earlier summary of ours described it as 30 terms at a time.

  2. 2026-10-31 scope found by a review of our findings ledger

    A review of our ledger recorded that the sampling changed after the search route refused requests past 100 results without sign-in, and that fitted lines pass by construction while only 5 percent of conjecture entries parse. now Both narrow the claim and are stated here.

Standing, and the ledger entries it rests on

  1. 2026-10-31 narrowed in part F422

    Set by hand from findings ledger entry F422, dated 2026-10-31: sampling and control. Rests on findings ledger, F422 correction pass.

Each correction is a dated note; the findings ledger is never rewritten, and a note governs where it differs.

Ledger and version dates up to publication are local dates in US Pacific time. Clock times in the text are UTC, seven or eight hours ahead, so a lock or a run stamped just after midnight UTC belongs to the previous local day. Corrections from 14 November 2026 on are dated in UTC.

References

  1. The OEIS Foundation. The On-Line Encyclopedia of Integer Sequences, entries and b-files, and the oeis/oeisdata repository. Retrieved 31 October 2026. Licence CC BY-SA 4.0. https://oeis.org run here Licence: as stated in the paper's data section used in Data and provenance
  2. Sloane, N. J. A. (2018). The On-Line Encyclopedia of Integer Sequences. Notices of the American Mathematical Society 65(9), 1062-1074. doi:10.1090/noti1734. arXiv:1805.10343 abstract or summary, 2026-11-09: abstracts, arXiv pages and search summaries; full text not read used in Introduction
  3. Kauers, M. and Koutschan, C. (2022). Guessing with little data. Proceedings of ISSAC 2022, 83-90. arXiv:2202.07966 abstract or summary, 2026-11-09: abstracts, arXiv pages and search summaries; full text not read used in Introduction, Discussion
  4. Kauers, M. and Koutschan, C. (2023). Some D-finite and some possibly D-finite sequences in the OEIS. Journal of Integer Sequences 26, article 23.4.5. arXiv:2303.02793 abstract or summary, 2026-11-09: abstracts, arXiv pages and search summaries; full text not read used in Introduction
  5. Wilson, E. B. (1927). Probable inference, the law of succession, and statistical inference. Journal of the American Statistical Association 22(158), 209-212. doi:10.1080/01621459.1927.10502953 abstract or summary, 2026-11-09: abstracts, arXiv pages and search summaries; full text not read used in Methods

Cited by later findings

  • F422 narrowed in part, sampling and control, 2026-10-31 (record findings ledger, F422 correction pass). A later review of our ledger recorded an error and a control that could not fail: the sampling changed after the search route refused, and fitted lines pass by construction.

Reproduce

Data

  • The OEIS Foundation. Licence: as stated in the paper's data section. https://oeis.org

Preregistration

sha256 9736ef8a01a18ddaa94949f06de0b127eb9bdc9085bf9265fbb1d33a061f9d37
plan f8fbd127e431e832302cdd548c974029630a778f7c14125e20711b5a5ffb045f

Steps

  1. Data: the public oeis/oeisdata repository and the b-files from oeis.org (CC BY-SA 4.0).
  2. Find every entry with a comment or formula line that contains "Conjecture" and a term a(n); keep entries with a line that the whitelist accepts; draw a seeded random 500.
  3. For each sampled entry, test the first qualifying line: at least 30 b-file terms beyond the data section and at least 10 indices where the equation can be evaluated. Record the first failing index.
  4. Compute the Wilson interval, eqs. 1 to 3. Raise the first integer coefficient of each passing equation by one and rerun. Build the cross-entry control from 200 draws of 30 equations and compute eq. 4.
  5. Preregistration SHA-256: 9736ef8a01a18ddaa94949f06de0b127eb9bdc9085bf9265fbb1d33a061f9d37. Plan SHA-256: f8fbd127e431e832302cdd548c974029630a778f7c14125e20711b5a5ffb045f. Run 20261031T223144Z; the earlier void run is 20261031T220825Z.

Cost. The analysis took about 6 s and the control under 1 s on one desktop CPU, after the data were downloaded. The study was not re-run for this paper.

Downloads

The PDF is typeset by BuildTeX from F308.bld, which is written from the same source as this page. The receipt records the source's SHA-256 and the PDF's (1cd38685d693), so anyone can rebuild it and compare. The copy here has its hidden author field blanked, as the site does for every file it publishes; blank the same field in a rebuild before comparing. The name stays on the first page.

Verified

Verified on 2026-11-09. On 9 November 2026 the frame counts (23,883, 1,179 and 500) were re-read from the frame count file, and the 531 lines, 512 parsed and 213 tested, the median of 967 terms, the single failure with its first failing index of 65 after 64 indices, the data and b-file lengths, the Wilson interval, the 212 of 212 planted catches, the cross-entry mean, percentile and p value, and the three verdicts were re-read from the run's result file. They match the findings ledgerDefinition: findings ledger our records The append-only, dated list of every result we have recorded, numbered F1, F2 and on. Corrections are added as new dated lines and old entries are never rewritten. Excludes a curated list of successes. full definition. The 2012 conjecture and the 2016 comment marking it false were read in the stored copy of entry A031740. The preregistration's SHA-256 matches the hash recorded in the result file and in the lock file. Both figures were drawn by a script that reads only the result file, the frame count file and the preregistration.

Not checked. The study was not re-run for this paper. The literature was found by searches run on 9 November 2026 and read at the level of abstracts, arXiv pages and search summaries; the full texts were not read.

Terms on this page

Each term is defined where it is first used on this page. Each name below opens its entry in the findings glossary, which lists every page that uses it.

To report an error, name the finding, the claim number and the source on the Work page, which gives the address. Accepted corrections join the Trail with their date.