-
Notifications
You must be signed in to change notification settings - Fork 14
š Semantic Types
Inputs and outputs in Qiime2 are compressed files with specific structures and contents. Only these special compressed files (called artifacts in Qiime 2 terminology) can be used or produced by Qiime2 actions, which are programs that fetch, transform, or analyze the data contained in the artifacts. The structure and contents of a given artifact are constrained by its associated semantic type. Qiime2 uses semantic types to check that only valid inputs are used and/or that valid outputs are produced for a given action.
See Qiime2 Documentation on semantic types and actions for more information.
Below we list some semantic types that are especially relevant to q2-moshpit
actions (semantic types are actually implemented in a different repository; q2-types
). By providing this information we hope to help users navigate their way through the functionality that q2-moshpit
offers. The links below will take you to semantic-type information pages, each of which contains the following sections:
- Short description of the contents of artifacts with the given semantic type.
- Artifact Format: The Python class that defines the given semantic type. Inside this class, the expected folder structure as well as the names of the files that the artifact should have are defined.
- Expected Folder Structure: Tree diagram of a folder and files that could comply with the given semantic type.
-
Where to find <
semantic-type-name
>: list actions where the given semantic type is used, either as input, output, or both.
Lastly, below you will find semantic types grouped by their corresponding composite type, which is just another semantic type that is used to group related semantic types.
Data organized by sample.
SampleData[MAGs]
SampleData[Contigs]
SampleData[BLAST6]
SampleData[SequencesWithQuality]
SampleData[PairedEndSequencesWithQuality]
SampleData[Kraken2Reports]
SampleData[Kraken2Outputs]
Data organized by feature (e.g. MAGs, sequences, taxonomy).
FeatureData[MAG]
FeatureData[NOG]
FeatureData[ProteinSequence]
FeatureData[Taxonomy]
FeatureData[Sequence]
FeatureData[Kraken2Outputs]
FeatureData[Kraken2Reports]
Reference databases.
ReferenceDB[BuscoDB]
ReferenceDB[Diamond]
ReferenceDB[Eggnog]
ReferenceDB[EggnogProteinSequences]
ReferenceDB[NCBITaxonomy]
KaijuDB
BrackenDB
Kraken2DB
Profile hidden Markov Models for protein sequences.