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

NDR runoff proxy index depends on watershed extent #1741

Open
emlys opened this issue Jan 16, 2025 · 1 comment
Open

NDR runoff proxy index depends on watershed extent #1741

emlys opened this issue Jan 16, 2025 · 1 comment
Assignees
Labels
science request A request/proposal from within natcap related to science (rather than engineering)
Milestone

Comments

@emlys
Copy link
Member

emlys commented Jan 16, 2025

@phawthorne raised this issue:
The runoff proxy index is calculated as $RPI_i = RP_i / RP_{av}$ (dividing runoff proxy by average runoff proxy within the watersheds). This is problematic because average runoff proxy $RP_{av}$ changes depending on which pixels/watersheds are included in the raster. @phawthorne said they have even considered inserting fake pixel values into the RP raster in order to change the $RP_{av}$. We could expose the $RP_{av}$ parameter and allow the user to specify it instead.

@emlys emlys added the science request A request/proposal from within natcap related to science (rather than engineering) label Jan 16, 2025
@phawthorne
Copy link
Member

Thanks for opening this, @emlys! An additional issue is that this makes it hard to run the model under different climate scenarios because any shifts in average precipitation between the baseline and future scenarios get normalized out so we can't actually assess the impact of the change. With an exposed $RP_{av}$ value, we could, for example, calculate $RP_{av}^{baseline}$ and then apply the same value to future scenarios.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
science request A request/proposal from within natcap related to science (rather than engineering)
Projects
None yet
Development

No branches or pull requests

4 participants