-
Notifications
You must be signed in to change notification settings - Fork 8
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
requesting a new QC feature #4
Comments
Hello! Thank you again! Barplots for the number of id. proteins per sample, and the percentage of missing values per samples are available in the QC tab, both are produced with the uploaded intensities before imputation: In the Analysis parameters you can specify to only include proteins that have been identified in at least n replicates of the same group (e.g 2 out of 3 replicates), and you can also apply this That being said, there are use cases were it would be beneficial to not perform the imputation at all. Best, |
I agree, this would be a good QC feature. Best, |
Thanks! Look forward to the new feature. |
Hello, To keep this feature general for many samples, and because set comparisons become very difficult to visualize for many sets, I decided to opt for a heatmap. You have 3 options to compare the overlap between samples in this heatmap (if you click on the wrench icons):
In addition, you can inspect the values of these metrics in a data table. Best, |
Dear Sebastian and amica team,
Thanks again for all your work to make this useful tool publicly available.
I understand that the imputation is necessary for some of the features in amica, however this may affect the analysis for some of the proteomics data. This includes the analysis of the IP samples, where the bait protein and some potential binders are only present in one group. Or the proteomic analysis of the samples with the knockout genes. Is there any options in amica to count for these cases?
Can we have a new feature to generate new plots (maybe Venn?) for the samples before imputation?
Thanks
The text was updated successfully, but these errors were encountered: