[Top][All Lists]

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

Re: data set opening bug

From: John Darrington
Subject: Re: data set opening bug
Date: Sun, 7 Feb 2016 15:23:59 +0100
User-agent: Mutt/1.5.21 (2010-09-15)

On Sun, Feb 07, 2016 at 12:50:58PM +0100, ftr wrote:
     Thank you for the clarification. It did not know these details.
     When you search for PSPP for Windows the first result that pops
     up is for and is version 0.9.0-g745ee3.
     - This is the one that took half a day to install here - .
     There is a warning in the first line of the site that the version
     0.9.0 is not fully tested, but a little later on the site states:
     There are no known issues with this release.
     Maybe a more cautionary phrase would help.
     When you look at the sourceforge the site
     lets you download a snapshot version:
     So the alternatives are either snapshot or snapshot ? and are not controlled
by the PSPP developers.   Those have been set up by Harry Thijssen 
(who is normally active on this list) as a service to those who find
it useful.  (Harry, maybe you could consider ftr's suggestions?)

     So, where do you get a real production version ?

     BTW: The snapshot version produced frequencies, but not always.
     And when you are waiting for the result the window remains blank.
     The user doesn't whether pspp works or crashed.

The qog_std_cs_jan16.sav  dataset which you posted earlier contains only:

 -   Numerical (scale) variables.
 -   Variables which are unique for each case.
 -   Variables which have only one value for the entire dataset.  

As such, I cannot see that there is any FREQUENCIES command which would
produce interesting results.  

Nethertheless, like you say, it does seem to take an extraordinarily long time 
to run, and I wouldn't have expected it on a dataset of that size.   I also
tried the same exercise with version 0.8.5 (the most recently released version)
and it seemed somewhat quicker.  So maybe this is a problem that we need to 
     I am not a programmer but if there could be a line in this case
     that tells "prog is working" or better "case no xxx being
     treated" this would be reassuring.

You are right. This would be better.  In fact there is an outstanding
wishlist item for this:


Avoid eavesdropping.  Send strong encryted email.
PGP Public key ID: 1024D/2DE827B3 
fingerprint = 8797 A26D 0854 2EAB 0285  A290 8A67 719C 2DE8 27B3
See or any PGP keyserver for public key.

Attachment: signature.asc
Description: Digital signature

reply via email to

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