On Sun, Jun 12, 2016 at 2:28 AM, Ken Mankoff <[email protected]> wrote: >> On Fri, Jun 3, 2016 at 4:19 PM, Ken Mankoff <[email protected]> wrote: >> How about distributing it as a docker image? > > A lot of people have suggested Docker. I'm thinking about reproducibility on > the decadal timeframe more than next month or next year. Perhaps that is the > wrong focus? Anyway, I don't trust Docker on these timescales.
Here an example what has been done Topic: Amazon Forest Green-Up During 2005 Drought Science article: http://science.sciencemag.org/content/318/5850/612 Others reproduced the computations: Reproduction of the computations on the article "Amazon Forest Green-Up During 2005 Drought" https://github.com/albhasan/amazonGreenUp2005 The git/docker repo itself is tiny, it basically installs itself, downloads the needed data, processes them, and runs the computations. Quite interesting. In the GRASS GIS case and maybe also your case, a shell/Python script to batch process the data might do the same as you say. Above just for illustration. Best Markus _______________________________________________ grass-user mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/grass-user
