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

exo5-D176A D176A invalid_error peptide sequence missing #1188

Open
ValWood opened this issue Jul 2, 2024 · 5 comments
Open

exo5-D176A D176A invalid_error peptide sequence missing #1188

ValWood opened this issue Jul 2, 2024 · 5 comments
Assignees

Comments

@ValWood
Copy link
Member

ValWood commented Jul 2, 2024

@manulera

do you know what this means?

SPBC685.02 SPBC685.02:allele-2 exo5-D176A D176A invalid_error peptide sequence missing
SPBC685.02 SPBC685.02:allele-3 exo5-D207A D207A invalid_error peptide sequence missing

These are correct ly describe as far as I can see. This gene has multiple transcripts, but this is the primary transcript?
I can't see what it might be?

@kimrutherford
Copy link
Member

Hi Val. Where are those messages coming from?

This gene has multiple transcripts, but this is the primary transcript?

How are specifying which transcript is the primary transcript?

@manulera
Copy link

manulera commented Jul 24, 2024

Hi @kimrutherford sorry I did not see this at the time. The problem here is that multi-transcript genes were handled assuming that the systematic_id qualifier would contain the "transcript id" ( gene systematic id + .1 or .2), and therefore there would be no feature in the genome assigned to the gene systematic id.

That's the case for the annotation of SPAC22A12.08c in chromosome 1, where there is two identical UTRs, one for each transcript:

FT   5'UTR           complement(1172127..1172209)
FT                   /systematic_id="SPAC22A12.08c.1"
FT                   /db_xref="PMID:18641648"
FT                   /db_xref="PMID:20118936"
FT                   /db_xref="PMID:30566651"
FT                   /db_xref="PMID:30566651"
FT                   /feature_source="evidence=ECO:0000309; source=SO:0001238;
FT                   condition=FYECO:0000126; during=GO:0072690; score=63.071;
FT                   db_xref=PMID:30566651"
FT   5'UTR           complement(1172127..1172209)
FT                   /systematic_id="SPAC22A12.08c.2"
FT                   /db_xref="PMID:18641648"
FT                   /db_xref="PMID:20118936"
FT                   /db_xref="PMID:30566651"
FT                   /db_xref="PMID:30566651"
FT                   /feature_source="evidence=ECO:0000309; source=SO:0001238;
FT                   condition=FYECO:0000126; during=GO:0072690; score=63.071;
FT                   db_xref=PMID:30566651"

In SPBC685.02, there is a single one with the "main" systematic id, then the specific part of each transcript:

FT   5'UTR           2772853..2772883
FT                   /systematic_id="SPBC685.02"
FT                   /db_xref="PMID:30566651"
FT                   /feature_source="evidence=ECO:0000309; source=SO:0001238;
FT                   condition=FYECO:0000126; during=GO:0072690;
FT                   score=1.028360; db_xref=PMID:30566651"
FT   CDS             join(2772884..2773046,2773102..2773166,2773317..2774093,2774223..2774447)
FT                   /colour=2
FT                   /primary_name="exo5"
FT                   /product="nuclear single stranded DNA specific 5'-3'
FT                   exodeoxyribonuclease Exo5.1"
FT                   /db_xref="SPD:25/25C04"
FT                   /db_xref="PMID:31563844"
FT                   /systematic_id="SPBC685.02.1"

This is handled at process_systematic_id in genome_functions by testing if systematic_id in genome. The solutions would be:

  • Do all genome annotation like in SPAC22A12.08c
  • Handle this alternative case testing whether peptide is in the dictionary of that systematic id.

@kimrutherford
Copy link
Member

Thanks very much for looking into this!

Do all genome annotation like in SPAC22A12.08c

I think that's the best plan.

Cheers.

@manulera
Copy link

manulera commented Jul 24, 2024

@kimrutherford
Copy link
Member

I've just changed the ID of the SPBC685.02 5'UTR to "SPBC685.02.1". I'll check on Friday to make sure that fixed things.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants