[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Octave-bug-tracker] [bug #57086] textscan "TreatAsEmpty" option produce

From: Rik
Subject: [Octave-bug-tracker] [bug #57086] textscan "TreatAsEmpty" option produces a garbled cell array
Date: Sun, 20 Oct 2019 22:14:53 -0400 (EDT)
User-agent: Mozilla/5.0 (Windows NT 10.0; WOW64; Trident/7.0; rv:11.0) like Gecko

Update of bug #57086 (project octave):

                 Summary: textscan produces a garbled cell array: some data
are missing, some values are wrong. => textscan "TreatAsEmpty" option produces
a garbled cell array


Follow-up Comment #3:

There is something wrong with the "TreatAsEmpty" option.  I don't know if this
is the only problem, but it certainly exists.

I've attached a simpler example for this.  When there is a pattern that should
be treated as empty and it is in the last position in the file, it is returned
as 0 instead of as NaN.

Incidentally, since the expression in Hic.m is using "TreatAsEmpty", "?" it
should be replacing "?" with NaN everywhere in the file.  If I open up the
data file using a text editor and search and replace to change "?" to NaN and
then use Hic.m to read the file, then there are 7440 data lines as expected.

(file #47724, file #47725)

Additional Item Attachment:

File name: tst_empty.m                    Size:0 KB

File name: tst_empty.csv                  Size:0 KB


Reply to this item at:


  Message sent via Savannah

reply via email to

[Prev in Thread] Current Thread [Next in Thread]