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

Merged tables not produced if not run with --run_profile_standardisation #494

Open
apalleja opened this issue Jun 11, 2024 · 1 comment
Open
Labels
enhancement Improvement for existing functionality

Comments

@apalleja
Copy link

Description of feature

I was running taxprofiler mapping reads to metaphlan and I was not obtaining a combined report table until I used --run_profile_standardisation (following @jfy133 advice). I think it is not obvious the link between this parameter and obtaining the combined report table (metaphlan_<db_name>_combined_reports.txt). Perhaps it needs to be explained in the parameters explanations/help text or an additional flag should be created for that?

@apalleja apalleja added the enhancement Improvement for existing functionality label Jun 11, 2024
@jfy133
Copy link
Member

jfy133 commented Jun 11, 2024

Thanks @apalleja !

my feeling we should have a separate subworkflow with it's own distinct parameter indeed. The behaviour of e.g. krakentools or metaphlan mergetables is not really standardisation.

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