Re: 0.6.0-10 PSPP windows - Queries (WinXP)

[David Purdy]

Ben,

 

Many thanks for the feedback.

 

> 1) Very long file save time ?

 

I was using the GUI version - the disk didn't seem to be especially active, nor PSPP using a lot of CPU time (I think).   I should mention that the file was saved in the 'portable' format (9Mb/90mins) - I've since saved the 'portable' file in the 'system' format instead (3Mb/2 mins), and the 'system' version also seems to load much more quickly.

 

Presumably the Command line version is pspp.exe ? - Although C:\Cygwin\usr\local\bin\pspp.exe won't run, an error message says it can't find cygwin1.dll (it's here: C:\Cygwin\bin\cygwin1.dll)

 

> 2) Copy from Output1 Window ?

 

I've noticed that, after a frequency computation, a file called C:\Cygwin\psppire.txt is created - which contains the output (but the file disappears immediately after 'quitting !).

 

Also, when following the frequency computation with a crosstabs computation, the crosstabs computation seems to take a long time, but this is shortened considerably by *deleting* psppire.txt *in between* the two computations - the crosstabs computation having then created its own output file, also called psppire.txt

 

Regards,

 

Dave.

 

----- Original Message -----

From: Ben Pfaff

To: David Purdy

Cc: address@hidden

Sent: Friday, August 01, 2008 4:52 AM

Subject: Re: 0.6.0-10 PSPP windows - Queries (WinXP)

"David Purdy" writes:

> 1) Very long file save time ? - I'm using a large third party SPSS .sav file
> (417 fields x 510,121 records = 265 Mb), but am only interested in 7 fields. 
> To ease the processing load, I deleted the unwanted fields in PSPP, but the
> resultant .sav file took over 90 minutes to save (9 Mb).   Are there any
> settings that could be adjusted to reduce the file save time ?

Wow!  That's a long time.  I don't know, off-hand, why it would
take that long.  Is the disk active during that time?  Is PSPP
using a lot of CPU time?  Is this in the GUI or the command-line
syntax version?

Increasing the workspace to a value larger than the size of your
file might help, e.g. SET WORKSPACE=300000.

> 2) Copy from Output1 Window ? - The select all/copy doesn't
> appear to paste into Windows notepad or Word 2003.  Is there
> another way of saving the output data ?

I vaguely remember another Windows user reporting the same
problem.  I think that this must be a Windows-specific bug that
we will have to have a Windows developers take a look at.
--
Ben Pfaff
http://benpfaff.org