Skip to content

Conversation

@har917
Copy link
Collaborator

@har917 har917 commented Jul 30, 2024

CABLE

Description

Following analysis in CABLE4 and discussion in #354 we should use total SW down in the call to spitter and apply the resultant Fbeam equally to the visible and near-infrared bands. The original intent (cable1.4) of spitter is to evaluate the fraction of SW down that is diffuse in nature - via the beam fraction Fbeam. This was evaluated once based on the total shortwave down. From CABLE2 onwards spitter was called twice - once for the visible and once for the near-infrared components. However the function itself was not adjusted - the result is that beam fraction is universally smaller than the original intent with unknown impacts on the model trajectory.

This change set reverts the evaluation of Fbeam to operate on the total SW down and then applies Fbeam equally to the two radiation bands.

This has been implemented as a bug fix, not on a switch. This change may require recalibration of the CABLE model (notably stomatal conductance parameters, leaf nitrogen exponential and any other parameters that impact GPP).

Fixes #355

Type of change

  • Bug fix
  • New or updated documentation

Checklist

  • The new content is accessible and located in the appropriate section.
  • I have checked that links are valid and point to the intended content.
  • I have checked my code/text and corrected any misspellings

📚 Documentation preview 📚: https://cable--357.org.readthedocs.build/en/357/

@har917 har917 linked an issue Jul 30, 2024 that may be closed by this pull request
@har917
Copy link
Collaborator Author

har917 commented Jul 30, 2024

As expected benchcab comparing MAIN and this branch detected differences in many (but interestingly not all) cases - this is expected. Closer inspection of these files indicates that this occurs in all output variables, in all output timestamps (except for some sites where run starts overnight) indicating exact replication up to the point of first non-zero SW_down which then triggers a change. Detailed output indicates that variability in output over time/correlation between outputs remains qualitatively similar as expected given a bug fix.

benchcab log at
benchmark_cable_qsub.sh.o122014778.txt

Proceeding to me.org for scientific assessment.

@har917
Copy link
Collaborator Author

har917 commented Jul 31, 2024

modelevaluation.org results at

General impression is that not much has changed - there is

  • a general shift from latent to sensible heat
  • slight overall improvement on LE
  • slight degradation on H [configuration dependent])
  • a general decrease in magnitude of NEE and degradation overall
  • no particular difference in impact by PFT type

355-spitter-me-aggregate

@har917
Copy link
Collaborator Author

har917 commented Jul 31, 2024

@ccarouge This looks safe enough to apply as is - however should this go in on a switch?

@har917 har917 requested a review from ccarouge July 31, 2024 03:38
@har917 har917 marked this pull request as ready for review July 31, 2024 03:44
Copy link
Member

@ccarouge ccarouge left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is good to go.

We will have to do a bugfix release for this, it will come in a few weeks I suspect once we agree on what information we should include in.

@har917 har917 merged commit d45a62c into main Aug 29, 2024
@har917 har917 deleted the 355-bug-in-spitter-call-main-branch branch August 29, 2024 02:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

bug in spitter call (MAIN branch)

3 participants