I did a lot of scripting on R 3.3.2 , and then I figured out that I have to use version 3.3.3
Problem is package AnomalyDetection doesn't exist on 3.3.3 (don't confuse with anomalyDetection (lower case 'a')).
Can I somehow use that package from older version? Isn't there some thing in R that makes older stuff work on newer version ?
If you have both versions installed and use emacs with ESS, is pretty straightforward to open any of them by typing
M-x R-3.3.2
or
M-x R-3.3.3
So you could just go back to the older version for your specific purposes.
The alternative is, Do you really need to have R-3.3.3 for any specific reason? if no, just install back R-3.3.2 and use it.
Related
When we ssh onto this Linux server, it says Welcome to Ubuntu 16.04.7 LTS (GNU/Linux 4.4.0-193-generic x86_64), so this is the type of server we are on.
When we run R to launch R in the server from terminal, and then version, we get:
What is the easiest way to upgrade from version 3.4.4 to version 3.5.3? We don't want to upgrade to v4 or to the latest version quite yet until we ensure no breaking issues with our codebase on R v4, however we would like to make this upgrade to 3.5.3 so we can run an R library that requires 3.5.3+.
How can we do this from the command line on the server here, and after switching from 3.4.4 to 3.5.3 do we then need to re-install all R libraries on the server as well? I'm worried if I start running stuff from the command line and I mess up that I'll break our current R app.
I would be surprised if there is a .deb available for this OS release/R release combination.
This page only offers R 4.1, but as far back as 16.04 LTS
This page offers older R versions, but only back to 18.04 LTS
It's also possible that one of the backports on the Debian packages page would work on your system (it reports that 3.5.3 is available for Debian "jessie", although I have no idea how that lines up with Ubuntu releases).
I guess it's possible that one of those .debs works for your system though ... ? If you do install from .deb, you may have to be careful not to clobber your current version (e.g. using the --instdir argument to dpkg).
Building from source:
download the source tarball for R 3.5.3
untar, ./configure, make, sudo make install (assuming you have all the necessary development tools, system libraries, etc.; you'll have to troubleshoot/install as you go along)
It might be worth ./configure --prefix=/path/to/testdir to put the new version in a completely separate location, just to make extra-sure you don't stomp on your current install. (This would also simplify the library-path stuff below.)
Packages do need to be re-installed when switching major versions (e.g. 3.4.x to 3.5.x); one way to do it is to copy the system library of packages to a new place (adjust library paths as necessary; see R installation and administration manual).
Then, you should be able to update.packages(checkBuilt=TRUE, ask=FALSE) to update everything.
The tricky spots are (1) getting the library paths right (this will depend a bit on how things are set up in your existing installation; (2) it's conceivable that some current versions of packages on CRAN will fail to re-install/re-build under R 3.5.3. devtools::install_version() would help, although you'd have to track down the correct version manually. I recall someone posting about a package that would install an archived version by date, which could save a lot of poking around ...
I am running R 3.6.1 on a Mac Mini running Sierra and a MacBook Pro running El Capitan. I normally get all the R packages that I need from CRAN or github and use them without issues, but I am trying to install and use an R package (NicheMapR) that requires a fortran compiler and this is giving me issues. Even after installing gfortran, the R package still does not work (the fortran code seems to be compiled but the package installation fails). The package developer suggested that installing R via homebrew might solve the problem. On the contrary, my hunch is that it would lead to a world of pain, to quote Walter from the Big Lebowski. My questions are:
What is the advantage of a homebrew version of R for MacOSX over the "regular" version installed from CRAN?
Can the two versions coexist?
Is the homebrew version going to affect the regular one?
Finally: is homebrew going to help or will it simply open a whole
new can of worms?
Many thanks in advance.
Yes, installing from homebrew is a recipe for pain. It's specifically recommended against by the official CRAN binary maintainer see his remarks from March 2016 on r-sig-mac.
Regarding your questions, this can be summarized as:
What is the advantage of a homebrew version of R for MacOSX over the "regular" version installed from CRAN?
Positives: Select your own BLAS and easily work with geospatial tools.
Downsides: Always needing to compile each R package.
Can the two versions coexist?
Yes. The homebrew version installs into a different directory. But, watch out for library collision (see next question). However, you will have to deal with symbolic linking regarding what version of R is accessible from the console and you will also need to look into using RSwitch to switch between R versions.
Is the homebrew version going to affect the regular one?
Yes, if the library paths overlap. There will be problems regarding package installation and loading. Make sure to setup different library paths. To do so, please look at the .libPaths() documentation.
Finally: is homebrew going to help or will it simply open a whole new can of worms?
Yes and no. Unless you know what you're doing, opt for the CRAN version of R and its assorted goodies.
Thought I'd give MRO a spin, to see if it speeds up my usage in general.
I can't find the installed R though. Not as a separate, not as an overwrite.
/usr/local/bin/R contains R version 3.4.0 (2017-04-21) -- "You Stupid Darkness", which is also the one used by RStudio.
/Library/Frameworks/R.framework/Versions/ also only contains 3.4.
The GUI "Microsoft R Open.app" has the description R 3.3.0 GUI 1.68 Mavericks build... but it also returns 3.4.
What am I missing?
You've identified a bug in the installer. Thanks!
Looks like we are not installing the MRO framework files because the package installer is detecting a newer version (CRAN 3.4). We will get this fixed in the next release.
In the meantime, you can work around this by renaming /Library/Frameworks/R.framework/Versions/3.4 to /Library/Frameworks/R.framework/Versions/0.3.4 and reinstalling MRO. Then go ahead and rename it back.
Please note, as a part of the install we update the symlinks to point to our version, so if you would prefer the default R installation to be CRAN 3.4 please do the install in the reverse order or manually update the symlink to Current in the Versions folder.
I can't access many Bioconductor packages in R 3.1.1 and I am quite disappointed with that. How can I downgrade from R 3.1.1 to R 3.0.2 or to some other version?
Note that this solution is not good enough for me as I don't have any issues with Bioconductor installation.
As point by #Deleet, this is FOR WINDOWS ONLY.
For the rest of the platforms, see: https://support.rstudio.com/hc/en-us/articles/200486138-Changing-R-versions-for-RStudio-desktop
Go to: Tools > Global Options > press the "Change" button (marked in Yellow) >
Select the version you want to use:
OK > OK > Apply > Restart R
Although your problem is not clear enough, I think it could be similar to my current problem ... I am not able to install or use Bioconductor 3.0 packages inside Rkward 0.6.2 with R 3.1.1, but with previous versions of R there were no problems.
I do not know the reasons for this problem, but when I tried to install Bioconductor inside a console (xterm for example, I am using Debian 8.0) there were no problems at all.
I used
source("http://bioconductor.org/biocLite.R")
biocLite()
and it worked fine.
I hope it is useful for you.
I have updated my R to the latest version, that is R version 3.1.0 beta (2014-03-28 r65330). My problems is that ggplot2 does not have a version that supports this R.
How can I fix this issue? I mean I guess I need to install an earlier version of R, but apart from this, which refers to Windows I hadn't found any specific way to install an older version.
UPDATE
#Yilun Zhang I cannot find the place where I should change the R version. Where should it be:
Just try again or tomorrow.
You ended up with a (March 28) prerelease of R 3.1.0 which came today (April 10). The CRAN mirrors were not yet set up for this (at that point: unreleased) version 3.1.0. They are now. You should find ggplot2.
If you are using RStudio and have the older r version:
go to the navigation bar
go to tools
Global options
there is a section where you can choose the r version
If you are using just the R console, just go to the old r directory and open it.