In addition to the user/client documentation, we need documentation for would be contributors to the project. This documentation can also reside in the
This document is concerned with the system design and the documentation of the system that is relevant te the implementation of the system. It explores some areas of GeneNetwork that might be unclear, or require some documentation. It is a discussion document to help with clarifying some concepts and critiquing the documentation.
The goal of this document is to encourage and track the documentation that assist with the development of the system.
Like GNU Guix has the concepts of Packages, Monads, G-Expressions and the like as some of the unifying principles that help with understanding, contributing to and extending the project, GeneNetwork has some, albeit undocumented, principles unifying the system. Understanding these principles is crucial for the would-be contributor.
As far as I (fredm) can tell [as of 2022-03-11], the unifying principles for the system are:
Datasets 'contain' or organise traits. The do not have much in terms of direct operations on them - most operations against a dataset operate agaist the traits within that dataset.
They can be envisioned as a bag of traits.
Common dataset traits are:
A trait is a abstract concept - with the somewhat concrete forms being
From the GeneNetwork2 repository, specifically the `wqflask.base.trait` module:
... a trait in webqtl, can be either Microarray, Published phenotype, genotype, or user input trait
From the `wqflask.base.trait.GeneralTrait` class, the common properties for all the trait types above are:
The *data* property of a trait has items with at least the following important properties:
the trait properties above are the ones I have run into that seem to be used in computations mostly.
There are other properties like:
that are used less often.
Some extra properties for 'ProbeSet' traits:
Some extra properties for 'Publish' traits:
When doing computations, it is unnecessary to load the display-only properties of a trait, deferring this to when/if we need to display such to the user/client.
How do these factor into the system?
According to my current understanding, these are different views into the data, and there might not be a clear distinction between them.
What is the mapping between these and the traits above?
Work has began on writing a technical specification document detailing the current state of the system, and the possible future implementation goals of the system. See branch `technical-specification` in the GeneNetwork3 repository.
Stored in the *GeneChip* table in the database.
These are in the *InbredSet* table in the database.
Groups are linked to the Species.
Stored in the *ProbeFreeze* table in the database.
Linked to platforms (ChipId), groups (InbredSetId) and tissues (TissueId).
A study can have multiple experiments, each of which provides a dataset.
Stored in the *ProbeSetFreeze* table in the database.
Linked to studies (ProbeFreezeId) and averaging methods (AvgId).
From my understanding so far, a dataset is the results from a single experiment within a study.
Stored in *ProbeSet* table in the database