Package picard.illumina.parser


package picard.illumina.parser
  • Class
    Description
    Parse various formats and versions of Illumina Basecall files, and use them the to populate ClusterData objects.
    A class that implements the IlluminaData interfaces provided by this parser One BclData object is returned to IlluminaDataProvider per cluster and each first level array in bases and qualities represents a single read in that cluster
    This class provides that data structure for cbcls.
    Store the information from Illumina files for a single cluster with one or more reads.
    IlluminaDataProviderFactory accepts options for parsing Illumina data files for a lane and creates an IlluminaDataProvider, an iterator over the ClusterData for that lane, which utilizes these options.
    List of data types of interest when parsing Illumina data.
    General utils for dealing with IlluminaFiles as well as utils for specific, support formats.
     
    Illumina's TileMetricsOut.bin file codes various metrics, both concrete (all density id's are code 100) or as a base code (e.g.
    The channels in a FourChannelIntensityData object, and the channels produced by a ClusterIntensityFileReader, for cases in which it is desirable to handle these abstractly rather than having the specific names in the source code.
    NextSeq-style bcl's have all tiles for a cycle in a single file.
    Parse .bcl.bgzf files that contain multiple tiles in a single file.
    MultiTileFileUtil<OUTPUT_RECORD extends picard.illumina.parser.IlluminaData>
    For file types for which there is one file per lane, with fixed record size, and all the tiles in it, so the s_.bci file can be used to figure out where each tile starts and ends.
    Read filter file that contains multiple tiles in a single file.
    Read locs file that contains multiple tiles in a single file.
    MultiTileParser<OUTPUT_RECORD extends picard.illumina.parser.IlluminaData>
    Abstract class for files with fixed-length records for multiple tiles, e.g.
    In multiple locations we need to know what cycles are output, as of now we output all non-skip cycles, but rather than sprinkle this knowledge throughout the parser code, instead OutputMapping provides all the data a client might want about the cycles to be output including what ReadType they are.
     
     
     
    PerTileParser<ILLUMINA_DATA extends picard.illumina.parser.IlluminaData>
    Abstract base class for Parsers that open a single tile file at a time and iterate through them.
     
    PosParser parses multiple files formatted as one of the three file formats that contain position information only (pos, locs, and clocs).
    While structurally identical to CompositeIndex, this class is maintained as it makes code more readable when the two are used together (see QSeqParser)
    Data for a single end of a paired-end read, a barcode read, or for the entire read if not paired end.
    Represents one set of cycles in an ReadStructure (e.g.
    Describes the intended logical output structure of clusters of an Illumina run.
    A read type describes a stretch of cycles in an ReadStructure (e.g.
    Represents a tile from TileMetricsOut.bin.
    Load a file containing 8-byte records like this: tile number: 4-byte int number of clusters in tile: 4-byte int Number of records to read is determined by reaching EOF.
     
    Utility for reading the tile data from an Illumina run directory's TileMetricsOut.bin file
    Captures information about a phasing value - Which read it corresponds to, which phasing type and a median value
    Defines the first or second template read for a tile