MétaCan
Menu
Back to cohort
Record W1792129892

Towards the profiling of scientific software for accuracy

2011· article· en· W1792129892 on OpenAlex

Why this work is in the frame

A frame that forgets how it found something cannot be audited. These are the routes that admitted this work.

affAt least one author lists a Canadian institution in the pinned OpenAlex snapshot.

Bibliographic record

VenueConference of the Centre for Advanced Studies on Collaborative Research · 2011
Typearticle
Languageen
FieldComputer Science
TopicSoftware Reliability and Analysis Research
Canadian institutionsRoyal Military College of CanadaQueen's University
Fundersnot available
KeywordsComputer scienceSoftwareProfiling (computer programming)Pareto principleSearch-based software engineeringPropagation of uncertaintySoftware qualityCode (set theory)Pareto analysisSoftware sizingData miningSoftware constructionSoftware developmentReliability engineeringSet (abstract data type)AlgorithmMathematical optimizationEngineeringMathematicsProgramming language
DOInot available

Abstract

fetched live from OpenAlex

For scientific computational software, accuracy is a constant concern. While existing tools and techniques can estimate the output accuracy, they do not attempt to locate where these errors come from and which parts of the code are most responsible for their amplification. In the related problem of software performance optimization, the Pareto principle, also known as the 80/20 rule, is used to great effect. Because the performance of software is typically dependent on only a few critical sections of code, efforts in optimization can be focused on locating these sections with the help of a profiler and then optimizing only the functions that will have the greatest effect on overall performance. Does the Pareto principle also apply in the case of software accuracy? To study this problem, we develop a novel approach for determining accuracy degradation at the function level using a combination of interval analysis and derivative techniques. We use the model to analyze a piece of scientific computational software from the field of nuclear engineering. Our results suggest that the Pareto principle does in fact apply for accuracy degradation: 88% of the analyzed functions had less than 2% average relative errors in their output, and error amplification only occurred on 19% of functions. These results imply that tools focused on locating the critical sections of code where accuracy degradation is high could be useful in helping scientific developers understand and improve the accuracy characteristics of their software.

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.

Full frame distilled prediction

Teacher imitation

Not calibrated prevalence, not ground truth. Human validation pending. Learned from the 10,348 direct Codex labels and 10,348 direct Gemma labels. Candidate is the union of thresholded teacher heads; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels or direct frontier model labels.

metaresearch head score (Codex)0.004
metaresearch head score (Gemma)0.031
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesMetaresearch
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.815
Threshold uncertainty score0.977

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0040.031
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0000.003
Science and technology studies0.0010.002
Scholarly communication0.0000.000
Open science0.0030.001
Research integrity0.0000.000
Insufficient payload (model declined to judge)0.0000.000

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.255
GPT teacher head0.426
Teacher spread0.171 · 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