NAME

bc_remove_unexpected_members - Remove community members not expected to occur, based on a reference community

SYNOPSIS

remove_unexpected_members -if my_communities.generic  \
                          -op my_modified_communities \
                          -cn theoretical

DESCRIPTION

This script reads a community file that contains a reference community. For every other community in the file, every member that is not also present in the reference community is removed. This is useful if you have sequenced mock communities and some of them have spurious members.

REQUIRED ARGUMENTS

-if <input_files>... | -input_files <input_files>...

This script reads a community file that contains reference communities. For every non-reference community in the file, every member that is not also present in the corresponding reference community is removed. This is useful if you have sequenced mock communities and some of them have spurious members.

OPTIONAL ARGUMENTS

-op <output_prefix> | -output_prefix <output_prefix>

Path and prefix for the output files. Default: output_prefix.default

-rn <ref_name> | -ref_name <ref_name>

Name of the reference community. Default: ref_name.default

-nt <name_type> | -name_type <name_type>

Specify if <ref_name> represents a 'prefix', 'suffix', or the 'full' name of the reference community. Using prefix or suffix allows to have multiple communities with their respective reference community in the same input file. For example, using a suffic of '_theo', community 'sample1' is expected to have a reference community named 'sample1_theo'. Default: name_type.default

-bs <base_sep> | -base_sep <base_sep>

For the purpose of determining the name of the reference community, strip characters before or after the specified separator. For example, when using the prefix 'ref' and the separator '_', community 'sample1_rep1' and 'sample1_rep2' are expected to have a reference community named 'sample1_ref'.

FEEDBACK

Mailing Lists

User feedback is an integral part of the evolution of this and other Bioperl modules. Send your comments and suggestions preferably to one of the Bioperl mailing lists.

Your participation is much appreciated.

bioperl-l@bioperl.org                  - General discussion
http://bioperl.org/wiki/Mailing_lists  - About the mailing lists

Support

Please direct usage questions or support issues to the mailing list:

bioperl-l@bioperl.org

rather than to the module maintainer directly. Many experienced and reponsive experts will be able look at the problem and quickly address it. Please include a thorough description of the problem with code and data examples if at all possible.

Reporting Bugs

Report bugs to the Bioperl bug tracking system to help us keep track the bugs and their resolution. Bug reports can be submitted via the web:

http://bugzilla.open-bio.org/

AUTHOR - Florent Angly

Email florent.angly@gmail.com