On Mon, 23 Oct 2000, Brian O'Keefe/Pittsburgh/IBM wrote:
> I have a couple polygraph runs in which the polyclt continued to run long
> after the polysrv (and the test itself) ended, and it was over the weekend,
> so I hadn't actually stopped the client until it had been running for 100
> hours. The problem with this is that the generated graphs all have the
> scale of 100 hours for them, and so the important 14 hours of the test are
> all bunched up at the beginning, and the graph isn't as easy to look at. My
> question is: is it possible to trim out data from the log file itself
> (which isn't very reader friendly) or can I tell the report to do that? I
> already use the --log_extractor_opts "--phases top2" to see only the top2
> info for most of the report, but the graphs show the whole test. I'd love
> to be able to do a report only, say, the first 15 hours of the test. Is
> this possible?
It is possible with some effort. There are several ways to trim the
graphs without writing code, although modifying binary logs is not one
of them.
Perhaps the simplest way is to use ./label_results like you always do
and then edit the corresponding /tmp/polyrep/*/clt.Traces.lx file to
cut the useless lines at the end (the first column is time in seconds,
I think). After you cut the lines, use ./make_report in the usual way.
I have never tried doing that, but it should work in principle. Please
let me know if it does not.
HTH,
Alex.
P.S. Why did your polyclts not stop? Were they configured to run for
100 hours? You are not using the --idle_tout on the client side,
are you?
This archive was generated by hypermail 2b29 : Tue Jul 10 2001 - 12:00:15 MDT