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

updates the loftee plugin #44

Merged
merged 3 commits into from
Oct 19, 2022
Merged

updates the loftee plugin #44

merged 3 commits into from
Oct 19, 2022

Conversation

MattWellie
Copy link
Contributor

@MattWellie MattWellie commented Oct 19, 2022

The main branch of loftee causes a ton of error logging messages when running on GRCh38.
Example here (similar errors being throw 27000+ times during processing of one variant subset)

There is a separate branch which we can use instead, with an updated version of the plugin files, see konradjk/loftee#84 (and other similar issues)

The path to copy the plugin files to contains a * -

  • for VEP 105.0, the path is /root/micromamba/share/ensembl-vep-105.0-1
  • for 107.0 this is /root/micromamba/share/ensembl-vep-107.0-0

This copy works for both situations when building the image, but doesn't resolve hard-coding like this

As of today I don't believe there's a way to set an env variable to the result of a RUN command, otherwise this could be used:

ls -l ${MAMBA_ROOT_PREFIX}/share/ | grep ensembl | awk '{ print $9}'

this could be used in setting the path in the production-pipelines job?

LOFTEE_PLUGIN_PATH="${MAMBA_ROOT_PREFIX}/share/$(ls -l ${MAMBA_ROOT_PREFIX}/share/ | grep ensembl | awk '{ print $9 }')"

... but this looks really heavy handed

gnupg2 \
lsb-release \
wget \
zip \
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can't see if it's just reformatted/reodered or a package added here?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ah yeah, this was just splitting the packages out and ordering alphabetically - no changes

@MattWellie
Copy link
Contributor Author

I'm going to merge/build this, and if it works well I'll look into the CI fixes (also broken on main, and I'm reluctant to change the working build)

@MattWellie MattWellie merged commit 0a44286 into main Oct 19, 2022
@MattWellie MattWellie deleted the upgrade_loftee_plugin branch October 19, 2022 06:09
vladsavelyev added a commit to populationgenomics/references that referenced this pull request Nov 1, 2022
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

Successfully merging this pull request may close these issues.

2 participants