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 tutorials to actually go through emulator validation #47

Open
5 tasks
abigailsnyder opened this issue Jun 11, 2020 · 2 comments
Open
5 tasks

Add tutorials to actually go through emulator validation #47

abigailsnyder opened this issue Jun 11, 2020 · 2 comments
Assignees

Comments

@abigailsnyder
Copy link
Contributor

Currently, we have offline r markdowns doing detailed emulator validation that Abigail just...emails to different people. That's not robust. Incorporate as additional tutorials in the package

  • store netcdf data on zenodo so R package utils can pull it, and an example tutorial emulator can be trained o n multiple realizations without including in the package.
  • train
  • validate trained EOFs
  • generate realizations
  • validate generated realizations

These tutorials could then be copied and adjusted by users for other emulators
fldgen-analysis.zip

@kdorheim
Copy link
Contributor

Tip and idea! So I think that this is going to introduce a dependency on rpkgutils which we will want to add in the Remotes section of the DESCRIPTION file. Also idea... may not be work it but could we move the test data to the zenodo cite too to decrease the size of the repo??

@abigailsnyder
Copy link
Contributor Author

could we move the test data to the zenodo cite too to decrease the size of the repo??

Probably. If we're putting multiple realizations of netcdf test data to zenodo for the in depth tutorial, might as well check into the impacts/feasibility of moving all of the test data from the testing suite there too.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants