s-news
[Top] [All Lists]

FW: ks.gof bug?

To: "'s-news@lists.biostat.wustl.edu'" <s-news@lists.biostat.wustl.edu>
Subject: FW: ks.gof bug?
From: "Kurbat, Matt" <Matt.Kurbat@kmv.com>
Date: Wed, 21 Mar 2001 11:56:46 -0800
Cc: "Kurbat, Matt" <Matt.Kurbat@kmv.com>
Dear Splus Users,

I have found what may be a bug in ks.gof.  
I've replicated several times and gotten the same result each time.  
My parameters: windows NT, Splus 2000.  



        I try to do the following: 

x<- c( 0.46, 0.08, 0.47, 0.14, 0.35, 0.61, 0.42, 0.13, 0.62, 0.44, 0.66,
0.13, 0.04, 0.17, 0.13,
0.43, 0.02, 0.22, 0.13, 0.27, 0.13, 0.45, 0.41, 0.46, 0.48, 0.83, 0.67,
0.97, 0.37, 0.96,
0.40, 0.33, 0.76, 0.67, 0.31, 0.93, 0.69, 0.65, 0.03, 0.58, 0.07, 0.14,
0.28, 0.32, 0.76,
0.47, 0.65, 0.54, 0.41, 0.89)

ks.gof(x,distribution="uniform",alternative = "two.sided", min=0,max=1)



        What happens is the following:

Splus.exe - Application Error

The instruction at "0x02cc02e2" referenced memory at
"0x03408000".  The memory  could not be "written".

Click on OK to terminate the application.
Click on CANCEL to debug the application.

When I click "CANCEL", Visual C++ is launched
and the following is highlighted:

"02CC02E2   mov         dword ptr [eax*8+305ABB8h],edx"




Does anyone know what is going on, and maybe how to circumvent it?  


Thank you,
Matt

<Prev in Thread] Current Thread [Next in Thread>