Update README.md

allaway · Jul 4, 2024 · b4b7352 · b4b7352
1 parent f2e6543
commit b4b7352
Showing 1 changed file with 5 additions and 5 deletions.
diff --git a/README.md b/README.md
@@ -1,18 +1,18 @@
 # vcf2maf-vep
 
 
-This Dockerfile is loosely based on [this gist](https://gist.github.com/ckandoth/61c65ba96b011f286220fa4832ad2bc0) and can be used to create a Docker image with all of the necessary dependencies for vcf2maf to run with Ensemble v107. You just need to provide (1) the VEP 107 cache (instructions for grabbing it with rsync below) and (2) the genomic FASTA that you aligned to (for the NF-OSI pipeline, we currently use the GATK GRCh38 build, which can be acquired from iGenomes (instructions for grabbing it with the AWS CLI below). 
+This Dockerfile is loosely based on [this gist](https://gist.github.com/ckandoth/61c65ba96b011f286220fa4832ad2bc0) and can be used to create a Docker image with all of the necessary dependencies for vcf2maf to run with Ensemble v112. You just need to provide (1) the VEP 112 cache (instructions for grabbing it with rsync below) and (2) the genomic FASTA that you aligned to (for the NF-OSI pipeline, we currently use the GATK GRCh38 build, which can be acquired from iGenomes (instructions for grabbing it with the AWS CLI below). 
 
 The Docker repository for this is: https://hub.docker.com/r/nfosi/vcf2maf
 
-Currently, this image uses a custom fork of vcf2maf to address a small incompatibility with VEP v107. When https://github.com/mskcc/vcf2maf/issues/322 is resolved, we can switch back to the real release of vcf2maf. 
+Currently, this image uses a custom fork of vcf2maf to address a small incompatibility with VEP v112. When https://github.com/mskcc/vcf2maf/issues/322 is resolved, we can switch back to the real release of vcf2maf. 
 
 ```
 ## Need to have rsync and the aws-cliv2 installed.
 
-## Get VEP 107 database. 
-rsync -avr --progress rsync://ftp.ensembl.org/ensembl/pub/release-107/variation/indexed_vep_cache/homo_sapiens_vep_107_GRCh38.tar.gz $HOME/.vep/
-tar -zxf $HOME/.vep/homo_sapiens_vep_107_GRCh38.tar.gz -C $HOME/.vep/
+## Get VEP 112 database. 
+rsync -avr --progress rsync://ftp.ensembl.org/ensembl/pub/release-112/variation/indexed_vep_cache/homo_sapiens_vep_112_GRCh38.tar.gz $HOME/.vep/
+tar -zxf $HOME/.vep/homo_sapiens_vep_112_GRCh38.tar.gz -C $HOME/.vep/
 
 ## Get GATK GRCh38 genome (or whatever genome you aligned to if not this one...)
 aws s3 --no-sign-request --region eu-west-1 sync s3://ngi-igenomes/igenomes/Homo_sapiens/GATK/GRCh38/ $HOME/Homo_sapiens_GATK_GRCh38/