| | 8 | * General Documentation needs to be reviewed to verify for readability and that it matches the actual functionality (does pressing the button do what it says) |
| | 9 | * Model docs need to be reviewed for |
| | 10 | * Clarity |
| | 11 | * That units on parameters are correct and properly formatted |
| | 12 | * That Equation matches what the code does |
| | 13 | * Completeness - elements of documentation are: |
| | 14 | * title |
| | 15 | * tool tip |
| | 16 | * Parameter table |
| | 17 | * Paragraph describing what the function does |
| | 18 | * equation used |
| | 19 | * Fig obtained when model is run with default parameters as listed in table above |
| | 20 | * Reference |
| | 21 | * NEW REQUIREMENT |
| | 22 | * Added by: name, ON: date |
| | 23 | * checked by: name, ON: date |
| | 24 | These last can be added by "DANSE" if old models with no name, or source if imported from other package, etc. |
| | 25 | |
