The segmenter is running and has produced a list of segments to write to file
The segments are being written to a FAST5 file intended to hold n reads per file (capture_f5_1.fast5, then capture_f5_2.fast5, and so on as the files reach their capacity of n reads). When the segmenter is finished, only 1 read is present in each file, specifically the nth read, the last read written to the file.
I believe this indicates that a new file named capture_f5_1.fast5 is being created for each read, writing over the file that was already there, instead of adding more reads to the same file.
Context:
capture_f5_1.fast5, thencapture_f5_2.fast5, and so on as the files reach their capacity of n reads). When the segmenter is finished, only 1 read is present in each file, specifically the nth read, the last read written to the file.I believe this indicates that a new file named
capture_f5_1.fast5is being created for each read, writing over the file that was already there, instead of adding more reads to the same file.