-
Notifications
You must be signed in to change notification settings - Fork 1
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
Suggestions #1
Comments
Hi @corneliusroemer, Thanks for the pointers. These are great suggestions. I just spoke with @NPSDC and @zzare-umd yesterday about having a top-level Snakemake file. I think that's the way to go. I'm not certain that it's ideal to assume that all tools are present directly in the path, as users may want to evaluate different versions of tools and provide custom paths to them (the replicable results are expected, of course, only for the versions we list here). As I can see that you're already addressing upstream, the newest version of NanoCount can currently only be obtained from their GitHub repository and installed from source (and not via bioconda). We will continue to try to make the pipeline simpler to run, and we'd be happy to welcome discussion on any PRs you might make, and include them if they make sense! Best, |
People can customize their environment if they want to - but offering a default is good practice to simplify testing.
One can pip+git install, see PR #2 ;) |
I tried to run the benchmarks but struggled. I suggest to make it more reproducible to:
bambu
,nanocount
andbustools
in bioconda nor conda-forgeHere's what I got as a start:
/mnt
, so that one can run the analysis straightaway without having to change thingsThe text was updated successfully, but these errors were encountered: