-
Notifications
You must be signed in to change notification settings - Fork 1
Home
Instructions on how to install Ant on a variety of operating systems are detailed in the ant manual but the basic steps are:
- download the binary distribution of Ant (on Linux it should be available via the package manager)
- unpack it somewhere (and keep track of its location!). On Linux this might be /opt/ant or /usr/local/ant or /usr/share/ant, on Windows it is wherever you decide to install it. For the purposes of this example we suggest a location like
C:\tools\ant - set the
JAVA_HOMEandANT_HOMEenvironment variables to point to the appropriate locations. The deploy.bat file in the foraging directory can be used as a template to deploy the software on Windows, just change the paths of ANT_HOME and JAVA_HOME to reflect your system's configuration. - set the PATH variable to include the bin directories under JAVA_HOME and ANT_HOME so you have access to the ant and java executables
A sesef experiment provides abstractions for a Server, many Clients / Participants partitioned into Groups, and a Facilitator that drives the experiment, sending custom commands to the experiment Server. Some examples of custom commands:
- advance all connected clients and participants to the next round of the experiment
- begin a dedicated communication round
- show instructions, quiz pages, or any custom interface (e.g., an embedded trust game, voting screen, or survey)
Clients and Facilitators make Requests to the Server, and informational data sent back are in the form of Events. There is also an EventChannel abstraction present aimed at decoupling component messaging within the client, server, and facilitator applications.
The Server is a command-line application, whereas the Clients and Facilitators are graphical applications that are typically delivered across the network using Java WebStart and configured to connect to the Server. They can also be deployed via a shared network drive though we recommend copying jars to the local machine before running them.
NOTE: Due to the recent security issues with Java WebStart, extra steps must be taken to get Java WebStart applications to deploy and install properly. You can either sign your generated jars with a code signing certificate or add a site exception to each client machine where you will be running your experiments.