Conversation
This PR replaces plain-text references to PEcAn functions and packages in the book with hyperlinks to the existing pkgdown documentation. The goal is to keep the book focused on concepts and workflows while directing readers to pkgdown for detailed API references. Changes are limited to documentation only and do not affect code execution. Fixes PecanProject#3745
|
"Apologies for the redundant request/commit. I realized I accidentally submitted the same changes twice. Please disregard the duplicate and focus on the latest commit (7bec24b). Thanks!" |
| This chapter describes the available meteorological drivers supported by | ||
| PEcAn and provides guidance on selecting an appropriate dataset. | ||
|
|
||
| ## Available drivers |
There was a problem hiding this comment.
This is a small subset of what's available in data.atmosphere. See the download and met2CF functions in https://github.com/PecanProject/pecan/tree/develop/modules/data.atmosphere/R
| ##### `met`: Meteorological inputs {#xml-run-inputs-met} | ||
|
|
||
| (Under construction. See the `PEcAn.data.atmosphere` package, located in `modules/data.atmosphere`, for more details.) | ||
| -(Under construction. See the |
There was a problem hiding this comment.
This system is pretty mature. Unless the "under construction" is meant to refer to the writing of the text I'd drop that bit
Removed the duplicate 'Example meteorological drivers' list in 02_pecan_standards.Rmd to clean up the introductory content and avoid repetition.
Co-authored-by: Chris Black <chris@ckblack.org>
| - [ERA5](#era5) | ||
| - [PRISM](#prism) | ||
|
|
||
| Note: This section highlights a subset of commonly used meteorological |
There was a problem hiding this comment.
This comment does "future proof" the list a bit, so should be kept, but I was thinking it would be good for you to add more examples
- Add list of available meteorological drivers to meteorology page - Clarify BETY, soil, and vegetation input sections in pecan.xml documentation - Remove redundant introductory text from standards page - Improve cross-referencing between documentation sections
…ecan into docs-add-intro-pages # Please enter a commit message to explain why this merge is necessary, # especially if it merges an updated upstream into a topic branch. # # Lines starting with '#' will be ignored, and an empty message aborts # the commit.
|
@man080107 Apologies that I merged #3766 without realizing how much it overlapped with this one -- I've resolved all the outright merge conflicts, but please review and see if there are further changes you want to make. @mdietze, I think some of your previous comments might be resolved by the newly merged material. |
3 participants
Description
Motivation and Context
Review Time Estimate
Types of changes
Checklist: