refactoring of split_libraries.py into separate scripts for quality filter and demultiplexing

[gregcaporaso]

No description provided.

[gregcaporaso]

Imported from trac issue 12. Created by caporaso on 2011-04-25T14:10:36, last modified: 2011-12-07T14:02:43

[gregcaporaso]

@walterst, what's the status on this? Will it be ready for 1.6.0?

[walterst]

I'd be worried about the limited time to test it fully as a workflow, but
I'll have the individual scripts in place in a couple of days (could be
used in place of split_libraries.py when applicable, and can get further
tests later to make sure it works as a workflow named "split_libraries.py"
but in the development version, I'd want that to be in place for many
months before committing it to a release version).

On Tue, Nov 27, 2012 at 9:22 PM, Greg Caporaso notifications@github.comwrote:

@walterst https://github.com/walterst, what's the status on this? Will
it be ready for 1.6.0?

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/12#issuecomment-10790232.

[gregcaporaso]

OK, so we'll keep split_libraries.py as is for this release, and refactor for 1.7.0?

[walterst]

Yep but the individual scripts (demultiplex_fasta.py and
quality_filter_fasta.py) will be implemented, just not the workflow that
calls these two and replaces split_libraries.py.

On Wed, Nov 28, 2012 at 7:44 AM, Greg Caporaso notifications@github.comwrote:

OK, so we'll keep split_libraries.py as is for this release, and refactor
for 1.7.0?

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/12#issuecomment-10804872.

[gregcaporaso]

I think we might not want to add these yet because that would create two independent ways that users could demultiplex/quality filter their 454 data, which could turn into a big support issue.