-
Notifications
You must be signed in to change notification settings - Fork 90
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
KeyError in yield_plot and occupancy #77
Comments
Yep we have seen this as well. I will look into a fix asap |
I've noticed this as well. It's because some of the failed files do not have any template data. A simple try, except should work in this regard. I'm working on a couple of scripts that split failed reads into folders explaining why they failed. |
I too am having this problem using poretools 0.6.0 |
Im using poretools 0.6.0 in a MacOs sierra 10.12.1 and having the same issue when files do not have template data. |
I think there may be a problem with these options for fail reads. I get KeyError: 'template' when I attempt these options for fail reads (MAP007, minKnow version 0.51.1.62, poretools version 0.5.1) I get the following error. I do not get this error for pass reads
Command: poretools_main.py yield_plot CNV_022516/reads/downloads/fail/
Error:
File "/seq/sara/poretools-master/poretools/poretools_main.py", line 519, in
main()
File "/seq/sara/poretools-master/poretools/poretools_main.py", line 513, in main
args.func(parser, args)
File "/seq/sara/poretools-master/poretools/poretools_main.py", line 53, in run_subtool
submodule.run(parser, args)
File "/isilon/seq/sara/poretools-master/poretools/yield_plot.py", line 72, in run
start_time = fast5.get_start_time()
File "/isilon/seq/sara/poretools-master/poretools/Fast5File.py", line 469, in get_start_time
node = self.find_event_timing_block()
File "/isilon/seq/sara/poretools-master/poretools/Fast5File.py", line 439, in find_event_timing_block
path = fastq_paths[self.version]['template'] % (self.group)
KeyError: 'template'
Thank for your help
The text was updated successfully, but these errors were encountered: