MELCOR Code Change History: Revision 14959 to 18019.

Ascomycete yeasts are metabolically diverse, with great potential for biotechnology. Here, we report the comparative genome analysis of 29 taxonomically and biotechnologically important yeasts, including 16 newly sequenced. We identify a genetic code change, CUG-Ala, in Pachysolen tannophilus in the clade sister to the known CUG-Ser clade. Our well-resolved yeast phylogeny shows that some traits, such as methylotrophy, are restricted to single clades, whereas others, such as l-rhamnose utilization, have patchy phylogenetic distributions. Gene clusters, with variable organization and distribution, encode many pathways of interest. Genomics can predict some biochemical traits precisely, but the genomic basis of others, such as xylose utilization, remains unresolved. Our data also provide insight into early evolution of ascomycetes. We document the loss of H3K9me2/3 heterochromatin, the origin of ascomycete mating-type switching, and panascomycete synteny at the MAT locus. These data and analyses will facilitate the engineering of efficient biosynthetic and degradative pathways and gateways for genomic manipulation.

Download Full-text

Is Bug Severity in Line with Bug Fixing Change Complexity?

International Journal of Software Engineering and Knowledge Engineering ◽

10.1142/s0218194020400306 ◽

2020 ◽

Vol 30 (11n12) ◽

pp. 1779-1800

Author(s):

Zengyang Li ◽

Peng Liang ◽

Dengwei Li ◽

Ran Mo ◽

Bing Li

Keyword(s):

Effort Estimation ◽

Severity Level ◽

Release Planning ◽

Bug Reports ◽

Bug Fixing ◽

Code Change ◽

Study Results ◽

Significant Difference ◽

Lower Severity ◽

Severity Levels

Both complexity of code change for bug fixing and bug severity play an important role in release planning when considering which bugs should be fixed in a specific release under certain constraints. This work investigates whether there are significant differences between bugs of different severity levels regarding the complexity of code change for fixing the bugs. Code change complexity is measured by the number of modified lines of code, source files, and packages, as well as the entropy of code change. We performed a case study on 20 Apache open source software (OSS) projects using commit records and bug reports. The study results show that (1) for bugs of high severity levels (i.e. Blocker, Critical and Major in JIRA), there is no significant difference on the complexity of code change for fixing bugs of different severity levels for most projects, while (2) for bugs of low severity levels (i.e. Major, Minor and Trivial in JIRA), fixing bugs of a higher severity level needs significantly more complex code change than fixing bugs of a lower severity level for most projects. These findings provide useful and practical insights for effort estimation and release planning of OSS development.

Download Full-text

The Development of Grid Code Requirements for New and Renewable Forms of Generation in Great Britain

Wind Engineering ◽

10.1260/030952405774354903 ◽

2005 ◽

Vol 29 (3) ◽

pp. 201-215 ◽

Cited By ~ 7

Author(s):

Antony Johnson ◽

Nasser Tleis

Keyword(s):

Great Britain ◽

Transmission System ◽

Wind Generation ◽

Transmission Network ◽

Code Change ◽

Fault Ride Through ◽

Key Stakeholders ◽

Before And After ◽

Power Frequency ◽

Technical Issues

This paper presents the development of Grid Code requirements for new and renewable forms of generation in Great Britain (GB). After briefly describing the background to the GB Transmission System and the volume of renewable generation which is anticipated to connect in the future, the paper discusses the Grid Code and Grid Code change process. In particular, the paper discusses the interfaces with key stakeholders, the technical issues considered in connecting other generation technologies to the Transmission network and the rationale for the final Grid Code requirements. The technical issues discussed include fault ride through, frequency range, frequency response, power/frequency characteristic, reactive range, voltage control and power quality. The paper concludes with the experiences gained in the connection of wind generation projects to the GB Transmission System both before and after the approval of new proposals to the GB Grid Code.

Download Full-text

Predicting Build Co-changes with Source Code Change and Commit Categories

2016 IEEE 23rd International Conference on Software Analysis, Evolution, and Reengineering (SANER) ◽

10.1109/saner.2016.22 ◽

2016 ◽

Cited By ~ 8

Author(s):

Christian Macho ◽

Shane McIntosh ◽

Martin Pinzger

Keyword(s):

Source Code ◽

Code Change

Download Full-text

Square Root 3: Background to the New Design Margin for High Pressure Vessels

Volume 5: High Pressure Technology, Nondestructive Evaluation, Pipeline Systems, Student Paper Competition ◽

10.1115/pvp2005-71295 ◽

2005 ◽

Author(s):

Jan Keltjens ◽

Philip Cornelissen ◽

Peter Koerner ◽

Waldemar Hiller ◽

Rolf Wink

Keyword(s):

High Pressure ◽

Pressure Vessel ◽

Pressure Vessels ◽

Design Code ◽

Code Change ◽

Section Viii ◽

Background Material ◽

Practical Information ◽

High Pressure Equipment ◽

Design Margin

The ASME Section VIII Division 3 Pressure Vessel Design Code adopted in its 2004 edition a significant change of the design margin against plastic collapse. There are several reasons and justifications for this code change, in particular the comparison with design margins used for high pressure equipment in Europe. Also, the ASME Pressure Vessel Code books themselves are not always consistent with respect to design margin. This paper discusses not only the background material for the code change, but also gives some practical information on when pressure vessels could be designed to a thinner wall.

Download Full-text

CODE-CHANGE IMPACT ANALYSIS USING COUNTERFACTUALS: THEORY AND IMPLEMENTATION

International Journal of Software Engineering and Knowledge Engineering ◽

10.1142/s0218194013500460 ◽

2013 ◽

Vol 23 (10) ◽

pp. 1459-1486

Author(s):

MANUEL PERALTA ◽

SUPRATIK MUKHOPADHYAY

Keyword(s):

Static Analysis ◽

Theorem Proving ◽

Program Analysis ◽

Impact Analysis ◽

Source Code ◽

Analysis Framework ◽

Change Impact Analysis ◽

Code Change ◽

Change Impact ◽

Automated Tool

This article shows a novel program analysis framework based on Lewis' theory of counterfactuals. Using this framework we are capable of performing change-impact static analysis on a program's source code. In other words, we are able to prove the properties induced by changes to a given program before applying these changes. Our contribution is two-fold; we show how to use Lewis' logic of counterfactuals to prove that proposed changes to a program preserve its correctness. We report the development of an automated tool based on resolution and theorem proving for performing code change-impact analysis.

Download Full-text