MétaCan
Menu
Back to cohort
Record W4300487085 · doi:10.26443/msurj.v4i1.76

Evolution of Algorithms to find Prime Numbers

2009· article· en· W4300487085 on OpenAlexaff
Maya Kaczorowski

Bibliographic record

VenueMcGill Science Undergraduate Research Journal · 2009
Typearticle
Languageen
FieldComputer Science
TopicComputational Physics and Python Applications
Canadian institutionsMcGill University
Fundersnot available
KeywordsPrime numberPrime (order theory)Prime factorPrime k-tupleMathematicsInteger (computer science)Prime timeNumber theoryArithmeticCombinatoricsComputer scienceAlgorithmDiscrete mathematics

Abstract

fetched live from OpenAlex

Prime numbers, and the deterministic formulas used to find them, have garnered considerable attention from mathematicians, professionals and amateurs alike. A prime number is a positive integer, excluding 1, whose only divisors are 1 and itself. For example, 23 is a prime number as it can only be divided by 1 and 23. A number that is not prime is called a composite number. While prime numbers under 100 are fairly abundant, they become less frequent and difficult to find in a systematic manner as the digits in the number increase since they do not appear to follow a predictable distribution. So why do researchers keep studying them? For over 150 years, mathematicians have attempted to uncover a deterministic formula to identify prime numbers. If such a formula existed, all numbers could be factored relatively quickly using computers. Paradoxically, much of electronic data today is encrypted by taking advantage of the fact that it is difficult and time consuming for a computer program to factor a large composite number. A formula to find all prime numbers would be a significant breakthrough in mathematics, but severely detrimental to data security.

Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.

How this classification was reachedexpand

Full frame machine prediction

Teacher imitation

Not calibrated prevalence, not ground truth. Human validation pending. The Gemma side is a direct model label for every work in the frame, read from the title-only record. The Codex side is a classifier learned from the 10,348 direct Codex labels and calibrated to design-weighted sample rates; fields without enough sample support carry no Codex call. Candidate is the union of the two sides; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels.

metaresearch head score (Codex)0.004
metaresearch head score (Gemma)0.039
Version: metacan-v3-hybrid-931329e0061cValidation status: machine_predicted_unvalidated
Candidate categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Bench or experimental · Consensus signal: none
GenreCandidate signal: Empirical · Consensus signal: none
Teacher disagreement score0.008
Threshold uncertainty score0.026

Distilled classifier scores by category (both heads)

CategoryCodexGemma
Metaresearch0.0040.039
Meta-epidemiology (narrow)0.0010.001
Meta-epidemiology (broad)0.0010.002
Bibliometrics0.0020.002
Science and technology studies0.0020.004
Scholarly communication0.0040.008
Open science0.0020.004
Research integrity0.0020.005
Insufficient payload (model declined to judge)0.0080.003

Machine scores (provisional)

The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.

Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.

Opus teacher head0.051
GPT teacher head0.379
Teacher spread0.328 · how far apart the two teachers sit on this one work
Validation statusscore_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from it

Classification

machine, unvalidated

Machine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.

The models applied no category: nothing in the taxonomy fit this work.
Study designBench or experimental
Domainnot available
GenreEmpirical

How this classification was reached, model by model and score by score, is at the end of the page under "How this classification was reached".

Quick stats

Citations0
Published2009
Admission routes1
Has abstractyes

Explore more

Same venueMcGill Science Undergraduate Research JournalSame topicComputational Physics and Python ApplicationsFrench-language works237,207