-
Notifications
You must be signed in to change notification settings - Fork 30
Open
Description
Hi there,
I am trying to run 'intervene upset'on 73 BED files that have ~40,000 intervals each.
intervene upset -i /data/alistairh/projects/SV_calling/data/peaks/DiscRegions/*{1,2,3}.bed --output SV_calling/data/peaks/DiscRegions/results_RT --save-overlaps
However, Intervene uses up all the available memory (62G) before being killed by the server. Is there a setting or a fix to limit the memory use of Intervene so it doesn't get killed by the server? This hasn't been a problem before when I have used intervene for 15-20 BED files.
Metadata
Metadata
Assignees
Labels
No labels