-
Notifications
You must be signed in to change notification settings - Fork 15
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
Screening for mitochondrion #65
Comments
Hello, We are actively investigating the identification of organelle hits with FCS-GX, and this should be available in an upcoming release. Unfortunately I can't give a timeline of when this will be available, so for now I would rely on other methods to identify mitochondrial sequences. Eric |
Thanks for the reply! So the internal version of fcs which is used to screen assemblies for submission is different than what is listed here? Is that correct? |
Yes, this is correct. The current FCS-GX release matches closely to that individual component of our internal screening, but the internal screen also has some additional functionality (e.g. the organelle ID) that we haven't distributed to the public tool yet. The ultimate goal of this project will be to unify those two pipelines such that running FCS on your own will recapitulate our internal screen results. |
Thanks so much! We would appreciate that well. |
Thanks @etvedte and @wharvey31 We also eagerly wait for organelle genomes to be included in the gxdb as contaminants. |
Hello,
We are running FCS on a set of genomes before submission to NCBI. We use the following command:
and are able to identify the same contamination as NCBI for the most part. What we are apparently missing is mitochondrion. Is there a parameter I am missing to flag this?
Thanks so much for the direction!
The text was updated successfully, but these errors were encountered: