From 7aa2e5770b98971762ff20ae64ce233b9e69b715 Mon Sep 17 00:00:00 2001 From: Antonino Sabetta Date: Wed, 10 May 2023 11:38:48 +0200 Subject: [PATCH] Update README.md --- prospector/README.md | 10 +++++++--- 1 file changed, 7 insertions(+), 3 deletions(-) diff --git a/prospector/README.md b/prospector/README.md index 71a01b46..a6dc36ff 100644 --- a/prospector/README.md +++ b/prospector/README.md @@ -130,15 +130,19 @@ Prospector makes use of `pytest`. ## History -The high-level structuring of the Prospector operation follows the approach of its -ancestor FixFinder, which is described in detail here: https://arxiv.org/pdf/2103.13375.pdf +The high-level structure of Prospector follows the approach of its +predecessor FixFinder, which is described in detail here: https://arxiv.org/pdf/2103.13375.pdf FixFinder is the prototype developed by Daan Hommersom as part of his thesis done in partial fulfillment of the requirements for the degree of Master of Science in Data Science & Entrepreneurship at the Jheronimus Academy of Data Science during a graduation internship at SAP. -The document can be cited as follows: +The main difference between FixFinder and Prospector (which has been implemented from scratch) +is that the former takes a definite data-driven approach and trains a ML model to perform the ranking, +whereas the latter applies hand-crafted rules to assign a relevance score to each candidate commit. + +The document that describes FixFinder can be cited as follows: @misc{hommersom2021mapping, title = {Automated Mapping of Vulnerability Advisories onto their Fix Commits in Open Source Repositories},