bc_manage_samples - Include, delete, merge, sort or rename samples
bc_manage_samples -input_files communities.generic \ -exclude_names soil1 \ -merge_names freshwater2 freshwater5 \ -merge_names marine* \ -output_prefix processed_communities
This script reads files containing biological communities and includes, deletes merges, sorts or renames the specified communities. See Bio::Community for more information.
Input file containing the communities to manipulate. When providing communities in a format that supports only one community per file (e.g. gaas), you can provide multiple input files.
Path and prefix for the output files. Default: output_prefix.default
Prefix to add to the beginning of all community names. Default: name_prefix.default
Suffix to add to the end of all community names. Default: name_suffix.default
If names of communities are specified, only these communities will be included in the output file, in the requested order. This is also useful to arrange the communities in a specific order.
Community names can be specified using wildcards, which means that 'marine*2013' will match all names starting with 'marine' and finishing with '2013', while '*gut*' will match all names containing 'gut'.
If names of communities are specified, these communities will be excluded from the output file. As with <include_names>, wildcards are supported.
Specify the name of the communities to merge. Use this option multiple time if you need to merge multiple sets of communities. The count of the members of these communities are added. As with <include_names>, wildcards are supported.
When merging communities, specify a method to generate a name for the merged community:
* a character that will join the names of the communities to merge, e.g. '+', '_', ...
* 'first': use the name of the first community
* 'common': The largest substring common between the names, starting from the left. After this, any trailing, non-alphanumerical character is considered a separator and removed.
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.
email@example.com - General discussion http://bioperl.org/wiki/Mailing_lists - About the mailing lists
Please direct usage questions or support issues to the mailing list:
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.
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: