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
Thanks to XXX: " - - This solution does not resolve all duplicates in the strain level data, so in the profile-level phyloseq object taxa rownames are simply indexes ‘sp’ * This is an issue because some default plotting commands don’t provide as nicely labeled output as they could. (How do you interpret a figure where the names are codes like ‘sp203’?) * Figure out how to replace code-like names in the figures with proper names? - - "
-> One solution could be to have an option in the plotting command that would allow using alternative labels and/or more informative lables constructed from tax_table
The text was updated successfully, but these errors were encountered:
Yes this would be good. Not yet sure how to do this but the idea here can be using the taxonomic classification like phylum-class-order-family-genus-species-otuid. Or simply the best taxonomic classification with more than 4 characters. Something similar to the solution we provide for core heat map issue. The number of levels to be included in labels can be specified by user.
Thanks to XXX: " - - This solution does not resolve all duplicates in the strain level data, so in the profile-level phyloseq object taxa rownames are simply indexes ‘sp’ * This is an issue because some default plotting commands don’t provide as nicely labeled output as they could. (How do you interpret a figure where the names are codes like ‘sp203’?) * Figure out how to replace code-like names in the figures with proper names? - - "
-> One solution could be to have an option in the plotting command that would allow using alternative labels and/or more informative lables constructed from tax_table
The text was updated successfully, but these errors were encountered: