Implementing the COARE v3.6 algorithm #36
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The COARE v3.6 algorithm was a bit harder to implement than the v3.5 algorithm, in part because it's a bit harder to define what has changed in this version (at least insofar as the use cases of this code is concerned, i.e., not gas transfer).
The most important changes that I can identify from the COARE v3.6 source code are:
However, the albedo function used in the v3.6 source code utilized a massive lookup table and required user entry for longitude and fractional date, which complicated input data (it would be great if this was consistent between versions). Instead, this implements a middle ground, by providing albedo as a function of latitude but assuming the hour is noon and the day is the equinox, so it's not an exact replica of v3.6 (unlike v3.5, which more or less is an exact replica).
Since the only changes are minor parameter changes and the new sea-state parameterization, so for the most part, running v3.6 will give you the same results as v3.5 to several decimal places for most variables. The only place it's really relevant is in these niche use cases. Therefore, I'm going to add documentation that recommends the user to use v3.5 unless they have a specific reason to prefer v3.6.