My colleagues and I have run r.cva three times and each time there is no sign
of the output raster. It is not in the working mapset or anywhere else in
the filesystem. We are using GRASS 6.2 on Fedora 7 running in vmware on
various Windows machines.
The command appears to be running properly acc
More details on the problem described above: writing the output file is
failing because of a segmentation fault error.
var/log/messages reads
localhost kernel: r.cva[7511]: segfault at 0005 eip 00120040 esp
bfc5a464 error 4
--
View this message in context:
http://www.nabble.com/r.cva-out
What is the size and x-y resolution of your mapset?
Try adjusting the cell sizes so that you have integer cell extents.
Benjamin
rmayer wrote:
> More details on the problem described above: writing the output file is
> failing because of a segmentation fault error.
>
> var/log/messages reads
>
>
> What is the size and x-y resolution of your mapset?
nsres: 86.08807728
ewres: 86.08807728
rows: 3793
cols: 3719
cells: 14106167
> Try adjusting the cell sizes so that you have
> integer cell extents.
r.cva works in this mapset when set to 'random' but
not 'sites' typ
Rebecca Mayer wrote:
>> What is the size and x-y resolution of your mapset?
>
> nsres: 86.08807728
> ewres: 86.08807728
> rows: 3793
> cols: 3719
> cells: 14106167
>
>> Try adjusting the cell sizes so that you have
>> integer cell extents.
>
> r.cva works in this mapset w
By going through the r.cva options I finally figured
out the key to doing 'sites' analysis without
triggering a segfault: use the -i flag. This flag
seems to tell r.cva to ignore fields in the vector map
that may define the parameters spot, offseta, offsetb,
azimuth1, azimuth2, vert1, vert2, radius
Rebecca,
thanks for your feedback. Glad things are working
for you now. I have made notes of all the problems
you reported and put them on my "to do" list for
an r.cva update.
Rebecca Mayer wrote:
> By going through the r.cva options I finally figured
> out the key to doing 'sites' analysis witho
