...
R is a language and environment for statistical computing and graphics. It is a GNU project which is similar to the S language and environment which was developed at Bell Laboratories (formerly AT&T, now Lucent Technologies) by John Chambers and colleagues. R can be considered as a different implementation of S. There are some important differences, but much code written for S runs unaltered under R.
R is the fastest growing statistical software/language and is rapidly overtaking all others (e.g. SPSS, STATA, & SAS in popularity.) It is growing so quickly that it is probably best to use a google search for finding resources to get you started. In spite of this claim, we'll provide a few resources here since the google search can be completely overwhelming.
Contents
| Table of Contents | ||||||
|---|---|---|---|---|---|---|
|
Product Details
...
You can install R for your personal use and even continue to use it after you leave Carleton.
...
Where Can I Find R?
R (and RStudio) is available on the Windows side in all refreshing labs and classrooms. For a complete list, click here pending LabStatssee: a list of what's where in the labs.
| Anchor | ||||
|---|---|---|---|---|
|
How Do I Request R?
...
You can install R on college owned (or any) equipment by downloading it from here.
...
You can install R on your personal machine by downloading it from here. It is also available for college owned computers via KBOX.
Getting Started with R (and RStudio)
Through our licensed access to Lynda.com, you can get go through the 2+hour 
"Up and Running with R" and/or try a more detailed (6 hr) look via "R-Statistics Essential Training" (This one includes a bit on RStudio as well. RStudio is a convenient and free interface to R that makes it a bit easier to navigate.) Note that you need to login via Carleton for access to these online courses.
...
| HTML Comment | ||
|---|---|---|
| ||
Who To CallWe should talk about this one. We have a request to include who customers / customer groups (Faculty, students, ITS staff) should go to for support questions. I think the idea is that, if RR get a call from e.g. faculty on the application and RR don't have the answer, the RR staff know who in ITS to ask for the answer. Questions, Tips and TricksThe meat and potatoes of the page. Base content should draw from the all existing Wiki content, as well as Web Help Desk, personal experience and other folks in the department. Content can then be added based on questions that we commonly receive, or questions that arise as the result of curricular assignments. Note: In places where step-by-step instructions are appropriate, I would like them written as numbered steps rather than bulleted or as fluent written English. The latter is impractical for the user to follow. The former makes it easier to track where in the process you are. Using numbers also allows you to use bullets for multiple points within a step if necessary. Technical TroubleshootingThis section should only address (potential) technical problems with the application e.g. Photoshop will not launch because of a licensing error. The content should either be instructions on how to resolve the problem, or who to contact to report and/or resolve the problem. Formatting should be basically identical to Questions, Tips and Tricks, and is likely to have more step-by-ste Some of this information may be restricted. Place a link to that here. A good rule of thumb is this: If you are getting troubleshooting information from a public vendor knowledge base, there isn't any reason to restrict it. If you are getting your information from a password protected knowledge base, or any warez site, it should be protected. Miscellaneous InformationI see this section being used for additional helpful information which may not have a corresponding question, but could be persuaded just to roll it in to Questions, Tips and Tricks. An example of content that might appear under this would be information on Photoshop Plug-ins. There is no specific question associated with it, just an informative paragraph. |