Re: readAsciiTable

From: Mary Haley <haley_at_nyahnyahspammersnyahnyah>
Date: Thu, 2 Jul 2009 08:52:18 -0600

Hi Jason,

As Dennis stated offline, it would be helpful if we can get a stripped
down version of your script.

One thing that could be a problem here is if you are reading in arrays
of strings.

There is one temporary variable that might be the culprit, and that is

If you look at the $NCARG_ROOT/lib/ncarg/nclscripts/csm/
contributed.ncl code,
and look for the readAsciiTable function, you will see "xs" being used.

Right after it is used in the "asciiwrite" call, you can try deleting


and see if this helps.

Temporary variables should get deleted by NCL, but maybe
there's a problem here.


On Jul 1, 2009, at 11:45 PM, Jason Evans wrote:

> I have a script that reads hundreds of files using readAsciiTable -
> assigning the read data directly into one time-step of a predefined
> variable. Every time readAsciiTable is called more memory is consumed
> and I can't seem to find any way to stop this.
> Is there some way to stop this memory increase? Is there a "temporary"
> variable created in the background that is never deleted (and that I
> never see)?
> Thanks,
> Jason
> --
> Dr. Jason P. Evans
> ARC Australian Research Fellow
> Senior Lecturer
> Climate Change Research Centre
> University of New South Wales
> Sydney, NSW, 2052
> Australia
> email:
> ph: +61-2-9385 7066
> fax: +61-2-9385 7123
> _______________________________________________
> ncl-talk mailing list
> List instructions, subscriber options, unsubscribe:

ncl-talk mailing list
List instructions, subscriber options, unsubscribe:
Received on Thu Jul 02 2009 - 08:52:18 MDT

This archive was generated by hypermail 2.2.0 : Thu Jul 02 2009 - 11:39:38 MDT