This page should describe Validation Tests performed for this stand alone feature and should provide links to all the result pages.
| Table of Contents |
|---|
Summary
Short summary of what was done and what was the resultValidation of the generic BGC interface will follow the validation tests of L6_Add phosphorus cycle.
Validation Test 1
Validation Test 1:
...
run clm-
...
bgc sub-model through interface
Date last modified:
Contributors:
...
Gangsheng Wang (Unlicensed)
Provenance: (Run provenance Link, Code Tag, etc.)
Results: (link to results, data and plots)
How was XXX be tested? i.e. how do we know when we have met requirement XXX. Will these unit tests be included in the ongoing going forward?The results should be BFB compared to ALM w/o interface and the most relevant variables (e.g., GPP, NPP, NEE, LAI, HR, vegetation/soil C/N/P pools) will be validated.
Validation Test 2
Validation Test 2:
short-desciption-of-testing-hererun pflotran-bgc through interface
Date last modified:
Contributors:
(add your name to this list if it does not appearGangsheng Wang (Unlicensed)
Provenance: (Run provenance Link, Code Tag, etc.)
Results: (link to results, data and plots)
How was XXX be tested? i.e. how do we know when we have met requirement XXX. Will these unit tests be included in the ongoing going forward?The results from ALM-pflotran coupled run are not required to be BFB as the pflotran-bgc module could be different from clm-bgc. However, we expect to obtain reasonable soil C/N/P pool sizes that are close to the clm-bgc results.