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

error in wellington_footprints.py #28

Closed
billgreenwald opened this issue Jan 30, 2018 · 5 comments
Closed

error in wellington_footprints.py #28

billgreenwald opened this issue Jan 30, 2018 · 5 comments

Comments

@billgreenwald
Copy link
Contributor

Hi!

I just downloaded wellington, and when running wellington_footprints.py I was getting the error:

error at line 85:
'<' is not defined for GenomicInterval objects

I determined this was happening only when a BED file with multiple chromosomes was passed. The full line 85 was

orderedbychr = [item for sublist in sorted(regions.intervals.values()) for item in sorted(sublist, key=lambda peak: peak.startbp)]

but, after some testing, it seemed like the error was coming from

sorted(regions.intervals.values())

Based on the comment above that the goal is to iterate by chromosome, then position, I edited line 85 to be

orderedbychr = [item for sublist in sorted(regions.intervals.values(),key=lambda genomicIntervalList: genomicIntervalList[0].chromosome) for item in sorted(sublist, key=lambda peak: peak.startbp)]

This has overcome the bug and the program runs. I am posting this to both confirm that this is the intended result and that my output should be correct, and to give a bugfix if so.

Thanks!

@davidhbrann
Copy link

Hi,
I'm trying to run wellington_footprints.py as well and was encountering the same error. I checked quickly and it looks like your fix also prevented the error on some data I downloaded from encode wellington_footprints.py -p $SLURM_NPROCS wgEncodeUwDgfHaspPk.bed wgEncodeUwDgfHaspAln.bam pydnase_out, but I'd also like to know if the fix that Bill posted is correct.

Thanks!

@billgreenwald
Copy link
Contributor Author

Hey @dhb2128, with my data, Wellington hangs with the last 80 threads finishing up and I get empty output. Do your output files have entries in them?

@davidhbrann
Copy link

I got the same message, "Waiting for the last 80 jobs to finish...", but it still produced a WellingtonFootprints.FDR.0.01.bed file, the WellingtonFootprints.wig file, and the files in the p value cutoff folder in the outdir.

@billgreenwald
Copy link
Contributor Author

was your WellingtonFootprints.FDR.0.01.bed empty?

@davidhbrann
Copy link

davidhbrann commented Feb 9, 2018

Not when I ran wellington_footprints.py. That one seemed to work. However, I get no output when I run wellington_bootstraps.py. Not sure if it's a threshold thing; self.scores is less than the FDR limit but self.findDiffFP() seems to not be returning any results.

Was it always empty for you?

@jpiper jpiper closed this as completed in 4ab1593 Mar 29, 2018
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