text: user4439: Does one chunk correspond to the raw signal of a single read read? Why does messing with this parameter affect basecalling results?
  
  user681: If you have access to the nanopore community website you can read more about this here: https://community.nanoporetech.com/posts/not-chunky-enough (I'm not sure to which extent I can copy paste from there so I won't).
  A TLDR version: basecalling doesn't happen simultaneously for an entire read, but it is broken in segments which are processed separately and combined afterward. Those segments are chunks. Basecalling results are affected mostly by low-complexity regions, in which a heavily biased region (in terms of nucleotide content) leads to artifacts in the per-chunk basecalling. Those issues are solved by taking a chunking-size larger than most low-complexity regions.
  
original_text: 4439: <p>Does one chunk correspond to the raw signal of a single read read? Why does messing with this parameter affect basecalling results?</p>
   681: <p>If you have access to the nanopore community website you can read more about this here: <a href="https://community.nanoporetech.com/posts/not-chunky-enough" rel="nofollow noreferrer">https://community.nanoporetech.com/posts/not-chunky-enough</a> (I'm not sure to which extent I can copy paste from there so I won't).</p>
  
  <p>A TLDR version: basecalling doesn't happen simultaneously for an entire read, but it is broken in segments which are processed separately and combined afterward. Those segments are chunks. Basecalling results are affected mostly by low-complexity regions, in which a heavily biased region (in terms of nucleotide content) leads to artifacts in the per-chunk basecalling. Those issues are solved by taking a chunking-size larger than most low-complexity regions.</p>
  