maintenance benchmarks

Overview of Data This dataset contains two new datasets for ArgoUML0.24 and ArgoUML0.26.2, as well as a suite of Java tools used to generate these benchmarks, and two Matlab scripts that use VSM and LSI to compute the similarities between a query and the methods of a system (i.e., the corpus). Traces Format The format of a JPDA trace is as following: ``` thread name Number of pipes ("|") denote call stack depth methodName -- ClassNameWithFullPath$InnerClass ``` Example: ``` main:0:| 5:2 processOptions -- org.mozilla.javascript.tools.shell.Main main:0:| 5:2 init -- org.mozilla.javascript.tools.shell.Global main:0:| | 5:2 -- org.mozilla.javascript.tools.shell.Global$1 main:0:| | 5:2 call -- org.mozilla.javascript.ContextFactory main:0:| | 5:2 call -- org.mozilla.javascript.ContextFactory main:0:| | 5:2 -- org.mozilla.javascript.ScriptableObject$Slot main:0:| | | 5:2 -- org.mozilla.javascript.Context main:0:| | | | 5:2 -- org.mozilla.javascript.ScriptRuntime main:0:| | | | | 5:2 classOrNull -- org.mozilla.javascript.Kit ``` Remarks * `$1` denotes an anonymous class * `` is the class constructor, and should be replaced with the actual name of the class (e.g., from org.mozilla.javascript.tools.shell.Global. to org.mozilla.javascript.tools.shell.Global.Global) * `` is for static block or class initialization (can be discarded) * the trace does not capture the signature of the methods