Eden is implemented in more than one tool. The first step is to choose which tool to use.
ttyeden
implements just the hybrid definitive and
procedural notation Eden and provides a UNIX shell-like
interface. It is useful for trying out ideas in Eden
quickly. ttyeden
has a line editing feature (GNU
readline), enabling full cursor editing of the input line and history.
tkeden
implements the Eden, DoNaLD (a Definitive
Notation for Line Drawing), SCOUT (a SCreen layOUT definitive
notation) and Sasami (definitive 3D graphics) notations. It is the
primary tool of the Empirical Modelling group.
dtkeden
extends tkeden
with
distributed communication features, adding the LSD
notation to do so. It is used when models use communication between
machines, for example in our Clayton tunnel railway accident model.
It is slower and has more bugs than tkeden
.
The Linux binaries are at this point almost totally untested, as
development mainly proceeds on the department's Solaris machines. The
binaries are currently just a tarball of the compiled executables and
library files as the time has not been available to investigate using
a package manager like RPM. Your mileage will vary as the binaries
are currently dynamically linked, and the binary may not be able to
find the required libraries at runtime on your system (you might try
playing with the $LD_LIBRARY_PATH
environment variable,
if this is implemented).
Download the tarball named
eden-linux-intel-binary-(version).tar.gz
with the highest
available version number from our FTP site.
Extract the files from the tarball and move into the resulting
directory:
$ zcat eden-linux-intel-binary-(version).tar.gz | tar xvf - $ cd tkeden-(version)
To run ttyeden
(if you are in the directory with the
executable):
$ ./ttyeden 1|> (<ctrl-D> to exit)
To run tkeden
(if you are in the directory with the
executable):
$ ./tkeden -l lib-tkeden
Both tools have many possible command line options. To list them,
use the -u
argument:
$ ./tkeden -u Usage: ./tkeden {-l<lib directory>} {-v|-u} {-e <code>}|{<filename>} {-e <code>}|{<filename>}... -l name of the directory containing the library files -v output version information and exit -u output this usage information and exit -e execute 'code' if file is '-', standard input will be read See http://www.dcs.warwick.ac.uk/modelling/ for more information
To "install" the tools, I would perhaps recommend placing
ttyeden
in a directory somewhere on your
$PATH
and writing a wrapper script to start
tkeden
, providing the correct location for the library
files as shown.
The usual practice when working with a model is to cd
into the directory containing the model and then run
ttyeden
or tkeden
, specifying the model
files as files to load on the command line. It is also possible to
use the File menu in tkeden
to achieve this.
The Windows binaries are receiving some use within the research group, and so are tested more than the Linux binaries. However, the tools originated on UNIX and a substantial amount of work is still required in order to make them fit neatly into the Windows environment.
Download the ZIP file named
eden-windows-binary-(version).zip
with the highest
available version number from our FTP site.
Then extract the files somewhere onto your disk (perhaps in "My
Documents" - note that spaces in the full directory name to the tools
used to be a problem, but this seems to be fixed now). Your operating
system may be able to extract the files, or you might need to download
winzip.
Now you should be able to simply double-click on
ttyeden.exe
or tkeden.exe
to start each
tool.
A small initial package of models is available from the FTP site at ftp://ftp.dcs.warwick.ac.uk/pub/modelling. The models package currently contains (cleaned up) versions of the jugs, OXO, racing, roadsys and VCCS models. Documentation to accompany each model is contained in the package, but note that the documentation is specific to each model - you will need the general Eden documentation package as well to get started.
An archive site giving access to our full library of models is being created -- watch this space for more details.
Check our Eden FAQ.
To compile the Eden tools, you will need a platform running UNIX of some kind, or you will need to install cygwin on a Windows platform. Download a source tarball named eden-source-(version).tar.gz from our FTP site, or the current source code using CVS from the repository at SourceForge (see the SourceForge Eden project page for more details). If you have downloaded a source tarball, extract the files:
$ zcat eden-source-(version).tar.gz | tar xvf -
Then follow the documentation in the Docs
directory
for more instructions.
Eden is an open source project, using the GNU General Public License. Contributions to the tool development are welcome.
Participation regarding definitive models is also welcomed, although there is no formal systematic support for this. Mail Dr. Meurig Beynon at wmb@dcs.warwick.ac.uk if you are interested.
Thanks for reading this, and good luck with the tools.
Ashley Ward, June 2001.
[an error occurred while processing this directive]