-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
18 changed files
with
393 additions
and
35 deletions.
There are no files selected for viewing
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,175 @@ | ||
--- | ||
hide: | ||
- toc | ||
--- | ||
|
||
## Allele description rules | ||
|
||
!!! warning "These are rules for allele descriptions, not names!" | ||
|
||
| Allele type | Example | | ||
| -------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------- | | ||
| amino acid insertion | A858AMKGYP (insertion of MKGYP after A858, note A before and after number) | | ||
| amino acid substitution(s) | K132A or F256A,F310A | | ||
| amino acid insertion and substitution | A858AMKGYP,F124D | | ||
| amino acid insertion and deletion | A858AMKGYP,100-200,P500* | | ||
| partial deletion and amino acid change | 100-200,F124D,P500* | | ||
| partial deletion, amino acid | Specify deleted residues - eg. 100-200 OR 10-20,40-50. Use P500* for nonsense mutation | | ||
| nucleotide insertion | C132CAATTT (insertion of AATTT after C132, note C before and after number) | | ||
| nucleotide substitution(s) | A25G, OR A(-25)G (for residues upstream of ATG -protein coding- or transcription start -RNA genes-) | | ||
| partial deletion, nucleotide | Specify deleted residues - eg. 100-200 OR (-20)-(-30) (for residues upstream of ATG -protein coding- or transcription start -RNA genes-) | | ||
| partial deletion and nucleotide change | 100-200,A124T,C128G (for residues upstream of ATG -protein coding- or transcription start -RNA genes- use negative numbers in parenthesis) | | ||
| nucleotide insertion and substitution | T858TAAGA,T(-124)A (for residues upstream of ATG -protein coding- or transcription start -RNA genes- use negative numbers in parenthesis) | | ||
|
||
## Allele naming rules | ||
|
||
!!! warning "These are rules for allele names, not descriptions!" | ||
|
||
<table> | ||
<tbody> | ||
<tr> | ||
<td colspan="2"> | ||
<p><strong>Variant type</strong></p> | ||
</td> | ||
<td> | ||
<p><strong>Example</strong></p> | ||
</td> | ||
</tr> | ||
<tr> | ||
<td colspan="2"> | ||
<p>Wild type</p> | ||
</td> | ||
<td> | ||
<p><em>ase1+</em></p> | ||
</td> | ||
</tr> | ||
<tr> | ||
<td colspan="2"> | ||
<p>Knockout / deletion</p> | ||
</td> | ||
<td> | ||
<p><em>ase1Δ</em></p> | ||
</td> | ||
</tr> | ||
<tr> | ||
<td rowspan="2"> | ||
<p>Partial deletion</p> | ||
</td> | ||
<td> | ||
<p>Indicate what’s left</p> | ||
</td> | ||
<td> | ||
<p><em>ase1(1-35)</em></p> | ||
<p><em>ase1(1-35, 40-700)</em></p> | ||
</td> | ||
</tr> | ||
<tr> | ||
<td> | ||
<p>Indicate what’s missing</p> | ||
</td> | ||
<td> | ||
<p><em>ase1Δ(114-120)</em></p> | ||
<p><em>ase1Δ(114-120,150-200)</em></p> | ||
</td> | ||
</tr> | ||
<tr> | ||
<td colspan="2"> | ||
<p>Residue insertion</p> | ||
</td> | ||
<td> | ||
<p><em>ase1-P114PVPAL</em></p> | ||
</td> | ||
</tr> | ||
<tr> | ||
<td rowspan="2"> | ||
<p>Substitution or deletion-insertion</p> | ||
</td> | ||
<td> | ||
<p>Single residues</p> | ||
</td> | ||
<td> | ||
<p><em>ase1-P114A,Q117A</em></p> | ||
<p><em>ase1-P114*</em></p> | ||
</td> | ||
</tr> | ||
<tr> | ||
<td> | ||
<p>Consecutive residues</p> | ||
</td> | ||
<td> | ||
<p><em>ase1-PLI114AAA</em></p> | ||
<p><em>ase1-PLI114LAVKK</em></p> | ||
</td> | ||
</tr> | ||
<tr> | ||
<td colspan="2"> | ||
<p>Combinations of the above</p> | ||
</td> | ||
<td> | ||
<p><em>ase1Δ(10-20)-P114A,Q117A</em></p> | ||
</td> | ||
</tr> | ||
<tr> | ||
<td colspan="2"> | ||
<p>Forward genetics, variant unknown</p> | ||
</td> | ||
<td> | ||
<p><em>ase1-35 </em>(must be unique)</p> | ||
</td> | ||
</tr> | ||
<tr> | ||
<td rowspan="6"> | ||
<p>CTD</p> | ||
</td> | ||
<td> | ||
<p>All repeats mutated</p> | ||
</td> | ||
<td> | ||
<p><em>rpb1-CTD-Y1F</em></p> | ||
</td> | ||
</tr> | ||
<tr> | ||
<td> | ||
<p>Some repeats mutated</p> | ||
</td> | ||
<td> | ||
<p><em>rpb1-CTD-Y1F(r1-r12)</em></p> | ||
</td> | ||
</tr> | ||
<tr> | ||
<td> | ||
<p>Some repeats deleted</p> | ||
</td> | ||
<td> | ||
<p><em>rpb1-CTD-Δ(r11-r29)</em></p> | ||
</td> | ||
</tr> | ||
<tr> | ||
<td> | ||
<p>Motifs mutated every 2 repeats, from repeat 1 to 29.</p> | ||
</td> | ||
<td> | ||
<p><em>rpb1-CTD-Y1F(r1-r29-2)</em></p> | ||
</td> | ||
</tr> | ||
<tr> | ||
<td> | ||
<p>Combinations of the above</p> | ||
</td> | ||
<td> | ||
<p><em>rpb1-CTD-S5A(r1-r12)Δ(r13-r29)</em></p> | ||
</td> | ||
</tr> | ||
<tr> | ||
<td> | ||
<p>CTD and non-CTD mutations</p> | ||
</td> | ||
<td> | ||
<p><em>rpb1-N494D-CTD-Δ(r11-r29)</em></p> | ||
</td> | ||
</tr> | ||
</tbody> | ||
</table> | ||
<p> </p> | ||
|
||
<!-- TODO add paper reference --> |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,28 @@ | ||
|
||
## Phenotype annotations | ||
|
||
### How do I indicate that a mutation or deletion is viable? | ||
|
||
Annotate a genotype including that allele to `viable vegetative cell population`. Viability can depend on conditions and other alleles present on the genotype. See [phenotypes](./phenotypes.md) | ||
|
||
### How do I indicate that a mutation or deletion is lethal? | ||
|
||
Annotate a genotype including that allele to `inviable vegetative cell population`. Lethality can depend on conditions and other alleles present on the genotype. See [phenotypes](./phenotypes.md) | ||
|
||
### How do I indicate that an allele is thermosensitive? | ||
|
||
Annotate a genotype including that allele to `inviable vegetative cell population`, including `high temperature` or `low temperature` as a condition. See [phenotypes](./phenotypes.md) | ||
|
||
## Genotype management | ||
|
||
### What's the difference between "Wild type product level" and "Not assayed"? | ||
|
||
Historically, `Wild type product level` and `Not assayed` have been used interchangeably when a non-wild type allele is expressed from the endogenous locus. We recommend `Not assayed` if you have not measured expression. See [Genotype management](./genotype_management.md) | ||
|
||
### What to do when control strains over-express the wild-type allele, or express it from a plasmid? | ||
|
||
PomBase does not capture the difference between strains expressing an allele from a plasmid or the native locus in phenotype annotations. Similarly, we do not have a way to capture the fact that the control of an experiments is over-expressing the wild-type allele. Therefore, if both the wild-type (control) and mutant allele are over-expressed / knocked-down, ???. See [Genotype management](./genotype_management.md) | ||
|
||
### What if the wild-type copy is still present in a mutant strain? | ||
|
||
Multi-loci phenotype can be used to indicate that the wild-type allele is still present in a strain expressing an allele of that gene. For example, a strain that bears both the wild type _cdc25_ and the mutant allele _cdc25-22_. For this purpose, you can create a wild-type allele with expression level `Wild type product level`. See [Genotype management](./genotype_management.md) |
This file was deleted.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,58 @@ | ||
--- | ||
hide: | ||
- toc | ||
--- | ||
|
||
??? info "Did you forget to add genes to the session or you want to remove some?" | ||
In the main menu, click on `Edit gene list` on the right side of the interface. | ||
|
||
* To remove genes, tick the boxes on the right, then click `Remove selected`. You can only delete genes that have not been used for annotations. | ||
* To add genes, click `Add more genes from ...`. | ||
* You can add multiple genes separated by any spacer (space, commas, line breaks). | ||
* You can refer to genes by their systematic id (SPAC3G9.12), primary name (peg1) or a synonym (cls1). | ||
* If a gene name is also the synonym of another gene (e.g. psu1), you will be asked to provide a primary name for that gene. | ||
|
||
## Video summary | ||
|
||
<div class="video-sizer"> | ||
<div class="video-wrapper"> | ||
<iframe src="https://www.youtube.com/embed/KY7ev8IEG00" frameborder="0" allowfullscreen></iframe> | ||
</div> | ||
</div> | ||
|
||
## Creating genotypes | ||
|
||
On the left side of the session page, click on `Genotype management`. This will take you to a screen where you can see all the genes you have added to the session. | ||
|
||
### Creating single-locus genotypes | ||
|
||
* To create a genotype with a deletion allele, click on `Deletion`. | ||
* To create a genotype where the expression level of the wild-type allele is altered, click on `Other Genotype` and select `wild type` as `allele type`. Then select the expression level. | ||
* For others, click on `Other Genotype`, then: | ||
* First, check if the allele you want to use already exist by writing its name on the `Allele name` text box. If you find it, click on it, and the allele details will be imported from PomBase. | ||
* Otherwise, create a new allele: | ||
* Give it the name that it has in the publication. Ideally, the name should follow [our guidelines](./describing_alleles.md#allele-naming-rules). | ||
* Select the type of allele, and add an allele description following the displayed example. See [all description examples](./describing_alleles.md#allele-description-rules). | ||
* Finally, select the expression level and click `OK`. | ||
|
||
### Creating diploid loci | ||
|
||
* If you want to make a diploid genotype with two different alleles, they must exist as separate single-locus genotypes. | ||
* Start from a haploid single-locus genotype that contains one of the desired alleles, and tick the box on its left. | ||
<div markdown style="max-width: 400px"> | ||
![](assets/diploid_genotype.png) | ||
</div> | ||
* Then, click on `Create diploid locus`, there you can choose to create either: | ||
* An homozygous locus with the starting allele. | ||
* An heterozygous locus with the starting allele and the wild-type. | ||
* An heterozygous locus with the starting allele and another allele from the session (choose from the dropdown). | ||
* Then click `OK`. | ||
|
||
### Creating multi-locus genotypes | ||
|
||
* Select all single-locus genotypes that you want to combine in a multi-locus genotype, by ticking the boxes on their left. | ||
<div markdown style="max-width: 400px"> | ||
![](assets/diploid_genotype.png) | ||
</div> | ||
* Click the button `Combine selected genotypes`. | ||
* You can also create diploid multi-locus genotypes by combining diploid single-locus genotypes. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,19 @@ | ||
// A simple script that displays a random did you know message at the footer | ||
|
||
const allMessages = [ | ||
'Canto has ways to save time during curation, visit our <a href="/productivity">productivity page</a>.', | ||
'You can submit high-throughput datasets of genetic and physical interactions to <a href="https://wiki.thebiogrid.org/doku.php/contribute">BioGrid</a>, and they will appear in PomBase.', | ||
'You can submit high-throughput annotations of GO, phenotype, modification, or gene expression data, visit our <a href="https://www.pombase.org/submit-data">data submission documentation</a>.', | ||
'You can submit sequence-linked data, and they will appear in PomBase genome browser. Visit our <a href="https://www.pombase.org/submit-data">data submission documentation</a>.' | ||
] | ||
|
||
const randomMessage = allMessages[Math.floor(Math.random() * allMessages.length)] | ||
|
||
// Set the initial message | ||
|
||
const footer = document.getElementsByClassName('md-footer-meta__inner')[0] | ||
|
||
const message = document.createElement('p') | ||
message.innerHTML = '<strong>Did you know?</strong> 🤔 ' + randomMessage | ||
|
||
footer.appendChild(message) |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.