Open thermokarst opened 3 years ago
% the `usage:initialize-data` directive is non-rendering, it is intended % for registration and setup of the example. ```usage:initialize-data data = use.init_data('data', data_factory) metadata = use.init_metadata('metadata', metadata_factory)
This might not be necessary- we might be able to just include the init-data in a bare usage block.
What if instead of being "non-rendering", it generated a "download" element like we have in the tutorials?
For usage:render-metadata
what if it was a direct analogy to inspect-metadata
? And there was some complex element which would summarize but also show you the entire metadata if you clicked about in it.
What if instead of being "non-rendering", it generated a "download" element like we have in the tutorials?
I like it, and I think that is currently register-factories behavior.
For
usage:render-metadata
what if it was a direct analogy toinspect-metadata
? And there was some complex element which would summarize but also show you the entire metadata if you clicked about in it.
Yep, that sounds perfect, I was kinda thinking something like the tabulate viz.
The following is a first-draft mockup of a potential interface-less QIIME 2 tutorial template format. The idea is to write once (in markdown), and render out the outputs (via execution), as well as a handful of interfaces.
% the
usage:initialize-data
directive is non-rendering, it is intended % for registration and setup of the example.The data here consists of single-end reads (6 reads total). There are two samples present in the data, with the following barcodes on the 5' end:
Demultiplex the reads
Now that we have everything imported, let's do the thing:
As you can see - the reads are now demuxed. Enjoy!