comp.lang.idl-pvwave archive: archive

Home » Public Forums » archive » .sav format

Show: Today's Messages :: Show Polls :: Message Navigator
E-mail to friend

Re: .sav format [message #52362 is a reply to message #52298]

Tue, 30 January 2007 09:58

JD Smith
Messages: 850
Registered: December 1999

Senior Member

On Tue, 30 Jan 2007 09:40:51 -0800, mgalloy@gmail.com wrote:

> On Jan 30, 6:21 am, "Haje Korth" <haje.ko...@nospam.jhuapl.edu> wrote:
>> Here is what I don't understand. In the first part of the notice that is
>> embedded in the sav files says that ANY reverse engineering is prohibited.
>> It does not distinguish between data and code elements. Thus it is my
>> understanding that nobody will ever be legally allowed to develop any
>> routine that messes with the sav file since it would automatically mean that
>> you would have to apply some sort of reverse engineering magic. The second
>> part of the notice says that I need a license for any non-RSI software that
>> reads/writes sav files. Doesn't that mean that anyone applying for such
>> license automatically incriminates himself/herself???
>
> I don't understand that either. Maybe apply for the license before
> doing the work? (I'm not a lawyer either.)

I think it was just a way to "grandfather in" Craig's work, which
occurred before they had such an explicit policy.

If you, like me, dislike closed and protected data formats (by the
DCMA, no less!), do let ITTVIS know. I mean, even Microsoft is being
forced to consider "open" XML formats for Word files, by government
agencies who refuse to be locked into data types over which they have
no control.

The ability to share data and use it in a variety of different ways is
fundamental to the progress of science. I use SAV files personally
since they are so convenient, but I will not distribute them, and I
always assume they have little long-term archival value. That, to me,
diminishes the value of IDL and its default file format. Luckily,
there are many other types of open, standard formats to choose from
(FITS, HDF, etc.). None offer the convenient mapping to IDL
variables/pointers/etc., but at least they can be read back in in 20
years.

JD

Report message to a moderator

[Message index]

		.sav format By: ChristopherFlorio on Mon, 29 January 2007 04:50
		Re: .sav format By: JD Smith on Tue, 30 January 2007 09:58
		Re: .sav format By: Michael Galloy on Tue, 30 January 2007 09:40
		Re: .sav format By: Paolo Grigis on Tue, 30 January 2007 07:36
		Re: .sav format By: Haje Korth on Tue, 30 January 2007 05:21
		Re: .sav format By: Michael Galloy on Mon, 29 January 2007 13:01
		Re: .sav format By: Craig Markwardt on Sat, 03 February 2007 23:04
		Re: .sav format By: JD Smith on Mon, 29 January 2007 12:49
		Re: .sav format By: Haje Korth on Wed, 07 February 2007 05:10
		Re: .sav format By: JD Smith on Tue, 06 February 2007 15:45
		Re: .sav format By: JD Smith on Tue, 06 February 2007 15:44
		Re: .sav format By: Haje Korth on Tue, 06 February 2007 12:00
		Re: .sav format By: Craig Markwardt on Sun, 11 February 2007 13:53
		Re: .sav format By: Guillermo on Tue, 06 February 2007 11:04
		Re: .sav format By: David Fanning on Tue, 06 February 2007 07:42
		Re: .sav format By: Haje Korth on Mon, 05 February 2007 15:02
		Re: .sav format By: JD Smith on Mon, 05 February 2007 12:46
		Re: .sav format By: Haje Korth on Mon, 05 February 2007 10:27
		Re: .sav format By: JD Smith on Mon, 05 February 2007 09:58
		Re: .sav format By: Craig Markwardt on Sun, 11 February 2007 13:47

Previous Topic:	Arrays of Structures
Next Topic:	Looking for routines to do tidal analysis in IDL

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

] [

]

Current Time: Thu Oct 09 22:10:32 PDT 2025

Total time taken to generate the page: 2.71417 seconds