Re: readAsciiHead

From: Mary Haley <haley_at_nyahnyahspammersnyahnyah>
Date: Tue, 20 Jun 2006 09:26:10 -0600 (MDT)

Sorry Mike, I wasn't more clear. We fixed the problem of the seg
fault, but the strings are still limited to 256 characters. This
is not considered a bug at the moment, as strings in NCL have
always been limited to 256 characters.

I believe one of our developers is looking into getting rid
of this limitation. I'll email you separately if there's any new
information.

--Mary

On Tue, 20 Jun 2006, Michael Notaro wrote:

> Mary,
> Thanks for your email. I tried using ncl.new just now
> using "head=readAsciiHead("usa_1_fixed.ascii",8)" and it gives
> the the message
> "warning:asciiread: one or more strings truncated because NCL maximum string
> length (256) exceeded."
> When I print "head", it only gives the 1st 256 characters still.
> So it seems the limit to 256 characters in NCL is not fixed but the core
> dump no longer occurs. So can I still no longer read this dataset with NCL?
> Thanks,
> Mike
>
> On Jun 20, 2006, at 10:10 AM, Mary Haley wrote:
>
>>
>> Mike and others,
>>
>> The problem is that the first line of the data file contains a string
>> with more than 256 characters, and NCL's strings are limited to 256
>> characters. We fixed this problem shortly after the latest version
>> (a033) was released, so that you will get a warning message instead of a
>> seg fault.
>>
>> Meanwhile, since you are on an NCAR computer, you can use "ncl.new" on
>> tempest, which contains the latest version of NCL. It is there for
>> test purposes only.
>>
>> If anybody else needs a fix to this problem, you can email me
>> directly and let me know what kind of system you have.
>>
>> --Mary
>>
>>
>> On Tue, 20 Jun 2006, Michael Notaro wrote:
>>
>>> Mary and David,
>>>
>>> On tempest, NCL is running off /contrib/bin/ncl .
>>>
>>> The dataset that I ultimately want to read is /ptmp/notaro/tree/
>>> usa_1_fixed.ascii .
>>> The first 8 rows are the header and the remaining rows are the data
>>> values.
>>> I want to read the station IDs in row 1, species in row 3, elevations in
>>> row 4,
>>> latitudes in row 5, and longitudes in row 6, along with the data values in
>>> rows
>>> 9-909 (for years 1100-2000).
>>>
>>> I could always write a fortran code to read this data but was hoping to
>>> use NCL
>>> if it is able to handle the data. Is it worth trying in NCL still?
>>>
>>> Thanks to everyone for their help.
>>>
>>> Mike
>>> _______________________________________________
>>> ncl-talk mailing list
>>> ncl-talk_at_ucar.edu
>>> http://mailman.ucar.edu/mailman/listinfo/ncl-talk
>>>
>
>
_______________________________________________
ncl-talk mailing list
ncl-talk_at_ucar.edu
http://mailman.ucar.edu/mailman/listinfo/ncl-talk
Received on Tue Jun 20 2006 - 09:26:10 MDT

This archive was generated by hypermail 2.2.0 : Tue Jun 20 2006 - 09:26:46 MDT