start
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
start [2012/09/25 20:43] – shouzheng | start [2015/01/27 16:54] (current) – bil | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | This page shows a guideline for installing FINDER. | + | This wiki outlines |
- | + | ||
- | Prerequisites: | + | |
- | You need to have [[http:// | + | |
- | + | ||
- | samples? | + | |
- | + | ||
- | Make sure you have set up certain environment variables for using all these tools, so that FINDER knows where they are. \\ | + | |
- | + | ||
- | samples? | + | |
- | + | ||
- | Installation: | + | |
- | Download and extract {{finder.zip|FINDER}}. \\ | + | |
- | + | ||
- | In order to detect patterns by FINDER, you will need to edit the following files in the conf directory: | + | |
- | + | ||
- | *software.xml | + | |
- | *directory -- path to the software java class files | + | |
- | *name -- software system name | + | |
- | *source_directory -- path to the software source code. | + | |
- | (Note: FINDER relies | + | |
- | + | ||
- | *scripts.xml | + | |
- | *scriptsDirectory -- path to FINDER scripts, which refer to FINDER/ | + | |
- | *candidateInstancesDirectory -- path to detection results output directory | + | |
- | + | ||
- | *designpatterns.xml | + | |
- | *designpattern -- By commenting in/out each " | + | |
- | *ql_script | + | |
- | + | ||
- | *run.properties | + | |
- | *input.design.patterns.xml.file -- path to the above designpatterns.xml file | + | |
- | *input.software.xml.file -- path to the above software.xml file | + | |
- | *input.scripts.xml.file | + | |
- | *output.exception.txt.file -- path to exception output file | + | |
- | + | ||
- | + | ||
- | To run FINDER, go to FINDER/ | + | |
- | java -Xms1024M -Xmx1024M -Xss5000K ca.yorku.cse.FINDER.Engine "path to run.properties file" | + | |
- | + | ||
- | \\ | + | |
- | \\ | + | |
- | \\ | + | |
- | \\ | + | |
- | + | ||
- | + | ||
- | + | ||
- | This page shows a guideline for using the MoRe application suite. | + | |
- | + | ||
- | Samples? | + | |
- | + | ||
- | Download and extract the {{MoRe.zip|MoRe application suite}}. Note that the " | + | |
- | + | ||
- | | + | |
- | + | ||
- | < | + | |
- | < | + | |
- | < | + | |
- | < | + | |
- | < | + | |
- | < | + | |
- | </ | + | |
- | + | ||
- | Usage: java -jar finderConverter.jar finder_tab2ps.xml | + | |
- | + | ||
- | An {{tab2ps-finder.zip|example}} can be downloaded to test the converter. The example contains FINDER raw results of the TAB2PS system with corresponding " | + | |
- | + | ||
- | *PINOT Converter | + | |
- | + | ||
- | Usage: | + | |
- | java -jar pinotConverter.jar TAB2PS rawResult.txt outputPath | + | |
- | + | ||
- | An {{tab2ps-pinot.txt|example of PINOT raw result}} can be downloaded to test the converter. | + | |
- | + | ||
- | *SSA Converter | + | |
- | + | ||
- | Usage: | + | |
- | java -jar ssaConverter.jar TAB2PS rawResult.txt outputPath | + | |
- | + | ||
- | An {{tab2ps-ssa.xml|example of SSA raw result}} can be downloaded to test the converter. | + | |
- | + | ||
- | *Presenter | + | |
- | + | ||
- | Usage: java -jar presenter.jar | + | |
- | + | ||
- | Also, we can provide a MoRe instance as a parameter for the presenter at the terminal. This loads the presenter with the corresponding MoRe instance together. | + | |
- | + | ||
- | Usage: java -jar presenter.jar aMoReInstance.xml | + | |
- | + | ||
- | *The Comparator | + | |
- | The comparator is able to compute all proposed metrics as well as raw precision and recall between two MoRe instance files. Calculation can be performed based on either roles in the Benchmark or the intersection of Automatic and Benchmark roles. Usage is shown in the following: | + | |
- | + | ||
- | Usage: java -jar comparator.jar Automatic Benchmark [option] | + | |
- | option: | + | |
- | -gap-b | + | |
- | -gar-b | + | |
- | -dap-b | + | |
- | -dar-b | + | |
- | -dapd-b | + | |
- | -dard-b | + | |
- | -gap-i | + | |
- | -gar-i | + | |
- | -dap-i | + | |
- | -dar-i | + | |
- | -dapd-i | + | |
- | -dard-i | + | |
- | -precision Regular precision | + | |
- | -recall | + | |
- | + | ||
- | Combination of two MoRe instances can also be obtained by the comparator in the following way: | + | |
- | Usage: java -jar comparator.jar result1 result2 combinedFile -c | + | |
- | + | ||
- | *Comparing All | + | |
- | The comparator can also compare detection results for all metrics of multiple patterns produced by two tools at one time. In order to do this, a configuration file is needed to specify the software system name, tool name of the automatic result set, tool name of the benchmark result set, comparison type (based on benchmark | + | |
- | roles or intersection roles), and a list of pairs of MoRe instances to be compared. | + | |
- | A sample configuration file is shown below: | + | |
- | < | + | |
- | < | + | |
- | < | + | |
- | < | + | |
- | < | + | |
- | < | + | |
- | < | + | |
- | | + | |
- | < | + | |
- | | + | |
- | </ | + | |
- | </ | + | |
- | + | ||
- | To perform the comparison, we use a separate jar in the following way: | + | |
- | Usage: java -jar compareAll.jar compareAll.xml | + | |
+ | Please choose a link from the sidebar (currently only one) to learn more on this research topic. | ||
+ | For any questions, please email [[bil@yorku.ca]] |
start.1348605812.txt.gz · Last modified: 2012/09/25 20:43 by shouzheng