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

QUESTION: specifying samples for sampleExclusionMask in OUTRIDER #553

Closed
Nicholas-Kron opened this issue Jun 5, 2024 · 2 comments
Closed

Comments

@Nicholas-Kron
Copy link

Hi there!

Thank you for making this convenient pipeline. I am planning on running this soon and I had a question regarding setting specific parameters for OUTRIDER that I did not see in the manual or in any issues. If I have trios in my dataset, is there a way to specify these samples in the config or annotation table to be excluded from the auto-encoder fit?

From the OUTRIDER vignette:

4.4.1 Excluding samples from the autoencoder fit
Since OUTRIDER expects that each sample within the population is independent of
all others, replicates could mask effects specific to this sample. This is also true if
trios are present in the data, where the parents can be seen as biological replicates.
Here, we recommend to exclude the sample of interest or the replicates from the
fitting. Later on, for all samples P-values are calculated.
In this rare disease data set we know that two samples (MUC1344 and MUC1365)
have the same defect. To exclude one or both of them, we can use the sampleExclusionMask function.

Thank you!

@vyepez88
Copy link
Collaborator

Hi, thanks for using DROP!
Indeed, we had made the sampleExclusionMask function for those kind of situations. However, recently, we also got trio data and saw that the fit of the masked samples is not optimal and leads to too many outliers. We are working on a dedicated solution to deal with trios. However, if your cohort is large enough, you should be able to run it as a whole anyway.

@Nicholas-Kron
Copy link
Author

Ok sounds good. Thank you!

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