EAMxx: 'computable or allow_invalid_fields' error for shared instance

[jsbamboo]

codebase: a RRMxx branch merged with the 25/11/03 master

e3sm.log:

8232 BACKTRACE:
 8233 /p/lustre2/zhang73/GitTmp/wprrmxx/WPRRMxx_251103_ctp_qmr/components/eamxx/src/share/io/scorpio_output.cpp:920
 8234 
 8235 FAILED CONDITION: 'computable or allow_invalid_fields'
 8236 
 8237 BACKTRACE:
 8238 /p/lustre2/zhang73/GitTmp/wprrmxx/WPRRMxx_251103_ctp_qmr/components/eamxx/src/share/io/scorpio_output.cpp:920
 8239 Error! Cannot compute a diagnostic. One dependency has an invalid timestamp.
 8240  - stream name: eamxx_wprrm.1hI_1x1_160E170E2.5N12.5N_Betts.yaml
 8241  - diag name: p3_T_mid_tend_vert_sum_dp_weighted
 8242  - dep  name: p3_T_mid_tend

this issue did not occur in a similar RRMxx branch that was merged with the 25/09/01 master. Could be related to PR #7715 ?

the issue only occurs for physics tend (p3, rrtmg, shoc), not for homme tend and other vars (e.g., shoc_cond) in my tests

[mahf708]

There's also another related PR that should be investigated: #7824

[mahf708]

Technically, p3_T_mid_tend isn't a diag, is it? I thought it was treated like a FM field

[jsbamboo]

yes I shouldn't have said diag - I just used that word to refer to an output var issue...

[bartgol]

I think #7824 may be the culprit. The tendencies are computed as "internal" fields now, and the base class does not automatically update their stamp. I can push a quick PR fix.