Build Status

Description

Here we have command-line utilities for popular Bio::Perl classes.

Specifically:

The motivation is to allow users to perform routine BioPerl manipulations of sequences, alignments, and trees without having to write full-blown scripts. For common operations of sequences and alignments, Bio::BPWrapper makes it easy to create workflows with a single BASH script containing a combination command-line calls: no Perl or BioPerl coding is necessary.

Internally, the programs follow a "Wrap, don't Write" design principle. That is, we have full faith in the robustness of the BioPerl development framework. As such, methods here should all be wrappers to BioPerl methods so that exceptions can be handled properly by BioPerl.

The Bio::BPWrapper module also include some useful methods which are not part of Bio::Perl.

Install & Test from git:

You need Perl 5.010 or later. There are other Perl dependencies, but the package will check and install that.

    $ git clone https://github.com/bioperl/p5-bpwrapper
    $ cd p5-bpwrapper
    $ cpan Module::Build  # may need sudo
    $ perl ./Build.PL
    $ ./Build installdeps
    $ ./Build
    $ make check
    $ ./Build install # may require sudo or root access

Each script, bioaln, biopop, bioseq and biotree give shorter usage help when given command-line option --help. Manual-page help is also giving the option --man.

Documentation is maintained in this project's wiki.

A help file with use cases is maintained at: http://diverge.hunter.cuny.edu/labwiki/Bioutils

Install from CPAN

The git code generally has the newest code. If git is not your thing, you can also install the last release from CPAN:

   $ cpan install Bio::BPWrapper
   $ cpanm --sudo Bio::BPWrapper

Install and run from docker

Use the bpwrapper docker image. It includes bioaln, biopop, bioseq, and biotree.

To download the image so that docker recognizes it:

docker pull rockyb/bpwrapper

For things other than getting help, you'll often need to pass a data in file to the program. Do that by sharing the directory that the file is in on the docker invocation.

You'll need to pay attention to the permissions on the data file its directory. The docker container runs as as a user that may not have access to data. I've found however that if you put the data in /tmp files will be seen inside the running docker container.

For example:

$ cp test-data/cds.fas /tmp/cds.fas
$ docker run -it -v /tmp:/test-files rockyb/bpwrapper bioseq -l /test-files/cds.fas
DK2	120
W70332	120
M1608	108
F2

Developers, Contact, Citation