Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

'empty header' error #5

Closed
beeso018 opened this issue Aug 3, 2015 · 4 comments
Closed

'empty header' error #5

beeso018 opened this issue Aug 3, 2015 · 4 comments

Comments

@beeso018
Copy link
Contributor

beeso018 commented Aug 3, 2015

Having problems with pysam I think... Any ideas about what's going on here?

Traceback (most recent call last):
  File "/panfs/roc/groups/3/mccuem/beesons/WGS/paleomix/bin/paleomix", line 250, in <module>
    sys.exit(main(sys.argv[1:]))
  File "/panfs/roc/groups/3/mccuem/beesons/WGS/paleomix/bin/paleomix", line 246, in main
    return module.main(argv)
  File "/home/mccuem/beesons/.local/lib/python2.7/site-packages/pypeline/tools/cleanup.py", line 313, in main
    return _pipe_to_bam()
  File "/home/mccuem/beesons/.local/lib/python2.7/site-packages/pypeline/tools/cleanup.py", line 85, in _pipe_to_bam
    with pysam.Samfile("-", "r") as input_handle:
  File "pysam/calignmentfile.pyx", line 311, in pysam.calignmentfile.AlignmentFile.__cinit__ (pysam/calignmentfile.c:4929)
  File "pysam/calignmentfile.pyx", line 510, in pysam.calignmentfile.AlignmentFile._open (pysam/calignmentfile.c:7138)
ValueError: file header is empty (mode='r') - is it SAM/BAM format?
@MikkelSchubert
Copy link
Owner

Did this error result from running the pipeline?

If so, can you include the pipe* files from the failed task?
This error is likely just the result of some other part of that task failing.

Cheers.

@beeso018
Copy link
Contributor Author

beeso018 commented Aug 4, 2015

Here is the whole temporary directory:

https://drive.google.com/file/d/0B4jvMTKwOo79OXZsbW9zSFp1ek0/view?usp=sharing

@MikkelSchubert
Copy link
Owner

That's a bit excessive; I only needed the pipe* logfiles (< 1mb in total), not the full temp folder.
However, assuming that bam_pipeline.20150803_152327_00.log is the log for your latest run, it looks like one of the BWA instances was SIGKILL'd (and the rest of the programs appear to have been SIGTERM'd by the pipeline).

Are you running the pipeline on a system with runtime or memory limits imposed, or simply with limited memory? If so, an instance of BWA may have been killed because this. Note that you'll need something like 12+ GB of RAM for a genome the size of the human genome, since the pipeline runs BWA aln / sampe in parallel.

@beeso018
Copy link
Contributor Author

beeso018 commented Aug 4, 2015

Yes, looks like memory is the problem here then since it's through a queue system and I have to request memory and walltime when I submit a job. I will try requesting >12GB and see if that solves the issue. Thanks!

@beeso018 beeso018 closed this as completed Aug 4, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants