Kerry Leith

Hi Volker, Good to see we're both right ;) The current 'hazard source material' output was including 0-coded cells as well as 1-coded cells (In fact, it's a good check that the hazard source material in that case is equal to the initial volume!). I've updated the inputs with NaN, and re-run. The output looks as expected. For reference, the initial source depth is up to 10 m, and the maximum depth of material that intersects the 'endangered' polygon is 0.45 m. That looks about right, given the dispersal...

Post removed

Model inputs & outputs

Hi Volker, Apologies for the delay, we've had a lot on here. I just ran a trial of the new version, and the good news is that the Material Flux is now working well, and the 'hazard path' and 'hazard source' terminology is clearer. The not-so-great news is that the 'hazard source material' grid is almost identical (within 10^-5) to the 'material' grid. As usual, I've had a search through the script, and I can't see where it's going wrong. If I had to guess, the error should be that the 'hazard source...

Thanks Volker, While we're at this - this week we're attending the New Zealand Geological Society conference. There's been quite some discussion by a number of presenters regarding not only the location of hazard sources, but also how much material has been derived from each source. On the face of it, it seems a reasonably straightforward task to adjust the material flux and endangered sources commits. You could just pass the Material Flux value, rather than the endangered object ID back to the source...

Perhaps just a comment to improve code legibility. You could change: -ENDANGERED_PATH="Endangered Objects (Path).sg-grd-z" -ENDANGERED_SOURCES="Endangered Objects (Sources).sg-grd-z" To -HAZARD_PATHS="Endangered Objects (Hazard Path).sg-grd-z" ^ -HAZARD_SOURCES="Endangered Objects (Hazard Sources).sg-grd-z" ^

Thanks Volker, Looks good. Does what it says on the box :) Kerry

Hi Volker, Next one.... I've been experimenting with the Endangered Objects output, and find it's really useful. However, the implementation you've chosen using the reverse iterator identifies the path of the debris that intersects the Endangered Object. The attached image presents a post-model DEM, with the material flux overlain (red->blue) by the endangered object paths (pink) that intersect the object polygon (green) - for reference. In our projects, we're particularly interested in the SOURCE...