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
Improvement Description
As it currently stands, the only way to get a TSV file with alpha diversity data is by generating the tabulated visualization, and from the visualization click on "Download as TSV". It would be nice to have a method in this plugin that didn't require the interaction with the browser.
References
This was briefly discussed in a forum post here.
The text was updated successfully, but these errors were encountered:
We wanted to encourage users to use artifacts as metadata instead of exporting to TSV, that way provenance is preserved. But I can also see this being a useful utility in practice -- perhaps it's just a user education type of thing, where we document and recommend retaining provenance when possible.
One way to accomplish this would be supporting a qiime tools export command that lets users export an artifact as a Metadata TSV file.
On (Aug-22-17|23:29), Jai Ram Rideout wrote:
We wanted to encourage users to use artifacts as metadata instead of exporting to TSV, that way provenance is preserved. But I can also see this being a useful utility in practice -- perhaps it's just a user education type of thing, where we document and recommend retaining provenance when possible.
One way to accomplish this would be supporting a `qiime tools export` command that lets users export an artifact as a `Metadata` TSV file.
--
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub:
#7 (comment)
Improvement Description
As it currently stands, the only way to get a TSV file with alpha diversity data is by generating the tabulated visualization, and from the visualization click on "Download as TSV". It would be nice to have a method in this plugin that didn't require the interaction with the browser.
References
This was briefly discussed in a forum post here.
The text was updated successfully, but these errors were encountered: