Skip to content

Commit 267dd22

Browse files
authored
v4.5.14.2 Create inputs for selected HUC(s) (#1178)
1 parent 1d81416 commit 267dd22

5 files changed

Lines changed: 472 additions & 32 deletions

File tree

README.md

Lines changed: 19 additions & 14 deletions
Original file line numberDiff line numberDiff line change
@@ -49,11 +49,6 @@ The available inputs, test cases, and versioned FIM outputs can be found by runn
4949
aws s3 ls s3://noaa-nws-owp-fim/hand_fim/ --profile esip
5050
```
5151

52-
Download a directory of sample outputs for a single HUC8:
53-
```
54-
aws s3 sync s3://noaa-nws-owp-fim/hand_fim/outputs/hand_4_5_2_11/12090301 \
55-
/your_local_folder_name/12090301 --profile esip
56-
```
5752
By adjusting pathing, you can also download entire directories such as the `hand_4_5_2_11` folder. An entire output HAND set is approximately 1.7 TB.
5853

5954
**Note**: There may be newer editions than `hand_4_5_11_1`, and it is recommended to adjust the command above for the latest version.
@@ -138,6 +133,25 @@ docker run --rm -it --name Robs_container \
138133
fim_4:dev_20230620
139134
```
140135

136+
### Subsetting input data
137+
A subset of the data required to run and evaluate FIM can be obtained with the use of ESIP AWS keys. In order to generate these data:
138+
1. Start a Docker container as in the previous step
139+
2. Run `/foss_fim/data/get_sample_data.py` replacing `<aws_access_key_id>` and `<aws_secret_access_key>` with your AWS access keys. To generate data for HUC 03100204, for example:
140+
```
141+
python /foss_fim/data/get_sample_data.py -u 03100204 -i s3://noaa-nws-owp-fim/hand_fim/ -o /outputs/sample-data -r hand_fim -s3 -ak <aws_access_key_id> -sk <aws_secret_access_key>
142+
```
143+
3. Exit the Docker container by typing `exit`. Alternatively, you can leave this container running and run the next command in a new terminal tab or window.
144+
4. Start a new Docker container with the `/data` volume mount pointing at the local output location (`-o`) used in `get_sample_data.py` (step 2). For example:
145+
```bash
146+
docker run --rm -it --name Robs_data_container \
147+
-v /home/projects/fim/code/inundation-mapping/:/foss_fim \
148+
-v /home/projects/fim/data/outputs/:/outputs \
149+
-v /home/projects/fim/data/outputs_temp/:/fim_temp \
150+
-v /home/projects/fim/data/outputs/sample-data:/data \
151+
fim_4:dev_20230620
152+
```
153+
5. Now you can run the following commands with the sample data.
154+
141155
### Produce HAND Hydrofabric
142156
```
143157
fim_pipeline.sh -u <huc8> -n <name_your_run> -o
@@ -161,15 +175,6 @@ The three sections are:
161175

162176
Running the `fim_pipeline.sh` is a quicker process than running all three steps independently, but you can run some sections more than once if you like.
163177

164-
### Testing in Other HUCs
165-
To test in HUCs other than the provided HUCs, the following processes can be followed to acquire and preprocess additional NHDPlus rasters and vectors. After these steps are run, the "Produce HAND Hydrofabric" step can be run for the new HUCs.
166-
167-
```
168-
/foss_fim/src/acquire_and_preprocess_inputs.py -u <huc8s_to_process>
169-
```
170-
Sorry, this tool is deprecated, replacement scripts are coming soon.
171-
172-
173178
### Evaluating Inundation Map Performance
174179
After `fim_pipeline.sh` completes, or combinations of the three major steps described above, you can evaluate the model's skill. The evaluation benchmark datasets are available through ESIP in the `test_cases` directory.
175180

0 commit comments

Comments
 (0)