Answers.Body: <p>There is no chromosome named <code>chr10</code>, but there is one named <code>10</code>. The problem is that you're mixing chromosome name systems with a tool that, like most, isn't able to handle that. Remove all instances of <code>chr</code> in your BED file and fix things like <code>chrM</code> -> <code>MT</code>.</p>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2019-05-29T12:07:30.347Z
Answers.Text: Well...that is depressingly simple. Thanks for the tip. It's worked just fine.
Answers.UserDisplayName: Sethzard
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2019-05-29T11:51:31.523Z
Answers.LastActivityDate: 2019-05-29T11:51:31.523Z
Answers.UserDisplayName: Devon Ryan
Body: <p>I'm trying to count the GC in regions leading up to polyA clusters. I found the bedtools command nuc, one of the outputs of which is the GC content. </p>
  
  <p>I took the mouse polyA cluster database from <a href="http://polyasite.unibas.ch/#22" rel="nofollow noreferrer">here</a>, and the mm10 primary assembly soft masked from <a href="ftp://ftp.ensembl.org/pub/release-96/fasta/mus_musculus/dna/" rel="nofollow noreferrer">here</a>. I imported the polyA clusters bed file to R. I then got a list of all the polyA clusters in the genes I'm interested in. For positive strands on polyA I took the start position, took 100 away from it and made that the start of the region of interest, then made the start of the polyA signal the end. For things on the negative strand I added 100 to the end of the polyA signal. I then exported the results to a bed file format. The code I used to do this is below.</p>
  
  <p>When I try to run:</p>
  
  <p>bedtools nuc -fi Mus_musculus.GRCm38.dna_sm.primary_assembly.fa -bed PolyA.bed</p>
  
  <p>Every signal returns some variant of: Feature (chr10:21,080,315-21,080,415) beyond the length of chr10 size (0 bp).  Skipping.</p>
  
  <p>I can however look at several of these regions in the UCSC genome browser without a problem, at least I don't think I had a problem.</p>
  
  <p>Can anyone point me to what's going wrong or to another way I can solve this.</p>
  
  <pre><code>GetRanges &lt;- function(FilteredClusters){
    for (x in 1:nrow(FilteredClusters)){
      if(FilteredClusters<span class="math-container">$Strand[x] == '+'){
    FilteredClusters$RegionEnd[x] &lt;- FilteredClusters$ClusterStart[x]
    FilteredClusters$RegionStart[x] &lt;- FilteredClusters$RegionEnd[x] - 100
  }
  else if(FilteredClusters$</span>Strand[x] == '-')
      {
        FilteredClusters<span class="math-container">$RegionStart[x] &lt;- FilteredClusters$</span>ClusterEnd[x]
        FilteredClusters<span class="math-container">$RegionEnd[x] &lt;- FilteredClusters$</span>RegionStart[x] + 100
      }
    }
      ClusterCut &lt;- select(FilteredClusters, 'Chr', 'RegionStart', 'RegionEnd')
  
      return(ClusterCut)
  }
  </code></pre>
  
Tags: <rna-seq><bedtools>
Title: bedtools feature out of bounds
ThreadText: # bedtools feature out of bounds
  
  (Asked by: username_0 on 2019-05-29)
  
  I'm trying to count the GC in regions leading up to polyA clusters. I found the bedtools command nuc, one of the outputs of which is the GC content.
  
  I took the mouse polyA cluster database from [here](http://polyasite.unibas.ch/#22), and the mm10 primary assembly soft masked from [here](ftp://ftp.ensembl.org/pub/release-96/fasta/mus_musculus/dna/). I imported the polyA clusters bed file to R. I then got a list of all the polyA clusters in the genes I'm interested in. For positive strands on polyA I took the start position, took 100 away from it and made that the start of the region of interest, then made the start of the polyA signal the end. For things on the negative strand I added 100 to the end of the polyA signal. I then exported the results to a bed file format. The code I used to do this is below.
  
  When I try to run:
  
  bedtools nuc -fi Mus\_musculus.GRCm38.dna\_sm.primary\_assembly.fa -bed PolyA.bed
  
  Every signal returns some variant of: Feature (chr10:21,080,315-21,080,415) beyond the length of chr10 size (0 bp). Skipping.
  
  I can however look at several of these regions in the UCSC genome browser without a problem, at least I don't think I had a problem.
  
  Can anyone point me to what's going wrong or to another way I can solve this.
  
  ```
  GetRanges <- function(FilteredClusters){
    for (x in 1:nrow(FilteredClusters)){
      if(FilteredClusters$Strand[x] == '+'){
    FilteredClusters$RegionEnd[x] <- FilteredClusters$ClusterStart[x]
    FilteredClusters$RegionStart[x] <- FilteredClusters$RegionEnd[x] - 100
  }
  else if(FilteredClusters$Strand[x] == '-')
      {
        FilteredClusters$RegionStart[x] <- FilteredClusters$ClusterEnd[x]
        FilteredClusters$RegionEnd[x] <- FilteredClusters$RegionStart[x] + 100
      }
    }
      ClusterCut <- select(FilteredClusters, 'Chr', 'RegionStart', 'RegionEnd')
  
      return(ClusterCut)
  }
  
  ```
  
  **Tags:** rna-seq, bedtools
  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_1 on 2019-05-29. Score: 3 | Accepted answer
  
  There is no chromosome named `chr10`, but there is one named `10`. The problem is that you're mixing chromosome name systems with a tool that, like most, isn't able to handle that. Remove all instances of `chr` in your BED file and fix things like `chrM` -> `MT`.
  
  > **Comments:**
  > **username_0**: Well...that is depressingly simple. Thanks for the tip. It's worked just fine.  
  
  ---
  
  