comp.lang.idl-pvwave archive
Messages from Usenet group comp.lang.idl-pvwave, compiled by Paulo Penteado
Home » Public Forums » archive » FILE_LINES change in 8.4
Show: Today's Messages :: Show Polls :: Message Navigator
E-mail to friend  		Switch to threaded view of this topic Create a new topic Submit Reply
FILE_LINES change in 8.4 [message #92723] Wed, 17 February 2016 06:44 Go to next message
Phillip Bitzer is currently offline  Phillip Bitzer
Messages: 223
Registered: June 2006
Senior Member
Folks-

Weird issue I've come across in the past few days. It seems the behavior of FILE_LINES has changed from 8.4 to 8.5.

I've used a line of code like this since pre-7 days with no problems:

nLines = FILE_LINES(f, /COMPRESS)

where f is a basic gzipped file.

Now, this returns zero for me.

Anyone else using FILE_LINES with compressed files?

Here's a concrete example:

IDL> f='LYLOUT_120522_030000_3600.dat.gz'

(File available here: https://goo.gl/ROaE3J)

Under 8.4, I get:
IDL> file_lines(f, /compress)
123806

but under 8.5 I get:
IDL> file_lines(f, /compress)
0

The file really is gzipped:
$ file LYLOUT_120522_030000_3600.dat.gz
LYLOUT_120522_030000_3600.dat.gz: gzip compressed data, was "LYLOUT_120522_030000_3600.dat", from Unix, last modified: Sat Jul 7 08:30:46 2012, max compression

Running on Mac 10.9.5 FWIW.

Report message to a moderator

Re: FILE_LINES change in 8.4 [message #92724 is a reply to message #92723] Wed, 17 February 2016 07:52 Go to previous messageGo to next message
markb77 is currently offline  markb77
Messages: 217
Registered: July 2006
Senior Member
I see the same thing on Windows x64, IDL 8.5

Report message to a moderator

Re: FILE_LINES change in 8.4 [message #92725 is a reply to message #92723] Wed, 17 February 2016 08:00 Go to previous messageGo to next message
Lajos Foldy is currently offline  Lajos Foldy
Messages: 176
Registered: December 2011
Senior Member
It's a bug. IDL 8.4 works fine:

IDL> print, !version & help, file_lines('LYLOUT_120522_030000_3600.dat.gz', /compress)
{ x86_64 linux unix linux 8.5.1 Nov 14 2015 64 64}
<Expression> LONG64 = 0

IDL> print, !version & help, file_lines('LYLOUT_120522_030000_3600.dat.gz', /compress)
{ x86_64 linux unix linux 8.4.1 Feb 16 2015 64 64}
<Expression> LONG64 = 123806

regards,
Lajos


It's a regressionOn Wednesday, February 17, 2016 at 3:44:15 PM UTC+1, Phillip Bitzer wrote:
> Folks-
>
> Weird issue I've come across in the past few days. It seems the behavior of FILE_LINES has changed from 8.4 to 8.5.
>
> I've used a line of code like this since pre-7 days with no problems:
>
> nLines = FILE_LINES(f, /COMPRESS)
>
> where f is a basic gzipped file.
>
> Now, this returns zero for me.
>
> Anyone else using FILE_LINES with compressed files?
>
> Here's a concrete example:
>
> IDL> f='LYLOUT_120522_030000_3600.dat.gz'
>
> (File available here: https://goo.gl/ROaE3J)
>
> Under 8.4, I get:
> IDL> file_lines(f, /compress)
> 123806
>
> but under 8.5 I get:
> IDL> file_lines(f, /compress)
> 0
>
> The file really is gzipped:
> $ file LYLOUT_120522_030000_3600.dat.gz
> LYLOUT_120522_030000_3600.dat.gz: gzip compressed data, was "LYLOUT_120522_030000_3600.dat", from Unix, last modified: Sat Jul 7 08:30:46 2012, max compression
>
> Running on Mac 10.9.5 FWIW.

Report message to a moderator

Re: FILE_LINES change in 8.4 [message #92783 is a reply to message #92725] Fri, 26 February 2016 14:02 Go to previous messageGo to next message
chris_torrence@NOSPAM is currently offline  chris_torrence@NOSPAM
Messages: 528
Registered: March 2007
Senior Member
On Wednesday, February 17, 2016 at 9:00:51 AM UTC-7, fawltyl...@gmail.com wrote:
> It's a bug. IDL 8.4 works fine:
>
> IDL> print, !version & help, file_lines('LYLOUT_120522_030000_3600.dat.gz', /compress)
> { x86_64 linux unix linux 8.5.1 Nov 14 2015 64 64}
> <Expression> LONG64 = 0
>
> IDL> print, !version & help, file_lines('LYLOUT_120522_030000_3600.dat.gz', /compress)
> { x86_64 linux unix linux 8.4.1 Feb 16 2015 64 64}
> <Expression> LONG64 = 123806
>
> regards,
> Lajos
>
>
> It's a regressionOn Wednesday, February 17, 2016 at 3:44:15 PM UTC+1, Phillip Bitzer wrote:
>> Folks-
>>
>> Weird issue I've come across in the past few days. It seems the behavior of FILE_LINES has changed from 8.4 to 8.5.
>>
>> I've used a line of code like this since pre-7 days with no problems:
>>
>> nLines = FILE_LINES(f, /COMPRESS)
>>
>> where f is a basic gzipped file.
>>
>> Now, this returns zero for me.
>>
>> Anyone else using FILE_LINES with compressed files?
>>
>> Here's a concrete example:
>>
>> IDL> f='LYLOUT_120522_030000_3600.dat.gz'
>>
>> (File available here: https://goo.gl/ROaE3J)
>>
>> Under 8.4, I get:
>> IDL> file_lines(f, /compress)
>> 123806
>>
>> but under 8.5 I get:
>> IDL> file_lines(f, /compress)
>> 0
>>
>> The file really is gzipped:
>> $ file LYLOUT_120522_030000_3600.dat.gz
>> LYLOUT_120522_030000_3600.dat.gz: gzip compressed data, was "LYLOUT_120522_030000_3600.dat", from Unix, last modified: Sat Jul 7 08:30:46 2012, max compression
>>
>> Running on Mac 10.9.5 FWIW.

Yep, I was able to reproduce this. In IDL 8.5 we fixed a different bug to allow GZ files greater than 4 Gb to work properly. That fix inadvertently broke file_lines with gzip compressed files.

It will be fixed in the next IDL version.

Thanks for reporting!

-Chris

Report message to a moderator

Re: FILE_LINES change in 8.4 [message #92788 is a reply to message #92783] Mon, 29 February 2016 03:47 Go to previous message
markb77 is currently offline  markb77
Messages: 217
Registered: July 2006
Senior Member
On Friday, February 26, 2016 at 11:02:34 PM UTC+1, Chris Torrence wrote:
> On Wednesday, February 17, 2016 at 9:00:51 AM UTC-7, fawltyl...@gmail.com wrote:
>> It's a bug. IDL 8.4 works fine:
>>
>> IDL> print, !version & help, file_lines('LYLOUT_120522_030000_3600.dat.gz', /compress)
>> { x86_64 linux unix linux 8.5.1 Nov 14 2015 64 64}
>> <Expression> LONG64 = 0
>>
>> IDL> print, !version & help, file_lines('LYLOUT_120522_030000_3600.dat.gz', /compress)
>> { x86_64 linux unix linux 8.4.1 Feb 16 2015 64 64}
>> <Expression> LONG64 = 123806
>>
>> regards,
>> Lajos
>>
>>
>> It's a regressionOn Wednesday, February 17, 2016 at 3:44:15 PM UTC+1, Phillip Bitzer wrote:
>>> Folks-
>>>
>>> Weird issue I've come across in the past few days. It seems the behavior of FILE_LINES has changed from 8.4 to 8.5.
>>>
>>> I've used a line of code like this since pre-7 days with no problems:
>>>
>>> nLines = FILE_LINES(f, /COMPRESS)
>>>
>>> where f is a basic gzipped file.
>>>
>>> Now, this returns zero for me.
>>>
>>> Anyone else using FILE_LINES with compressed files?
>>>
>>> Here's a concrete example:
>>>
>>> IDL> f='LYLOUT_120522_030000_3600.dat.gz'
>>>
>>> (File available here: https://goo.gl/ROaE3J)
>>>
>>> Under 8.4, I get:
>>> IDL> file_lines(f, /compress)
>>> 123806
>>>
>>> but under 8.5 I get:
>>> IDL> file_lines(f, /compress)
>>> 0
>>>
>>> The file really is gzipped:
>>> $ file LYLOUT_120522_030000_3600.dat.gz
>>> LYLOUT_120522_030000_3600.dat.gz: gzip compressed data, was "LYLOUT_120522_030000_3600.dat", from Unix, last modified: Sat Jul 7 08:30:46 2012, max compression
>>>
>>> Running on Mac 10.9.5 FWIW.
>
> Yep, I was able to reproduce this. In IDL 8.5 we fixed a different bug to allow GZ files greater than 4 Gb to work properly. That fix inadvertently broke file_lines with gzip compressed files.
>
> It will be fixed in the next IDL version.
>
> Thanks for reporting!
>
> -Chris


hi Chris,

Can you give us more details about the change with respect to opening zipped files larger than 4GB?

thanks
Mark

Report message to a moderator

  Switch to threaded view of this topic Create a new topic Submit Reply
Previous Topic: Re: Open Source LiDAR LAS file manipulator for IDL and ENVI
Next Topic: Looping through structures

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

Current Time: Wed Oct 08 11:39:23 PDT 2025

Total time taken to generate the page: 0.00497 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.7.
Copyright ©2001-2013 FUDforum Bulletin Board Software