Adriaan Dokter

Hi @gmolto, any chance pulling from AWS ECR will become an option soon in SCAR? Docker Hub has started to implement [pull limits](https://news.ycombinator.com/item?id=24262757). Until last week, I used to use...

Thanks for the pointers @gmolto, I'll look into it!

Thanks very much @srisco for the pointers, I will look into it

@jorge-lip @mariojmdavid any chance AWS ECR support will be added to udocker in the near future? Docker Hub has started to implement [pull limits](https://news.ycombinator.com/item?id=24262757) that are easily met by my...

Should tackle this issue first before writing its associated unit tests.

I was thinking specifically of changing the color palette of the plot, which is problematic. i.e. I can't add a statement `+ scale_fill_gradientn( ....)` to change to color gradient

color gradients are defined [here](https://github.com/adokter/bioRad/blob/9c277cbed7aaf382046e83f9d111836d532a3feb/R/color_scale.R#L21-L39)

The problem occurs only with ggmapping, not ggplotting: ``` my_ppi=project_as_ppi(example_scan) my_map=basemap(my_ppi) map(my_ppi,my_map) + scale_fill_gradientn( colours = c( "black", "grey", "blue", "darkblue", "green", "orange" ) ) ``` 

`map` command for ppi's is coded [here](https://github.com/adokter/bioRad/blob/9c277cbed7aaf382046e83f9d111836d532a3feb/R/map.R#L236-L243). Could the `suppressWarnings()` statement cause the problem?

The problem is that we use `inset_raster` to overlay the data on the map. `inset_raster` requires the datapoints to be already hex color values. Therefore in `bioRad::map` the data are...