-
Notifications
You must be signed in to change notification settings - Fork 25
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
Segmentation during scanning for optimal CRF weight for certain chromosomes only #19
Comments
I have had the same problem. My data was 33551 individuals with 248611 SNPs (for one chr) and is not working after setting 300GB RAM |
Has this issue been resolved? I have core dumps as well. The cause might be a little bit different, though: segmentation faults only occur only "-e 1" is used. If the same command excluding "-e 1" is used, everything works fine. Memory usage is preset to be 250GB. |
Similar problem here. I'm running on 100 samples and some of the chromosomes works fine, but for others we got Killed. Also, I'm using this docker image with rfmix: quay.io/biocontainers/rfmix:2.03.r0.9505bfa--h1b792b2_2
Do you have any updates on this issue? |
My guess is that the core dump has nothing to do with the number of samples you are painting, since rfmix paint sample one by one. It looks like the core dump has something to do with the number of SNPs used. Bigger chromosomes have more SNPs and require more memory and thus cause problems. |
Hello.
For chromosome 6 to 22, it works fine. But I am getting segmentation fault only for the first 5 human chromosomes.
It creates a core dumped file -> core.XXXXX
Initially, I thought it was due to memory but the maximum amount of memory it uses was way below what is available. This is the LSF summary of the job:
My command :
rfmix --query-file=qgp_chrall.vcf.gz --reference-file=1kgp_snp_only.vcf.gz --sample-map=subpop_1kg.txt --genetic-map=genetic_map_hg19_withX_3col.txt --output-basename=REF_1kg_QUERY_qgp_chr1 --chromosome=1 --n-threads=143
As I mentioned earlier, I am getting the error only for chr1 until chr5 and the rest works fine. Any idea what is going?
The text was updated successfully, but these errors were encountered: