RStudio requires R 3. Linux users may need to import RStudio's public code-signing key prior to installation, depending on the operating system's security policy. RStudio requires a bit operating system. If you are on a 32 bit system, you can use an older version of RStudio.
Open Source. Hosted Services. Learn more about RStudio Team. Deliver open source data science at scale Learn how RStudio's enterprise-ready pro products help data science teams securely deploy their work, collaborate, and communicate with decision makers.
See our pro products in action. RStudio Desktop Install R. For example, any of the following installed versions of R will be automatically detected by RStudio Server:. If you have versions of R located at other places in the file system, the RStudio Server can still utilize them. When multiple versions of R are installed you will need to specify which version is the default one for new R sessions. This can be done automatically via the system PATH.
However, several other mechanisms are provided when more flexibility is required. RStudio will therefore by default bind to the same version that is run when R is executed from a terminal.
If you want to override which version of R is used, then you can use the rsession-which-r setting. For example:. You can use the User and Group Profiles feature to specify distinct default versions of R for various users and groups. For example, the following profile configuration uses R 3. Users can also configure their own default version of R.
This is done using the General pane of the Global Options dialog:. See the Disabling Use of Multiple Versions section for details on how to disable version switching entirely either system-wide or on a per-user or per-group basis. This is described in more detail in the Recommended Installation Directories section. In addition, any version of R referenced in an r-version directive within User and Group Profiles is also recognized.
In order to be usable, the R home path must be readable by the RStudio server account usually rstudio-server ; see Access and Security for details. The following table lists the fields that are available for each R entry in the file. It is important that each entry consists of the fields as specified above. Each field must go on its own line. There should be no empty lines between field definitions.
If only the path is being specified, with no label, script, or module, you may simply list the path to the installation as in previous versions. Paths are not separated by a blank line, but they must be separate from extended definitions by a blank line as in the above example. By setting the name of a module in an environment definition, that version of R will be loaded entirely by module.
When a module is defined and the Path is not specified, the default R binary on the path will be used once the module is loaded. Otherwise, if Path is specified, that specific binary will be used.
If you do not specify a Path to the R installation, you must ensure that RStudio Server can load the module by specifying the location of the module shell initialization script for sh. Failure to do so will result in RStudio Server being unable to verify the version, which will cause it to be unavailable for use. After switching, the specified version will be used for the duration of the current session see the section on Multiple R Sessions for more details on the lifetime of sessions.
Newly created R sessions will continue to use whatever default R version has been configured for the user. This is in fact the behavior by default for RStudio projects however can be changed from the the General pane of the Global Options dialog. If you want to prevent users from being able to change R versions entirely you can use the r-versions-multiple option:.
0コメント