# PureCN Custom Analysis error

**URL:** <https://forum.depmap.org/t/purecn-custom-analysis-error/4246>\
**Category:** Report an Issue\
**Created:** [May 30, 2025, 1:55pm UTC](https://forum.depmap.org/t/purecn-custom-analysis-error/4246 "2025-05-30T13:55:30Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Beernaert](https://avatars.discourse-cdn.com/v4/letter/b/f14d63/32.png) [@Beernaert](https://forum.depmap.org/u/Beernaert)\
**Post date:** [May 30, 2025, 1:55pm UTC](https://forum.depmap.org/t/purecn-custom-analysis-error/4246/1 "2025-05-30T13:55:30Z")

</div>

Hi there,

There seems to be an issue when one attempts Pearson correlation with Omics Signatures derived from PureCN (WGD, CIN, LOHFraction) and CRISPR or RNAi screen sensitivities.

 ![Screenshot 2025-05-27 at 11.05.39](https://canada1.discourse-cdn.com/flex035/uploads/depmap/original/2X/9/98f11893f6c30a2e71d83c3b4876d3640f26e752.png)

---

<div class="post-metadata">

**Author:** ![pmontgom](https://yyz1.discourse-cdn.com/flex035/user_avatar/forum.depmap.org/pmontgom/32/4_2.png) [@pmontgom](https://forum.depmap.org/u/pmontgom)\
**Post date:** [June 6, 2025, 2:09pm UTC](https://forum.depmap.org/t/purecn-custom-analysis-error/4246/2 "2025-06-06T14:09:11Z")

</div>

This appears to have the same underlying cause as the problem reported in [Error in Custom Analysis: Omics Signatures Public](https://forum.depmap.org/t/error-in-custom-analysis-omics-signatures-public/4245).

However I have some good news: After reproducing this on the portal, I checked in our dev environment (which contains our next release, which is tentatively scheduled to go out on Monday) and it was working there. I believe this should be addressed when the new release goes out.

---

<div class="post-metadata">

**Author:** ![Beernaert](https://avatars.discourse-cdn.com/v4/letter/b/f14d63/32.png) [@Beernaert](https://forum.depmap.org/u/Beernaert)\
**Post date:** [June 6, 2025, 2:44pm UTC](https://forum.depmap.org/t/purecn-custom-analysis-error/4246/3 "2025-06-06T14:44:58Z")

</div>

Thanks for the speedy and very helpful reply - much appreciated!
