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

seeking help #276

Open
ErinBecker opened this Issue Jun 1, 2017 · 6 comments

Comments

Projects
None yet
5 participants
@ErinBecker
Collaborator

ErinBecker commented Jun 1, 2017

Submitted via email for instructor checkout ---

Notes on Contribution to R
“Seeking help” section
These contributions are needed in the ‘seeking help’ section
• In R studio, in order to set your working directory, go to session, click on set working directory and choose directory where you have your data apart from the ‘setwd()’ command
• If your computer or laptop switch off during your work using R studio and you have been saving the scripts in the R script, all you have to do is

o Open R studio
o Click on file, a drop-down will come up, click on recent file (the folder you have been working with will be there, click on it and all the scripts will return)

@hkronenb

This comment has been minimized.

Contributor

hkronenb commented Jun 6, 2017

Would it potentially make more sense to put the setwd() command in the "Project Management with R Studio" section. I could actually see both going in that section but particularly setwd() because it has tips about putting files in directories and saving data in certain directories.

@naupaka

This comment has been minimized.

Member

naupaka commented Jun 8, 2017

I think general best-practice these days is to use RStudio projects to keep paths set properly, as opposed to setting the path itself with setwd() via console or GUI. Certainly seems to be easiest approach IME, especially for beginners.

I agree that setting paths seems like a better fit for the Project Management section.

@bbolker

This comment has been minimized.

Contributor

bbolker commented Jul 2, 2017

I would vote for including the setwd() stuff somewhere. I would prefer not to unnecessarily lock the lessons into one particular approach (i.e. using RStudio projects), and changing working directories is an issue that is definitely going to come up in practice, no matter how much you try to avoid it by using projects.

@naupaka

This comment has been minimized.

Member

naupaka commented Jul 3, 2017

I definitely agree with that sentiment, @hkronenb @bbolker. Probably would fit best in Project Management episode. I'd be happy to review a PR adding this content to that episode.

@naupaka

This comment has been minimized.

Member

naupaka commented Jan 8, 2018

See also discussion on #332

@jcoliver

This comment has been minimized.

Collaborator

jcoliver commented Jan 18, 2018

In my workshop experiences, setwd often ends up in headaches (because it happened somewhere, and it takes a while for instructor or helper to figure out why the files aren't being found). The one benefit is that this affords an "opportunity" to teach getwd.

Is there a way to introduce setwd explicitly, early on, and explain what it does (and the implications)? I would love to propose a solution, but I avoid it myself. Some analogous issues arise with attach.

fmichonneau pushed a commit that referenced this issue Jun 19, 2018

Merge pull request #276 from rgaiacs/274
Make Jekyll ignore .Rproj
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment