Content deleted Content added
adding journal ISSN to the reference |
→Search space: add reference to mining software repositories for search space analysis |
||
Line 59:
If one explicitly enumerates all possible variants in a repair algorithm, this defines a design space for program repair.<ref name="Martinez2019">{{Cite journal |last1=Martinez |first1=Matias |last2=Monperrus |first2=Martin |date=2019 |title=Astor: Exploring the design space of generate-and-validate program repair beyond GenProg |journal=Journal of Systems and Software |volume=151 |pages=65–80 |arxiv=1802.03365 |doi=10.1016/j.jss.2019.01.069 |s2cid=3619320}}</ref> Each variant selects an algorithm involved at some point in the repair process (e.g. the fault localization algorithm), or selects a specific heuristic which yields different patches. For instance, in the design space of generate-and-validate program repair, there is one variation point about the granularity of the program elements to be modified: an expression, a statement, a block, etc.<ref name="Martinez2019" />
It is also possible to analyze whether known search spaces encompass existing commits.<ref>{{Cite journal|last=Etemadi|first=Khashayar|last2=Tarighat|first2=Niloofar|last3=Yadav|first3=Siddharth|last4=Martinez|first4=Matias|last5=Monperrus|first5=Martin|date=2022|title=Estimating the potential of program repair search spaces with commit analysis|url=https://linkinghub.elsevier.com/retrieve/pii/S0164121222000309|journal=Journal of Systems and Software|language=en|volume=188|pages=111263|doi=10.1016/j.jss.2022.111263}}</ref> Such a search space analysis means [[Mining software repositories|mining a software repository]], this results in an approximation of the applicability and usefulness of a given repair algorithm.
== Overfitting ==
| |||