Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

PESCAn Error: cannot allocate vector of size 150.9 Gb #354

Open
YuZhang337 opened this issue Apr 17, 2024 · 4 comments
Open

PESCAn Error: cannot allocate vector of size 150.9 Gb #354

YuZhang337 opened this issue Apr 17, 2024 · 4 comments

Comments

@YuZhang337
Copy link

Hi, @teunbrand

I am so sorry to bother you again. When I use the PESCAn function, I always encounter the problem of cannot allocating vector of size. Even if I adjust the number of peak beds to 2k, I still encounter such an error. Is PESCAn determined by the upper limit of the load matrix or bed? ? What do you recommend?

I'm looking forward to your guidance. Thanks.

Best,
Yu

@teunbrand
Copy link
Collaborator

The bed file affects this. If you have 10k peaks on a chromosome, it will try (10e3^2)/2= 5e7 combinations for that chromosome, so you quickly run out of memory this way. I'd recommend only taking the the top 5000 peaks or clustering nearby peaks, as it wasn't designed with raw peak calls in mind.

@YuZhang337
Copy link
Author

OK, I understand, thank you very much.

@YuZhang337
Copy link
Author

Hi, @teunbrand

I have another question, although it has nothing to do with error reporting, but I will ask you under this issue, thank you.
I did an APA analysis and the results are as follows:
image

My understanding is that the 3' upstream and 5' upstream of the loop interact more strongly in the mutant group than in the Ctrl group,and the interaction between loops also enhanced, right?

@teunbrand
Copy link
Collaborator

teunbrand commented Apr 17, 2024

The dark feature in the bottom-left might be part of the diagonal, in which case it probably isn't too interesting with regards to looping. You should be able to set the minimum distance to get rid of the diagonal. Otherwise, yes, your mutant indeed has stronger loops.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants