Commit Quality in Five High Performance Computing Projects

Agrawal, Kapil; Amreen, Sadika; Mockus, Audris

doi:10.1109/se4hpcs.2015.11

Cited by 11 publications

(5 citation statements)

References 9 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Given all previous obstacles, the majority of code evolution studies not only use a small sample of projects of a single language, but also choose to analyze only a limited number of (often major) releases [19], [52], [54]. Considering that modern software development typically sees several commits per day for a given project [7], [30], analyzing only a few releases can give an incomplete picture. To give an example, fig.…”

Section: A Challengesmentioning

confidence: 99%

“…For example, if a file underwent changes in revisions 5 and 10, it will not be parsed in revisions 6 to 9, resulting in two ranges and . But the syntax nodes within are actually present in the source in-between these revisions, necessitating a range extension for a final configuration of [5][6][7][8][9][10-10], or even [5][6][7][8][9][10] if the two parsed revisions contain the same metadata in the given vertex. 4) Finally, the metadata of a vertex for two adjacent revisions may also exhibit some overlap.…”

Section: B Low Redundancy Graph and Metadatamentioning

confidence: 99%

See 1 more Smart Citation

Reducing redundancies in multi-revision code analysis

Alexandru

Panichella

Gall

2017

2017 IEEE 24th International Conference on Software Analysis, Evolution and Reengineering (SANER)

View full text Add to dashboard Cite

Software engineering research often requires analyzing multiple revisions of several software projects, be it to make and test predictions or to observe and identify patterns in how software evolves. However, code analysis tools are almost exclusively designed for the analysis of one specific version of the code, and the time and resources requirements grow linearly with each additional revision to be analyzed. Thus, code studies often observe a relatively small number of revisions and projects. Furthermore, each programming ecosystem provides dedicated tools, hence researchers typically only analyze code of one language, even when researching topics that should generalize to other ecosystems. To alleviate these issues, frameworks and models have been developed to combine analysis tools or automate the analysis of multiple revisions, but little research has gone into actually removing redundancies in multi-revision, multi-language code analysis. We present a novel end-to-end approach that systematically avoids redundancies every step of the way: when reading sources from version control, during parsing, in the internal code representation, and during the actual analysis. We evaluate our open-source implementation, LISA, on the full history of 300 projects, written in 3 different programming languages, computing basic code metrics for over 1.1 million program revisions. When analyzing many revisions, LISA requires less than a second on average to compute basic code metrics for all files in a single revision, even for projects consisting of millions of lines of code.

show abstract

Section: A Challengesmentioning

confidence: 99%

Section: B Low Redundancy Graph and Metadatamentioning

confidence: 99%

Reducing redundancies in multi-revision code analysis

Alexandru

Panichella

Gall

2017

2017 IEEE 24th International Conference on Software Analysis, Evolution and Reengineering (SANER)

View full text Add to dashboard Cite

show abstract

“…They focus on modularity and use of state-of-theart numerics, and they develop a set of maintainable libraries. Paper [29] is an analysis of commit comments in scientific software projects. Good commit comments help in maintaining software.…”

Section: Resultsmentioning

confidence: 99%

“…Only one paper was published as a technical report and, hence, definitely non-refereed. [33], [34], [35], [36], [37], [27], [40], [30], [41], [31], [43], [32], [44] Empirical study without intervention 11 [18], [22], [24], [26], [15], [29], [19], [42], [20], [17], [21] Empirical study with intervention 5 [23], [38], [39], [25], [28] Opinion/philosophical paper 4 [13], [14], [2], [16] We also classified the included article in different types. We show the results in Tab.…”

Section: Scalability Efficiencymentioning

confidence: 99%

“…Furthermore, we identified four different classes of contributions in the included articles as shown in Table IV. [18], [26], [16], [29], [19], [17], [21] Describe/analyze trade-off 5 [13], [22], [24], [2], [20] Solutions for single attributes 8 [33], [14], [23], [25], [15], [28], [30], [32] Solutions for trade-off 13 [34], [35], [36], [37], [38], [39], [27], [40], [41], [31], [42], [43], [44] The papers describing or analyzing single attributes concentrate on one or more of the quality attributes. We have seven such papers.…”

Section: A Principal Findingsmentioning

confidence: 99%

See 1 more Smart Citation

The Scalability-Efficiency/Maintainability-Portability Trade-Off in Simulation Software Engineering: Examples and a Preliminary Systematic Literature Review

Pflüger

Mehl

Valentin

et al. 2016

2016 Fourth International Workshop on Software Engineering for High Performance Computing in Computational Science and Engineer

View full text Add to dashboard Cite

Abstract-Large-scale simulations play a central role in science and the industry. Several challenges occur when building simulation software, because simulations require complex software developed in a dynamic construction process. That is why simulation software engineering (SSE) is emerging lately as a research focus. The dichotomous trade-off between scalability and efficiency (SE) on the one hand and maintainability and portability (MP) on the other hand is one of the core challenges. We report on the SE/MP trade-off in the context of an ongoing systematic literature review (SLR). After characterizing the issue of the SE/MP trade-off using two examples from our own research, we (1) review the 33 identified articles that assess the trade-off, (2) summarize the proposed solutions for the tradeoff, and (3) discuss the findings for SSE and future work. Overall, we see evidence for the SE/MP trade-off and first solution approaches. However, a strong empirical foundation has yet to be established; general quantitative metrics and methods supporting software developers in addressing the trade-off have to be developed. We foresee considerable future work in SSE across scientific communities.

show abstract

Developer Dynamics and Syntactic Quality of Commit Messages in OSS Projects

Chahal

Saini

2018

IFIP Advances in Information and Communication Technology

View full text Add to dashboard Cite

HAL is a multi-disciplinary open access archive for the deposit and dissemination of scientific research documents, whether they are published or not. The documents may come from teaching and research institutions in France or abroad, or from public or private research centers. L'archive ouverte pluridisciplinaire HAL, est destinée au dépôt et à la diffusion de documents scientifiques de niveau recherche, publiés ou non, émanant des établissements d'enseignement et de recherche français ou étrangers, des laboratoires publics ou privés.

show abstract

Commit Quality in Five High Performance Computing Projects

Cited by 11 publications

References 9 publications

Reducing redundancies in multi-revision code analysis

Reducing redundancies in multi-revision code analysis

The Scalability-Efficiency/Maintainability-Portability Trade-Off in Simulation Software Engineering: Examples and a Preliminary Systematic Literature Review

Developer Dynamics and Syntactic Quality of Commit Messages in OSS Projects

Contact Info

Product

Resources

About