-
Notifications
You must be signed in to change notification settings - Fork 54
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
missing table in LoF #23
Comments
I get this error too. I'd like to be able to use the DONOR_DISRUPTION_PROB. |
I have the same missing table. and what I get: |
I also got this error. Any solution for that? |
No, no solution so far, as you can tell I've raised this issue back in October but the developers of this tool couldn't care less! Makes you wonder about the quality! |
I'll think you'll be better off using similar tools from people who care and know what they are doing! |
😕 not sure "couldn't care less" is called for. Apologies for the error. I've identified the issue, but am thinking about the best way to use and distribute the gerp data (it is quite large, and sqlite isn't cutting it anymore). I hope to have a fix for this soon. In the meantime, if you have an urgent analysis to run, I suggest falling back to the most recent stable version (0.3): https://github.com/konradjk/loftee/tree/v0.3-beta |
Finally a reply!! It seems some people only react to an insult! |
Really? Doubling down, huh? First one wasn't enough? I thought you would have learned after the last time: vcflib/vcflib#206 |
No, not really, I don't learn anything from people like you! |
Anyway, this is what was preventing you from solving the issue during all this time? Some little mean "personal" revenge ?? |
Not at all. In fact, you'll see that I responded to your emails back in August when you first emailed me about this issue. We got part of the way, but I did not have the time to fix it properly (the current development team is just me, a postdoc with lots of various responsibilities). LOFTEE is a part of my research but not the only component, and I mentioned I'd work on this. I did, at the time propose the same solution:
|
Two communictaions from @deniseduma above have been reported as abuse under github terms of service, section C item 3 (https://help.github.com/articles/github-terms-of-service/):
While using GitHub, you agree that you will not under any circumstances:
|
@deniseduma you must be the worst user of this community. You are not a customer who has the right to complain, definitely not insult maintainers. This is a community of programmers developing open source software and sharing it in the hope to help someone else. It's not a service. It's free. You don't have to use it. Fixing issues like this is not part of the job description and now you are demanding the maintainers to put other work on hold or sacrifice free/family time. Go make your own perfect software please. |
https://help.github.com/articles/blocking-a-user-from-your-personal-account/ |
@bryketos I'm not sure what was violent or abusive in what I said but if you personally felt violent-ed or abused please try to get over it and you'll feel better! I promise! |
To everybody who has mentioned me in their kind comments: I know I'm a mean girl who gives hard times to nice cool developers! My apologies! |
you are a living legend. never change.
…--t
On Fri, Feb 2, 2018 at 11:02 PM, deniseduma ***@***.***> wrote:
To everybody who has mentioned me in their kind comments: I know I'm a
mean girl who gives hard times to nice cool developers! My apologies!
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#23 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AAARIh9UFddFVRKc3-OGE4qe0fPTEtWWks5tQ9pPgaJpZM4QBlAz>
.
|
Is this issue now resolved? I'm getting errors like: (This is running f6789b9, the current master.) |
I've also tried checking out the suggested above commit ( Both these commits seem to be missing a number of files that are needed that were added in subsequent commits ( I've stepped through the commits up to HEAD, but haven't managed to get it to run successfully. It'd be great to get this tool working! Does anyone have any suggestions to try? |
AFAIK https://github.com/konradjk/loftee/tree/v0.3-beta should only require |
Thanks for the quick response! I've just tried a fresh checkout of
|
Aha, I see you have a |
Very good point, thank you for spotting that! I copied the latest LoF.pm to the plugins directory when I first checked out the repository and forgot it was from I'm actually ultimately interested in using the Broad's Hail to run VEP. From the README, it looks like the |
Yes! Let's move that back to the Hail forum though. |
Alright the files and README have now been updated. For GRCh37, https://personal.broadinstitute.org/konradk/loftee_data/GRCh37/phylocsf_gerp.sql.gz will have both the PhyloCSF and GERP files needed to run v1.0 of LOFTEE. GRCh38 coming soon! |
I have ran into the similar issue. A year passed and any updates ? |
I get this error too. Is this issue now resolved? I'm getting errors like: |
Hi,
I'm unable to use LoF to annotate my variants as it seems it is missing a feature/SQL table.
Specifically, when I run VEP
./vep --plugin LoF,loftee_path:/path/to/loftee,
human_ancestor_fa:/path/to/loftee/human_ancestor.fa.gz,
conservation_file:/path/to/loftee/phylocsf.sql,
fast_length_calculation:0,get_splice_features:1,check_complete_cds:1
I get the following errors:
DBD::SQLite::db prepare failed: no such table: gerp_bases at /path/to/loftee/gerp_dist.pl line 82, line 5015.
Plugin 'LoF' went wrong: Can't call method "execute" on an undefined value at /path/to/loftee/gerp_dist.pl line 83, line 5015.
basically saying that gerp_bases is missing.
Could you please add that table to LoF?
Thank you,
Denise
The text was updated successfully, but these errors were encountered: