Flow ships with tasks that do not have all of their dependencies included.  On startup Flow will attempt to install the dependencies, but not every system is equipped to install them.

In the case of any difficulties, it is highly recommended to instead use a docker deployment  (cluster installations may require singularity instead, which is somewhat still a work-in-progress)

CNVkit

Requires Python 2.7 or later.

On startup Flow will attempt to install additional python packages using the command pip install --user cnvkit==0.8.5

If pip cannot be installed on the target machines then the packages can be downloaded from: 

customer.partek.com/cnvkit_packages-0.8.5.zip for ubuntu

customer.partek.com/cnvkit_packages-centos7.zip  for centos7

Extract the file in the home directory (Make .local a symlink if the home directory doesn't have enough free space)

Requires R 3.2.3 or later.

On startup Flow will attempt to install additional R packages. 

There are cascading dependencies, but you can view the core libraries in partek_flow/bin/cnvkit-0.8.5/install.R

If these packages can't be built locally, it may be possible for the user to download them from us (see below).

DESeq2

Requires R 3.0 or later.

On startup Flow will attempt to install additional R packages. 

There are cascading dependencies, but you can view the core libraries in partek_flow/bin/deseq_two-3.5/install.R

If these packages can't be built locally, it may be possible for the user to download them from us (see below).

RcppArmadillo may also have dependencies on multi-threading shared objects that may not be on the LD_LIBRARY_PATH

The recommendation is to copy those .so files to a folder and make sure it is available from the LD_LIBRARY_PATH when the server/worker starts.

Additional dynamic libraries (such as libxml2.so) may be missing and we can provide a copy appropriate for the target OS.

HTSeq

Requires Python 2.7 or 3.4 or above

On startup Flow attempts to install using pip

Python

If there are any conflicts with preinstalled python packages, Flow should be configured to run with its own virtual environment:

pip install virtualenv

virtualenv ~/.partekflow/.local

source ~/.partekflow/.local/bin/activate

(optionally add this line to a flow startup script)

pip install HTSeq==0.11.0

pip install cnvkit==0.8.5

or 

wget customer.partek.com/python-dependencies.zip

unizp -d ~/.partekflow/ python-dependencies.zip

Variant Effect Predictor

This is a compiled Perl script (so it has no direct dependency on Perl itself) we have had one report (istem.fr) of it failing to run. 

R

R can usually be installed from the package manager.  If the user installs Flow via apt or yum it should already be installed.

For older operating systems R is not available and will need to be installed from source 

Currently, we offer a set of R packages compatible with some versions of R

• 3.2.3
• 3.4.0
• 3.4.3

Extract this file in the home directory.  (Make .R a symlink if the home directory doesn't have enough free space)

These packages include the dependencies for both CNVkit and DESeq2

When running R diagnostic commands outside flow, it can simplify things if the environment includes a reference to the ~/.R folder:

export R_LIBS_USER=$HOME/.R

or load 

.libPaths("~/.R")

in ~/.Rprofile

list loaded packages: 

(.packages())

get the version:

packageVersion("packageName")

R_HOME=/path/to/R

see also:  Minimum System Requirements

Your Rating:

Thanks for voting!

Please Wait

Results:

2

rates