Re: readAsciiHead

From: David Ian Brown <dbrown_at_nyahnyahspammersnyahnyah>
Date: Mon, 19 Jun 2006 13:32:42 -0600

It shouldn't be core-dumping Mike. I'll take a look.
  -dave
On Jun 19, 2006, at 1:23 PM, Michael Notaro wrote:

> Thanks Dennis. On NCAR's tempest, I get:
>
> tempest% ncl
> Copyright (C) 1995-2006 - All Rights Reserved
> University Corporation for Atmospheric Research
> NCAR Command Language Version 4.2.0.a033
> The use of this software is governed by a License Agreement.
> See http://www.ncl.ucar.edu/ for more details.
>
> ncl 0> load "$NCARG_ROOT/lib/ncarg/nclscripts/csm/contributed.ncl"
> ncl 1> head=readAsciiHead("usa_1_fixed_small.ascii",8)
> Bus error (core dumped)
>
>
> Isn't that the same version that you are using? Why do I get an error
> then?
>
> Mike
>
>
> On Jun 19, 2006, at 2:18 PM, Dennis Shea wrote:
>
>>> I am trying to read the 8-line header in the attached ascii file but
>>> I only get a core dump.
>>> What am I doing wrong?
>>>
>>> head=readAsciiHead("usa_1_fixed_small.ascii",8)
>>>
>> ======================
>>
>> Hi Mike,
>>
>> I don't get a core dump . With version a033 I get
>>
>> ====
>>
>>
>> ncl 0> load "$NCARG_ROOT/lib/ncarg/nclscripts/csm/contributed.ncl"
>> ncl 1> head=readAsciiHead("usa_1_fixed_small.ascii",8)
>>
>> ncl 2> head=readAsciiHead("asciiData",8)
>> ncl 3> print(head)
>>
>>
>> Variable: head
>> Type: string
>> Total Size: 32 bytes
>> 8 values
>> Number of Dimensions: 1
>> Dimensions and sizes: [8]
>> Coordinates:
>> (0) File ak001 ak006 ak007 ak008 ak009 ak010 ak011
>> ak012
>> ak013 ak014 ak015 ak016 ak017 ak018 ak019ak020 ak021
>> ak022
>> ak023 ak024 ak025 ak026 ak027 ak028 ak029 ak030 ak031
>> ak032
>> ak033 ak034 ak035 ak036ak037 ak038 ak039 ak040 ak041
>> ak042
>> ak043 ak044 ak045 ak046
>> (1) File ak001 ak006 ak007 ak008 ak009 ak010 ak011
>> ak012
>> ak013 ak014 ak015 ak016 ak017 ak018 ak019ak020 ak021
>> ak022
>> ak023 ak024 ak025 ak026 ak027 ak028 ak029 ak030 ak031
>> ak032
>> ak033 ak034 ak035 ak036ak037 ak038 ak039 ak040 ak041
>> ak042
>> ak043 ak044 ak045 ak046
>> (2) File ak001 ak006 ak007 ak008 ak009 ak010 ak011
>> ak012
>> ak013 ak014 ak015 ak016 ak017 ak018 ak019ak020 ak021
>> ak022
>> ak023 ak024 ak025 ak026 ak027 ak028 ak029 ak030 ak031
>> ak032
>> ak033 ak034 ak035 ak036ak037 ak038 ak039 ak040 ak041
>> ak042
>> ak043 ak044 ak045 ak046
>> (3) File ak001 ak006 ak007 ak008 ak009 ak010 ak011
>> ak012
>> ak013 ak014 ak015 ak016 ak017 ak018 ak019ak020 ak021
>> ak022
>> ak023 ak024 ak025 ak026 ak027 ak028 ak029 ak030 ak031
>> ak032
>> ak033 ak034 ak035 ak036ak037 ak038 ak039 ak040 ak041
>> ak042
>> ak043 ak044 ak045 ak046
>> (4) File ak001 ak006 ak007 ak008 ak009 ak010 ak011
>> ak012
>> ak013 ak014 ak015 ak016 ak017 ak018 ak019ak020 ak021
>> ak022
>> ak023 ak024 ak025 ak026 ak027 ak028 ak029 ak030 ak031
>> ak032
>> ak033 ak034 ak035 ak036ak037 ak038 ak039 ak040 ak041
>> ak042
>> ak043 ak044 ak045 ak046
>> (5) File ak001 ak006 ak007 ak008 ak009 ak010 ak011
>> ak012
>> ak013 ak014 ak015 ak016 ak017 ak018 ak019ak020 ak021
>> ak022
>> ak023 ak024 ak025 ak026 ak027 ak028 ak029 ak030 ak031
>> ak032
>> ak033 ak034 ak035 ak036ak037 ak038 ak039 ak040 ak041
>> ak042
>> ak043 ak044 ak045 ak046
>> (6) File ak001 ak006 ak007 ak008 ak009 ak010 ak011
>> ak012
>> ak013 ak014 ak015 ak016 ak017 ak018 ak019ak020 ak021
>> ak022
>> ak023 ak024 ak025 ak026 ak027 ak028 ak029 ak030 ak031
>> ak032
>> ak033 ak034 ak035 ak036ak037 ak038 ak039 ak040 ak041
>> ak042
>> ak043 ak044 ak045 ak046
>> (7) File ak001 ak006 ak007 ak008 ak009 ak010 ak011
>> ak012
>> ak013 ak014 ak015 ak016 ak017 ak018 ak019ak020 ak021
>> ak022
>> ak023 ak024 ak025 ak026 ak027 ak028 ak029 ak030 ak031
>> ak032
>> ak033 ak034 ak035 ak036ak037 ak038 ak039 ak040 ak041
>> ak042
>> ak043 ak044 ak045 ak046
>>
>> NCL only reads string lengths of 256 ... after that there
>> is silenent truncation.
>>
>> Version a034 yields
>>
>> warning:asciiread: one or more strings truncated because NCL maximum
>> string
>> length (256) exceeded
>>
>> ====
>>
>> this is what I call a "complicated ascii file".
>>
>> You can read the file as character and parse the file yourself.
>>
>> NCL does not provide for the level of character granularity needed.
>>
>> I'd suggest call a fortran subroutine or C function
>>
>> D
>>
>
> _______________________________________________
> 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 Mon Jun 19 2006 - 13:32:42 MDT

This archive was generated by hypermail 2.2.0 : Mon Jun 19 2006 - 15:40:00 MDT