summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorzsloan2022-07-21 05:19:22 -0500
committerGitHub2022-07-21 05:19:22 -0500
commit470c0ee1f923af28e00aa69c30034fdb619a713e (patch)
treedc5171e4e532215b879a671a0f0a7bc368e83822
parentf3e57b92e57362653de411f41198641d60409fa4 (diff)
downloadgn-gemtext-470c0ee1f923af28e00aa69c30034fdb619a713e.tar.gz
Create enable-intergroup-analysis.gmi
-rw-r--r--issues/enable-intergroup-analysis.gmi16
1 files changed, 16 insertions, 0 deletions
diff --git a/issues/enable-intergroup-analysis.gmi b/issues/enable-intergroup-analysis.gmi
new file mode 100644
index 0000000..a4bbfdb
--- /dev/null
+++ b/issues/enable-intergroup-analysis.gmi
@@ -0,0 +1,16 @@
+# Allow analyses to be done between traits from "individuals" groups and their corresponding "main" group
+
+# Tags
+
+* assigned: zsloan
+* priority: medium
+* type: feature-request
+* status: open, in progress
+* keywords: data, meta-data
+
+# Description
+
+Currently you can't do an analysis beween traits from the "main" BXD group and traits from any of the BXD individuals groups, but it should technically be possible to do so as long as there's a mapping of individuals with their respective strains.
+
+My idea to enable this is to have some code (probably as a decorator function) that, prior to an analysis, checks if there are traits from both a "main" and "individuals" group (for example a BXDPublish phenotype and a phenotype from BXD-LongevityPublish). These mappings could be stored in a simple JSON file.
+The "main" group trait(s) could then have their sample data converted to the sample list of the "individuals" group, provided the mappings of individuals to strains exists in the CaseAttributes tables. A Temp trait could be created for the purposes of the analysis (though this presents potential issues with trait page links).