Difference between revisions of "MinKNOW folders and log files"
| (2 intermediate revisions by the same user not shown) | |||
| Line 8: | Line 8: | ||
* The root folder is usually called '''data'''. | * The root folder is usually called '''data'''. | ||
| + | * MinKNOW deposits log files in the root folder, but uses a subfolder called '''reads''' for the FAST5 files. | ||
| + | * Generally speaking one read yields one FAST5 files. | ||
| + | * At this ealy stage FAST5 files contain signal and events, but the bases are not called, so there is no DNA yet. | ||
| + | * Within '''reads''', MinKNOW separates reads into | ||
| + | :- '''pass''' | ||
| + | :- '''fail''' | ||
| + | :- '''skip''' | ||
| + | :- '''tmp''' | ||
= Log files = | = Log files = | ||
Latest revision as of 12:15, 14 March 2017
Introduction
The way The MinKNOW program organises folder, and the makeup of its various log files is complicated.
This page is an attempt to keep track of them
Folders
- The root folder is usually called data.
- MinKNOW deposits log files in the root folder, but uses a subfolder called reads for the FAST5 files.
- Generally speaking one read yields one FAST5 files.
- At this ealy stage FAST5 files contain signal and events, but the bases are not called, so there is no DNA yet.
- Within reads, MinKNOW separates reads into
- - pass
- - fail
- - skip
- - tmp
Log files
Found in:
<ROOT_FOLDER>/logs/<MN12345>/
The log files seem to have prefixes that reflect their type. One set of log files could look like:
- ws_event_sampler_*
- control_server_*
- ws_raw_data_sampler_*
- read_writer_*
- ws_longpoll_*
- analyser_*
- bulk_writer_*
- manta_*
- Script_events_*
These files usually have the date and time added to their name and all have extension txt.
