|
Helmut ★★★ ![]() Vienna, Austria, 2013-03-08 15:47 (4835 d 20:45 ago) Posting: # 10174 Views: 13,459 |
|
|
Dear all, yesterday EMA’s PK working party published Rev. 7 of the Q&A document. According to the new #14:
![]() Note 1: The CI in the pooled analysis is not affected if compared to a model without Bonus question: What if p <0.05? Note 2: Phoenix/WinNonlin-users: Such a setup was already needed for an ‘all fixed-effects’ model. Model Specification > Fixed Effects > Stage+Sequence+Sequence*Stage+Subject(Sequence*Stage)+Period(Stage)+Treatment
— Dif-tor heh smusma 🖖🏼 Довге життя Україна! ![]() Helmut Schütz ![]() The quality of responses received is directly proportional to the quality of the question asked. 🚮 Science Quotes |
|
ElMaestro ★★★ Denmark, 2013-03-08 16:12 (4835 d 20:20 ago) @ Helmut Posting: # 10175 Views: 11,142 |
|
|
Hi Helmut, ❝ yesterday EMA’s PK working party published Rev. 7 of the Q&A document. According to the new #14:
![]() Thanks for posting this. Given that they request those sequence-related fixed factors it sounds to me like they implicitly are assuming that all two-stage studies are crossovers. While it is of course true that Potvin & Montague so far only studied those cases I can't believe the intention is to eliminate an option for parallel 2-stage studies. But what do I know?!? — Pass or fail! ElMaestro |
|
d_labes ★★★ Berlin, Germany, 2013-03-08 16:40 (4835 d 19:52 ago) @ Helmut Posting: # 10176 Views: 11,447 |
|
|
Dear Helmut! ❝ yesterday EMA’s PK working party published Rev. 7 of the Q&A document. According to the new #14:
![]() Numbering by me First: Thanx for this valuable information! Indeed I have a 2-stage study under way. Second: From Potvin et.al.: "If the individual ln-transformed data are to be used in the analysis instead of the differences, then the error term derived from the GLM ANOVA model including sequence2, stage1, period(stage)5, treatment6, subject(sequence × stage)4 will give the appropriate s2 term." Thus the emphasis should be at sequence × stage .❝ Note 1: The CI in the pooled analysis is not affected if compared to a model without subject(sequence × stage)... Typo? If you fit without subject(sequence × stage) you would omit totally the subjects effects! This will heavily affect the CI I guess. If you meant sequence × stage you are totally right. Since stage and sequence are between-subjects effects the additional inclusion of the sequence × stage interaction is only a further breakdown of the subjects effect. The question is why the mighty oracle want us to include such a term .BTW: Where did your p-value came from? — Regards, Detlew |
|
Helmut ★★★ ![]() Vienna, Austria, 2013-03-08 17:43 (4835 d 18:49 ago) @ d_labes Posting: # 10177 Views: 11,018 |
|
|
Dear Detlew! ❝ First: Thanx for this valuable information! Indeed I have a 2-stage study under way. You are not alone. ![]() ❝ Second: From Potvin et.al.: ❝ "If the individual ln-transformed data are to be used in the analysis instead of the differences, then the error term derived from the GLM ANOVA model including ❝ ❝ will give the appropriate s2 term." ❝ Thus the emphasis should be at Yep. Doesn’t the order of factors influence the analysis in SAS as well (aka type III limbo)? ❝ ❝ Note 1: The CI in the pooled analysis is not affected if compared to a model without subject(sequence × stage)... ❝ ❝ Typo? If you fit without subject(sequence × stage) you would omit totally the subjects effects! This will heavily affect the CI I guess. ❝ If you meant Sure – bloody typo; corrected. ❝ Since stage and sequence are between-subjects effects the additional inclusion of the sequence × stage interaction is only a further breakdown of the subjects effect. The question is why the mighty oracle want us to include such a term Maybe Señor García-Arieta’s footprints? See the quoted (d) in this post. ❝ BTW: Where did your p-value came from? Grml; duno… Model Specification and User SettingsNow what? Will the mighty oracle not accept pooling since stages are highly significant different? Would not be the first time ignoring Potvin et al.
P.S.: In the mixed-effects model I used in my previous studies [fixed: Sequence, Stage, Period(Stage), Treatment and random: Subject(Sequence × Stage)] p for stage is 0.403286…— Dif-tor heh smusma 🖖🏼 Довге життя Україна! ![]() Helmut Schütz ![]() The quality of responses received is directly proportional to the quality of the question asked. 🚮 Science Quotes |
|
d_labes ★★★ Berlin, Germany, 2013-03-12 13:12 (4831 d 23:20 ago) @ Helmut Posting: # 10190 Views: 10,770 |
|
|
Dear Helmut, dear All! ❝ ❝ ❝ ❝ ❝ ❝ ❝ ❝ ❝ ❝ ❝ Seems to me like all the F-tests are done with MSE as denominator. My beasty SAS gives almost the same: Source DF Type III SS Mean Square F Value Pr > FThe question is: Are these tests appropriate? Like the test for the sequence effect in the classical 2x2x2 crossover I would suppose to test stage and sequence as between-subject effects and also the new introduced interaction sequence*stage with subject(stage*sequence) as denominator. But I'm not quite sure. The as bogus suspected RANDOM statement in Proc GLM may assist is in getting the 'right' F-tests. But as always when the Almighty miraculous oracle prophesies difficulties are just around the corner (at least for statistical sermons).Formulating RANDOM stage sequence subject(sequence*stage) / test;gives me the anticipated denominator Source DF Type III SS Mean Square F Value Pr > FBut! The F-test for stage is only valid if sequence*stage is assumed zero. Formulating RANDOM stage sequence sequence*stage subject(sequence*stage) / test;gives: Source DF Type III SS Mean Square F Value Pr > FNo warning, but ... Rather wild denominators in the F-tests for sequence and stage! Especially unique for sequence with non-interger df's .Any opinion out there? BTW: The whole mess is "für die Katz" (strictly for the birds). The confidence intervals are not affected at all. with sequence*stage 101.454363 (88.445194 ... 116.377016)— Regards, Detlew |


![[image]](https://static.bebac.at/pics/Blue_and_yellow_ribbon_UA.png)
![[image]](https://static.bebac.at/img/CC by.png)
.
.
.