The Design Document page provides a description of the algorithms, implementation and planned testing including unit, verification, validation and performance testing. Please read Step 1.3 Performance Expectations that explains feature documentation requirements from the performance group point of view.
Design Document
In the table below 4.Equ means Equations and Algorithms, 5.Ver means Verification, 6.Perf - Performance, 7. Val - Validation, 
- competed, 
- in progress, 
- not done
Overview table for the owner and an approver of this feature
1.Description | Addition of phosphorus cycle in ALM, coupled to carbon and nitrogen cycles |
| 2.Owner | Xiaojuan Yang |
| 3.Created | |
| 4.Equ | |
| 5.Ver | |
| 6.Perf | |
| 7.Val | |
| 8.Approver | Peter Thornton |
| 9.Approved Date |
Title: Implement prognostic phosphorus cycle into ACME land model
Requirements and Design
ACME Land Group
Date: 09/15/2015
Summary
The importance of nutrient in regulating carbon(C)-climate feedbacks has been increasingly recognized. While ACME V0 includes prognostic nitrogen(N) cycle and C-N interactions, phosphorus(P), the most limiting nutrient in productive lowland tropical forests, has yet to be considered. Here we implement prognostic P cycle and C-N-P interactions into ACME land model. This implementation will lead to a more accurate representation of C-nutrient interactions in ACME.
References:
Yang, X., Thornton, P. E., Ricciuto, D. M., and Post, W. M.: The role of phosphorus dynamics in tropical forests – a modeling study using CLM-CNP, Biogeosciences, 11, 1667-1681, doi:10.5194/bg-11-1667-2014, 2014.
Yang, X., Post, W. M., Thornton, P. E., and Jain, A.: The distribution of soil phosphorus for global biogeochemical modeling, Biogeosciences, 10, 2525-2537, doi:10.5194/bg-10-2525-2013, 2013.
Requirements
Requirement: Implement prognostic phosphorus cycle
Date last modified: 09/15/2015
Contributors: @ Xiaojuan Yang
All the needed phosphorus state and flux variables are added. Both geochemical and biological phosphorus processes are represented.
Requirement: Represent C-N-P interactions
Date last modified: 09/15/2015
Contributors: @ Xiaojuan Yang
This includes (1) P limitation on carbon cycle processes (2) biochemical mineralization through phosphatase activity
Requirement: Resolve N limitation vs P limitation
Date last modified: 09/15/2015
Contributors: @ Xiaojuan Yang
With both N and P in the model, N limitation vs P limitation is resolved to represent overall nutrient constraint on carbon cycle processes
Requirement: Model initialization for various P pools
Date last modified: 09/15/2015
Contributors: @ Xiaojuan Yang
Phosphorus cycle operates on geological time scales, it is not reasonable to spinup the model for tens of millions of years for model initialization. Instead we initialize the slow P pools globally with P maps that was generated(Yang et al., 2013)
Algorithmic Formulations
Design solution: Implement prognostic phosphorus cycle
Date last modified: 09/16/2015
Contributors: Xiaojuan Yang
All algorithmic formulations can be found at section 2.1.3 and 2.1.4 in Yang et al. (2014)
Design solution: Represent C-N-P interactions
Date last modified: 09/16/2015
Contributors: Xiaojuan Yang
All algorithmic formulations can be found at section 2.1.3 and 2.1.4 in Yang et al. (2014)
Design solution: Resolve N limitation vs P limitation
Date last modified: 09/16/2015
Contributors: Xiaojuan Yang
All algorithmic formulations can be found at section 2.1.2 in Yang et al. (2014)
Design solution: Implement prognostic phosphorus cycle
Date last modified: 09/16/2015
Contributors: Xiaojuan Yang
The initialization can be found at Yang et al.(2013)
Design and Implementation
Implementation: Implement prognostic phosphorus cycle
Date last modified: 09/16/2015
Contributors: Xiaojuan Yang
This section should detail the plan for implementing the design solution for requirement XXX. In general, this section is software-centric with a focus on software implementation. Pseudo code is appropriate in this section. Links to actual source code are appropriate. Project management items, such as svn branches, timelines and staffing are also appropriate. How do we typeset pseudo code?
Planned Verification and Unit Testing
Verification and Unit Testing: short-desciption-of-testing-here
Date last modified:
Contributors: (add your name to this list if it does not appear)
How will XXX be tested? i.e. how will be we know when we have met requirement XXX. Will these unit tests be included in the ongoing going forward?
Planned Validation Testing
Validation Testing: short-desciption-of-testing-here
Date last modified:
Contributors: (add your name to this list if it does not appear)
How will XXX be tested? What observational or other dataset will be used? i.e. how will be we know when we have met requirement XXX. Will these unit tests be included in the ongoing going forward?
Planned Performance Testing
Performance Testing: short-desciption-of-testing-here
Date last modified:
Contributors: (add your name to this list if it does not appear)
How will XXX be tested? i.e. how will be we know when we have met requirement XXX. Will these unit tests be included in the ongoing going forward?