By: Karthik Janar in data-science Tutorials on 2018-04-30
In this tutorial, you'll learn how to examine your local workspace in R and begin to explore the relationship between your workspace and the file system of your machine. Because different operating systems have different conventions with regards to things like file paths, the outputs of these commands may vary across machines.
However it's important to note that R provides a common API (a common set of commands) for interacting with files, that way your code will work across different kinds of computers.
Determine which directory your R session is using as its current working directory using getwd().
##  "C:/Users/User/DataScience/Articles"
List all the objects in your local workspace using ls().
Some R commands are the same as their equivalents commands on Linux or on a Mac. Both Linux and Mac operating systems are based on an operating system called Unix.
Assign 9 to x using x <- 9.
x <- 9
Now take a look at objects that are in your workspace using ls().
##  "x"
List all the files in your working directory using list.files() or dir().
##  "mytest3.R" "testdir" ##  "testdir2" "workingwithfilesinR.html" ##  "workingwithfilesinR.Rmd"
Check out the help page for list.files with the command ?list.files.
One of the most helpful parts of any R help file is the See Also section. Read that section for list.files.
Using the args() function on a function name is also a handy way to see what arguments a function can take.
Use the args() function to determine the arguments to list.files().
## function (path = ".", pattern = NULL, all.files = FALSE, full.names = FALSE, ## recursive = FALSE, ignore.case = FALSE, include.dirs = FALSE, ## no.. = FALSE) ## NULL
Assign the value of the current working directory to a variable called "old.dir".
Saving it to a variable makes it easy to assign back to the original working directory after this tutorial.
A lot of query functions like getwd() have the useful property that they return the answer to the question as a result of the function.
Use dir.create() to create a directory in the current working directory called "testdir".
## Warning in dir.create("testdir"): 'testdir' already exists
We will do all our work in this new directory and then delete it after we are done. This is the R analog to "Take only pictures, leave only footprints."
Set your working directory to "testdir" with the setwd() command.
In general, you will want your working directory to be someplace sensible, perhaps created for the specific project that you are working on. In fact, organizing your work in R packages using RStudio is an excellent option. Check out RStudio at http://www.rstudio.com/
Create a file in your working directory called "mytest.R" using the file.create() function.
##  TRUE
This should be the only file in this newly created directory. Let's check this by listing all the files in the current directory.
##  "mytest2.R" "mytest3.R" ##  "testdir" "testdir2" ##  "workingwithfilesinR.html" "workingwithfilesinR.Rmd"
Check to see if "mytest.R" exists in the working directory using the file.exists() function.
##  TRUE
These sorts of functions are excessive for interactive use. But, if you are running a program that loops through a series of files and does some processing on each one, you will want to check to see that each exists before you try to process it.
Access information about the file "mytest.R" by using file.info().
## size isdir mode mtime ctime ## mytest.R 0 FALSE 666 2018-04-30 15:33:36 2018-04-30 15:33:36 ## atime exe ## mytest.R 2018-04-30 15:33:36 no
You can use the $ operator - e.g., file.info("mytest.R")$mode - to grab specific items.
Change the name of the file "mytest.R" to "mytest2.R" by using file.rename().
##  TRUE
Your operating system will provide simpler tools for these sorts of tasks, but having the ability to manipulate files programatically is useful. You might now try to delete mytest.R using file.remove('mytest.R"), but that won't work since mytest.R no longer exists. You have already renamed it.
Make a copy of "mytest2.R" called "mytest3.R" using file.copy().
##  FALSE
You now have two files in the current directory. That may not seem very interesting. But what if you were working with dozens, or millions, of individual files? In that case, being able to programatically act on many files would be absolutely necessary.
Provide the relative path to the file "mytest3.R" by using file.path().
##  "mytest3.R"
You can use file.path to construct file and directory paths that are independent of the operating system your R code is running on. Pass 'folder1" and 'folder2" as arguments to file.path to make a platform-independent pathname.
##  "folder1/folder2"
Take a look at the documentation for dir.create by entering ?dir.create . Notice the 'recursive" argument. In order to create nested directories, 'recursive" must be set to TRUE.
Create a directory in the current working directory called "testdir2" and a subdirectory for it called "testdir3", all in one command by using dir.create() and file.path().
dir.create(file.path('testdir2','testdir3'), recursive = TRUE)
## Warning in dir.create(file.path("testdir2", "testdir3"), recursive = TRUE): ## 'testdir2\testdir3' already exists
Go back to your original working directory using setwd(). (Recall that we created the variable old.dir with the full path for the orginal working directory at the start of these questions.0
It is often helpful to save the settings that you had before you began an analysis and | then go back to them at the end. This trick is often used within functions; you save, say, the par() settings that you started with, mess around a bunch, and then set them back to the original values at the end. This isn't the same as what we have done here, but it seems similar enough to mention.
After you finish this lesson delete the 'testdir" directory that you just left (and everything in it)
In this TUTORIAL, you learned how to examine your R workspace and work with the file system of your machine from within R. Thanks for playing!
This policy contains information about your privacy. By posting, you are declaring that you understand this policy:
- Your name, rating, website address, town, country, state and comment will be publicly displayed if entered.
- Aside from the data entered into these form fields, other stored data about your comment will include:
- Your IP address (not displayed)
- The time/date of your submission (displayed)
- Your email address will not be shared. It is collected for only two reasons:
- Administrative purposes, should a need to contact you arise.
- To inform you of new comments, should you subscribe to receive notifications.
- A cookie may be set on your computer. This is used to remember your inputs. It will expire by itself.
This policy is subject to change at any time and without notice.
These terms and conditions contain rules about posting comments. By submitting a comment, you are declaring that you agree with these rules:
- Although the administrator will attempt to moderate comments, it is impossible for every comment to have been moderated at any given time.
- You acknowledge that all comments express the views and opinions of the original author and not those of the administrator.
- You agree not to post any material which is knowingly false, obscene, hateful, threatening, harassing or invasive of a person's privacy.
- The administrator has the right to edit, move or remove any comment for any reason and without notice.
Failure to comply with these rules may result in being banned from submitting further comments.
These terms and conditions are subject to change at any time and without notice.
Most Viewed Articles (in data-science )
Latest Articles (in data-science)
- Data Science
- React Native
- Cloud Computing
- Java Beans
- Mac OS X
- Office 365
- Tech Reviews