just_dna_format.model_organisms¶
just_dna_format.model_organisms ¶
The model-organism evidence table, model_organisms.csv (0.8, RM335).
One row is one model-organism lifespan finding about a human gene: which orthologue was altered, in which species, by which intervention, under which sex and diet, what happened to lifespan, and whether the direction agrees with the human allele's. It is the table for evidence that has nowhere else to go:
- a
studies.csvrow naming the rsID claims a mouse study was about the human variant; - a
studies.csvrow naming no variant attaches to the whole module, sinceStudyRowhas nogene; - a meta-table member names a variant, a genotype row, a diplotype or a
(gene, allele)pair, never a bare gene, and a mouse genotype such asIgf1r+/-is not a human allele.
Annotation only. Nothing here reaches an effect column, a weight or a tier: a consumer reads the rows beside the module's findings and never scores a genome from them. That is why the table is keyed on the gene itself and carries no variant, genotype or allele column, and why it is not a lead table — a module whose only rows are model-organism evidence has nothing a genome is matched against.
ModelOrganismRow ¶
Bases: CitationPair, AuthoredModel
One row of model_organisms.csv: a model-organism lifespan finding about a human gene.
The key is every column except the two that state the finding (lifespan_effect, concordance): one
gene, orthologue, species, intervention, sex, diet and citation make one experiment, and the same
experiment stated twice with two effects is a contradiction the compiler refuses like every other keyed
table's duplicate. A male and a female cohort, or a chow and a high-fat one, are two rows.
pmid/doi are optional and draw no warning when both are empty (PT2 §3 item 23): GenAge-style
entries carry no paper, and the table never reaches a score. When a row does cite, the pair's rules
apply as on every citing table (CitationPair, RM336).