SEQanswers

Go Back   SEQanswers > Applications Forums > RNA Sequencing



Similar Threads
Thread Thread Starter Forum Replies Last Post
HISAT2 vs. TopHat2: Discrepancies between Hg19 & Hg38 Sbamo RNA Sequencing 0 01-26-2016 06:05 AM
Incorrect Genotype information in VCF Karen Chait Berman Bioinformatics 0 08-20-2012 06:40 AM
Inconsistent genotype in VCF file rlegendre Bioinformatics 1 04-16-2012 06:17 AM
vcf snp genotype M&M Bioinformatics 1 09-02-2011 10:52 AM
vcf: difference between position DP and genotype DP melo Bioinformatics 0 05-10-2011 08:50 AM

Reply
 
Thread Tools
Old 07-15-2016, 04:30 AM   #1
kevinrue
Member
 
Location: London

Join Date: Jan 2013
Posts: 25
Default HISAT2 / hisat2_extract_snps_haplotypes_VCF.py / --genotype-vcf & VCF_fnames

Dear all,

I would like to use the Python script hisat2_extract_snps_haplotypes_VCF.py.

I cannot fully understand some of the command line options from the description printed using the --help option.

I am confused about the role of the positional argument VCF_fnames and the optional argument --genotype-vcf.

Here is a copy paste of those two argument descriptions (let me know if I should paste the complete output of --help, it is not so long):
VCF_fnames A comma-seperated VCF files (plain text or gzipped
file is accepted: GRCh38_dbSNP_no_SVs.vcf or
GRCh38_dbSNP_no_SVs.vcf.gz


--genotype-vcf GENOTYPE_VCF
VCF file name for genotyping (default: empty)



I have access to merged VCF files: one per human chromosome, each file contains genotypes and VEP predictions for the same set of samples.
I thought these files should go as the positional argument VCF_fnames, however, I would like to know:
  1. whether my files contain the right information for the positional argument
  2. what kind of VCF file should go in the optional argument --genotype-vcf

Many thanks in advance!

Kevin
kevinrue is offline   Reply With Quote
Old 07-15-2016, 04:34 AM   #2
GenoMax
Senior Member
 
Location: East Coast USA

Join Date: Feb 2008
Posts: 6,579
Default

Can you provide a reference for where you got the said script from?
GenoMax is offline   Reply With Quote
Old 07-15-2016, 05:46 AM   #3
kevinrue
Member
 
Location: London

Join Date: Jan 2013
Posts: 25
Default

https://github.com/infphilo/hisat2/b...lotypes_VCF.py
kevinrue is offline   Reply With Quote
Old 07-15-2016, 06:29 AM   #4
kevinrue
Member
 
Location: London

Join Date: Jan 2013
Posts: 25
Default

Just to clarify, in my previous message I sent the link to the Python script itself.
However, I installed the software from the source code availabe at https://ccb.jhu.edu/software/hisat2/...html#options-1

Thanks in advance for looking into this!
kevinrue is offline   Reply With Quote
Old 02-23-2017, 05:36 AM   #5
xris
Junior Member
 
Location: Barcelona

Join Date: Feb 2017
Posts: 1
Default

Hi Did you resolve your question? I have the same doubt.

If I run

hisat2_extract_snps_haplotypes_VCF.py -v path/to/.fa path/to/.vcf test

I get only empty output files .snp .haplotype

Thanks

Last edited by xris; 02-23-2017 at 05:39 AM.
xris is offline   Reply With Quote
Old 02-23-2017, 07:05 AM   #6
kevinrue
Member
 
Location: London

Join Date: Jan 2013
Posts: 25
Default

Hi xris,

Sorry, no, never sorted that one out. Ended up using using the UCSC snp146Common.txt file.

Regarding you empty .snp and .haplotype issue, does this other post help you in any way?

You say empty, but in my case, I had one entry in the output, because the script relies on the rsid field to uniquely identify variants, while in my case all the variants had "." and therefore all variants after the first one were skipped. However, that was over a year ago, and the script may behave differently now.

Best wishes,
Kevin
kevinrue is offline   Reply With Quote
Reply

Tags
hisat2, index, rna-seq aligners

Thread Tools

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off




All times are GMT -8. The time now is 08:35 PM.


Powered by vBulletin® Version 3.8.9
Copyright ©2000 - 2017, vBulletin Solutions, Inc.
Single Sign On provided by vBSSO