MétaCan
Menu
Back to cohort
Record W2594297796

An exploratory study on change suggestions for methods using clone detection

2016· article· en· W2594297796 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

VenueComputer Science and Software Engineering · 2016
Typearticle
Languageen
FieldComputer Science
TopicSoftware Engineering Research
Canadian institutionsUniversity of Saskatchewan
Fundersnot available
KeywordsRanking (information retrieval)Computer scienceChange detectionPrecision and recallRank (graph theory)Change analysisInformation retrievalData miningComplement (music)Software evolutionRecallData scienceSoftwareMachine learningArtificial intelligenceSoftware systemCognitive psychologyMathematics
DOInot available

Abstract

fetched live from OpenAlex

A number of studies investigated providing change suggestions to programmers on the basis of the evolution history of a software system. While existing studies provide change suggestions considering code fragment level or even line level granularities, we investigate providing change suggestions at the method level. Providing a suggestion to change the entire method at one time is intuitively more time saving for developers compared to providing suggestions separately for different fragments of a method. In this research we empirically investigate whether we can infer change suggestions at the method level by analyzing the past evolution history of a software system through detection of method clones, and if so, then how we can rank the method level change suggestions. According to our investigation on thousands of commits of seven diverse subject systems, we can provide change suggestions at the method level with up to 83% precision and 13.49% recall. Moreover, for up to 34% of the commits we can provide correct method level change suggestions. Compared to the existing fragment level change suggestion techniques, our method level change suggestion technique has promising precision and recall. We investigate the ranking of method level change suggestions and find that recency ranking (i.e., ranking on the basis of how recently the change suggestions appeared in the past) is a better choice than frequency ranking (ranking considering how frequently the suggestions appeared). We believe that while a method level change suggestion technique can never be a replacement for the existing fine grained change suggestion techniques, it can complement these existing ones.

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.002
metaresearch head score (Gemma)0.001
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Other design · Consensus signal: none
GenreCandidate signal: Methods · Consensus signal: none
Teacher disagreement score0.936
Threshold uncertainty score0.668

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0020.001
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0010.001
Science and technology studies0.0000.000
Scholarly communication0.0000.002
Open science0.0010.000
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.081
GPT teacher head0.353
Teacher spread0.272 · 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