Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • D darshan
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 72
    • Issues 72
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • Deployments
    • Deployments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Repository
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • darshan
  • darshan
  • Issues
  • #24
Closed
Open
Issue created Sep 24, 2015 by Shane Snyder@ssnyderOwner

mismatch in variance table

To reproduce using attached log file:

$ darshan-job-summary.pl darshan-summary-table-bug-example.darshan.gz --output darshan-summary-table-bug-example.pdf

$ darshan-parser darshan-summary-table-bug-example.darshan.gz |grep 392949181 |grep RANK_BYTES

-1	17827256362278409223	CP_FASTEST_RANK_BYTES	8388608	...392949181	/intrepid-fs0	gpfs
-1	17827256362278409223	CP_SLOWEST_RANK_BYTES	8388608	...392949181	/intrepid-fs0	gpfs
-1	17827256362278409223	CP_F_VARIANCE_RANK_BYTES	0.000000	...392949181	/intrepid-fs0	gpfs

If you compare that darshan-parser output to the 2nd entry in the variance table in the summary pdf, then you acn see that the number of bytes doesn't match up.

Assignee
Assign to
Time tracking