Jump to content

Genetic improvement (computer science): Difference between revisions

From Wikipedia, the free encyclopedia
Content deleted Content added
m E.g. -based
W102102 (talk | contribs)
Line 29: Line 29:
==Tools==
==Tools==
*GIN https://github.com/gintool/gin
*GIN https://github.com/gintool/gin
*Magpie https://github.com/bloa/magpie
*PyGGI https://github.com/coinse/pyggi
*PyGGI https://github.com/coinse/pyggi

Revision as of 09:44, 2 June 2023

In computer software development, genetic Improvement is the use of optimisation and machine learning techniques, particularly search-based software engineering techniques such as genetic programming to improve existing software.[1] [2] The improved program need not behave identically to the original. For example, automatic bug fixing improves program code by reducing or eliminating buggy behaviour.[3] In other cases the improved software should behave identically to the old version but is better because, for example: it runs faster,[4] it uses less memory,[5] it uses less energy[6] or it runs on a different type of computer.[7] GI differs from, for example, formal program translation, in that it primarily verifies the behaviour of the new mutant version by running both the new and the old software on test inputs and comparing their output and performance in order to see if the new software can still do what is wanted of the original program and is now better.

Genetic improvement can be used to create multiple versions of programs, each tailored to be better for a particular use or for a particular computer.

Genetic improvement can be used with multi-objective optimization to consider improving software along multiple dimensions or to consider trade-offs between several objectives, such as asking GI to evolve programs which trade speed against the quality of answers they give. Of course it may be possible to find programs which are both faster and give better answers.

Mostly Genetic Improvement makes typically small changes or edits (also known as mutations) to the program's source code but sometimes the mutations are made to assembly code, byte code[8] or binary machine code.[9]

References

  1. ^ Langdon, William B. (2015). Genetically Improved Software. pp. 181–220. doi:10.1007/978-3-319-20883-1_8. ISBN 978-3-319-20882-4. {{cite book}}: |journal= ignored (help)
  2. ^ Justyna Petke and Saemundur O. Haraldsson and Mark Harman and William B. Langdon and David R. White and John R. Woodward (2018). "Genetic Improvement of Software: a Comprehensive Survey" (PDF). IEEE Transactions on Evolutionary Computation. 22 (3): 415–432. doi:10.1109/TEVC.2017.2693219. hdl:1893/25358.
  3. ^ Weimer, Westley; et al. (2010). "Automatic program repair with evolutionary computation". Communications of the ACM. 53 (5): 109. CiteSeerX 10.1.1.170.188. doi:10.1145/1735223.1735249.
  4. ^ Langdon, William B.; Harman, Mark (2015). "Optimizing Existing Software With Genetic Programming". IEEE Transactions on Evolutionary Computation. 19: 118–135. doi:10.1109/TEVC.2013.2281544.
  5. ^ Wu, Fan; Weimer, Westley; Harman, Mark; Jia, Yue; Krinke, Jens (2015). Deep Parameter Optimisation. pp. 1375–1382. doi:10.1145/2739480.2754648. ISBN 9781450334723. {{cite book}}: |journal= ignored (help)
  6. ^ Bruce, Bobby R.; Petke, Justyna; Harman, Mark (2015). Reducing Energy Consumption Using Genetic Improvement. pp. 1327–1334. doi:10.1145/2739480.2754752. ISBN 9781450334723. {{cite book}}: |journal= ignored (help)
  7. ^ Langdon, William B.; Harman, Mark (2014). Genetically Improved CUDA C++ Software. Lecture Notes in Computer Science. Vol. 8599. pp. 87–99. doi:10.1007/978-3-662-44303-3_8. ISBN 978-3-662-44302-6. {{cite book}}: |journal= ignored (help)
  8. ^ Orlov, Michael; Sipper, Moshe (2011). "Flight of the FINCH Through the Java Wilderness". IEEE Transactions on Evolutionary Computation. 15 (2): 166–182. CiteSeerX 10.1.1.298.6272. doi:10.1109/TEVC.2010.2052622.
  9. ^ Schulte, Eric M.; Weimer, Westley; Forrest, Stephanie (2015). Repairing COTS Router Firmware without Access to Source Code or Test Suites. pp. 847–854. doi:10.1145/2739482.2768427. ISBN 9781450334884. {{cite book}}: |journal= ignored (help)

Tools