headers
Juan Manuel Barreneche | 19 Aug 23:28

address (nil), cause 'memory not mapped'

Dear users,
I got this problem and i don't have a clue of what it could be happening...

The context: i'm running a loop in which i extract information from a raster
map (I work with GRASS and R, using spgrass6 package), and rearrange it to
create a matrix. I've tried it with small maps and it works smoothly, but in
large maps I have to resort to saving data in the hard disk regularly in
order to avoid the "cannot allocate vector of size..." problem (builted in
the loop itself).

Even so, the message "address (nil), cause 'memory not mapped'" appeared,
and i really don't have a clue of what it means.

I run R 2.7.0 on openSUSE 10.2

If anyone can be of any help, it'll be greatly appreciated... below I'm
writing the output i got (and the R.Version() output...)

thank you,

Juan

<grass output>
Null cells excluded from cost evaluation.
Source map is: Floating point (double) cell type
189 rows, 178 cols
Creating some temporary files
Reading riosypondas3000
 100%
Initializing output
(Continue reading)

Permalink | Reply |
headers
Juan Manuel Barreneche | 19 Aug 23:41

Re: address (nil), cause 'memory not mapped'

just to mention that the loop was already running for about 20 hours...

Juan

On Tue, Aug 19, 2008 at 6:31 PM, Juan Manuel Barreneche
<jumanbar <at> gmail.com>wrote:

> Dear users,
> I got this problem and i don't have a clue of what it could be happening...
>
> The context: i'm running a loop in which i extract information from a
> raster map (I work with GRASS and R, using spgrass6 package), and rearrange
> it to create a matrix. I've tried it with small maps and it works smoothly,
> but in large maps I have to resort to saving data in the hard disk regularly
> in order to avoid the "cannot allocate vector of size..." problem (builted
> in the loop itself).
>
> Even so, the message "address (nil), cause 'memory not mapped'" appeared,
> and i really don't have a clue of what it means.
>
> I run R 2.7.0 on openSUSE 10.2
>
> If anyone can be of any help, it'll be greatly appreciated... below I'm
> writing the output i got (and the R.Version() output...)
>
> thank you,
>
> Juan
>
> <grass output>
(Continue reading)

Permalink | Reply |
headers
Roger Bivand | 20 Aug 12:48
Favicon

Re: address (nil), cause 'memory not mapped'

Juan Manuel Barreneche <jumanbar <at> gmail.com> writes:

> 
> just to mention that the loop was already running for about 20 hours...
> 
> Juan
> 
> On Tue, Aug 19, 2008 at 6:31 PM, Juan Manuel Barreneche
> <jumanbar <at> gmail.com>wrote:
> 
> > Dear users,
> > I got this problem and i don't have a clue of what it could be happening...
> >
> > The context: i'm running a loop in which i extract information from a
> > raster map (I work with GRASS and R, using spgrass6 package), and rearrange
> > it to create a matrix. 
...
> > Even so, the message "address (nil), cause 'memory not mapped'" appeared,
> > and i really don't have a clue of what it means.
> >

This question was also posted to the statgrass list, where it belongs. 
The thread will continue there (cross-posting is not a good idea). 
The messages so far do not contain information about what is happening, 
other than that a system() call from the R side, provoking an issue 
in running a GRASS module, should not bring R down. I feel that 
the general workflow is not adequate, and that very possibly 
the same instance of R should not be left running (script the other 
way round from the shell or similar)
(Continue reading)

Permalink | Reply |

Gmane