You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Annotations to anatomy term P6.p are problematic because when computed on, one cannot arrive at it's vulval or non-vulval nature; Annotations need to be changed to either 'P6.p hermaphrodite' or 'P6.p male', depending on the context in the paper.
Affects gene tissue-expression, gene regulation and phenotype data.
The text was updated successfully, but these errors were encountered:
Looking at the postgres app tables (allele phenotype), there are 21 annotations that with P6.p as an anatomy annotation; 9/21 are concurrently annotated with a larval life stage. The default for all 21 annotations is that they are for hermaphrodites. 2/21 of the annotations are to hermaphrodite specific terms (e.g., vulval cell fate specification and VPC cell division variant).
In addition to using male specific anatomy terms, phenotype sex-based anatomy discrimination is and can be supported by using the
*lifestage ontology (e.g., adult male (WBls:0000056), L4 larval male Ce (WBls:0000073))
*male specific phenotype terms - male behavior variant (WBPhenotype:0000888) and male physiology variant (WBPhenotype:0000928), male tail development variant (WBPhenotype:0001297)
If male specific cell lineages were included in the anatomy ontology, I should think that would be the cleanest way forward.
Annotations to anatomy term P6.p are problematic because when computed on, one cannot arrive at it's vulval or non-vulval nature; Annotations need to be changed to either 'P6.p hermaphrodite' or 'P6.p male', depending on the context in the paper.
Affects gene tissue-expression, gene regulation and phenotype data.
The text was updated successfully, but these errors were encountered: