Calling UpicReplay

UpicReplay plays the recorded UPIC conversations back again, see "Functioning of UpicReplay". During this step, log messages and warnings are output to stdout and debugging or error messages are output to stderr.

UpicReplay is called as follows from a Linux shell:

UpicReplay InputFileName [-c<numberOfClients>]
                                               [-s<speedPercentage>] [-d[d]]

Meaning of the parameters

InputFileName
	Name of the UPIC ReplayFile that you have created with UpicAnalyzer. Mandatory parameter.
-c<numberOfClients>
	numberOfClients specifies the number of UPIC clients for which the recorded conversations are to be replayed. Default: 1, (corresponds to -c1) i.e. only one client is simulated. The actual limit depends on the relevant system limit.
-s<speedPercentage>
	speedPercentage specifies the replay speed as a percentage of the original speed. This makes it possible to simulate long and short thinking times. Default: 100 (corresponds to -s100) i.e. original speed. -s200 means 200%, i.e. twice the speed, achieved by halving the thinking time.
-d	Enable debug output to stderr, i.e. debug messages are output on thread generation and there are fewer messages on send and receive calls.
-dd	Enables extended debug output to stderr, i.e. detailed debug messages are output. This option is only intended for internal UpicReplay diagnoses. -dd is only of value when simulating a small number of clients. Default: no debug output.

Example

The UPIC conversations recorded in the file Replay.1239 are to be replayed at normal speed for 100 clients. The call is as follows:

UpicReplay Replay.1239 -c100