----------------------------------------
REPLAY FRAMEWORK CONTENTS
----------------------------------------
1. Overview

2. Replay source

3. Debugging

4. Building

5. Replaying

****************************************
1. Overview
****************************************
The replay tool allows a user to replay the communication
of an MPI application traced by the recording framework.
The replay framework reads in a comprehensive trace and 
distributes it among all tasks.  Each task parses the 
trace and creates their individual task-level 
operation queues.  These are used to replay the
actual communication.

****************************************
2. Replay source
****************************************
replay.c - Location of main function.  This reads in 
a trace file and replays based on the trace's format.

op_exec.c - Utility functions that replay.c uses
to replay compressed traces.  Th excludes parsing 
the input file (done in rsd_reader.c) and
traversal of the operation queues (done in prsd_traverse.c)

****************************************
3. Debugging
****************************************
See the usage of macro DEBUG in replay.c. This is primarily
used to verify correctness of the trace parser.

****************************************
4. Building
****************************************
Set all compiler options in Makefile and enter the 
command: "make".

Dependencies :
 - We use mpiP to measure (profile) the trace replay.
 In the absence of mpiP, the target 'replay' can be built
 for replay, but timing information would not be available.
 - For stack signatures, we use libstackwalk ( ../../stackwalk)
 - 

****************************************
5. Replaying
****************************************
To replay: ./replay [-X] -p <trace dir> where <trace dir>
specifies the directory of the trace.  The trace itself
must be named '0'. To replay per-node trace an extra -X 
parameter must be specified.

$Id: README,v 1.4 2008/09/25 10:51:17 pratn Exp $
