-
Notifications
You must be signed in to change notification settings - Fork 23
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
Should be aware that, the index subdirectory should be set up as default or make one manually #14
Comments
Hello BioWu, Did you figure out what are the correct locations to store the index files? I got the error messages: Could not locate a Bowtie index corresponding to basename "mm10_junctions_scrambled" But I stored the files as specified below:
|
Preparing those required files
createJunctionIndex.sh
In the index directory, all below files should be provided
|
Thank you very much for your reply! I‘m using the mouse indexes provided by the KNIFE authors and I have all the files in the index/ directory. But the program still complains. Maybe I should try building a new index on my own. |
Linda, thanks for your effort for develop this tool. But I think there may exist some space to make this tool more friendly to use.
For instance, I tried several times when build one novel reference for my own. But they all failed. I then look at the
createJunctionIndex.sh
and found there no any command to check if the index subdirectory exsit or is it a pre-existed file ? I think may be additional sentences needed here:67 # put the regular junction fasta file into the pipeline index directory 68 mv ${OUT_DIR}/fastas/${FILE_ID}_junctions_reg.fa ${PIPELINE_DIR}/index
.Besides, I can not understand where should be the true file path for your index that could be identitied by you pipeline. Is this
circularRNApipeline/denovo_scripts/index
or just thiscircularRNApipeline/index/
? I think may be you should set one as default and update the README file in thecreateJunctionIndex
directory.Hope this could be help to make KNIFE be a little better.
:)
The text was updated successfully, but these errors were encountered: