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.

Sign up for GitHub

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

Jump to bottom

per-crossing upstream habitat QA/tracking #454

Open
smnorris opened this issue Feb 9, 2024 · 0 comments
Open

per-crossing upstream habitat QA/tracking #454

smnorris opened this issue Feb 9, 2024 · 0 comments
Milestone
v0.6.0

Comments

@smnorris
Copy link
Owner

smnorris commented Feb 9, 2024 •
edited
Loading

To highlight per-crossing regressions like #453, add another query logging per crossing (or barrier) upstream habitat numbers.

If just used for QA, we could just log a few crossings/barriers - but I think logging upstream habitat per-crossing for each model run would be valuable for tracking impacts of changes to methods/parameters/data.
@smnorris smnorris changed the title per crossing QA per-crossing upstream habitat QA/tracking Feb 9, 2024
@smnorris smnorris added this to the v0.4.0 milestone Mar 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
v0.6.0
Development

No branches or pull requests
1 participant
@smnorris