2026-01-20 assignment and help

[btupper]

Hi All,

@aanh1009 @aabrossi @Ajordan00 @calebboxwell @IzzyTheChromodoris @jabren26-dev @lrkerm28-spec @livmacel @lnblom28 @pkhuat @rohanunis @shantgard @snnaroola @canura8818 @ngvt1n @zoeahmiegbe @SeascapeScience @btupper

From Nick

If you have a start on the text for your report and would like to get preliminary feedback please email your work to me.

From Ben

I'll be hosting 2 drop in hours via zoom tomorrow... one at 9am and one at 6pm using this zoom You can always shoot me an email, too. The home is described at the end of the "Covariates" section.

[btupper]

I made a mistake regarding running Rmarkdown files - I'm sorry about that! Here are a couple of things you can do to fix my mistake.

1. Adjust the path in setup.R

Modify this block of code in your setup.R so that the full path description to the functions directory is passed to list.files(). On our Colby Forecasting server that might look like this...

for (f in list.files("/home/<username>/<ColbyForecasting>/functions", 
                     pattern = glob2rx("*.R"), 
                     full.names = TRUE)) {
  source(f, echo = FALSE)
}

Of course, you would replace <username>/<ColbyForecasting> with your username on the server (not on github) and with the name you gave to your project directory.

2. Adjust the path used for source("setup.R") in your Rmarkdown code block.

Include the full path to setup.R in the Rmarkdown block when you source it.

source("/home/<username>/<ColbyForecasting>/setup.R")

Again, you would replace <username>/<ColbyForecasting> with your username on the server (not on github) and with the name you gave to your project directory.

If that doesn't resolve things for you then hop on one of the help sessions or reach out via email.

[btupper]

BTW, the makers of RStudio provide a "cheatsheet" with the most common tasks when creating Rmarkdown documents. In fact, the provide many other "cheatsheets". Enjoy!