<HashMap><database>GEO</database><file_versions><headers><Content-Type>application/xml</Content-Type></headers><body><files><Other>ftp://ftp.ncbi.nlm.nih.gov/geo/series/GSE331nnn/GSE331453/</Other></files><type>primary</type></body><statusCode>OK</statusCode><statusCodeValue>200</statusCodeValue></file_versions><scores/><additional><omics_type>Genomics</omics_type><species>Homo sapiens</species><gds_type>Genome binding/occupancy profiling by high throughput sequencing</gds_type><full_dataset_link>https://www.ncbi.nlm.nih.gov/geo/query/acc.cgi?acc=GSE331453</full_dataset_link><repository>GEO</repository><entry_type>GSE</entry_type></additional><is_claimable>false</is_claimable><name>Benchmarking normalisation methods for differential binding analysis in CUT&amp;RUN [BRG1]</name><description>CUT&amp;RUN (Cleavage Under Targets and Release Using Nuclease) is an increasingly popular method for profiling protein interactions (transcription factors, histone modifications, etc) with DNA across the whole genome. When performing differential binding analysis of CUT&amp;RUN data to identify genomic regions where interaction profiles vary between conditions, data normalisation is essential for accurate biological interpretations. Despite this, there are no clear guidelines on the optimal normalisation method for CUT&amp;RUN datasets. Here, we examine five normalisation approaches (spike-in, library size, background, reads-in-peak and greenlist) and highlight that different methods can result in widely discrepant interpretations of the data. We test these normalisation methods by simulating a variety of plausible differential binding scenarios as well as an in-house generated dataset. We determined that normalisation by either (i) library size or (ii) background to be the most robust. Importantly, we find spike-in normalisation to be the least reliable method. Our findings inform the use of normalisation methods for CUT&amp;RUN data and should thus facilitate reproducible and robust analysis.</description><dates><publication>2026/05/20</publication></dates><accession>GSE331453</accession><cross_references><GSM>GSM9746053</GSM><GSM>GSM9746054</GSM><GSM>GSM9746055</GSM><GSM>GSM9746056</GSM><GSM>GSM9746057</GSM><GPL>30173</GPL><GSE>331453</GSE><taxon>Homo sapiens</taxon></cross_references></HashMap>