Dear grass-users and developers,
I am currently using grass 7 svn version 48293.
( Part Output of command " svn info" Last Changed Rev: 48293 )
Software and Hardware specifications of my computer are listed below:
Hardware: AMD Phenom(tm) II X6 1055T Processor, 2 * 1 tb hard disk, 16 gb
ram, grap
On Thu, Nov 17, 2011 at 6:03 AM, Pankaj Kr Sharma wrote:
> Dear grass-users and developers,
>
> I am currently using grass 7 svn version 48293.
> ( Part Output of command " svn info" Last Changed Rev: 48293 )
>
> Software and Hardware specifications of my computer are listed below:
> Hardware: AMD
Pankaj Kr Sharma wrote:
> I am getting error " WARNING: Subprocess failed with exit code 9 " from
> r.watershed command , whenver I use more than 8.5 gb ram.
The "exit code 9" could either refer to an exit status or a signal. I
suspect it's the latter. Signal 9 is SIGKILL, which may be sent by t
Dear Users and Developers,
Further details with debug level 3 attached.
On Thu, Nov 17, 2011 at 8:46 PM, Glynn Clements wrote:
>
> Pankaj Kr Sharma wrote:
>
> > I am getting error " WARNING: Subprocess failed with exit code 9 " from
> > r.watershed command , whenver I use more than 8.5 gb ram.
Pankaj Kr Sharma wrote:
> I am getting error " WARNING: Subprocess failed
> with exit code 9 " from r.watershed command ,
> whenver I use more than 8.5 gb ram.
probably the task wants more RAM.. does it work
for a smaller region?
if you are running linux, try adding another 20gb
of virtual disk s
Pankaj wrote:
> Is there any GRASS - internal limit on usage of
> memory.
No, not that I know of. Usually it is the operating
system which poses the limit.
there is of course the possibility of a small bug
somewhere getting in the way, but for the most
part I would expect it to cope with large ra
Hamish wrote:
> note that at a region size of 46341 x 46341 we
> get to 2^31 cells, and to the point where a signed
> 32bit integer overflows and wraps backwards on
> itself. If that were the case I'd suspect a malloc
> error or a segfault not SIGKILL, but it may be a
> clue.
your region is 42001x
Hamish wrote:
> note that at a region size of 46341 x 46341 we
> get to 2^31 cells, and to the point where a signed
> 32bit integer overflows and wraps backwards on
> itself. If that were the case I'd suspect a malloc
> error or a segfault not SIGKILL, but it may be a
> clue.
The value of 9 indi
Dear Grass users and developers,
The region is only 42001 * 42001 i.e. smaller than the limit of 46341 x
46341.
The module r.watershed didn't work without -m due to memory requirement.
So, the next best, I thought was to assign RAM as much as possible.
And I began trying with 15500 MB downwards.
I
Glynn Clements wrote:
>
> AFAICT, r.watershed requires far more memory than just the size of the
> underlying raster data. It's possible that it isn't interpreting the
> memory= parameter correctly.
Yes, there was an error in the distribution of memory over the various
temporary data structures, f
Pankaj Kr Sharma wrote:
> Dear Grass users and developers,
>
> The region is only 42001 * 42001 i.e. smaller than the limit of 46341 x
> 46341.
> The module r.watershed didn't work without -m due to memory requirement.
> So, the next best, I thought was to assign RAM as much as possible.
> And I b
11 matches
Mail list logo
