-
Notifications
You must be signed in to change notification settings - Fork 6
Human Friendly Read ID
Chee-Hong Wong edited this page Sep 11, 2017
·
1 revision
Each MinION sequenced read is assigned a unique 128-bits number (aka read_uuid) by the MinKNOW software. The read_uuid is reported as 32 hexidecimal digits (e.g. 27bc311c-87ef-496b-9153-7f198ed69e63). To make tracking reads alignment easier in IGV browser, we assigned a human-friendly read id composed of 7 elements as follow:
Element | Description | Examples |
---|---|---|
1 | experiment id | WTD09 |
2 | unique running serial number from 1 assigned to each read | 1 |
3 | 1D or 2D status of read | 2D |
4 | Pass or Fail status of read | P |
5 | Read code | 1 = Read template sequence is present 2 = Read complement sequence is present 3 = Both read template and complement sequence are present |
6 | Read sequence code | T=Template C=Complement M=Merged consensus 2D sequence |
7 | Read sequence length prefixed with 'L' | L23284 |
To facilitate tracking these IDs back to the read_uuid, each run/experiment has an associated hash table (<experiment>-hash.xls). The first line of the hash table contains the columns header prefixed by '#'. Each line contains 7 columns as follow:
Column | Description | Examples |
---|---|---|
1 | read_uuid | UUID assigned by MinKNOW software |
2 | fast5 | .fast5 file where read sequences is extracted from |
3 | PassFail | P=Pass, F=Fail |
4 | 1D_2D | 1D read(s) or 2D-reads |
5 | template_hash_id | human-friendly read id for read's template sequence |
6 | complement_hash_id | human-friendly read id for read's template sequence |
7 | 2d_hash_id | human-friendly read id for read's template sequence |