-
Notifications
You must be signed in to change notification settings - Fork 20
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
Chromap process gets kill #59
Comments
Can you provide me with the test data so that I can reproduce the error and figure out the issue? Thanks! |
Sure, sorry I reproduced the error I got with me own files using the test files in this repo: https://github.com/haowenz/chromap/tree/master/test |
I see. I had no issue running it on my machine. It seems that there is some problem for Chromap to run on Ubuntu 18 as #37. This is really weird. I will get such a machine and try to reproduce the error. |
I was only able to reproduce the error with a low memory machine. So this should be an out of memory issue. How much memory do you have on your machine? |
I free some memory in my machine and then it worked, but it needed ~11 Gb for the test data. Actually, I started to perform this test since I was also trying to run some real data in the cluster of my institution (running
I requested 62.0 GB for the execution above (since a previous execution with just 32.0 GB got the same error). Thanks a lot for the help! |
As the human genome index is more than 10GB, Chromap will take at least 10GB memory when running with human sequencing data. So this was somehow made as an assumption and hard-coded at the moment. But it is not necessary for small genome like the test genome. I will tune this down for next version.
This may not be an out of memory issue. If your data is publicly available, you can let me know the way to download it and I will debug on that. Otherwise, as you said, since the adapters have been trimmed, it is very likely that it is caused by the same reason. In this case, I will fix #46 first and then let you know. Then you can try on your data again and see if the problem is still there. |
Fair enough!
You can download the files from here. The commands that I used were: # index creation cmd
chromap \
-i \
-t 6 \
-r genome.fa \
-o genome.index
# mapping cmd
chromap \
--preset chip --SAM \
-t 6 \
-x genome.index \
-r genome.fa \
-1 INPUT_TKO_REP1_T1_trimmed.fq.gz \
-o INPUT_TKO_REP1_T1.Lb.sam Thanks a lot! 😃 |
I was able to confirm that the error is caused by out of memory. After the pull request, I was able to finish mapping this dataset in 18GB memory. You can use the master branch if you want to give it a try. Or you can wait a couple of more days and we will include this fix in the next release on conda. |
Thanks a lot @haowenz! I will give it a try to version |
Hi again, I checked and version |
Hi there,
When running chromap with the following:
chromap --preset chip -x genome.index -r genome.fa -1 SPT5_INPUT_REP1_T1_1_val_1.fq.gz -2 SPT5_INPUT_REP1_T1_2_val_2.fq.gz -o SPT5_INPUT_REP1_T1.bed
, I get the process kill, as you can see below:I reproduced the error using the test data:
However, if I just use one of the fastq files, both with the real and the test data, it works e.g. with the test data
chromap --preset chip -x ref.index -r ref.fa -1 read1.fq -o test.bed
I am running it using the last version of chromap
0.1.5-r302
in a conda environment in Ubuntu 18.04.6.Thanks a lot!
The text was updated successfully, but these errors were encountered: