MétaCan
Menu
Back to cohort
Record W4415896010 · doi:10.1016/j.jss.2025.112694

Domain-specific conflict resolution and model merge

2025· article· en· W4415896010 on OpenAlexafffund
Manouchehr Zadahmad, Eugene Syriani

Bibliographic record

VenueJournal of Systems and Software · 2025
Typearticle
Languageen
FieldComputer Science
TopicModel-Driven Software Engineering Techniques
Canadian institutionsUniversité de Montréal
FundersMitacs
KeywordsMerge (version control)Conflict resolutionSoftwareSyntaxResolution (logic)High resolution

Abstract

fetched live from OpenAlex

• Domain-specific version control system: DSMCompare • Domain-specific model merging • Curated labeled dataset for model merging • Comparative evaluation with EMFCompare and Git • User study validating DSMCompare Software developers often collaborate by contributing to different branches in a version control system. However, merging the changes from the different branches often leads to conflicts, and resolving these conflicts is a tedious task. This challenge is exacerbated when the software to merge are domain-specific models, since they follow a graph-like structure rather than linear text. DSMCompare is a tool for comparing domain-specific models, detecting differences, and visualizing conflicts using the concrete syntax of the domain-specific language. In this paper, we enhance DSMCompare with conflict resolution capabilities to reduce the effort of merging model versions. Our evaluation demonstrates that DSMCompare is effective in achieving highly accurate automatic conflict resolution with minimal manual intervention. A user study further validates the tool, revealing a significant decrease in resolution time coupled with higher accuracy and user satisfaction.

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 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.001
metaresearch head score (Gemma)0.000
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Theoretical or conceptual · Consensus signal: none
GenreCandidate signal: Methods · Consensus signal: Methods
Teacher disagreement score0.941
Threshold uncertainty score0.390

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0010.000
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0000.000
Science and technology studies0.0000.000
Scholarly communication0.0000.000
Open science0.0000.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.016
GPT teacher head0.239
Teacher spread0.223 · 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 teacher head, not a consensus.

The models applied no category: nothing in the taxonomy fit this work.
Study designTheoretical or conceptual
Domainnot available
GenreMethods

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
Published2025
Admission routes2
Has abstractyes

Explore more

Same venueJournal of Systems and SoftwareSame topicModel-Driven Software Engineering TechniquesFrench-language works237,207