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

Setup a repo for the p1_camels_daily_streamflow evaluation #330

Open
mgdenno opened this issue Nov 17, 2024 · 3 comments · Fixed by #335
Open

Setup a repo for the p1_camels_daily_streamflow evaluation #330

mgdenno opened this issue Nov 17, 2024 · 3 comments · Fixed by #335
Assignees
Milestone

Comments

@mgdenno
Copy link
Contributor

mgdenno commented Nov 17, 2024

We need to setup a separate repo for the p1_camels_daily_streamflow evaluation. The idea here is that the notebooks used to evaluate a particular dataset (e.g., camels_daily_streamflow) should be in their own repo. We could have some set-up notebooks, a clone notebook to clone from S3, and then a series of different notebooks used to evaluate the performance.

@mgdenno
Copy link
Contributor Author

mgdenno commented Nov 19, 2024

ToDo

  • Rename the folders in S3 to be, for example e0_camels_daily_streamflow (remove the "p" which meant protocol)
  • Update evaluations.yaml to ref new folder names
  • Update examples to ref new folder names
  • Create a new repo and put a readme and some example notebooks
    • 01_clone_from_s3.ipynb
    • 02_evaluation_summary.ipynb
    • 03_evaluate.ipynb

@mgdenno
Copy link
Contributor Author

mgdenno commented Nov 19, 2024

@kvanwerkhoven currently the camels_daily_streamflow evaluation dataset contains the camels_daymet_05, marrmot_37_hbv_obj1 and nwm30_retrospective configurations. I am not really sure how those were chosen of they make sense to have in the baseline dataset. I assume the nwm30_retrospective is good to have, but not sure about the others. Trying to get this initial evaluation repo setup to demonstrate our vision. Happy to add of remove configurations as you think makes sense. Lets discuss.

@mgdenno mgdenno modified the milestones: v0.5 Release, AGU 2024 Nov 19, 2024
@mgdenno mgdenno linked a pull request Nov 19, 2024 that will close this issue
@mgdenno
Copy link
Contributor Author

mgdenno commented Nov 19, 2024

Reopening because the new repo is not created yet.

@mgdenno mgdenno reopened this Nov 19, 2024
@mgdenno mgdenno self-assigned this Nov 20, 2024
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

Successfully merging a pull request may close this issue.

1 participant