I started working on a test implementation of the outputs file structure based loosely on this sketch by Kale:
When working with .Rmd files (assuming a distinct .Rmd file per "analysis"), the working directory is assumed to be the location where that .Rmd file is stored. If storing .Rmd files in a version of the scheme above, this effectively breaks access to the input_files and R_functions folders. The solution I've found is the use the function here() from the R package here to coerce file paths to include the root folder to enable access to the input_files and R_functions folders
example:
I think making this edit to fw_creel.Rmd would be harmless working from the root folder, while enabling project specific copies to work from a sub-folder. Thoughts? @kalebentley @daauerbach
I started working on a test implementation of the outputs file structure based loosely on this sketch by Kale:
When working with .Rmd files (assuming a distinct .Rmd file per "analysis"), the working directory is assumed to be the location where that .Rmd file is stored. If storing .Rmd files in a version of the scheme above, this effectively breaks access to the input_files and R_functions folders. The solution I've found is the use the function here() from the R package here to coerce file paths to include the root folder to enable access to the input_files and R_functions folders example:
I think making this edit to fw_creel.Rmd would be harmless working from the root folder, while enabling project specific copies to work from a sub-folder. Thoughts? @kalebentley @daauerbach