-
Notifications
You must be signed in to change notification settings - Fork 68
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
--modified-bases all option #227
Comments
Hey @Kirk3gaard What do you imagine Good point on the consistency of the argument separators. |
Hi @iiSeymour Detecting all modifications that you have models for. I think for most users whether they want to call modifications or not is a yes/no question rather than I only want to call 6mA or 5mC. Best regards |
Good point of Rasmus |
I second the feature mentioned by @Kirk3gaard |
Interesting, but a couple of thoughts
In general, I'd prefer to specify exactly which models I want unless all of the above points are solved or not detrimental. |
Hi
I think for an improved user experience it would be great to have an option to activate "all" modifications without manually specifying the models.
Another thing I noticed is that it is confusing that --modified-bases takes a space separated list whereas --modified-bases-models takes a comma separated list. Probably easier to stick with one way of supplying arguments.
Best regards
Rasmus
The text was updated successfully, but these errors were encountered: