Skip to content
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

Add resp.bound.neg100 mc3 method for CCTE Simmons proliferation assays #299

Open
madison-feshuk opened this issue Oct 9, 2024 · 2 comments · May be fixed by #301
Open

Add resp.bound.neg100 mc3 method for CCTE Simmons proliferation assays #299

madison-feshuk opened this issue Oct 9, 2024 · 2 comments · May be fixed by #301
Assignees

Comments

@madison-feshuk
Copy link
Collaborator

Since we’ve switched to fitting everything bidirectionally, gain/loss responses in this proliferation/cytotox assay with an asymmetrical +100% gain/-300% loss are missed and we end up only fitting the loss. I don’t think we want to NOT fit bidirectionally and lose that cytotox response. “Overwriting” the hitcall based on intended direction also wouldn’t solve this.

image

The -300% is essentially an artificial response calculated relative to baseline, so we could try adding a correction method so that no values fall below -100%. The extreme values may be contributing to model fitting in the negative direction, so bounding should improve this.

Some examples with less extreme negative responses appear to accurately capture proliferation followed by cytotoxicity with biphasic poly2 and gnls models:
image

@cthunes cthunes self-assigned this Oct 11, 2024
@cthunes
Copy link
Contributor

cthunes commented Oct 11, 2024

Instead, create method resp.censormed.neg25 to remove all responses from concentrations which the median falls below -25.

@madison-feshuk
Copy link
Collaborator Author

New method to censor responses below -25% seems to be working great. See reprocessed Zearalenone example:
image

Will share ne output with PI for review.

@cthunes cthunes linked a pull request Oct 15, 2024 that will close this issue
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

Successfully merging a pull request may close this issue.

2 participants