From #3935
At the moment we don't have specific class and syntax for curating frameshift alleles.
Most are curated as Type: Other, but some ended up as disruptions and can have a fairly long description, such as
klp5-del(short deletion with a frameshift at codon 772, resulting in a different 772–814 C-terminus)[Not assayed] - klp5
in the session: https://curation.pombase.org/pombe/curs/93e1b181a0463890/genotype_manage/ro
We should revise the existing frameshift alleles and define a specific syntax for their description (perhaps for a new Type: frameshift)
We have often used fs@ to indicate a frameshift at a position, which could be a good way to go.
This could be quite tricky as it might require to model the fs in Artemis to see how many amino acids are added from the alternative frame.
From #3935
At the moment we don't have specific class and syntax for curating frameshift alleles.
Most are curated as Type: Other, but some ended up as disruptions and can have a fairly long description, such as
klp5-del(short deletion with a frameshift at codon 772, resulting in a different 772–814 C-terminus)[Not assayed] - klp5in the session: https://curation.pombase.org/pombe/curs/93e1b181a0463890/genotype_manage/ro
We should revise the existing frameshift alleles and define a specific syntax for their description (perhaps for a new Type: frameshift)
We have often used fs@ to indicate a frameshift at a position, which could be a good way to go.
This could be quite tricky as it might require to model the fs in Artemis to see how many amino acids are added from the alternative frame.