Answers.Body: <p>Usually, a single sequencing library is created from each sample. Assuming you are using barcoded indexes to identify multiple samples, the index is attached to each library, and the libraries are pooled to make a library pool.  A library pool can be frozen, and is very stable.  </p>
  
  <p>A pool can be sequenced multiple times by pipetting a portion of the pool and supplying it to the sequencing process.  Each time, a sample of the molecules in the pool will be sequenced.</p>
  
  <p>Generally, it is true that sequencing runs are very repeatable, and that you will not suffer any batch effects.</p>
  
  <p>If you want to check for batch effects you would need to analyse all of your sequence files separately, and check this first, or in parallel, to your main analysis.</p>
  
  <p>One thing you might want to check is whether the same library pool was sequenced multiple times, or whether separate pools or libraries were made for each sequencing run.  In the second case, there may be more likely to be batch effects.</p>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2019-09-30T10:27:08.270Z
Answers.Text: Oh, thanks. I think they submitted a portion of the library pool because the index are the same. However, why they didn't add more sample from the pool from the beginning?
Answers.UserDisplayName: llrs
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2019-09-30T12:30:56.937Z
Answers.Text: Regarding your sample pooling question, probably this is not happening in your case but here is our workflow, which generates multiple output files per sample like you get: We use 10x and the most expensive part is the sequencing run. As single cells are delicate and not all "droplet formation" steps go smoothly, first we do "shallow sequencing" on NextSeq to see if there are enough number of good quality cells in a given sample (after mapping, read counting, single cell QC) and then continue with deeper sequencing (one or more runs) with NovaSeq until we reach saturation with number of reads.
Answers.UserDisplayName: haci
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2019-09-30T13:30:08.233Z
Answers.Text: The number of sequences has a limit per sequencing run, even if you add more of the pool to the run - it is limited by the flow cell.  For this reason, it is normal to only sequence a part of the pool in any one run - enough to fill the flow cell - and if you need more reads, then carry out more runs with additional flow cells.
Answers.UserDisplayName: Jay Moore
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2019-09-30T14:22:11.830Z
Answers.Text: Another alternative would be to allocate some samples to one run, some samples to another run, and to fill up the flowcells that way.  However, this would mean that, if there are any batch effects it would be much more difficult to separate them from sample effects.  At least if all samples are included on every flow cell, the batch effects will not affect any between-samples comparison.
Answers.UserDisplayName: Jay Moore
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2019-10-02T07:15:55.347Z
Answers.Text: @Jonathan Well, in our case not all samples where included in all the runs, that's partially why I ask about the batch effect.
Answers.UserDisplayName: llrs
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2019-09-30T09:29:01.147Z
Answers.LastActivityDate: 2019-09-30T10:08:28.593Z
Answers.LastEditDate: 2019-09-30T10:08:28.593Z
Answers.UserDisplayName: Jay Moore
Body: <p>We send some samples to sequence and we got several (fastq.gz) files for each sample. The files are distributed at two or three folders with different dates (more than a week apart). The dates of the folders where the data is in:</p>
  
  <pre><code>2019-08-12
  2019-08-21
  2019-08-21
  2019-09-04
  2019-09-14
  </code></pre>
  
  <p>I asked the facility about why there are the same file in different folders, and they told us that:</p>
  
  <blockquote>
    <p>we have split sequencing of that project on different flowcells, so all
    files are correct and you have to merge the individual (duplicate) files
    to get the requested total read numbers.</p>
  </blockquote>
  
  <p>How can different flow cells be from the same experiment and be run with more than a week of difference? (I thought that all the flow cells are run at the same time in each sequencing)</p>
  
  <p>Can be there some batch effect? How can I check if there is batch effect if we merge the files before trimming, mapping and counting?</p>
  
Tags: <ngs>
Title: Sequencing center returns data in several files
ThreadText: # Sequencing center returns data in several files
  
  (Asked by: username_0 on 2019-09-30)
  
  We send some samples to sequence and we got several (fastq.gz) files for each sample. The files are distributed at two or three folders with different dates (more than a week apart). The dates of the folders where the data is in:
  
  ```
  2019-08-12
  2019-08-21
  2019-08-21
  2019-09-04
  2019-09-14
  
  ```
  
  I asked the facility about why there are the same file in different folders, and they told us that:
  
  > we have split sequencing of that project on different flowcells, so all
  > files are correct and you have to merge the individual (duplicate) files
  > to get the requested total read numbers.
  
  How can different flow cells be from the same experiment and be run with more than a week of difference? (I thought that all the flow cells are run at the same time in each sequencing)
  
  Can be there some batch effect? How can I check if there is batch effect if we merge the files before trimming, mapping and counting?
  
  **Tags:** ngs
  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_1 on 2019-09-30. Score: 5 | Accepted answer
  
  Usually, a single sequencing library is created from each sample. Assuming you are using barcoded indexes to identify multiple samples, the index is attached to each library, and the libraries are pooled to make a library pool. A library pool can be frozen, and is very stable.
  
  A pool can be sequenced multiple times by pipetting a portion of the pool and supplying it to the sequencing process. Each time, a sample of the molecules in the pool will be sequenced.
  
  Generally, it is true that sequencing runs are very repeatable, and that you will not suffer any batch effects.
  
  If you want to check for batch effects you would need to analyse all of your sequence files separately, and check this first, or in parallel, to your main analysis.
  
  One thing you might want to check is whether the same library pool was sequenced multiple times, or whether separate pools or libraries were made for each sequencing run. In the second case, there may be more likely to be batch effects.
  
  > **Comments:**
  > **username_0**: Oh, thanks. I think they submitted a portion of the library pool because the index are the same. However, why they didn't add more sample from the pool from the beginning?  
  > **username_2**: Regarding your sample pooling question, probably this is not happening in your case but here is our workflow, which generates multiple output files per sample like you get: We use 10x and the most expensive part is the sequencing run. As single cells are delicate and not all "droplet formation" steps go smoothly, first we do "shallow sequencing" on NextSeq to see if there are enough number of good quality cells in a given sample (after mapping, read counting, single cell QC) and then continue with deeper sequencing (one or more runs) with NovaSeq until we reach saturation with number of reads.  
  > **username_1**: The number of sequences has a limit per sequencing run, even if you add more of the pool to the run - it is limited by the flow cell.  For this reason, it is normal to only sequence a part of the pool in any one run - enough to fill the flow cell - and if you need more reads, then carry out more runs with additional flow cells.  
  > **username_1**: Another alternative would be to allocate some samples to one run, some samples to another run, and to fill up the flowcells that way.  However, this would mean that, if there are any batch effects it would be much more difficult to separate them from sample effects.  At least if all samples are included on every flow cell, the batch effects will not affect any between-samples comparison.  
  > **username_0**: @Jonathan Well, in our case not all samples where included in all the runs, that's partially why I ask about the batch effect.  
  
  ---
  
  