From 53db1da5ea2184287d5eefd8198d27de52bb31a9 Mon Sep 17 00:00:00 2001
From: jgart
Date: Thu, 3 Mar 2022 17:06:33 -0500
Subject: issue: databases getting out of wack a bit

---
 issues/gemma/databases-getting-out-of-wack.gmi | 25 +++++++++++++++++++++++++
 1 file changed, 25 insertions(+)
 create mode 100644 issues/gemma/databases-getting-out-of-wack.gmi

(limited to 'issues/gemma')

diff --git a/issues/gemma/databases-getting-out-of-wack.gmi b/issues/gemma/databases-getting-out-of-wack.gmi
new file mode 100644
index 0000000..7c3f7ca
--- /dev/null
+++ b/issues/gemma/databases-getting-out-of-wack.gmi
@@ -0,0 +1,25 @@
+# Databases Getting Out of Wack
+
+## Let's use Gemma instead of Reaper
+
+* assigned: Bonface, Zach, jgart
+* priority: high
+* bug
+
+Zachary:
+> Yeah, I think you'd want to get the mean (which is simple) + run qtlreaper
+> (which I think would need to be run in the background) after a change.
+
+Pjotr:
+> Current qtlreaper runs in one of Arthur's scripts globally.
+
+Rob:
+> Yes, that and more. These values are displayed in search results and used
+> to sort by expression mean and peak LRS (using pathetically old code and
+> genotypes). Now if GEMMA were wicked fast we could recompute the 60 million
+> BXD vector results and store that as a big juicy TRANSFORMATIVE blob of
+> data. A big paper in doing just that. Reaper is just wrong at this
+> point. We have LMM: We should use it.
+
+
+
-- 
cgit v1.2.3