-
Notifications
You must be signed in to change notification settings - Fork 14
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
modified old method to allow only specific models #138
Conversation
…133) * changed uppercase parameter descriptions to lowercase so they match what is in the function call * changed plot for page to plots per page * indicated that lists of flags are not yet available * indicate only multi-conc is supported * indicate winning model is listed at the top of the table for verbose TRUE * The goal of this section is to provide example quantitative metrics, such as z-prime and coefficient of variance, to evaluate assay performance relative to controls * changed level 0 preprosessing to custom preprocessing step to match the diagram * added text: defined in level 2 * removed section that mentions or an apparent negative response within a positively-analyzed, unidirectional endpoint because everything is fit bidirectionally now * attempt to clarify zero centering and added a note about 0 values in the baseline * removed extra space on overview figure * updated hitcalling information based on manuscript text and continous hitcall discussions * attempt to clarify pval section
@brown-jason can you rebase to the dev branch? I don't think I'd be able to test this given the mc4 column changes |
…om/USEPA/CompTox-ToxCast-tcpl into 137-mc4_method-bounded-models-only
This reverts commit fcd4354.
@madison-feshuk I made this way harder than it needed to be but I believe I've successfully rebased to dev |
If we squash and merge at the end nobody will know |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Padilla phenotype score data processed successfully. It seems to be working great!
This is based on an old method, but untested so we will need to run it through for associated endpoints and modify if necessary.