<?xml version="1.0" encoding="utf-8" standalone="yes" ?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>GenomicRanges on Pierre-François Roux</title>
    <link>https://www.pierre-francois-roux.com/tags/genomicranges/</link>
    <description>Recent content in GenomicRanges on Pierre-François Roux</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <copyright>&amp;copy; 2021 Pierre-François Roux</copyright>
    <lastBuildDate>Fri, 19 Jun 2026 09:40:00 +0000</lastBuildDate>
    
	<atom:link href="https://www.pierre-francois-roux.com/tags/genomicranges/index.xml" rel="self" type="application/rss+xml" />
    
    
    <item>
      <title>Make enhancer analyses gene-aware, but not gene-blind</title>
      <link>https://www.pierre-francois-roux.com/2026/06/19/make-enhancer-analyses-gene-aware-but-not-gene-blind/</link>
      <pubDate>Fri, 19 Jun 2026 09:40:00 +0000</pubDate>
      
      <guid>https://www.pierre-francois-roux.com/2026/06/19/make-enhancer-analyses-gene-aware-but-not-gene-blind/</guid>
      <description>Enhancer analyses often fall into two traps. The first is to treat enhancers as isolated genomic intervals. The second is to assign every enhancer to the nearest gene and pretend the problem is solved.
A better compromise is to make enhancer analyses gene-aware, but not gene-blind.
Classify Enhancers Before Linking Them Start by defining interpretable enhancer classes. For example:
 Active enhancers: H3K27ac and H3K4me1 positive. Poised enhancers: H3K4me1 positive, low H3K27ac.</description>
    </item>
    
  </channel>
</rss>