Question: .dict file created by picard and by samtools
1
gravatar for haiying.kong
19 months ago by
haiying.kong120
Germany
haiying.kong120 wrote:

There are 2 ways of generating .dict file for human genome.

java -jar picard.jar CreateSequenceDictionary REFERENCE=reference.fa OUTPUT=reference.dict

samtools faidx ref.fasta

I found that the 2 files generated in the 2 different command have different file size.

I need .dict file for GATK and Picard. Which one is correct one?

Thank you very much.

next-gen • 2.4k views
ADD COMMENTlink modified 4 days ago by nabiyogesh40 • written 19 months ago by haiying.kong120

The files created by both the tools are different. I guess u need both .fai and .dict to use .fa as a reference 

ADD REPLYlink modified 19 months ago • written 19 months ago by Goutham Atla7.1k
1
gravatar for igor
19 months ago by
igor3.9k
United States
igor3.9k wrote:

Picard CreateSequenceDictionary creates .dict file and samtools faidx creates a .fai file. Both are needed for GATK.

ADD COMMENTlink modified 19 months ago • written 19 months ago by igor3.9k
0
gravatar for nabiyogesh
4 days ago by
nabiyogesh40
South Korea
nabiyogesh40 wrote:

I am not able to understand how to create a dictionary by using the latest version of Picard 2.8.1.

It is different from the previous version.

Should I use i for input instead of REFERENCE and what will be option for output?

Old Picard 1.8.1 Command:

jar /home/yog/software/picard-2.8.1/src/main/java/picard/sam/CreateSequenceDictionary.java REFERENCE=R1_R9.fasta OUTPUT=R1_R9.dict

New Command options:

 jar /home/yog/software/picard-2.8.1/src/main/java/picard/sam/CreateSequenceDictionary.java

Illegal option: /

Usage: jar {ctxui}[vfmn0PMe] [jar-file] [manifest-file] [entry-point] [-C dir] files ... Options:

-c  create new archive

-t  list table of contents for archive

-x  extract named (or all) files from archive

-u  update existing archive

-v  generate verbose output on standard output

-f  specify archive file name

-m  include manifest information from specified manifest file

-e  specify application entry point for stand-alone application

    bundled into an executable jar file

-0  store only; use no ZIP compression

-P  preserve leading '/' (absolute path) and ".." (parent directory) components from file names

-M  do not create a manifest file for the entries

-i  generate index information for the specified jar files

-C  change to the specified directory and include the following file
ADD COMMENTlink modified 4 days ago • written 4 days ago by nabiyogesh40
Please log in to add an answer.

Help
Access

Use of this site constitutes acceptance of our User Agreement and Privacy Policy.
Powered by Biostar version 2.3.0
Traffic: 1818 users visited in the last hour