From 4378bba0314a7242aa2b781c41bef0729ea57b8d Mon Sep 17 00:00:00 2001 From: Benjamin Poirier Date: Mon, 14 Dec 2009 11:44:49 -0500 Subject: [PATCH] Correct the README regarding eval mode usage Signed-off-by: Benjamin Poirier --- lttv/lttv/sync/README | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/lttv/lttv/sync/README b/lttv/lttv/sync/README index 6e76ec17..0e331ea0 100644 --- a/lttv/lttv/sync/README +++ b/lttv/lttv/sync/README @@ -137,8 +137,11 @@ eval is a special module, it doesn't really perform synchronization, instead it calculates and prints different metrics about how well traces are synchronized. Although it can be run like other analysis modules, it is most useful when run in a postprocessing step, after another synchronization module -has been run. Eval is most common run in text mode. To do this, run -lttv -m eval [usual options, ex: -t traces/node1 -t traces/node2 --sync ...] +has been run. Eval is most common run in text mode. To do this, run: +lttv -m sync_chain_batch [usual options, ex: -t traces/node1 -t traces/node2 +--sync ...] +It can also be run from the lttv source tree via runlttv: +./runlttv -m eval [usual runlttv options, ex: traces/node1 traces/node2] eval provides a few more options: --eval-rtt-file - argument: FILE -- 2.34.1