Skip to content

transformation in response is not allowed #400

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
2 tasks done
clarkliming opened this issue Jan 3, 2024 · 3 comments
Closed
2 tasks done

transformation in response is not allowed #400

clarkliming opened this issue Jan 3, 2024 · 3 comments

Comments

@clarkliming
Copy link
Collaborator

clarkliming commented Jan 3, 2024

it is natural and allowed in other linear models that the transformation applied to response can work, e.g.

lm(log(FEV1) ~ ARMCD + FEV1_BL, data = fev_data)

however mmrm has some issues related to it

mmrm(log(FEV1) ~ ARMCD + FEV1_BL + ar1(AVISIT|USUBJID), data = fev_data)

works

however in the vignette of #396

mmrm(log(FEV1) ~ ARMCD + FEV1_BL + ar1(AVISIT|USUBJID), data = fev_data, start = emp_start)

do not work and gives error like

Error in fit_single_optimizer(tmb_data = tmb_data, formula_parts = formula_parts, :
Assertion on 'all.vars(model_formula)' failed: Must be a subset of {'log(fev1)','trt','time','pts','(weights)'}, but has additional elements {'fev1'}.

in #396 we may break something and we should fix them

@danielinteractive
Copy link
Collaborator

Thanks @clarkliming , and just to be sure, this is really just within the PR #396 right? so technically not a bug on main?

@clarkliming
Copy link
Collaborator Author

yes this is not a issue on main, but a recent issue from emp_start

@danielinteractive
Copy link
Collaborator

cool. So generally I would say, in such cases no need to open a new issue on the repo - just comment on the PR conversation page and resolve there (because the PR is not merged yet, still ongoing work anyway)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants