Originally posted by coldturkey
View Post
The grey scale levels indicate the mapping quality for the template, from dark grey (bad) to white (good). You can control whether it colours this using the average of each end sequence, the minimum of the two, or the maximum of the two by using the menu towards the top left. Additionally the Filter button allows you to filter out poor quality (or peversely good quality) mapping reads.
However this is only the base colour. It will be changed to one of the following if it fits into another category:
Blue: single ended read. Or more specifically, only *this* end is in the Gap5 database. (That doesn't necessarily mean it was a single ended library.)
Red: Inconsistent orientation. Ie instead of ---> <--- it finds ---> --->, <--- <--- or <--- --->. This needs some more work as certain library construction types (eg 454) will yield ---> ---> as standard. My plan here is to auto-analyse each library and attempt to work out the normal orientation. Then anything abnormal will be labelled as red.
Orange: paired, but the other end isn't visible. It's not actually possible with ease to tell whether the other end is in another contig (most likely) or whether it is a long way away in this contig - significantly off the edge of the screen in other words. The ">>Acc" button (accurate mode) attempts to work out this distinction correctly, but it's slow as it has to read more data in order to figure out the correct location.
The reason for this is that Gap5, being an editor, doesn't actually track *where* the other end is, only the record number. If it was found in the same range query then we know they form a pair, if not we require more searching to figure this out. The reason I don't cache such data is that it would mean contig joining or contig breaking suddenly requires millions of edits (to check whether the intra-contig or inter-contig spanning status needs changing).
Having said that, I just noticed the >>Acc button crashed Gap5 for me on one of my test databases. Oops!
For reads (2nd menu from left; set to "reads") the colours simply indicate forward vs reverse reads. It's not possible in all file formats though to distinguish which is which so sometimes it's simply a case of the "left" one being one colour while the "right" one is another. The main use of this is simply to see the extent that the physical sequence data extends along the insert.
Finally I'd recommend using the Y-spread function when in Template Size mode (left-most menubutton). This mode is the default template display view where the Y coordinate is governed by the size of the insert. Thus structural variations stand out. However you can't easily tell how many lines are stacked up on the same pixel row - it maybe an isolated template or it may be a whole stack of templates with very similar start/end positions. The Y-spread slider basically adds a bit of pseudo-randomness to the Y coordinate making it easier to distinguish between 1 template and lots of templates stacked up at the same coordinates.
James
Leave a comment: