Depletion setting and unexpected behavior

[jennieli421]

This is the depletion setting:

[[regions]]
name = "analysis"
control = false
min_chunks = 1 # minimum number of chunks before a decision can be made
max_chunks = 20 # maximum number of chunks to use in decision making - after this perform the above_max_chunks action
targets = []  # Genomic targets for this region
single_on = "unblock" 	 
multi_on = "proceed"  
single_off = "proceed" 
multi_off = "proceed"         
no_seq = "proceed"            
no_map = "proceed"            
above_max_chunks = "proceed"  
below_min_chunks = "proceed"  

I expect to see multiple rejection peaks with this setting, however, there's only three. I couldn't understand this behavior. Please let me know your thoughts on this.

[github-actions]

Thank you for your issue. Give us a little time to review it.

PS. You might want to check the FAQ if you haven't done so already.

This is an automated reply, generated by FAQtory

[Adoni5]

Even if you had reads that had sequenced longer than 2kb without a decisions, (which I'm not certain about), MInKNOW won't unblock reads that are longer than a certain length in order to not risk rupturing the membrane or blocking the pore, and I think it's about 2kb that is the longest that MinKNOW won't unblock.