Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add sample VIC input/output dataset to archive #50

Closed
tbohn opened this issue Aug 25, 2013 · 2 comments
Closed

Add sample VIC input/output dataset to archive #50

tbohn opened this issue Aug 25, 2013 · 2 comments
Assignees
Milestone

Comments

@tbohn
Copy link
Contributor

tbohn commented Aug 25, 2013

We currently have a small sample dataset posted on the vic website for people to download and play with as an example. One reason for adding this to the archive could simply be because when people download the model source code, it's nice for them to just get the sample dataset with it.

Another reason would be because different VIC versions require different parameters and/or different formats for the input files. It would be good to be able to tag these and associate them with the version of the model that they correspond to.

Theoretically, this could be extended to archiving the inputs (and even outputs) of various projects. But I'm leaning away from that - it could take up a lot of space and wouldn't really lend itself to incremental deltas. It's probably best just to publish them elsewhere and make a note of the exact VIC version that worked with them. Perhaps the way to handle this is: if you archive a version of VIC (like my dissertation work) on a support branch, you should archive a small set of sample inputs (e.g., veg library, global parameter file with the various options visible, one cell's worth of soil, veg, etc. parameters and forcings and states) along with it?

@bartnijssen bartnijssen added this to the 4.2 milestone Mar 27, 2014
@jhamman jhamman modified the milestones: 5.0, 4.2 Sep 25, 2014
@bartnijssen bartnijssen modified the milestones: 5.0, 4.2 Oct 10, 2014
@bartnijssen
Copy link
Member

Important - but I do not want to delay the V4.2 upgrade

@jhamman
Copy link
Member

jhamman commented Mar 24, 2016

closed via #387

@jhamman jhamman closed this as completed Mar 24, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants