summary refs log tree commit diff
diff options
context:
space:
mode:
authorPjotr Prins2025-12-19 07:00:23 +0100
committerPjotr Prins2025-12-19 07:00:23 +0100
commitb73b684d000236dfaa3924aee0c87aa0e7efecb7 (patch)
treed972ebcadbaf92e221a4c3211446c4c59ca3fa65
parent2264a6b50a67b987da098cecda292fcb22651fb7 (diff)
downloadgn-ai-b73b684d000236dfaa3924aee0c87aa0e7efecb7.tar.gz
On genotyping
-rw-r--r--topics/genetics/standards/gemma-genotype-format.gmi3
-rw-r--r--topics/systems/mariadb/precompute-publishdata.gmi6
2 files changed, 9 insertions, 0 deletions
diff --git a/topics/genetics/standards/gemma-genotype-format.gmi b/topics/genetics/standards/gemma-genotype-format.gmi
index daf748b6..6ca5998f 100644
--- a/topics/genetics/standards/gemma-genotype-format.gmi
+++ b/topics/genetics/standards/gemma-genotype-format.gmi
@@ -92,5 +92,8 @@ timestamp =>
 ```
 
 The 'geno' database will therefore always the *first* version. These records make it possible to roll forward on changes and present an updated genotype matrix. Used genotypes are retained. This, naturally, can be handled in a cache. So any rewritten genotype files will be available in cache for a period of time.
+In the future a tool, such as GEMMA, could support dynamic application of these edits. That way we only have to cache the latest version.
 
 This way users may be able to select changes (i.e. pick and choose), use all (latest) or use original (init).
+
+For the editing we should provide an API.
diff --git a/topics/systems/mariadb/precompute-publishdata.gmi b/topics/systems/mariadb/precompute-publishdata.gmi
index a434ff60..74c278f8 100644
--- a/topics/systems/mariadb/precompute-publishdata.gmi
+++ b/topics/systems/mariadb/precompute-publishdata.gmi
@@ -3362,3 +3362,9 @@ We can also look for details like skewness by adding
 We continue testing new genotypes in this document:
 
 => ../genetics/test-pangenome-derived-genotypes
+
+# Introducing epochs
+
+see
+
+=> topics/data/epochs