Skip to content
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

explanation of the naming convention in the config and pipeline when using bowtie2_mapping rule #3

Closed
cokelaer opened this issue Jan 22, 2020 · 1 comment

Comments

@cokelaer
Copy link
Contributor

bowtie2_mapping (and other rules) are dynamic rules. This means that we can use them several
times in a pipeline. To do so, we must set their name as follows:

exec(open(sequana.modules["bowtie2_mapping_dynamic"], "r").read())
include: bowtie2_mapping_dynamic("ref", manager)

So here the actual rule is called bowtie2_mapping_ref. However, in the rule itself, the expected name in the configuration file is bowtie2_mapping. Therefore, the config file should bowtie2_mapping and not bowtie2_mapping_ref./

@cokelaer
Copy link
Contributor Author

I was wondering whether this is a bug in the rule itself, and yes it is:

I fixed the rule bowtie2_mapping to make it fully

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant