-
Notifications
You must be signed in to change notification settings - Fork 8
Error with using WALT #38
Comments
Hi Verda, Could you provide the command line you used when encountering this error? This "bad index file" error is reported by |
So what I tried was:
I've seen that other files were created by the makedb line. Should I be referencing that folder or the specific .dbindex file? |
hg38.dbindex_CT00 these were the other files that were created |
Your command line looks good to me, and I was not able to reproduce this error. In the error message of |
Hi Verda, If possible could you also clarify whether you cloned the repository or if you are using the release? Thank you! |
I cloned the repository using this command line: followed by the instructions you listed in the manual (cd walt, make all, make install). Should I be using the repository or the release? If you see my last post above, I mentioned several .dbindex files were generated when I made my index: hg38.dbindex, hg38.dbindex_CT00, hg38.dbindex_CT01, hg38.dbindex_GA10, hg38.dbindex_GA11 Should I be referencing that folder or the specific .dbindex file when mapping? |
@aganve If you could try the same thing with a "release" it might be very helpful. We are having trouble understanding/reproducing the issue. |
So I deleted walt and cloned it again. This time I didn't get an error that said 'bad index file.' This solved that problem. Now I have a new issue. I got an emtpy .mr file as well as an empty .mpstats files after mapping. I am using the reads you provided, snippet_1.fq and snippet_2.fq, to map to hg38. No errors came up. Any ideas on how to fix this problem..? |
I've used both the repo and release now to try to get my mapped reads but have had 0 success. I'm still getting an empty .mr file. Ideas? Thanks |
Hi Verda, Can you point us to where you downloaded the hg38 reference? I'm going to try to reproduce the problem. Thank you! |
@aganve It would also help if you could send one of us a direct message, and we could provide you with a very small test case file to see if you are able to get success on that file, and if so, whether what you see is identical to what we see when we run it. |
I downloaded the hg38 reference from UCSC (https://hgdownload.soe.ucsc.edu/goldenPath/hg38/bigZips/ ). This is what my output error file looks like when mapping to either hg38 or hg19 index:
I am using test data (snippet_1.fq and snippet_2.fq) that was provided with the 2013 version of MethPipe. It looks like rmapbs-pe program was used at that time for mapping. Could there be an issue with the .fq files that doesn't work with walt? Do you have a test case file you could provide me with? Not sure how to send you a direct message @andrewdavidsmith |
Hello,
I'm in the process of running through the MethPipe pipeline using some practice data provided by your lab. I'm using WALT as recommend for mapping reads. I tried to create an index for hg38 but then got an error saying 'bad index file' so I wasn't able to map my reads. I also used an index available from my lab’s cluster and it gave me the same error. Why am I getting this error? Any ideas on how to fix this?
Verda
The text was updated successfully, but these errors were encountered: