25 replies to this topic

[Linda Hughes]

I tried this in SAS (thanks to Helmet for filling in the missing lines from the Progesterone guidance), and my CV% from SAS matched Helmet's Phoenix workflow, 33.16. However, my critbound value was different than both of the previous values given here, -0.040468, although I'll admit I'm a poor SAS programmer and I could have errors in handling the datasets.

 

stats06, would it be possible to get the SAS code that your company used? I attached a file with my code.

 

Linda Hughes

[Helmut Schütz]

Hi Linda!

Helmet

Helmut, not Helmet. The first a name, the second not quite. ;-)

CV% from SAS matched Phoenix workflow, 33.16.

Fine, but that's not so important.

However, my critbound value was different than both of the previous values given here, -0.040468

So what did you get?

I attached a file with my code.

Can you please edit you post - the usual story with attached files leading to electronc nirvana (= they are not displayed as a link at all).

[Linda Hughes]

Hi Helmut,

 

Sorry about the misspelling!

 

The critbound value I got was in my post, -0.040468.

 

Simon is going to help me with getting the file attached.

 

Linda

[Helmut Schütz]

Hi Linda!

Sorry about the misspelling!

I have heard that numerous times from English speakers but never saw it written. Helmut - helmet is a running gag in Jim Jarmusch's ‘Night On Earth’. Great movie.

The critbound value I got was in my post, -0.040468.

Fits perfectly with my workflow’s -0.040467813. Good to hear. Now we have three instances where we obtained the same results as SAS. I guess stat06's CRO screwed up.

P.S.: Is the implementation of getting access to internal statistical distributions (most important Chi2, non-central t) in a custom transformation on the to-do-list?

[Linda Hughes]

Hi Helmut,

 

That's great news! I was looking at one of the older posts that still had the typo:

"critbound -0.04467813 CV(%) 33.16"

 

So your Phoenix workflow actually yields -0.040467813, which matches my SAS. That's excellent!

 

About your other question, what is on the to-do list is better support for RSABE. How that will be done is still under discussion. We really appreciate your Phoenix workflows showing folks a way to do this in PHX 1.3.

 

Linda

 

Edit by Simon, the attached file is actually a .sas file. [file name=fastdata.txt size=2939]http://www.pharsight.com/extranet/media/kunena/attachments/legacy/files/fastdata.txt[/file]

[shikha rawat]

hi Linda ,

 

Thanks for confirming the answer... i am sure that the CRO did some mistake in his codes.. i have requested them to send me the same . so if they do i'll post them here and then u can analyze them.

 

regards,

stats06