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

APARENT - number of predictions seems off #342

Open
robertzeibich opened this issue Jun 24, 2022 · 3 comments
Open

APARENT - number of predictions seems off #342

robertzeibich opened this issue Jun 24, 2022 · 3 comments

Comments

@robertzeibich
Copy link

Hi, I am currently running Kipoi APARENT.

The provided example VCF file contains 15,077 variants, but the output only has 416 predictions for delta_logit_distal_prop and delta_logit_proximal_prop. I was expecting 15,077 predictions. Do you know why I only get 15,077 predictions?
Kipoi APARENT
Kipoi APARENT

@Hoeze
Copy link
Member

Hoeze commented Jun 24, 2022

Hi @robertzeibich, we currently only evaluate variants that are close to a polyA-site:

def get_roi_from_transcript(transcript_start: int, transcript_end: int, is_on_negative_strand: bool) -> (int, int):
"""
Get region-of-interest for APARENT in relation to the 3'UTR of a transcript
:param transcript_start: 0-based start position of the transcript
:param transcript_end: 1-based end position of the transcript
:param is_on_negative_strand: is the gene on the negative strand?
:return: Tuple of (start, end) position for the region of interest
"""
# CSE should be roughly around position 70 of the 205bp sequence.
# Since CSE is likely 30bp upstream of the cut site, we shift the cut site
# by 100bp upstream and 105bp downstream
if is_on_negative_strand:
end = transcript_start + 100
# convert 0-based to 1-based
end += 1
start = end - 205
else:
start = transcript_end - 100
# convert 1-based to 0-based
start -= 1
end = start + 205
return start, end

Some notes:

What would you like to use APARENT for?

@robertzeibich
Copy link
Author

Thank you for getting back to me that quickly. I used the keep_metadata parameter and then concatenated the output with a pandas dataframe.
poly(A) scores
Can you inform me once the bug was fixed?

I want to integrate the poly(A) scores in my whole genome sequence analysis. Perhaps compare the scores against healthy controls (1000 Genomes project) and see if patients with epilepsy and individuals from the 1000 Genomes project cluster somehow. If you have another idea what I could do with the scores, I am all ears. The data I am currently analyzing is whole genome sequenced data from people with epilepsy.

@Hoeze
Copy link
Member

Hoeze commented Jul 4, 2022

Hi @robertzeibich, I did merge now the PR to fix the reverse-complement issue.
Still, I'm not 100% sure if the implementation is perfectly fine, so please look at the predictions with a bit of caution for now :)

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