Closed yantosca closed 3 months ago
For GEOS-Chem Classic, timing information is also saved to a JSON file, so it would be easy to parse that with Python.
The GCHP log file also includes each gridded component broken down into further timing. The section that includes GEOS-Chem looks like this (example is transport tracers simulations hence chemistry is so low):
Min, mean, and max are included to show the range of times across CPUs. Inclusive means it includes subroutines called , while exclusive means it does not (e.g. timer is stopped for the sub-processes).
See PR #319 for sample output. I will also try to scrape the timings of the GCHP component.
This has now been completed, so we can close this issue.
Name and Institution (Required)
Name: Bob Yantosca Institution: Harvard + GCST
Confirm you have reviewed the following documentation
New GCPy feature or discussion
Currently, we have to copy GEOS-Chem Classic and GCHP timing information from log files into a spreadsheet. It would be great if we could have a script to scrape this information and put it into a table.
The script could take an existing file with a table as an optional input argument and append to it. And it could take either one log or a list of logs to create a new table with.
GCHP log file info looks like this:
GEOS-Chem Classic timers info looks like this:
Looking for volunteers!