summaryrefslogtreecommitdiff
path: root/topics
diff options
context:
space:
mode:
authorMuriithi Frederick Muriuki2021-08-31 07:24:51 +0300
committerMuriithi Frederick Muriuki2021-08-31 07:24:51 +0300
commit4a9f3008f0428fb7daa5e90f0a573686d182d7b2 (patch)
tree8ff6b90dc106ae88c3f17b4ff852682878e92a45 /topics
parent89d448585589d9912ac974b6e4645b47e365bf1c (diff)
downloadgn-gemtext-4a9f3008f0428fb7daa5e90f0a573686d182d7b2.tar.gz
Update with progress
* Update issue with progress on genotype files
Diffstat (limited to 'topics')
-rw-r--r--topics/gn1-migration-to-gn2/clustering.gmi13
1 files changed, 13 insertions, 0 deletions
diff --git a/topics/gn1-migration-to-gn2/clustering.gmi b/topics/gn1-migration-to-gn2/clustering.gmi
index 363b4bc..74cd3de 100644
--- a/topics/gn1-migration-to-gn2/clustering.gmi
+++ b/topics/gn1-migration-to-gn2/clustering.gmi
@@ -293,3 +293,16 @@ The traits files should only contain the strains that can be found in the corres
I should also look into reworking ~gn3.computations.export_trait_data~ function, so that each value is linked to the strain that it corresponds to, so that we do not rely on numerical order. This should help reduce chances of bugs where the strains and the values are not in the same order.
I also need to figure out how the strains in the genotype are passed around in GN1. I have mostly ignored that since in GN1, those details were passed around in a class object.
+
+
+## 2021-08-31
+
+### 06:59
+
+Succeeded in
+
+* figuring out how to link the genotype files to traits
+* loading samples/strains from the genotype files
+* testing the /rust-qtlreaper/ interface code
+
+Now to integrate the results into the main code, and start looking into parsing the results of running qtlreaper into data we can use to generate heatmaps.