This week you’ll be working on your projects. This means no separate lab-07 repo for your lab, everything goes in your project repo. Your lab score will be based on having completed these steps and, as usual, individual contributions to the project repo for these particular tasks.
Once you complete these, use the rest of the time to, well, work on your project! Remember, your project assignment is here.
If you haven’t yet done so (I know some team members have not!) go to the course organization on GitHub and clone your project repo titled project-TEAM_NAME. And if you have, pull before you proceed since I’ve made some updates to your repos.
extra
A new folder called extra has been added to your repos. Any extra documents you might have go here. This might include Rmd files you’re using to develop your project, any notes, or anything else. The contents of this folder will not be marked, it’s just a convenient place to store documents and collaborate with teammates without cluttering the rest of your repo.
If you have any extra documents in your repo, move them into this folder. To move files in RStudio: go to your Files pane and check the boxes next to the files you want to move, click on More, and then Move… and select the extra folder.
Commit and push your changes. Once you do, your Check allowed files check should pass.
README
Add your project title and team name to the README.Rmd file in the repo. Knit, commit, and push your changes to README.Rmd and README.md. Observe that these are updated in the README of the repo.
Slides
Open the presentation.Rmd file in the presentation folder, knit the document, and review the presentation format. This is where your presentation will go. Update the YAML with your project title, team name, etc. and commit and push your changes.
Remember that your data lives in a folder called data that is not inside your presentation folder. So you need to specify the path to your data with here::here(“data/name_of_datafile”) in your read_csv() (or similar) function.
Load your data in your presentation.Rmd, knit, and make sure everything works. Commit and push your updated proposal to your project repo.
ghpages
Go to your project repo on GitHub, click on Settings on the top right corner, and scroll down to the section titled GiHub Pages. Under Source, select main branch and the root folder. This will give you a URL where the website for your project will be automatically built from the content in your README. This might take a few minutes. Click on the link to confirm that the website has been built. Once the website is built, pull changes to your project.
This website is public, but your repository will remain private, unless… you as a team decide you would like to feature your repos in your personal GitHub profiles. If so, I will help you convert your repo to a public repo at the end of the semester.
You can see how a project repo website looks here. Click on the link in the presentation section and you should be able to view the rendered slides. This is the link we will use to for your slides during the presentations (if you choose to present “live”, more on this below…).
Click on the gear icon next to About and add a very brief description of your project and the URL of your project website.
Planning
Now that all the logistical details are done, start work on the planning of your project.
Discuss how, if at all, you might incorporate modeling into your project. Note that this is not a requirement, but since we hadn’t introduced modelling at the time of writing your proposal, this is a good time think about how, if at all, you might use modelling in your project.
Discuss next steps for your project, identifying concrete tasks that need to be done. Assign at least one task to each member.
When done, close the issue with the relevant commit. You can do this by prefacing your commits with “Fixes”, “Fixed”, “Fix”, “Closes”, “Closed”, or “Close” and then the number of the issue followed by a hashtag (e.g. Fixes #2). The issue will be closed when you push the changes to your repo.
Each member should then open an issue on the repo with their task, and assign it to themselves. Include as much detail as possible to make sure you remember your discussion.
Strongly recommended: Get a hold of a tutor and run your ideas by them.
Presentations
You have two options for presenting: live during the workshop on Zoom or submitting a pre-recorded video. Logistically, the live presentation might be easier (you show up, give your 5 minute presentation as a team, listen to the presentations of others in your workshop group, and carry on!). But some of you might choose to not do a live presentation if you have geographically distributed members on the team, potentially with tricky internet setup. If so, you might want to pre-record your presentation and submit the video. You can find instructions for pre-recording your presentations here. Discuss as a team which you prefer and submit your preference on the form here. Only one response per team!
