On Sun, Jul 16, 2023 at 11:45 AM Jared Crean <jcrea...@gmail.com> wrote:
> Hello, > > I stumbled upon a small bug in the printing of the data when running > Petsc with -log_view. The entire table is attached, but here is an > example row: > Yes, we prescribe the exact number of spaces for each output, instead of allowing it to grow, so if the number exceeds the size, we lose our space. We wanted to keep the line length fixed. We do not recommend this form for processing. We usually use either the XML output for flame graphs since it does nesting, or the CSV output for processing with Pandas. Thanks, Matt > > ------------------------------------------------------------------------------------------------------------------------ > Event Count Time (sec) > Flop --- Global --- --- Stage ---- Total > Max Ratio Max Ratio Max Ratio Mess AvgLen > Reduct %T %F %M %L %R %T %F %M %L %R Mflop/s > > ------------------------------------------------------------------------------------------------------------------------ > > --- Event Stage 0: Main Stage > > BuildTwoSided 7 1.0 1.3282e-0271.6 0.00e+00 0.0 6.0e+01 4.0e+00 > 5.0e+00 0 0 0 0 0 0 0 0 0 0 0 > > > Notice how the Time Max and Time Ratio values are missing a space > separator (the other rows have only two digits for the exponents, I > think there should be a space after the e-02 and before the 7). > > Configuration details: > > * Petsc 3.17 > > * Arm64 architecture (and AWS c7g.xlarge instance, which use the > new Graviton3 processor) > > * ubuntu 22.04 > > * MPICH MPI (version 4.0, I think, whatever apt-get install mpich > gives) > > * clang-15 compiler > > > Jared Crean > > -- What most experimenters take for granted before they begin their experiments is infinitely more interesting than any results to which their experiments lead. -- Norbert Wiener https://www.cse.buffalo.edu/~knepley/ <http://www.cse.buffalo.edu/~knepley/>