The latest update to Revolution R Open, RRO 3.2.1, is now available for download from MRAN. This release upgrades to the latest R engine (3.2.1), enables package downloads via HTTPS by default, and adds new supported Linux platforms.
Revolution R Open 3.2.1 includes:
- The latest R engine, R 3.2.1. Improvements in this release include more flexible character string handling, reduced memory usage, and some minor bug fixes.
- Multi-threaded math processing, reducing the time for some numerical operations on multi-core systems.
- A focus on reproducibility, with access to a fixed CRAN snapshot taken on July 1, 2015. Many new and updated packages are available since the previous release of RRO — see the latest Package Spotlight for details. CRAN packages released since July 1 can be easily (and reproducibly!) accessed with the checkpoint function.
- Binary downloads for Windows, Mac and Linux systems, including new support for SUSE Linux Enterprise Server 10 and 11, and openSUSE 13.1.
- 100% compatibility with R 3.2.1, RStudio and all other R-based applications.
You can download Revolution R Open now from the link below, and we welcome comments, suggestions and other discussion on the RRO Google Group. If you're new to Revolution R Open, here are some tips to get started, and there are many data sources you can explore with RRO. Thanks go as always to the contributors to the R Project upon which RRO is built.
please stop forcing us to use fixed cran. not everyone is doing reproducible research. Any one who is can use the respective packages to do so.
Posted by: myschizobuddy | July 23, 2015 at 12:33
@myschizobuddy, you don't have to use the fixed CRAN snapshot -- that's merely the default. If you want to use a regular daily-updating CRAN mirror, just add one line to your .Rprofile file.
Posted by: David Smith | July 23, 2015 at 13:00
Download is not possible.
404 Not Found
Posted by: Justfor | July 23, 2015 at 15:55
@JustFor, we've had a few reports of DNS issues when accessing that page. Can you try the link again? We're investigating the cause, but others have reported trying a second time fixes the problem.
Posted by: David Smith | July 24, 2015 at 07:44