Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Wrapper scripts and container are not portable #6

Open
moskalenko opened this issue Sep 27, 2019 · 0 comments
Open

Wrapper scripts and container are not portable #6

moskalenko opened this issue Sep 27, 2019 · 0 comments

Comments

@moskalenko
Copy link

Hi,

I'm looking at CN_Learn to see if it can be installed on a compute cluster. However, I am concerned that the included wrapper scripts all have to be manually patched since they are not written to be portable. For example, even if though ${DOCKER_COMMAND} can be overridden in the user's environment to run a singularity container created from the provided docker container virtually all calls to executables in the container take the form of ${DIRECTORY_NAME}program whereas the convention is that all executables would be in standard path or paths specified in the docker container's environment, so all wrappers don't have to be painstakingly manually patched on every installation and upgrade.

At the same time the /opt/tools/CN_Learn/config.params in the container has hardcoded paths to directories likely present on the system(s) the author(s) work on like

REF_GENOME='/data/bx_references/GRCh37/human_g1k_v37.fasta'
DATA_BPCOV_DIR='/data2/RF_Model_SVIP/data/extract/bp_level_coverage/'

Regards,

Alex

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant