get_entity_ContigChunk

ContigChunks are strings of DNA thought of as being a string in a 4-character alphabet with an associated ID. We allow a broader alphabet that includes U (for RNA) and the standard ambiguity characters. The notion of ContigChunk was introduced to avoid transferring/manipulating huge contigs to access small substrings. A ContigSequence is formed by concatenating a set of one or more ContigChunks. Thus, ContigChunks are the basic units moved from the database to memory. Their existence should be hidden from users in most circumstances (users are expected to request substrings of ContigSequences, and the Kbase software locates the appropriate ContigChunks).

Example:

get_entity_ContigChunk -a < ids > table.with.fields.added

would read in a file of ids and add a column for each filed in the entity.

The standard input should be a tab-separated table (i.e., each line is a tab-separated set of fields). Normally, the last field in each line would contain the id. If some other column contains the id, use

-c N

where N is the column (from 1) that contains the id.

This is a pipe command. The input is taken from the standard input, and the output is to the standard output.

Related entities

The ContigChunk entity has the following relationship links:

IsSectionOf ContigSequence

Command-Line Options

-c Column

Use the specified column to define the id of the entity to retrieve.

-h

Display a list of the fields available for use.

-fields field-list

Choose a set of fields to return. Field-list is a comma-separated list of strings. The following fields are available:

sequence

Output Format

The standard output is a tab-delimited file. It consists of the input file with an extra column added for each requested field. Input lines that cannot be extended are written to stderr.