-
Notifications
You must be signed in to change notification settings - Fork 21
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
Lod tutorial documentation #364
Conversation
adding try catch to the example Co-Authored-By: kristynchin-olink <145140889+kristynchin-olink@users.noreply.github.com>
…e of LOD and PCNormalizedLOD in vignette
…ral vignette for LOD
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.
LGTM
OlinkAnalyze/vignettes/LOD.Rmd
Outdated
+ The negative control contains an assay QC warning across all assays, excluding Olink's internal control assays | ||
+ The negative control does not pass sample QC criteria (sample QC failure or warning) in all Explore HT blocks or all Explore 3072 panels | ||
|
||
For each assay, the median NPX is calculated for all negative controls present in a project. For Explore 3072, overlapping assays are assessed separately, within their respective panels. The LOD for each assay is then calculated as the assay's median negative control NPX value plus 0.2 Standard Deviations. |
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.
@kathy-nevola
median negative control NPX value plus 0.2 Standard Deviations. or
3 Standard Deviations or 0.2 whichever higher
?
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.
Good catch, fixed this
Title: Write a very short summary here
Problem: Write a description of your problem here.
Solution: Write a short summary of your solution.
Key Features:
Checklist
Type of changes
What type of changes does your code introduce?
Put an
x
in the boxes that applyFurther comments
If this is a relatively large or complex change, kick off the discussion by explaining why you chose the solution you did and what alternatives you considered, any questions you have, etc...
Consider linking any issues (#issue-number ) or adding @mentions to ensure specific people see it.