Updating the toString limit to not be final so it can be changed on the fly; updated the toString in SumOfCl... to write how many clients and machines it is skipping

Performance tests JUnit file added, shows runtime and memory usage (beware of the garabage collector, make sure to use the object after you calculate the memory usage)

Adding a maximum information leak to the ClientToClientInformationLeakage; tests it for: the constructor, addTo, and subtractFrom(); adds more Javadoc strings and fixed a couple old comments

Converted the EpochHistory to store the ClientToClientInformationLeakage instead of the PlacementMap; REQUIRES more JUnit tests for the added functions

Updating the package-info.java for ILP because CPLEX JUnit tests fail if IBM CPLEX is not installed on the computer (found out on my laptop)

Provide timing tests for "hard ILP" test values as well as a random placement generator for this and arbitrary test values

Revert "HOTFIX: ArrayList.remove thought I wanted to remove the object and not the index, used .intValue() to force it to remove the index"

This reverts commit c39d64d9.

HOTFIX: ArrayList.remove thought I wanted to remove the object and not the index, used .intValue() to force it to remove the index

Removing the calculate Information Leakage  from EpochHistory and moving it to the ClientToClientInformationLeakage (see the excutive decision stating that we are focusing on Client to Client instead of total information leakage)

Adding a setting for the type of Information Leakage to calculate; turning off printing statements to the standard console (TURN ON LATER)

SumOfClientVMsPerMachine and ClientToClientInformationLeakage with their tests (ClientToClientInformationLeakageTests is incomplete)

REMOVING Epoch.java (Not Needed); RENAMING SumOfClientToClientInformationLeakage to ClientToClientInformationLeakage (better name because we need to single epochs worth of this as well as a sum)

[COMMIT BECAUSE I AM MOVING TO LAPTOP] small oject ideas that will need to be flushed out later today

VERSION UPGRADE 0.0.2 - so many changes since the last one, but the most important is the agreement of ReduceTo, RunSolver, and the EPOCH LOOP

[JAVADOC] @see to the description of what each setting variable is attached to in VagabondOptionString; the remaining functions are commented

Changed the naming convention,  and [BUG FIX] ReduceTo returned NULL instead of false. The fix was to switch to boolean instead of Boolean.

1. Create an empty ReduceTo and RunSolver of the appropriate reductionAlgorithm setting
2. reduction.reduce(epochHistory)
3. runSolver.load(reduction)
4. newEpochHistory = runSolver.run()
5. epochHistory.add(newEpochHistory)
6. GOTO Step 1 or Quit