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

Empty data is always automatically set as the punched raster #18

Open
Qinyh123 opened this issue Apr 30, 2024 · 3 comments
Open

Empty data is always automatically set as the punched raster #18

Qinyh123 opened this issue Apr 30, 2024 · 3 comments

Comments

@Qinyh123
Copy link

Hello, the input parameters I've set are:

Read path: /f_driver/tdem/
Read filename: left
Write path: /f_driver/tdem/
Write filename: left
CHeads file: NULL
Read extension: bil
Write extension: bil

Parameters for preprocessing

write_hillshade: true
min_slope_for_fill: 0.0001
surface_fitting_window_radius: 90
print_channels_to_csv: true
remove_seas: true
threshold_contributing_pixels: 100

Parameters for floodplain extraction

use_absolute_thresholds: true
relief_threshold: 10
slope_threshold: 0.05
threshold_SO: 4
fill_floodplain: true

Parameters to get the valley centreline

channel_source_fname: coords.csv
get_valley_centreline: false
convert_csv_to_geojson: true
centreline_loops: 5
trough_scaling_factor: 0.5
extract_single_channel: true
search_radius_nodes: 20

Parameters for valley widths

get_valley_widths: true
width_node_spacing: 50
valley_banks_search_radius: 50

However, when the program runs, it always exits with the message:

"PRINT THE PARAMETERS..."
Read filename is: /f_driver/tdem/left
Write filename is: /f_driver/tdem/left
Data Type = 4
Got the dem: /f_driver/tdem/left
I am going to use the raster
/f_driver/tdem/.bil as the punched raster.
Segmentation fault (core dumped)

I'm not sure where the problem is occurring. Could you please provide more details or debug information?

@simon-m-mudd
Copy link
Member

Hello, it looks like you are running this analysis using lsdtt-basic-metrics (that is the only place where the last message occurs)
Can you confirm you are running this driver file using lsdtt-valley-metrics ?

@Qinyh123
Copy link
Author

Qinyh123 commented May 2, 2024

Sorry about that, I didn't manage to download the section for extracting valley widths from lsdtopotools yesterday. I actually thought that module was included.

@fclubb
Copy link
Member

fclubb commented May 2, 2024

We have also been working on a Python notebook in Google Colab to calculate the valley widths, which you might want to try and might find easier. if you want to try it you can access it here. It means you run LSDTopoTools in your browser using Google's cloud service.

You would need to have a Google account. To open it in Google Colab, just click on the link and then click the little button that says "Open in Colab". You would then need to upload your DEM to Colab, and make sure you download the data that's generated at the end.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants