RE: [ferret_users] "limit on storage for coordinates has been reached"after loading (& canceling) several data sets

["McCann, Mike" <mccann@xxxxxxxxx>]

Thanks Ansley.

 

I'm using Ferret v6 now and don't have this problem.

 

-Mike

---

From: Ansley Manke [mailto:Ansley.B.Manke@noaa.gov]
Sent: Friday, September 29, 2006 12:19 PM
To: McCann, Mike
Cc: ferret_users
Subject: Re: [ferret_users] "limit on storage for coordinates has been reached" after loading (& canceling) several data sets

Hi Mike,
Ok, often files really have regular time axes but just aren't marked as such, so that's often the quickest solution.

More recent versions of Ferret store the coordinates more efficiently than v5.6 does; for a while we stored the coordinate values, plus the upper and lower box-bounds. of each irregular  Since boxlo[n] = boxhi[n-1] we changed this so that we only store the coordinate  values and one set of box edges. With Ferret v6.0 I am able to open up all four of your files without hitting the coordinate storage limit.

In addition, sometime before Ferret v6.0 there was a change to the behavior of CANCEL DATA command so that it does reset the coordinate storage when the variables and their axes are removed.

Ansley


McCann, Mike wrote:

Hi Ansley,

 

The data are not on a regular time axis.  They are observations that may be close to regularly gridded, but may also contain large gaps.

 

The commands below are from a script that reads these irregular data, grids to an hourly time axis, and saves to a file.  I suppose I could do the task in chunks, restarting ferret after each few files.

 

Is there no way to clear the memory taken up for coordinate storage?

 

Thanks,

Mike

---

From: Ansley Manke [mailto:Ansley.B.Manke@noaa.gov]
Sent: Thursday, September 28, 2006 4:37 PM
To: McCann, Mike
Cc: ferret_users
Subject: Re: [ferret_users] "limit on storage for coordinates has been reached" after loading (& canceling) several data sets

Hi Mike,
Are the data really intended to be on regular time axes?  The files are not marked as having regular timesteps, and Ferret's detecting slight variations in the time intervals.  If they're actually regular time steps, you'll have no trouble opening a bunch of files by specifying the /REGULART qualifier on the USE command:

yes? use/REGULART "http://dods.mbari.org/cgi-bin/nph-nc/data/ssdsdata/deployments/m1/200510/m1_imctd_20051020_original.nc"

McCann, Mike wrote:

Hello Ferreters,
 
I can load this data set in a fresh ferret session without error:
 
  

ferret
    

        NOAA/PMEL TMAP
        FERRET v5.60
        Linux(g77) 2.4.18 - 04/09/04
        28-Sep-06 12:17
 
yes?  use "http://dods.mbari.org/cgi-bin/nph-nc/data/ssdsdata/deployments/m1/200510/m1_imctd_20051020_original.nc"
yes?

 
If I load other data sets before I load this one I get the "limit on storage for coordinates has been reached" error, e.g.:
 
  

ferret
    

        NOAA/PMEL TMAP
        FERRET v5.60
        Linux(g77) 2.4.18 - 04/09/04
        28-Sep-06 12:23
 
yes? use "http://dods.mbari.org/cgi-bin/nph-nc/data/ssdsdata/deployments/m1/200510/m1_ctd0000_20051020_original.nc"
yes? use "http://dods.mbari.org/cgi-bin/nph-nc/data/ssdsdata/deployments/m1/200510/m1_ctd0010_20051020_original.nc"
yes? use "http://dods.mbari.org/cgi-bin/nph-nc/data/ssdsdata/deployments/m1/200510/m1_ctd0020_20051020_original.nc"
yes? use "http://dods.mbari.org/cgi-bin/nph-nc/data/ssdsdata/deployments/m1/200510/m1_imctd_20051020_original.nc"
 **TMAP ERR: limit on storage for coordinates has been reached
             MAX= 250000
 **TMAP ERR: limit on storage for coordinates has been reached
             MAX= 250000
 **TMAP ERR: limit on storage for coordinates has been reached
             MAX= 250000
 **TMAP ERR: limit on storage for coordinates has been reached
             MAX= 250000
 **TMAP ERR: limit on storage for coordinates has been reached
             MAX= 250000
 **TMAP ERR: limit on storage for coordinates has been reached
             MAX= 250000
 **TMAP ERR: limit on storage for coordinates has been reached
             MAX= 250000
 **TMAP ERR: limit on storage for coordinates has been reached
             MAX= 250000
yes?



I've tried every CANCEL command I can think of to clear storage, but still get the error, e.g.:

yes? cancel memory/all
 PERMANENT data cleared from memory
 TEMPORARY data cleared from memory
yes? cancel data/all
yes? use "http://dods.mbari.org/cgi-bin/nph-nc/data/ssdsdata/deployments/m1/200510/m1_imctd_20051020_original.nc"
 **TMAP ERR: limit on storage for coordinates has been reached
             MAX= 250000
 **TMAP ERR: limit on storage for coordinates has been reached
             MAX= 250000
 **TMAP ERR: limit on storage for coordinates has been reached
             MAX= 250000
 **TMAP ERR: limit on storage for coordinates has been reached
             MAX= 250000
 **TMAP ERR: limit on storage for coordinates has been reached
             MAX= 250000
 **TMAP ERR: limit on storage for coordinates has been reached
             MAX= 250000
 **TMAP ERR: limit on storage for coordinates has been reached
             MAX= 250000
 **TMAP ERR: limit on storage for coordinates has been reached
             MAX= 250000
yes?



Is there a way I can clear the storage short of restarting Ferret?


Thanks in advance,
Mike

--
Mike McCann 
Software Engineer
Monterey Bay Aquarium Research Institute
7700 Sandholdt Road
Moss Landing, CA 95039-9644
Voice: 831.775.1769  Fax: 831.775.1736 http://www.mbari.org


  

-- 

~>   ~>   ~>   ~>   ~>   ~>   ~>   ~>   ~>   ~>   ~> 

Ansley Manke, NOAA/PMEL   ansley.b.manke@noaa.gov
7600 Sand Point Way NE, Seattle WA
Phone 206-526-6246,  FAX 206-526-6744

    

-- 

~>   ~>   ~>   ~>   ~>   ~>   ~>   ~>   ~>   ~>   ~> 

Ansley Manke, NOAA/PMEL   ansley.b.manke@noaa.gov
7600 Sand Point Way NE, Seattle WA
Phone 206-526-6246,  FAX 206-526-6744