-
Notifications
You must be signed in to change notification settings - Fork 30
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
[1pt] PR: Update FIM pipeline to process in Alaska #1106
Conversation
Inputs to be copied from EFS to various locations (S3, ESIP, and the two OWP servers): inputs/3dep_dems/10m_South_Alaska/23_11_07/ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The PR was tested on one non-alaska HUC (12090301) and four Alaska HUCs (19020504, 19020202, 19020301, 19020101) successfully. inundation_nation.py was run to map the results and they look great.
All inputs pushed to all enviros. :) |
…into dev-fim-pipeline-alaska
This PR updates the FIM pipeline to be able to process HUCs in southern Alaska. Running FIM in southern Alaska requires that a different CRS and a few different files be used. Additionally, some of the Alaska HUCs displayed an issue where the input stream density was too high, so this update introduces some logic to adjust the threshold of stream orders to exclude based on whether an Alaska HUC is listed as high or medium-high stream density.
Changes
data/wbd/generate_pre_clip_fim_huc8.py
src/bash_variables.env
src/check_huc_inputs.py
included_huc_list
variable to refer to a HUC list that includes Alaska.src/derive_level_paths.py
src/run_by_branch.sh
src/run_unit_wb.sh
src/utils/shared_variables.py
Testing
Issuer Checklist (For developer use)
You may update this checklist before and/or after creating the PR. If you're unsure about any of them, please ask, we're here to help! These items are what we are going to look for before merging your code.
[_pt] PR: <description>
dev
branch (the default branch), you have a descriptive Feature Branch name using the format:dev-<description-of-change>
(e.g.dev-revise-levee-masking
)dev
branchpre-commit
hooks were run locally/foss_fim/
, run:pytest unit_tests/
)4.x.x.x
Merge Checklist (For Technical Lead use only)