ncsa/Swift-T-Variant-Calling

Issues

• logging function causing race conditions

  #39 opened 7 years ago by jacobrh91
  0

• exec_check function fails if a symbolic link is present

  #38 opened 7 years ago by jacobrh91
  1

• Scaling Up the Workflow on BW

  #35 opened 7 years ago by jacobrh91
  0

• BW Error when running 601 Node run

  #22 opened 7 years ago by jacobrh91
  23

• Memory limits

  #26 opened 7 years ago by azzaea
  2

• Spacing problem in tmp timing logs

  #31 opened 7 years ago by jacobrh91
  1

• Timing.log in the deliverables folder is empty

  #32 opened 7 years ago by jacobrh91
  1

• Dead link in readme

  #33 opened 7 years ago by jacobrh91
  2

• BW Error when running 110 Node run

  #30 opened 7 years ago by jacobrh91
  5

• Problem running new Blue Waters Swift/T installation

  #23 opened 7 years ago by jacobrh91
  8

• Check for executables pull problem

  #25 opened 7 years ago by jacobrh91
  5

• Undetected Executables' path errors

  #24 opened 7 years ago by azzaea
  3

• Aligner options

  #18 opened 7 years ago by azzaea
  1

• Send mail when errors are detected

  #6 opened 8 years ago by jacobrh91
  2

• Ensure Multiple Novosort Processes Are Not Run Concurrently on One Node

  #10 opened 8 years ago by jacobrh91
  1

• Make workflow keep going even if one branch of loop fails for as long as possible

  #8 opened 8 years ago by jacobrh91
  3

• Split workflow into stages with different resource options

  #7 opened 8 years ago by jacobrh91
  0