Difference between revisions of "Preparing and loading data"

From GenomeView Manual
Jump to: navigation, search
Line 1: Line 1:

Revision as of 22:20, 3 September 2013


Preparing data recipe

  1. Match identifiers: GenomeView uses the identifiers to link different sources, so make sure that the identifiers match (case-sensitive).
  2. Create indices for data files that need it (check table below)
  3. Convert file formats to get desired visuals (check table below)
  4. Load data

Index your files

Indexing will create a look-up table for GenomeView to load data on-the-fly. This will will speed up browsing and loading speed, as well as significantly reduce the amount of memory you need. For some file formats we recommend you create indices, for other we do not. See the table below for more details and links to instructions.

Data formats

Data typeFile formatIndex*Max size**Comments
Reference sequencefasta ¤Recommended
50 MbunlimitedGenomeView will query the user create index for you if you don't have one and the file is very large.
embl, genbankNot possible50 Mb--EMBL and genbank are mixed file formats that can contain both annotation and reference sequence at the same time.
Annotationgff ¤Not recommended Index GFF50 Mbunlimited
embl, genbankNot possible50 Mb--EMBL and genbank are mixed file formats that can contain both annotation and reference sequence at the same time.
bedNot recommended Index BED50 Mb or lessunlimitedBy default data from a bed file is added to the CDS track, if you want it in a different track, you have to add a line a the top of the file 'track name=Track_name'. No white-space is allowed in the track name.
ptt, tbl Not possible50 Mb or less--Other standard annotation formats GenomeView understands
various formatsNot possible50 Mb or less--GenomeView can directly parse the output of the following programs: Blast, GeneMark, TransTermHP, FindPeaks, MaqSNP, tRNA-scan
Multiple genome alignmentmaf ¤Recommended100 MbunlimitedGenomeView will prompt you to create a compressed maf file and index it for you, if you're trying to load an unindexed maf file.
MAF is the recommended file format for whole genome alignemnt of large/complex genomes
multi-fasta ¤Not possible100 Mb--Recommended for small/simple genomes with a near 1:1 relationship.
aln, ClustalWNot possible100 Mb--
Sequence read alignment<a href="/content/preparing-short-read-alignments">bam</a> ¤Required--unlimitedGenomeView will prompt you if there is no index and will create one for you.
MAQ, MapView, BroadSolexaNot possible100 Mb--
Read coverage summary <a href="/content/preparing-pileup#tdf">tdf</a> ¤NativeunlimitedunlimitedTDF files <a href="/content/preparing-pileup#tdf">can be created with the tdformat tool</a> that is available for <a href="https://sourceforge.net/projects/genomeview/files/TDformat/">download.</a>
bigwigNativeunlimitedunlimitedThis format can be used for any wig file, not just read coverage
<a href="/content/preparing-pileup#pileup">pileup</a>Required--unlimitedThe pileup format becomes slow when you have extreme read depth (>5000 x coverage)
wigNot possible50 Mb--We strongly recommend to convert your wig files to bigwig or TDF. GenomeView can automatically convert wig files to TDF. Caveats: 'track' information should all be on a single line, 'browser' lines will be ignored as the are specific to the UCSC Genome Browser. WIG files need to be sorted by chromosome and by genomic coordinate within the chromosome. BedGraph as well as Wiggle_0 format is supported. For the wiggle_0 type, both variableStep and fixedStep should work.
Allele diversity summary <a href="/content/preparing-pileup#pileup">pileup</a> ¤Required--unlimitedThe pileup format becomes slow when you have extreme read depth (>5000 x coverage)
* Indicates whether this file format can/should be indexed. 
** Recommended maximum file size. First value is without index, the second with index. This values are only guidelines. When loading multiple data sets, you should add the sizes.
*** Unindexed data files can be gzip compressed.

¤ Recommended file format for this data type.

Output formats

(Modified) annotations can be saved as either GFF or EMBL.

All data that is loaded can be exported in their original format. This will not include modifications.

Converting formats

<a href="http://genomeview.org/loki/">We offer a few tools to convert files between formats.</a>

Previous documentation pages

Load data tutorial

Supported data formats Fasta files

Feature files

Read data

Coverage plots