Sure, that's a great catch, thanks for bringing it up! Would you be willing to open a PR for the same?

Yes, do those timings seem reasonable to you? I.e. 10-15 mins. I haven't actually taught this episode so unsure how long it takes in real life.

Yup, I've personally never spent longer than ten minutes but 10-15 sounds perfect. :)

I went to open a PR and noticed that exercise time is also missing from other episodes e.g. http://swcarpentry.github.io/r-novice-inflammation/02-func-R/index.html. It might be worth someone going through all the lessons to check, but I didn't yet have time.

Also, changing these will require updating the home page (http://swcarpentry.github.io/r-novice-inflammation/) to update the timings, but I wasn't able to work out how to do this or whether it is done automatically.

I noticed the same thing, It looks like every episode in the lesson has 0 mins for exercises.
Happy to open a pull request for all, just want to check the timings seem sensible:

1. Analyzing patient data: 10-15 mins as @worcjamessmith suggests
2. Creating functions: 10 mins
3. Analyzing multiple data sets: 10 mins
4. Making choices: 10-15 mins
5. Command-line programs: 5 mins
6. Best Practices for Writing R Code: 5 mins
7. Dynamic Reports with knitr: 5 mins
8. Making Packages in R: 3 mins
9. Introduction to RStudio: 0 mins
10. Addressing Data: 7 mins
11. Reading and Writing CSV Files: 5 mins
12. Understanding Factors: 5 mins
13. Data Types and Structures: 7-10 mins
14. The Call Stack: 2-3 mins
15. Loops in R: 0 mins

I'd also echo the question about whether the timings on the main page are updated manulally or automatically for this.

Hi @ubdbra001. Thanks for going over these, the timings look great. I can't recall at the moment if they are updated or not, we can deal with that in a separate PR. Please go ahead with the timings from lesson 2 onwards. @worcjamessmith It would be good to have a PR relating to the first lesson :)

Great will do!

Hi @worcjamessmith & @ubdbra001, thanks again for catching this and offering to fix it.

Are you still interested and available to submit pull requests for this?

We're always happy to let people contribute directly but if it doesn't work for you, I can integrate the changes myself and mark you as co-authors of the changes.