New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add R Markdown work flow to 01-rstudio-intro #427

Open
rgaiacs opened this Issue Sep 9, 2018 · 3 comments

Comments

Projects
None yet
4 participants
@rgaiacs
Contributor

rgaiacs commented Sep 9, 2018

http://swcarpentry.github.io/r-novice-gapminder/01-rstudio-intro/index.html has

There are two main ways one can work within RStudio.

  1. Test and play within the interactive R console then copy code into a .R file to run later.
  2. Start writing in an .R file and use RStudio’s short cut keys for the Run command to push the current line, selected lines or modified lines to the interactive R console.

What about add R Markdown work flow? I know that it is a variant of the R script workflow but for beginners might worth mention it.

@jcoliver

This comment has been minimized.

Collaborator

jcoliver commented Sep 12, 2018

Thanks for the suggestions, @rgaiacs . I worry a little about adding to the cognitive load of our audience at this point. The nuanced difference between point #2 (R scripts) and an R Markdown workflow, which proceeds much the same way (write R code, push the current line, selected lines, modified lines, current block, selected blocks, or modified blocks to the interactive R console) might be unnecessarily distracting at this point. But I'd still be interested to know what point #3 would look like...

@carmelwoods

This comment has been minimized.

carmelwoods commented Nov 13, 2018

@rgaiacs I had the same thought when I was preparing to teach this lesson. But now that I've taught it a couple of times, I can see how it's better to delay the introduction of R Markdown to the later section Producing reports with knitr. I think one or two new concepts at a time is all people can handle.

@mawds

This comment has been minimized.

Collaborator

mawds commented Nov 23, 2018

I agree with @carmelwoods and @jcoliver - I think it adds too much cognitive load at the start of the course

(especially if users save their notebooks in a subdirectory off the project directory - which the "good enough practices for scientific computing in http://swcarpentry.github.io/r-novice-gapminder/02-project-intro/index.html implies they should. The .Rmd file takes its location as its working directory, which can be confusing).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment