You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
With #302, we have all the difficult-to-implement columns in place for manysearch CSV output - including especially the abundance of the query in the metagenome. That having been said, there are a few columns we should consider adding.
I'm particularly interested in supporting "nice" output, as provided by the containment_search plugin / per the containment search tutorial link:
query p_genome avg_abund p_metag metagenome name
-------- -------- --------- ------- ---------------
F. prausnitzii 4.3% 24.7 2.5% CD136
B. uniformis 48.3% 2.0 3.4% CD136
F. prausnitzii 0.0% 0.0 0.0% CD237
B. uniformis 62.6% 14.5 26.5% CD237
in particular, it looks like we cannot calculate p_metag from the information we have available in manysearch which is kind of a problem for some use cases 😅 . It might need to be an optional switch because it could slow down manysearch too.NOTE: added in #388
While we're at it, we might usefully add a few other columns like ksize, scaled, and so on. I'm mildly worried about the file becoming too big, but these are useful columns... not sure how to think about it.
here's a script that produces the mgmanysearch nice output from manysearch CSV output -
With #302, we have all the difficult-to-implement columns in place formanysearch
CSV output - including especially the abundance of the query in the metagenome. That having been said, there are a few columns we should consider adding.I'm particularly interested in supporting "nice" output, as provided by the containment_search plugin / per the containment search tutorial link:in particular, it looks like we cannot calculateNOTE: added in #388p_metag
from the information we have available inmanysearch
which is kind of a problem for some use cases 😅 . It might need to be an optional switch because it could slow down manysearch too.While we're at it, we might usefully add a few other columns like ksize, scaled, and so on. I'm mildly worried about the file becoming too big, but these are useful columns... not sure how to think about it.
here's a script that produces the
mgmanysearch
nice output frommanysearch
CSV output -display-manysearch.py
:The text was updated successfully, but these errors were encountered: