No subject

grass-lists-owner at max.cecer.army.mil grass-lists-owner at max.cecer.army.mil
Thu Aug 19 09:55:44 EDT 1993


***** UNDELIVERABLE MAIL sent to bonifaz, being returned by igiris!bonifaz *****
mail: Error # 8 'Invalid recipient' encountered on system igiris

Received: from max.cecer.army.mil by igiris via SMTP (911016.SGI/890607.SGI)
	(for bonifaz) id AA12771; Thu, 19 Aug 93 06:55:23 -0700
Received: from amber.cecer.army.mil by max.cecer.army.mil with SMTP id AA24329
  (5.67a/IDA-1.5 for <bonifaz%igiris at igiris.igeograf.unam.mx>); Thu, 19 Aug 1993 06:42:43 -0500
Received: from zorro.cecer.army.mil by amber.cecer.army.mil (4.1/SMI-4.1)
	id AA07598; Thu, 19 Aug 93 06:27:49 CDT
Received: from amber.cecer.army.mil by zorro.cecer.army.mil with SMTP id AA09097
  (5.67a/IDA-1.4.4 for <grassu-people at amber>); Thu, 19 Aug 1993 06:27:50 -0500
Received: from max.cecer.army.mil by amber.cecer.army.mil (4.1/SMI-4.1)
	id AA07592; Thu, 19 Aug 93 06:27:39 CDT
Received: from sunl.cr.usgs.gov by max.cecer.army.mil with SMTP id AA24180
  (5.67a/IDA-1.5 for <grassu-list at max.cecer.army.mil>); Thu, 19 Aug 1993 06:27:40 -0500
Received: from dlgeo.cr.usgs.gov by sunl.cr.usgs.gov (4.1/SMI-3.2)
	id AA11027; Thu, 19 Aug 93 06:27:37 CDT
Received: by dlgeo.cr.usgs.gov (5.4.1/1.34)
	id AA05064; Thu, 19 Aug 1993 06:32:13 -0500
Date: Thu, 19 Aug 1993 06:32:13 -0500
From: mcclanah at dlgeo.cr.usgs.gov
Message-Id: <9308191132.AA05064 at dlgeo.cr.usgs.gov>
Sender: grass-lists-owner at max.cecer.army.mil
Reply-To: grassu-list at max.cecer.army.mil
Precedence: Bulk
Sender: grass-lists-owner at moon.cecer.army.mil.
Reply-To: grassu-list at moon.cecer.army.mil.
Precedence: Bulk
To: grassu-list at max.cecer.army.mil
Subject: Re: rle out of memory problem using patch

> We also have the rle landscape structure programs from the
> Univ. of Wyoming.
What is the 'rle landscape structure programs' and how does one
get them from U of W?

> G_calloc out of memory
I am not familiar with the structure of rle(?) files or how the
patch program works, but... I have often seen the G_calloc error when
something like a data file that was created on an Intel machine is 
used on a machine that has the opposite byte ordering. This screws up
the values in a data file and GRASS pukes when it attempts to allocate
large (or negative) amounts of memory. Is it possible that this type of
scenario is true in your case?  Just a thought :)

Let me know if it works.
Pat McClanahan		Internet:mcclanah at dlgeo.cr.usgs.gov
EROS Data Center 		 mcclanah at edcserver1.cr.usgs.gov
Sioux Falls, SD
605-361-4607





More information about the grass-user mailing list