You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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
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.
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.
The text was updated successfully, but these errors were encountered: