text: user149: Is there a specification anywhere for how a Nanopore FASTQ header should be formatted?   
  I am creating strategies for generating test FASTQ files and would like to ensure I am generating "correct" nanopore sequence identifiers.
  
  user14692: The headers are defined by the basecaller (guppy, Albacore, bonito, etc) during basecalling. They have changed many times over the years, but generally they start with a readID of @+UUIDv4 followed by multiple entries separated by spaces, of form key=value
  For example:
  @945da76d-b7ef-4c65-91a1-e69c85832185 runid=2cf9e7c4dd1888d9a1090ebc394dd5b7cb2fe3f0 read=126 ch=181 start_time=2017-10-17T06:43:19Z barcode=barcode01
  
  This is still valid, however, there is some movement to add sam tags to parse data through to sam files when aligned.
  
original_text: 149: <p>Is there a specification anywhere for how a Nanopore FASTQ header should be formatted?   </p>
  
  <p>I am creating <a href="https://lab41.github.io/hypothesis-bio/api/fastq.html" rel="nofollow noreferrer">strategies for generating test FASTQ files</a> and would like to ensure I am generating "correct" nanopore <a href="https://lab41.github.io/hypothesis-bio/api/sequence_identifiers.html" rel="nofollow noreferrer">sequence identifiers</a>.</p>
   14692: <p>The headers are defined by the basecaller (guppy, Albacore, bonito, etc) during basecalling. They have changed many times over the years, but generally they start with a readID of <code>@+UUIDv4</code> followed by multiple entries separated by spaces, of form key=value</p>
  <p>For example:</p>
  <pre><code>@945da76d-b7ef-4c65-91a1-e69c85832185 runid=2cf9e7c4dd1888d9a1090ebc394dd5b7cb2fe3f0 read=126 ch=181 start_time=2017-10-17T06:43:19Z barcode=barcode01
  </code></pre>
  <p>This is still valid, however, there is some movement to add sam tags to parse data through to sam files when aligned.</p>
  