The current GATK version is 3.7-0
Examples: Monday, today, last week, Mar 26, 3/26/04

Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!

Get notifications!


You can opt in to receive email notifications, for example when your questions get answered or when there are new announcements, by following the instructions given here.

Did you remember to?


1. Search using the upper-right search box, e.g. using the error message.
2. Try the latest version of tools.
3. Include tool and Java versions.
4. Tell us whether you are following GATK Best Practices.
5. Include relevant details, e.g. platform, DNA- or RNA-Seq, WES (+capture kit) or WGS (PCR-free or PCR+), paired- or single-end, read length, expected average coverage, somatic data, etc.
6. For tool errors, include the error stacktrace as well as the exact command.
7. For format issues, include the result of running ValidateSamFile for BAMs or ValidateVariants for VCFs.
8. For weird results, include an illustrative example, e.g. attach IGV screenshots according to Article#5484.
9. For a seeming variant that is uncalled, include results of following Article#1235.

Did we ask for a bug report?


Then follow instructions in Article#1894.

Formatting tip!


Wrap blocks of code, error messages and BAM/VCF snippets--especially content with hashes (#)--with lines with three backticks ( ``` ) each to make a code block as demonstrated here.

Jump to another community
Picard 2.9.4 is now available. Download and read release notes here.
GATK 3.7 is here! Be sure to read the Version Highlights and optionally the full Release Notes.

GATK Queue ./.queue/ directory translated to an absolute path? All jobs fail on SGE.

When trying to run the Haplotype caller using GATK Queue all my jobs failed because they couldn't write to the tmp files in the ./.queue directory.

This seems to be related to the working directory from which the Queue command is started, and the ./.queue directory is created.

The head node of the SGE grid I want to use and from where I start the Queue is server8.

When I start the Queue command on that server the working directory is translated from a path that is accessible from everywhere on the SGE cluster to a path that is only accessible locally.

Example working directory: /home/sge_share_sever8/variantCalling is translated to the absolute path /data/variantCalling which is only accesible locally.

If I start the Queue from a working directory that is mounted from another server everything workes fine.

Example working directory: /home/sge_share_sever12/variantCalling stays /home/sge_share_sever12/variantCalling and everything works fine.

Is it a bug or feature that the ./.queue directory is translated from a normal path to an absolute path?

Or can I specify another location for the ./.queue directory that will not be translated to an absolute path.

Tagged:

Best Answer

Answers

Sign In or Register to comment.