Repository navigation
Add explicit weights_file configuration option - #98
toakinrele wants to merge 3 commits into
Conversation
|
@toakinrele Thanks for the PR! Could you push the |
|
Thanks! The file is only 3.1 KB, so I added |
quinnylee
left a comment
There was a problem hiding this comment.
Overall functionality looks good! Pytests are passing locally.
Only thing I would ask for is maybe a unit test in test_forcingprocessor.py to test the weights override functionality
There was a problem hiding this comment.
@toakinrele Thanks for this PR! The changes here look good though a couple things before we merge.
There are a couple checks to see if plotting will proceed and one of them will be influenced by these changes.
Here:
forcingprocessor/src/forcingprocessor/processor.py
Lines 973 to 978 in e9782e8
and here:
forcingprocessor/src/forcingprocessor/processor.py
Lines 1324 to 1329 in e9782e8
Ideally we perform this check in only one spot, and it seems like that first location is ideal. Could you combine these with the logic you're implementing in this PR?
Also, this branch is from your forked repo, so please clone the original repo, make a branch, and PR that one. This allows the git actions tests to run that require the AWS secrets stored in the CIROH-UA repo.
|
I’ve addressed the review comments and added the weights_file override test. The new test passes locally, along with the plotting test and the local output tests. I also tried pushing the branch directly to
Could you grant me permission to push a branch to the upstream repository, or create the branch there so I can push the changes and allow the AWS-dependent GitHub Actions to run? |
|
@arpita0911patel could we get @toakinrele permissions? |
|
Thank you @toakinrele for this PR! Provided write permission to you for this repo. |
|
Closing this pr as this work has moved to #99 |
Summary
Adds an explicit
weights_fileconfiguration option so precomputed forcing weights can be provided separately fromgpkg_file.Previously, precomputed weights could be passed through
gpkg_fileas a workaround. This change separates the two inputs while preserving the existing GeoPackage-based behavior whenweights_fileis not provided.Changes
weights_filein the forcing configuration.weights_fileis provided.gpkg_fileworkflow when noweights_fileis provided.gpkg_fileavailable for operations that require the hydrofabric.Testing
Tested using
cat-1555522_subset.gpkgand precomputedweights.parquet.Compared forcing output from the existing GeoPackage-based workflow against the new explicit
weights_fileworkflow:TrueTrue0.0Closes #45