Menu
▾
▴
Tree [1a0922] master / History
| File | Date | Author | Commit |
|---|---|---|---|
| bin | 2013-04-25 |
Daniel D
|
[ea132d] Merge branch 'master' of ssh://edacc.git.source... |
| contrib | 2012-02-15 |
Daniel D
|
[b90e0c] added sydbox config example |
| src | 2013-06-29 |
Daniel D
|
[09988e] preliminary bugfix: limit solver output to 512 ... |
| verifiers | 2014-03-06 |
Daniel D
|
[1a0922] EDACC verifier for DRAT unsat proof format |
| .gitignore | 2012-03-28 |
Daniel D
|
[0aea38] support for cost binaries |
| AUTHORS | 2011-04-16 |
Simon G
|
[209dfa] Merge branch 'master' of ssh://edacc.informatik... |
| LICENSE | 2011-04-16 |
Simon G
|
[209dfa] Merge branch 'master' of ssh://edacc.informatik... |
| Makefile | 2012-03-16 |
Daniel D
|
[3a603b] adjusted Makefiles, no longer put verifier bina... |
| README.rst | 2013-08-01 |
Daniel D
|
[4f42e0] rename readme |
Read Me
EDACC Client
This is the computation client of the EDACC (Experiment Design and Analysis for Computer Clusters) system. See http://sourceforge.net/projects/edacc/ for more info.
After creating experiments with the EDACC GUI Application the client can be started on large computer clusters and grids to process the generated computation jobs in a multi-processing, distributed environment.
Dependencies
- GCC
- zlib
- MySQL libraries: The compilation requires the MySQL C Connector development libraries.
This includes a working mysql_config command which will point GCC to the directories with the necessary header files and libraries. Ideally you should compile the client in the target environment, otherwise you can consider a static compilation which might work if the build and target systems are not too different.
Compilation
Run "make" in the top level directory. Binaries are put into bin/.
Usage
Use ./client --help to see a list of command line options the binary accepts. Configure the database settings in the 'config' text file and make sure "runsolver" and verifier binaries that are specified in the configuration file exist in the correct paths. The client will call these programs with paths relative to the working(!) directory at runtime. Furthermore, the client has to be able to create directories and write files in either the working directory or the directory that can be specified as "base path" (see --help).
The EDACC client is is able to run on any system where individual nodes can access the EDACC database, i.e. establish a TCP connection. If direct internet access from the nodes is not possible, this can often be achieved by tunneling to the database server over the cluster's login node via SSH.
