Closed callumparr closed 3 years ago
Hi @callumparr -- thanks for letting us know. We'll have a look.
Hi @callumparr -- it looks like this error usually occurs when a file is corrupt or incorrect. Are you using files that you've rescued using MinKNOW's read recovery script, or that you've manually converted from tmp
to fast5
?
If you can isolate this to a particular file and upload it then we can have a look.
Hi @callumparr -- it looks like this error usually occurs when a file is corrupt or incorrect. Are you using files that you've rescued using MinKNOW's read recovery script, or that you've manually converted from
tmp
tofast5
?If you can isolate this to a particular file and upload it then we can have a look.
there was nothing particularly weird about them. all reads passed to the basecalled folder once run was completed. There was several runs for this particular sample and original storage may have be different and i ended up collating them all in once SSD drive. I've been seeing some input/ouput error messages when moving things around. I will dig one multi_fast5 file out and see if I can upload somewhere.
I recently run the compress_fast5 with the --sanitize for the sole benefit of removing MinKNOW basecall groups before I proceed to do anything. It seems to run but it will output lots of errors around halfway through. I've check the input and output files and it seems like its worked. Firstly it outputs the same no. of files, viewing in HDFviewer I can the Analyses group has been stripped, and file size is smaller with an equivalence. As they were initially vbz compressed, setting --compression vbz does not seem to alter anything relating to compression.
Can I just ignore these?
then this error repeated a lot