Opened 16 years ago
Closed 12 years ago
#545 closed defect (fixed)
r.cost warning on negative values
Reported by: | pcav | Owned by: | |
---|---|---|---|
Priority: | major | Milestone: | 6.4.3 |
Component: | Raster | Version: | 6.3.0 |
Keywords: | r.cost | Cc: | |
CPU: | Unspecified | Platform: | Unspecified |
Description
In case ov even a few negative values, r.cost fails badly (running forever). If the cost map contains any negative values, it should either generate a fatal error, or treat such cells as nulls (exclude them or use the null_cost= value) and generate a warning. Thanks Glynn for the hint.
Attachments (1)
Change History (6)
comment:1 by , 16 years ago
comment:2 by , 16 years ago
Glynn: http://lists.osgeo.org/pipermail/grass-user/2009-April/049731.html
Patch proposal attached.
Markus
comment:3 by , 15 years ago
Component: | default → Raster |
---|---|
Keywords: | r.cost added |
follow-up: 5 comment:4 by , 12 years ago
Milestone: | 6.4.0 → 6.4.3 |
---|
Applied to GRASS 6.5.svn in r52740. Needs to be backported to 6.4.
Note:
See TracTickets
for help on using tickets.
Perhaps add a test in the NULL testing section source:grass/trunk/raster/r.cost/main.c@35369#L397
?