Closed DirkMittelstrass closed 2 years ago
Solve that strange bug about auto-naming the output folder for the reports
@DirkMittelstrass What do you mean here?
@RLumSK The HTML reports are saved correctly in the report_dir
path. However, the images for the report might be saved in the parent directory of the target directory.
Btw: I striked out three points and added another. The package is not dead :-)
As this package is meant for a release at the CRAN server in
Mid-December 2020January 2022, there are some ToDo's left.:create (and test) a tutorial to publish it in the vignette, at luminescence.de and in the GitHub Wiki(The tutorial at luminescence.de/ should be enough for now)Spell- and style-check the documentation and the automatic reports(Many thanks to @eiskeil for the review)Re-iterate(skipped for now; not of importance for basic users and a solvable issue of advanced users)sum_OSLcurves()
. A list ofdata.frame
ormatrix
objects should be accepted(Pulse-pair correction works now. Check signal level is removed)RLum.OSL_correction()
contains unused parameters. Activate them or (temporally) remove themProvide working but fast script examples for all functions for the CRAN testsSolve that strange bug about auto-naming the output folder for the reports(Solved)Move(Done this for kableExtra but not for rmarkdown. Package should now run on Ubuntu smoothly)rmarkdown
andkableExtra
from Imports to Suggests and test their availability in the code.I will strike out the points as they are solved. If I missed something, please write a comment.