-
Notifications
You must be signed in to change notification settings - Fork 14
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
Using run_ceres directly #11
Comments
Hi Jessica, It looks like the bowtie and samtools issues you're seeing are just that your shell isn't finding them. The function prepare_inputs accepts arguments for bowtie_exe and samtools_exe. You can just pass the absolute paths to these tools in those arguments. Best, Josh |
Is there no way to run it directly with inputs as described in my question? I still get errors:
|
I'm running into similar issues as well. With the same error message. Any solutions to this? |
Just an update that I was able to run the example In case anyone else stumbles on this issue in the future, I used the following bowtie and samtools versions:
|
Thanks for sharing this! :) |
I can't get
prepare_ceres_inputs
to work consistently with my proxy settings and, on the rare occasion I do, I can't get it to work with my bowtie and samtools:As a result, I've tried to put together the correct data and supply it directly to
run_ceres
. It fails with error:and the warnings are:
Obviously I'm using real data, but I thought dummy data would help you to spot what I'm doing wrong:
The text was updated successfully, but these errors were encountered: