comp.lang.idl-pvwave archive
Messages from Usenet group comp.lang.idl-pvwave, compiled by Paulo Penteado

Home » Public Forums » archive » G4-related problem
Show: Today's Messages :: Show Polls :: Message Navigator
E-mail to friend 
Return to the default flat view Create a new topic Submit Reply
Re: G4-related problem [message #36615 is a reply to message #36021] Sun, 05 October 2003 07:34 Go to previous messageGo to previous message
DPJ is currently offline  DPJ
Messages: 3
Registered: October 2003
Junior Member
Hi Ken,

Thanks for the response. I will post the code I am using (it's only a few
lines long) and also include a data file tomorrow (Monday) when I am back at
work. I will start a new thread. I've checked the ascii file and it is
fine. It certainly *could* be a coding error (I am pretty new to this) but
the code is soooo simple (read in data and look at it), I would be surprised
if this was the problem.

David

"Kenneth P. Bowman" <kpb@null.com> wrote in message
news:kpb-4530AA.11252804102003@corp.supernews.com...
> One possibility is that your ASCII file is corrupted. Another is a
> coding error. Can you post your code (minimum example that demostrates
> the problem)?
>
> Ken Bowman
>
>
> In article <vwzfb.27799$3S.8589@newsread2.news.atl.earthlink.net>,
> "DPJ" <dpjackson@yahoo.com> wrote:
>
>> I have an ascii file with two columns of tab delimited floating point
data
>> (x and y). I have no trouble reading in this data and making a plot of
it.
>> This seems to be true whether there is 5000 lines of data or 50,000
lines of
>> data (I have not tried to rigorously test out if it would fail at some
>> point).
>>
>> However, if I try to read a file with 10 columns of data (x1 y1 x2
y2...),
>> the following happens. The first two columns read in fine but the
following
>> columns do not. This seems to be true no matter how many lines of data
>> there are.
>>
>> They all read in fine up to some point and then there is what appears to
be
>> random integer data for a while, and then good data again. It appears
as
>> though columns 3-9 always have good data up to item 256. That is,
>> data.x3[255] is good while data.x3[256] is bad. Column 10 appears to
"go
>> bad" at item 128.
>>
>> I am really feeling screwed. Going back to OSX 10.1 is not an option.
I
>> don't think my program is doing any graphics before/while this data
input is
>> going on (although it does plot the data after it has been read). I
will
>> try the workaround that Karl suggested to turn off the timer and
hopefully
>> that will work. If anyone has any additional suggestions, please let me
>> know. (Please remember that I am a novice if you respond.) This is
>> important because I have a ton of these data files to analyze.
>>
>> David
>>
[Message index]
 
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: Re: spatial interpolation
Next Topic: idl on linux other than redhat?

-=] Back to Top [=-
[ Syndicate this forum (XML) ] [ RSS ] [ PDF ]

Current Time: Sat Oct 11 07:46:41 PDT 2025

Total time taken to generate the page: 0.88010 seconds