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

Expose mutually exclusive parameters in Cutadapt to user #60

Open
lina-kim opened this issue Jun 7, 2023 · 0 comments
Open

Expose mutually exclusive parameters in Cutadapt to user #60

lina-kim opened this issue Jun 7, 2023 · 0 comments
Labels
enhancement New feature or request quick-fix Low-hanging fruit

Comments

@lina-kim
Copy link
Collaborator

lina-kim commented Jun 7, 2023

In our current q2-turducken implementation of Cutadapt, only one of mutually exclusive flags are exposed to the user. The other option should also be available if ever needed; this applies to both processes CUTADAPT_DEMUX and CUTADAPT_TRIM.

e.g. in CUTADAPT_TRIM, the flag --p-indels is exposed but --p-no-indels is not.

This will be a bigger issue for flags that may filter for reads with or without input sequences.

@lina-kim lina-kim added quick-fix Low-hanging fruit enhancement New feature or request labels Jun 7, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request quick-fix Low-hanging fruit
Projects
None yet
Development

No branches or pull requests

1 participant