[Darshan-users] A bug report and a feature request

[Bill Barth]

I'm interested in a tool that would scan a bunch of logfiles and throw up
some red flags suggesting users/codes that we should be looking at.

Any thoughts on metrics for that?

Bill.
--
Bill Barth, Ph.D., Director, HPC
bbarth at tacc.utexas.edu        |   Phone: (512) 232-7069
Office: ROC 1.435             |   Fax:   (512) 475-9445







On 9/15/11 12:56 PM, "Rob Latham" <robl at mcs.anl.gov> wrote:

>On Thu, Sep 15, 2011 at 01:34:33PM -0400, Phil Carns wrote:
>> On 09/15/2011 01:17 PM, Bill Barth wrote:
>> >The Bug Report:
>> >
>> >I think that the summary.pdf has swapped the summaries for read and
>>write
>> >in the "Data Transfer Per Filesystem" table. I'm happy to share a
>>logfile
>> >if you can't reproduce on your end.
>> 
>> That would be great if you could send us a log file example.  I just
>> tried a quick test on an old log file and it looked Ok in that
>> particular case.  It might depend on the contents of the log.
>> 
>> >The Feature Request:
>> >
>> >darshan-job-summary.pl should produce its output pdf file based on the
>> >name of the input logfile rather than calling it "summary.pdf".
>> 
>> We could probably add a command line option to produce that
>> behavior.  In the mean time you can at least use the --output option
>> to specify the file name.
>
>I've started looking at how to make the tool output one summary file
>per program data file (motivating case study: visualization tools read
>one set of input data and write a separate output file -- two distinct
>workloads).
>
>==rob
>
>-- 
>Rob Latham
>Mathematics and Computer Science Division
>Argonne National Lab, IL USA
>_______________________________________________
>Darshan-users mailing list
>Darshan-users at lists.mcs.anl.gov
>https://lists.mcs.anl.gov/mailman/listinfo/darshan-users