WARPED Installation Notes

Supporting software for installation

To install WARPED, you will require the following supporting tools (links to this software is at the end of this file).

makedepend: current version released with X11R6 (part of X-windows software)
the GNU Make makefile utility (part of GNU software)
g++: the GNU C++ compiler and accompanying libc, version 2.7.0 or later (part of GNU software)
an implementation of MPI (e.g. MPICH) if parallel simulation is desired

Note: g++ version 2.8.0/2.8.1 is not recommended if you are planning to download and compile the TyVIS and WARPED simulation kernels. g++ versions 2.8.x have problems compiling templatized classes with arbitrary number of parameters. Here is an example program that you can use to test the compiler.

Installation:

Step 1: Download and untar the WARPED source distribution.
Step 2: Change directory into the "warped" directory. The directory will contain the following files:

WARPED | --------------------------------------------------------------- | | WARPED Configuration Files Other Directories -- Makefile -- NoTime -- Makefile.common.in -- Sequential -- aclocal.m4 -- TimeWarp -- configure -- common -- configure.in -- install-sh -- mkinstalldirs -- warped_global_config.h.in NoTime - is an UNSYNCHRONIZED parallel discrete-event simulation kernel Sequential - is a highly optimized sequential discrete-event simulation kernel TimeWarp - is the optimistic parallel discrete-event simulation kernel common - is a directory that contains files that are common to all three simulation kernels

Step 3: Now run the configure script in the current directory by issuing the following command: ./configure. This will result in the script running through several options and configuring WARPED for your system. If the configure script terminates with errors then you will need to fix these errors before proceeding. However, if the script terminates successfully, then it will result in the creation of the "Makefile.common" file. This file gets included by every other Makefile in the system. Hence, any compiler/loader flags or libraries that need to included in the system should be added here.
If you're installing on a system with MPI installed in a non-standard place, you'll want to run the configure script with a command line like "env LDFLAGS=-L [directory libmpi.a is in] CPP=-I [directory mpi.h is in] ./configure". If you need to rerun configure for any reason, delete config.cache as it will cause configure to not retest everything.
Step 4: Issue a make depend to generate and check dependencies. Now there are two ways of building the system: (a) The first method is to build all three simulation kernels by issuing a make command in the current directory. This will build all three simulation kernels; or (b) Alternatively, the user can selectively build the simulation kernels of his/her choice (by changing directory to one of the three available simulation kernels and then issuing the make command in that directory).
Step 5: After building the simulation kernel, the user can select any application to run on the simulation kernel. For example, to run the SMMP application model, the user needs to change directories to "warped/TimeWarp/SMMP" and then issue the make command. This will result in the generation of a SMMP application executable that can then be simulated.
Note: The WARPED TimeWarp kernel is highly configurable. In "warped/TimeWarp/src" directory, there is a file named "config.hh" that contains the various configurations that can be deployed in the WARPED kernel. For example, there are two different GVT Managers, several types of State Managers, and several communication related optimizations such as message aggregation. For more details on configuring these optimizations, please consult the "README" file in the TimeWarp/src" directory.

Note: In this version of WARPED, we have separated the Sequential kernel from the TimeWarp kernel. By default, a sequential version of the kernel will be built. However, if the user wishes to perform parallel simulations, then the system needs to be compiled with the "-DMPI" compiler flag. A sample "Makefile.common" file is illustrated below:
For example, to generate a parallel simulation kernel for running any application model, the following "Makefile.common" needs to be used (generated for a dual processor Pentium II workstation running Linux): export LIBS = -lm -lnsl -L/local/mpich/lib/LINUX/ch_p4/ -lmpi export CFLAGS=-g -O2 export CPPFLAGS+=-I. -DMPI -DHAS_BOOLEAN -I/local/mpich/include export LDFLAGS= export INSTALL = /local/packages/common/bin/install -c export INSTALL_PROGRAM = ${INSTALL} export MKINSTALLDIRS= ./mkinstalldirs

WARPED, version 1.0
warped@ece.uc.edu