Input and output¶
Input file formats¶
File name extensions matter as file types are usually recognized by their extension. Reading remote files might require starting java with the option
-Djava.net.useSystemProxies=true (see issue#6).
Unless noted otherwise remote URL links are supported. However, there are issues reading tabix files on ftp servers (http are ok), see htsjdk/issue#797. Reading such files is possible but ASCIIGenome will first download them locally.
||Can be gzipped (
|bed||Any||Can be gzipped (
||Can be gzipped (
||Useful for quantitative data on very large intervals.|
||Can be gzipped (
|bam and sam||
||BAMs without index and SAM files are first sorted and indexed. Remote URLs are painfully slow (same for IGV).|
Note that the recognition of the extension is case insensitive, so .bigBed is the same as .bigbed.
A notable format currently not supported is CRAM.
Handling large files¶
ASCIIGenome always makes use of indexing to access data so that the memory usage stays low even for large files. Tabular data files (bed, gtf/gff, bedgraph, etc) which are not block compressed and indexed are first sorted, compressed and indexed to temporary working files. This is usually quick for files of up to 1/2 million rows. For larger files consider compressing them with external utilities such as tabix. For example, to sort, compress and index a bed file:
sort -k1,1 -k2,2n my.bed \ | bgzip > my.bed.gz tabix -p bed my.bed.gz
Setting a genome¶
An optional genome file can be passed to option
-g/--genome or set with the
setGenome command to give a set of allowed sequences and their sizes so that browsing is
constrained to the real genomic space. The genome file is also used to represent the position of
the current window on the chromosome, which is handy to navigate around.
There are different ways to set a genome:
- A tag identifying a built-in genome, e.g. hg19. See genomes for available genomes.
- A local file, tab separated with columns chromosome name and length. See genomes for examples.
- A bam file with suitable header.
- A fasta reference sequence (see Reference sequence).
A reference sequence file is optional. If provided, it should be in fasta format, and uncompressed. If the fasta file does not have an index, ASCIIGenome will create a temporary index file that will be deleted on exit. A permanent index can be created with:
samtools faidx ref.fa
Formatting of reads and features¶
When aligned reads are show at single base resolution, read bases follow the same convention as
samtools: Upper case letters and
. for read align to forward strand, lower case and
, otherwise; second-in-pair reads are underlined; grey-shaded reads have mapping quality of <=5.
GTF/GFF features on are coded according to the feature column as below. For forward strand features the colour blue and upper case is used, for reverse strand the colour is pink and the case is lower. Features with no strand information are in grey.
This is an example of a BAM file and a GTF file. The top track shows the read coverage, the middle track the aligned reads and the bottom track the GTF features in this genomic window.
If available, the feature name is shown on the feature itself. For BED features, name is taken from column 4, if available. Default for GTF/GFF is to take name
Name, if absent try:
gene_name. To choose an attribute see command
Read coverage tracks at single base resolution show the consensus sequence obtained from the
underlying reads. If the reference fasta file is present the
= symbol is used to denote a
match. Heterozygote bases or variants are shown using the iupac ambiguity codes for up to two variants (N otherwise). Variants
are called with a not-too-sophisticated heuristics: Only base qualities >= 20 are considered, an
alternative allele is called if supported by at least 3 reads and makes up at least 1% of the total
reads. The first and second allele must make at least 98% of the total reads otherwise the base is
PileupLocus.getConsensus() for exact implementation). Insertion/deletions are
currently not considered.
The title lines contains information about the track and their content depends on the track type.
For all tracks, the title line shows the file name (e.g.
hg19_genes_head.gtf.gz) with appended an identifier (e.g.
The filename and the identifier together make the name of the track. All commands
operating on tracks use this name to select tracks. The suffix identifier is handy
to capture tracks without giving the full track name.
Annotation tracks (bed, gtf, gff, vcf)¶
hg19_genes_head.gtf.gz#1; N: 13; grep -i exon -e CDS
After the track name (
hg19_genes_head.gtf.gz#1), the title shows the number of features
in the current window (
N: 13). Other information is shown depending on the track
settings. In this example the title shows settings used to filter in and out features (
This title type applies to quantitative data such as bigwig and tdf and to the read coverage track.
ear045.oxBS.actb.bam#2; ylim[0.0 auto]; range[44.0 78.0]; Recs here/all: 255/100265; samtools -q 10
ear045.oxBS.actb.bam#2: Track name as described above
ylim[0.0 auto] limits of the y-axis, here from 0 to the maximum of this window.
range[44.0 78.0] Range of the data on the y-axis.
Recs here/all: 255/100265 number of alignments present in this window (255) versus the
total number in the file (100265).
samtools -q 10 information about mapping quality and bitwise filter set with the samtools command.
omitted if not applicable and if no filter is set. See also explain sam flag.
This is the track showing individual reads. Example:
ear045.oxBS.actb.bam@3; samtools -q 10
ear045.oxBS.actb.bam@3 As before, this is the track name composed of file name and
track ID. In contrast to other tracks, the id starts with @ instead of #. This is
handy to capture all the read tracks but not the coverage tracks, for example trackHeight 10 bam@ applies
to all the read tracks but not to the coverage tracks.
Screenshots can be saved to file with the commands
save. Output format is either ASCII text or
pdf, depending on file name extension. For example:
[h] for help: save mygene.txt ## Save to mygene.txt as text [h] for help: save ## Save to chrom_start-end.txt as text [h] for help: save .pdf ## Save to chrom_start-end.pdf as pdf [h] for help: save mygene.pdf ## Save to mygene.pdf as pdf
save writes to file named after the current genomic position e.g.
chr1_1000-2000.txt. The ANSI formatting (i.e. colours) is stripped before saving so that files
can be viewed on any text editor (use a monospace font like
courier). For convenience the
%r in the file name is expanded to the current genomic coordinates, for example
save mygene.%r.pdf is expanded to e.g.
See also Advanced filtering with awk for saving screenshots in batch by iterating through a list of positions.
This is a screenshots of bisulfite-seq data. The BSseq mode was set and methylated cytosines are shown in red while unmethylated cytosines in blue.