@@ -37,67 +37,46 @@ Javadoc documentation is in the /docs folder as well as at https://jpt.cicirello
37
37
Source code is found in the /src folder. JUnit test classes are found in the /tests folder, which
38
38
mirrors the package structure of /src.
39
39
40
- Compiled jar files of the library are in the /lib folder.
40
+ Compiled jar files of the library are in the /dist folder.
41
41
42
42
The /examples folder includes source code to illustrate how to use the library. The /replication
43
43
folder includes source code that recreates results found in publications associated with the library.
44
44
45
45
## Building the Library (with ant)
46
46
47
- The /build directory contains an ant build file. The build file also executes the JUnit tests, and the build directory contains
48
- the relevant jar files for the JUnit libraries. If you prefer, you can replace these with the latest versions available
49
- from https://junit.org/junit4/ (just be sure to edit the property fields in the build.xml to point to the locations of the JUnit jar files).
50
-
51
- To execute the build process do one of the following. If your working directory is the build directory, then simply execute
52
- ` ant ` from the command line. If your working directory is the parent of build, then execute: ` ant -f build/build.xml `
53
-
54
- The default of the provided ant build file, compiles all source files and all JUnit tests, executes all test cases,
55
- and generates the jar file of the library. The build process will terminate on any test case failures. The default
56
- does not compile the example programs or the experiment replication programs. To include those in the build as well
57
- then execute ` ant all ` (if your working directory is the build directory) or ` ant -f build/build.xml all ` (if your
58
- working directory is the parent of build).
59
-
60
- If you use the ant build file, the build will generate the following directories: bin (for the compiled Java classes),
61
- testbin (for the compiled JUnit tests), lib (for the jar file of the library), and exbin (for the compiled example
47
+ The /build directory contains an ant build file. The build file
48
+ also executes the JUnit tests, and the build directory contains
49
+ the relevant jar files for the JUnit libraries. If you prefer,
50
+ you can replace these with the latest versions available
51
+ from https://junit.org/junit4/ (just be sure to edit the property
52
+ fields in the build.xml to point to the locations of the JUnit jar files).
53
+
54
+ To execute the build process do one of the following. If your working
55
+ directory is the build directory, then simply execute
56
+ ` ant ` from the command line. If your working directory is the
57
+ parent of build, then execute: ` ant -f build/build.xml `
58
+
59
+ The default of the provided ant build file, compiles all source
60
+ files and all JUnit tests, executes all test cases,
61
+ generates the jar file of the library, and compiles the example
62
+ programs and the experiment replication programs. The
63
+ build process will terminate on any test case failures.
64
+
65
+ If you use the ant build file, the build will generate the
66
+ following directories: bin (for the compiled Java classes),
67
+ testbin (for the compiled JUnit tests), dist (for the jar file of the library),
68
+ and exbin (for the compiled example
62
69
programs and experiment replication programs).
63
70
64
71
## Running the Example Programs
65
72
66
73
The examples directory contains example usage of several of the classes of the API.
67
74
The replication directory additionally contains more complex examples that replicate the
68
75
experiments from published papers that have used the library. Those directories contain
69
- readmes that provide more detail on the examples.
70
-
71
- Assuming the build was successful, the compiled examples and replication programs will be
72
- in the exbin directory. If your working directory is the root
73
- of the repository, then you can run these programs from the command line with the following:
74
-
75
- ```
76
- java -cp "lib/jpt2.jar;exbin" org.cicirello.examples.jpt.AverageDistance
77
- java -cp "lib/jpt2.jar;exbin" org.cicirello.examples.jpt.TableOfDistances
78
- java -cp "lib/jpt2.jar;exbin" org.cicirello.examples.jpt.PermutationExamples
79
- java -cp "lib/jpt2.jar;exbin" org.cicirello.examples.jpt.SimpleDistanceExamples
80
- java -cp "lib/jpt2.jar;exbin" org.cicirello.examples.jpt.SequenceDistanceExamples
81
- java -cp "lib/jpt2.jar;exbin" org.cicirello.examples.jpt.PermutationHashCodes
82
- java -cp "lib/jpt2.jar;exbin" org.cicirello.replication.flairs2013.Flairs2013
83
- java -cp "lib/jpt2.jar;exbin" org.cicirello.replication.ieeetevc2016.FDC
84
- java -cp "lib/jpt2.jar;exbin" org.cicirello.replication.bict2019.BICT2019
85
- ```
86
-
87
- In each of the above cases, the source code includes comments explaining the example
88
- usage of the library.
89
-
90
- ** Memory Intensive Example** : Note that depending on your processor speed,
91
- the experiment replication programs may be slow (certainly slower than
92
- the examples from the examples folder). Additionally, the ` org.cicirello.replication.ieeetevc2016.FDC ` is memory intensive,
93
- and depending upon your system may require increasing the heap allocation to the Java virtual machine.
94
- If it throws an ` OutOfMemoryError ` , then execute as follows (note the additional command line argument):
95
-
96
- ```
97
- java -Xms1g -cp "lib/jpt2.jar;exbin" org.cicirello.replication.ieeetevc2016.FDC
98
- ```
99
-
76
+ READMEs that provide more detail on the examples, including on running the examples.
100
77
101
78
## Contribute
102
79
103
- Report bugs, suggestions, feature requests, etc via the [ issues tracker] ( https://github.com/cicirello/JavaPermutationTools/issues ) . If you would like to directly contribute new code, you may also fork the repository, and create pull requests.
80
+ Report bugs, suggestions, feature requests, etc via the [ issues tracker] ( https://github.com/cicirello/JavaPermutationTools/issues ) . If you would
81
+ like to directly contribute new code, you may also fork the repository,
82
+ and create pull requests.
0 commit comments