-
Notifications
You must be signed in to change notification settings - Fork 0
walt
ludwa6 edited this page Nov 13, 2018
·
2 revisions
Currently: i'm working in another repo, where i'm trying to update and port-over my JupyterLab Notebook from Python to R, so i can run checcomi's code in the same environment.
Progress thus far: Have installed R-Studio on my machine, using the Anaconda package manager, which has most of the libraries on which i see that this code depends, but not all.
Here's the list of successes and failures thus far:
- installed packages: (all with prefix of 'r-'):
- library(viridis) # nice color palette
- library(dplyr) # use for fixing up data
- library(readr) # reading in data/csv
- library(RColorBrewer) # for color palettes
- library(purrr) # for mapping over a function
- library(maptools)
- library(ggplot2)
- library(sp)
- library(plotly)
- library(data.table)
- library(stringr)
- library(lubridate)
- library(raster)
- And geotiff and rasterio, related in descr. Also: the MANY dependencies!
- yet to install:
- library(ggmap) # ggplot functionality for maps
- library(magick) # this is call to animate/read pngs
- no... but have r-magic
- library(gpclib)
- library(rgdal)
- library(RStoolbox)
- library(gapminder)
- library(RgoogleMaps)
- library(rasterVis)
All those on the "yet to install" list were not known to my Anaconda package manager; this does not mean that they cannot be installed, but i'm afraid that installing them via some other installer at the command-line might mess-up some dependencies in my software stack... So i would ask:
- Are all these essential tools? Is there any other functionally equivalent substitute? and
- Is there some alternative way of installing that could mitigate the risk of broken dependencies?