[Top][All Lists]

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

Re: Textscan and csv fitness data problem

From: Ben Abbott
Subject: Re: Textscan and csv fitness data problem
Date: Tue, 02 Jan 2018 16:58:40 -0800

> On Jan 1, 2018, at 11:51 AM, PhilipNienhuis <address@hidden> wrote:
> NJank wrote
>> On Jan 1, 2018 12:13 PM, "PhilipNienhuis" &lt;
>> pr.nienhuis@
>> &gt; wrote:
>> NJank wrote
>>> On Jan 1, 2018 9:06 AM, "Thomas Esbensen"
>> As to textscan, Dan did a lot of good work lately, I think the bugs you
>> implied have been fixed in the development branch.
>> Yeah, i noticed that. Would those make it into a 4.2.2 or not until 4.4.0?
>> Been keeping my fingers crossed that it would suddenly "just work" and I
>> wouldn't have to dive into his data again.
> Have a look in the log:
> bugs 52116 and 52479 have been fixed on stable, the last one (bug 52550)
> not. If you want you can ask in the latter bug report to backport it to
> stable.
> As to csv2cell's erroneous column conversion, I've fixed that stupid bug and
> pushed it. To use it, get from here:
> and then do
> mkoctfile
> to build a fixed version. Swap it into place, using 
> "pkg load io; which csv2cell" 
> to find out where it should live, followed by 
> "pkg unload io; clear -f"
> to clear the way for copying (otherwise csv2cell.oct is locked), and then
> copy csv2cell.oct into place.
> Philip

The original file has lines with a varied number of columns.  As a result …

error: csv2cell: incorrect CSV file, line 2 too short

The first row are the column labels (127 of them), and 2nd row only has 19 
columns (18 commas). There are other rows deep in the file with 127 columns too.


reply via email to

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