search

JGCRI / JGCRIutils

Common utilities for JGCRI work
MIT License
1 stars 0 forks source link

Other ideas for JGCRIutils? #2

Open bpbond opened 9 years ago

bpbond commented 9 years ago

Logging (see #1 ) is done for the moment. Do people have other ideas for useful functionality that a JGCRIutils package could provide? Are there particular tasks you either find yourself re-implementing again and again, or wish lists?

If you have ideas, enter 'em below...

amundra commented 9 years ago

I would like a standard ggplot2 style. Things I always copy from previous pieces of code are the theme parameters and resolution/size for saving the plot. I know there is already some function somewhere that takes care of a part of these.

bpbond commented 9 years ago

@amundra can you give specific examples of settings you frequently find yourself setting? I'm thinking we could have, for example, theme_jgcri_standard(), theme_jgcri_alternate(), etc.

@amundra check out the cowplot package and in particular its vignette here: https://cran.r-project.org/web/packages/cowplot/vignettes/introduction.html

bpbond commented 9 years ago

Another possibility would be to encourage use of the lightweight checkpoint package:

The goal of checkpoint is to solve the problem of package reproducibility in R. Specifically, checkpoint solve the problems that occur when you don't have the correct versions of R packages. Since packages get updated on CRAN all the time, it can be difficult to recreate an environment where all your packages are consistent with some earlier state.

To solve this, checkpoint allows you to install packages from a specific snapshot date. In other words, checkpoint makes it possible to install package versions from a specific date in the past, as if you had a CRAN time machine.

I'm not sure how this would work w.r.t. JGCRIutils, though. We could have a best_practices() function that encourages people to use checkpoint? Auto-load checkpoint? Hmm...

pralitp commented 9 years ago

We already have parts of this in other places. In particular the GCAM diagnostics, and IIASA data system. Should we try to pull them all in here / reduce duplication /fix add features /and then try to back port them from where they came?

Pralit On Sep 16, 2015 3:10 PM, "Ben Bond-Lamberty" notifications@github.com wrote:

Logging (see #1 https://github.com/JGCRI/JGCRIutils/issues/1 ) is done for the moment. Do people have other ideas for useful functionality that a JGCRIutils package could provide? Are there particular tasks you either find yourself re-implementing again and again, or wish lists?

  • process GCAM inputs or outputs?
  • have an in-house, customized ggplot2 style?
  • automatic upload/download to IIASA or other institutions?
  • reboot_computer_for_nth_time() for @cahartin https://github.com/cahartin ?

If you have ideas, enter 'em below...

— Reply to this email directly or view it on GitHub https://github.com/JGCRI/JGCRIutils/issues/2.

bpbond commented 9 years ago

Good question. It depends on how broad we want something like JGCRIutils to be--that is, should GCAM diagnostics and IIASA data system be their own individual packages?

My personal inclination, I guess, is to have individual packages for different tasks, rather than a single all-encompassing JGCRI package, but happy to be convinced otherwise.

Either way, it would be great to get them onto GitHub I think.