[Octave-bug-tracker] [bug #57086] textscan produces a garbled cell array: some data are missing, some values are wrong.

[anonymous]

URL:
  <https://savannah.gnu.org/bugs/?57086>

                 Summary: textscan produces a garbled cell array: some data
are missing, some values are wrong.
                 Project: GNU Octave
            Submitted by: None
            Submitted on: Sun 20 Oct 2019 08:40:19 AM UTC
                Category: Octave Function
                Severity: 3 - Normal
                Priority: 5 - Normal
              Item Group: Incorrect Result
                  Status: None
             Assigned to: None
         Originator Name: Nicky McLean
        Originator Email: address@hidden
             Open/Closed: Open
         Discussion Lock: Any
                 Release: 5.1.0
        Operating System: GNU/Linux

    _______________________________________________________

Details:

   Exactly the same misbehaviour was found with Octave 4.4.0 on a wunduhs XP
system (32-bit) and on rebooting to Linux Mint 64-bit, Octave 4.2.2. On
noticing that the "release" options in the bug submission form now go up to
5.1.0, after an extensive exercise with "flatpak" (there being no apparent
upgrade arrangement for 4.2.2), the same test gives the same results.
   The test run is via file Hic.m, which reads data from file Dave.csv.
   The first problem is that lines of data are lost. The data file has three
heading lines followed by data in records 4 to 7443. But only 6778, or
instead, 6777 sets of values appear in the cell array. The first column of
data contains a date, and the conversion of the date to a daynumber via
datenum failed (this was the initial encounter, involving a much more general
700-line script)  Grist{1}(6777) = 25/03/2013 but Grist{1}(6778) = .49, which
is not valid input for datenum.
   The second problem is that zero values are supplied when the input data
file does not have them. A command scatter(Grist{8},Grist{10}); (temperatures
at the Baring Head site vs. temperatures at Dave's home) shows two zero values
(outside expectations for these data) at elements 1159 and 6777 of Grist{10}.
Inspection of the source data file Dave.csv shows no such zero values.

   The original script file Gnash.m was developed for Matlab and used the name
GnashData instead of Grist as in Hic.m. To the best of my recollection, the
above problems did not occur via MatLab. The data file Dave.csv was written by
a prog. Gnash.exe that has the ability to read in its output format; it found
all data records correct and produced no extraneous zero values.



    _______________________________________________________

File Attachments:


-------------------------------------------------------
Date: Sun 20 Oct 2019 08:40:19 AM UTC  Name: Hic.m  Size: 611B   By: None
Hic.m should read Dave.csv and show some of the odd results.
<http://savannah.gnu.org/bugs/download.php?file_id=47719>
-------------------------------------------------------
Date: Sun 20 Oct 2019 08:40:19 AM UTC  Name: Dave.csv  Size: 566KiB   By: None
Hic.m should read Dave.csv and show some of the odd results.
<http://savannah.gnu.org/bugs/download.php?file_id=47720>

    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?57086>

_______________________________________________
  Message sent via Savannah
  https://savannah.gnu.org/