[BUG/ISSUE] Budget operations table not working for GCHP data sets

[lizziel]

Describe the bug

In testing a different GCPy feature I noticed that the budget operations table values for GCHP are always NaN. For example, here is a GCHP vs GCHP table using the same ref and dev for simplicity.

SOAIE budgets (Ref=14.2.0; Dev=14.2.0)
Full [Gg] : SOAIE
+-------------+-------+-------+--------+------------+
| Operation   |   Ref |   Dev |   Diff |   Pct_diff |
|-------------+-------+-------+--------+------------|
| Chemistry   |   nan |   nan |    nan |        nan |
| Convection  |   nan |   nan |    nan |        nan |
| EmisDryDep  |   nan |   nan |    nan |        nan |
| Mixing      |   nan |   nan |    nan |        nan |
| WetDep      |   nan |   nan |    nan |        nan |
+-------------+-------+-------+--------+------------+

This happens when comparing GCHP (Dev) and GCC (Ref) as well.

ACET budgets (Ref=14.2.0; Dev=14.2.0)
Full [Gg] : ACET
+-------------+----------+-----------+-----------+------------+
| Operation   |      Ref |       Dev |      Diff |   Pct_diff |
|-------------+----------+-----------+-----------+------------|
| Chemistry   | -3.93806 | nan       | nan       |        nan |
| Convection  | -0.00000 | nan       | nan       |        nan |
| EmisDryDep  |  0.00004 | nan       | nan       |        nan |
| Mixing      |  3.11183 | nan       | nan       |        nan |
| WetDep      |  0.00000 |   0.00000 |   0.00000 |        nan |
+-------------+----------+-----------+-----------+------------+

I verified that there are no NaN values in the dataset.

To Reproduce

Turn budget table on when running a 1-month benchmarking with GCHP as dev, or both ref and dev. For my test I used output from a 1-hr run to generate the tables.

Expected behavior

There should be real values in the table for GCHP.

Additional context

This is not an urgent problem because we do not have the operation budget table turned on in GEOS-Chem benchmarking. However, I would like to get this fixed at some point.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. If there are no updates within 7 days it will be closed. You can add the "never stale" tag to prevent the Stale bot from closing this issue.

[github-actions]

Stale issue message

[github-actions]

Stale issue message

[lizziel]

I will test this again for my upcoming budget diagnostic PR.