merging VCF files or not
0
0
Entering edit mode
4.6 years ago
Sara ▴ 240

I am working with VCF file (one file per sample) and the goal is to report the genes with mutation. so, my question is since I have many files and at the end I need to have one file as report, shall I merge the files or I need to do something else?

SNP vcf • 1.3k views
ADD COMMENT
2
Entering edit mode

Sure, why wouldn't you?

ADD REPLY
0
Entering edit mode

If the boss asks for one file, you give one file =)

ADD REPLY
0
Entering edit mode

Also, no real advantage to keeping things separate, I guess.

ADD REPLY
0
Entering edit mode

@ WouterDeCoster: Ok Thanks. then I will merge the files using bcftools and then parse the new file. is that correct?

ADD REPLY
0
Entering edit mode

Please respond to guillaume.rbt's question. Note, that, if you merge all VCFs together, you can still produce a separate annotation file for each sample using ANNOVAR.

ADD REPLY
0
Entering edit mode

What do you mean by "report the genes with mutation", can you give more details?

ADD REPLY
0
Entering edit mode

@guillaume.rbt: to make it clear let me rephrase my question. I have many VCF files and I want to summarize all of them into a csv file. the csv file should have some columns including gene names, REF and ALT per sample(file). so, now the question is: how should I organize all the data from all samples in one csv file? do you have any experience?

ADD REPLY
0
Entering edit mode

Please use ADD COMMENT/ADD REPLY when responding to existing posts to keep threads logically organized. SUBMIT ANSWER is for new answers to original question.

ADD REPLY
0
Entering edit mode

yes you can do it, by using git bash to merge all vcf/HapMap files in one file. cat *hmp.txt >all_comine.txt

ADD REPLY
2
Entering edit mode

That would not be a valid VCF file and definitely not useful in any way.

ADD REPLY

Login before adding your answer.

Traffic: 2601 users visited in the last hour
Help About
FAQ
Access RSS
API
Stats

Use of this site constitutes acceptance of our User Agreement and Privacy Policy.

Powered by the version 2.3.6