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

plans to adapt for vsearch? #5

Open
gregcaporaso opened this issue Aug 25, 2015 · 1 comment
Open

plans to adapt for vsearch? #5

gregcaporaso opened this issue Aug 25, 2015 · 1 comment

Comments

@gregcaporaso
Copy link

Hi, I was wondering if you'd thought at all about adapting CFF to use vsearch under-the-hood in place of usearch, since vsearch is open source, has more permissive licensing, etc.

@hepcat72
Copy link
Owner

Hi Greg,

Thanks. This has been recently suggested and it sounds like a good idea. Currently, CFF is in a maintenance phase, so we don't have any plans for new features in the immediate future. However if what I've heard is true, and the interface is the same (haven't heard about output format) then it might be worth a try to simply supply vsearch as the usearch executable using the -y option and see what happens. The two scripts which use usearch (and have those options) are getReals.pl & interestingPairs.pl. If you try it out, please let me know how it goes. All this might require is a change to the documentation.

Rob

Robert William Leach
133A Carl C. Icahn Lab
Lewis-Sigler Institute for Integrative Genomics
Princeton University
Princeton, NJ 08544

On Aug 25, 2015, at 5:59 PM, Greg Caporaso [email protected] wrote:

Hi, I was wondering if you'd thought at all about adapting CFF to use vsearch under-the-hood in place of usearch, since vsearch is open source, has more permissive licensing, etc.


Reply to this email directly or view it on GitHub.

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

No branches or pull requests

2 participants