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
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?
The text was updated successfully, but these errors were encountered:
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.
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?
The text was updated successfully, but these errors were encountered: