Re:Starting data analysis with R: Things I wish I'd been told
by hadley on Sunday November 23, 2014 @08:15PM
(#8650597)
The closest equivalent to virtualenv for R is packrat: http://rstudio.github.io/packrat/. It doesn't (yet) support different R versions for different projects, but that's on the roadmap.
Re:Starting data analysis with R: Things I wish I'd been told
by mrgordon on Monday November 24, 2014 @02:18AM
(#8651381)
Yeah packrat is great! It is a really important package which has greatly increased my willingness to use R in production.
Re:Starting data analysis with R: Things I wish I'd been told
by Gatsky on Sunday November 23, 2014 @07:24PM
(#8650493)
Ok that's good to know. Sure, R breaks inexplicably sometimes due to dependencies, no doubt about that.
virtualenv sounds useful. Is it used much when python code is published in a paper?
About HDF5: I was just making the point that the Pandas docs recommend I install Anaconda to get Pandas, thus also installing HDF5. I am sure there are other ways, but the way the documentation is phrased suggests that these other ways are overly difficult.
Re:Starting data analysis with R: Things I wish I'd been told
by eevilspock on Sunday November 23, 2014 @10:09PM
(#8650884)
I'm just learning Python to do some data and graph ananlysis experiments. Should I go with Python 2 or 3?
Re:Starting data analysis with R: Things I wish I'd been told
by vegabook on Monday November 24, 2014 @03:16AM
(#8651473)
You are strongly encouraged by the Python powers that be to move to 3, and I have only in the past few months begun to agree with them, and that is because some serious standard libraries like asyncio are now only available on 3. It's (finally) the future. However a big caveat is that if you're learning Python, most of the sample code you will find on the web will be 2-based and will not work well under 3. It's not so much the print statement, but range() works subtly differently too now (return a generator not a list - too subtle for beginners to properly understand in my view) and unicode strings can break older code too. Just be aware of these things and move to 3 is my (51/49) advice, but this is a controversial point and others will have differing points of view.
Reproducible computing? The ipython notebook is awesome, though I am not sure if there is anything as good as knitr if your workflow is LaTeX oriented.
R "hands" will usually find Python a backward step when it comes to vectorized data manipulation, but its a forward leap if your data becomes too big or if you have to step out of the comfy environment of exploratory analysis into any form of (even trivial) production settings.
And no you definitely do not need HDF5 to effectively use Pandas.