Strange output for timing results #248
Description
I just did an AMRClaw run and noticed some strange timing results for the regridding time. I don't have a lot of insight into what might have happened, other than that I had set the regrid interval to 1 (regrid every time step) and the buffer region to 0. I've saved the data files and setrun.py file, as well as the example.
============================== Timing Data ==============================
Integration Time (stepgrid + BC + overhead)
Level Wall Time (seconds) CPU Time (seconds) Total Cell Updates
clock_rate 1000
1 62.787 62.664 0.492E+07
2 130.457 130.201 0.443E+08
3 107.296 107.045 0.379E+09
total 300.540 299.910 0.428E+09
All levels:
stepgrid 64.123 63.988
BC/ghost cells 154.562 154.231
Regridding -2146807.188 675.064
Output (valout) 28.806 28.371
Total time: -2146472.862 1008.295
Using 1 thread(s)
Note: The CPU times are summed over all threads.
Total time includes more than the subroutines listed above
Note: timings are also recorded for each output step
in the file timing.csv.