The tree view of CPS contains quite a lot of directories. The aim of this section is to give a quick overview of what each one of them is for.
It is divided in two parts, each one being dedicated to one of the main folders: cps and data.
This is where the source files (with the .java extension) are stored. Their content is detailed in a dedicated part of this website.
This ones contains the Javadoc of CPS. This folder is classical for Java projects and it allows softwares like Eclipse to display it while you are coding.
Contains all the data necessary for doxygen to work, i.e a configuration file, a script launching the creation of the documentation and a folder containing additional files, such as the header to use.
This folder contains the external library used by CPS, for example jdom (used to parse and write xml files).
At last, this folder contains the bytecode resulting from the compilation of the source files.
More details on what this is used for here.
More details on what this is used for here.
CPS will write the csv files to upload to CrowdFlower here. You should not have to touch anything here.
This is where CPS will write the results downloaded from CrowdFlower. The download, the extraction of the file and its renaming are performed in one operation.
No matter what the arguments specified are, CPS will create a log file here when you launch it. The name of the log files have the following structure, describing the time at which it was started: dd-mm-yyyy-(hh-mm-ss).log, where:
In order to be able to start again where he left, CPS stores the intermediary results of the sort in this folder. Therefore, if a splitsort is running, it will contain a file for each axis studied. It also contains a tiny file simply containing the number of the job from where results should be retrieved.
This folder contains data used to interact with the MySQL database. The most important is the dump.sh script performing the dump of the database.