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
Hi Linda! [quote]Helmet[/quote] Helmut, not Helmet. The first a name, the second not quite. 
[quote]CV% from SAS matched Phoenix workflow, 33.16.[/quote] Fine, but that’s not so important. [quote]However, my critbound value was different than both of the previous values given here, -0.040468[/quote] So what did you get? [quote]I attached a file with my code.[/quote] 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).
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
Hi Linda! [quote]Sorry about the misspelling![/quote] 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. [quote]The critbound value I got was in my post, -0.040468.[/quote] 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?
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]Certara | Drug Development Solutions (2.87 KB)
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