From cb85e02461198d21c62cc9b3027e8988aca0786f Mon Sep 17 00:00:00 2001
From: Frederick Muriuki Muriithi
Date: Fri, 22 Apr 2022 13:50:31 +0300
Subject: New Issue: pcorrs - add Target Column

---
 issues/add-target-column-in-pcorrs-table.gmi | 24 ++++++++++++++++++++++++
 1 file changed, 24 insertions(+)
 create mode 100644 issues/add-target-column-in-pcorrs-table.gmi

diff --git a/issues/add-target-column-in-pcorrs-table.gmi b/issues/add-target-column-in-pcorrs-table.gmi
new file mode 100644
index 0000000..3de155a
--- /dev/null
+++ b/issues/add-target-column-in-pcorrs-table.gmi
@@ -0,0 +1,24 @@
+# Add "Target" (Y) Column in Partial Correlations Selection Table
+
+## Tags
+
+* assigned: fredm
+* priority: medium
+* type: migration, feature-request
+* status: pending
+* keywords: partial correlations, datatables
+
+## Description
+
+Currently, the partial correlations in GN2 are run against a selected dataset, and not against a selection of specific traits.
+
+The problem with this arises in the fact that the region of interest in any experiment might fall outside of the cutoff selection (top 100, 200, 500, 1000, 10000, etc) and there is no real way of knowing that beforehand.
+
+There is a need, therefore, to run partial correlations against a target that is a list of user-selected traits.
+
+GN1 allows this with the "Target" (Y) Column.
+
+### Requirements
+
+* Add a new "Target (Y)" column to the table
+* Have all traits be targets by default, rather than ignored
-- 
cgit v1.2.3