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

Profiling: consider cross-database merge for KMCP #353

Open
jfy133 opened this issue Aug 18, 2023 · 0 comments
Open

Profiling: consider cross-database merge for KMCP #353

jfy133 opened this issue Aug 18, 2023 · 0 comments
Labels
enhancement Improvement for existing functionality

Comments

@jfy133
Copy link
Member

jfy133 commented Aug 18, 2023

Description of feature

Merge search results from multiple databases

Input:
  *. Searching results of the same reads in different databases.
  *. The order of multiple input reads files should be the same during searching.
  *. When only one input given, we just copy and write to the input file.
     This is friendly to workflows which assume multiple inputs are given.

We don't currently support this for other tools so we should think if we should include it, but we could consider it as an optional post-processing step, as we explicitly design taxprofiler to allow running of multiple databases

@jfy133 jfy133 added the enhancement Improvement for existing functionality label Aug 18, 2023
@jfy133 jfy133 added this to the 1.2.0 - Bouncy Basenji milestone Aug 18, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement Improvement for existing functionality
Projects
None yet
Development

No branches or pull requests

2 participants