Closed jakobjassmann closed 2 years ago
Forgot to say @logan-berner you will also have to run devtools::document()
before regenerating the PDF manual with devtools::build_manual(path = "man/manuscript/")
. Sorry!
@jakobjassmann - I added examples to all functions and then cleaned up and rebuilt the documentation. The examples rely on an example dataset that I generated using your example for lsat_export_ts(). Those data are located in data/. I wasn't able to run devtools::build_manual(path = "man/manuscript/")... evidently because tinytext isn't installed, isn't available for R/4.0.2, and out of my bandwidth to track down today. Anyways, it would be great if you could do a final read through and package build!
Nice job Logan! I just ran the checks and rebuild the manual.
During the checks I receive the following errors:
Warning: [lsat_evaluate_phenological_max.R:29] @examples mismatched braces or quotes
Warning: [lsat_fit_phenological_curves.R:45] @examples mismatched braces or quotes
Error: unexpected symbol in:
"lsat.pheno.dt <- lsat_fit_phenological_curves(lsat.dt, si = 'ndvi)
lsat.gs.dt <- lsat_summarize_growing_seasons(lsat.pheno.dt, si = 'ndvi"
I suggest we add a documentation for the dataset. The r-pkgs books has a chapter on that: https://r-pkgs.org/data.html#documenting-data with some simple guidelines. In brief: You have to create an .R file with the name of the dataset in /R and write a roxygen header. There are some important details on how a dataset roxygen header differs to a fucntion - see link.
I rebuild the manual for you. 1fda742576920cf3b0d55ac7903afb0cea347ab3
Thanks @jakobjassmann! That was all a stupid missing quote that I accidently propagated while copy/pasting examples between functions. I fixed those errors, updated function documentation, and added documentation for lsat.example.dt dataset following the guidelines you sent.
@logan-berner I finished with a first full run through of the documentation. Here are the most critical points that need to be addressed.
We need to:
If you have devtools and tinytext installed, then you can regenerate the PDF with
devtools::build_manual(path = "man/manuscript/")
.Personally, I found it easier to spot issues in the PDF than in the roxygen documentation.
Very happy to help with a final read through once you have polished the documentation for all your functions! Just let me know :)