A user must still understand the additional arguments required for each
type of import data. Those arguments are described in detail at the
import_* links below. Each clustering tool / package / pipeline
has its own idiosyncratic set of file names / types, and it remains the
responsibility of the user to understand which file-path should be provided
to each argument for the particular importing submethod. This method
merely provides a central documentation and method-name, and the arguments
are passed along as-is.
(Required). Character string. The name of the
analysis tool / pipeline / package
that created the OTU-cluster data or other data that you now want to import.
Current options are
(Required). Additional named arguments providing file paths, and possible other paramaters to the desired tool-specific import function.
In most cases a
phyloseq-class will be returned, though
the included component data will vary by pipeline/tool, and also
by the types of data files provided.
The expected behavior is to return the most-comprehensive object possible,
given the provided arguments and pipeline/tool.
RDP pipeline: http://pyro.cme.msu.edu/index.jsp
For BIOM format, see:
For mothur, see:
For PyroTagger, see:
For QIIME legacy format, see:
For RDP pipeline, see:
## See documentation of a specific import function
Add the following code to your website.
For more information on customizing the embed code, read Embedding Snippets.