From 3eec32073912a32720554331b03dbb51c1b86685 Mon Sep 17 00:00:00 2001
From: "Qian, Hai" <hqian@gopivotal.com>
Date: Tue, 10 Sep 2013 19:17:10 -0700
Subject: [PATCH] More clarification on coef_all and coef_nonzero

---
 src/ports/postgres/modules/elastic_net/elastic_net.sql_in | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/ports/postgres/modules/elastic_net/elastic_net.sql_in b/src/ports/postgres/modules/elastic_net/elastic_net.sql_in
index 06d7a1dda..5bb10b6a5 100644
--- a/src/ports/postgres/modules/elastic_net/elastic_net.sql_in
+++ b/src/ports/postgres/modules/elastic_net/elastic_net.sql_in
@@ -293,7 +293,7 @@ elastic_net_predict(
 <DT>regress_family</DT>
 <DD>TEXT. The type of regression, either 'gaussian' ('linear') or 'binomal' ('logistic').</DD>
 <DT>coefficients</DT>
-<DD>DOUBLE PRECISION[]. Fitting coefficients.</DD>
+<DD>DOUBLE PRECISION[]. Fitting coefficients. If you use all the features in the following <em>ind_var</em>, then this should be <em>coef_all</em> in the fitting result table. If you use the selected features (features with non-zero coefficients) in <em>ind_var</em>, then this should be <em>coef_nonzero</em> </DD>
 <DT>intercept</DT>
 <DD>The intercept for the model.</DD>
 <DT>ind_var</DT>