Skip to content

Commit c3e3527

Browse files
authored
ENH Adds the details about the numpy arrays and strings in SLEP007 (#61)
1 parent c7d1b3c commit c3e3527

File tree

1 file changed

+8
-6
lines changed

1 file changed

+8
-6
lines changed

slep007/proposal.rst

Lines changed: 8 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -131,17 +131,19 @@ Input Feature Names
131131
The input feature names are stored in a fitted estimator in a
132132
``feature_names_in_`` attribute, and are taken from the given input data, for
133133
instance a ``pandas`` data frame. This attribute will be ``None`` if the input
134-
provides no feature names.
134+
provides no feature names. The ``feature_names_in_`` attribute is a 1d NumPy
135+
array with object dtype and all elements in the array are strings.
135136

136137
Output Feature Names
137138
####################
138139

139140
A fitted estimator exposes the output feature names through the
140-
``get_feature_names_out`` method. Here we discuss more in detail how these
141-
feature names are generated. Since for most estimators there are multiple ways
142-
to generate feature names, this SLEP does not intend to define how exactly
143-
feature names are generated for all of them. It is instead a guideline on how
144-
they could generally be generated.
141+
``get_feature_names_out`` method. The output of ``get_feature_names_out`` is a
142+
1d NumPy array with object dtype and all elements in the array are strings. Here
143+
we discuss more in detail how these feature names are generated. Since for most
144+
estimators there are multiple ways to generate feature names, this SLEP does not
145+
intend to define how exactly feature names are generated for all of them. It is
146+
instead a guideline on how they could generally be generated.
145147

146148
As detailed bellow, some generated output features names are the same or a
147149
derived from the input feature names. In such cases, if no input feature names

0 commit comments

Comments
 (0)