Инженеринг на характеристиките

Raw records can contain numbers, categories, timestamps, and repeated observations that require a representation suitable for a chosen model. Feature engineering creates or transforms those inputs. Extracting a day from a timestamp, encoding a category, and calculating an activity count over a defined earlier period are different examples. The choices should reflect the prediction task and the measurements available when a prediction will be made. A feature derived from an outcome observed only afterward can leak information into evaluation. Fitting a transformation on held-out data can also contaminate an assessment: a scaler should learn its mean and standard deviation on training data, then reuse them on validation or test inputs. Encoding choices address another issue. One-hot encoding represents categories with indicator columns; target encoding uses outcome information and requires additional care to avoid leaking targets. Numeric scaling can matter for objectives or distances sensitive to feature magnitude, but it is not a universal guarantee that no input dominates every model. StandardScaler uses estimated mean and variance, which are sensitive to outliers. An extreme observation can influence those estimates, motivating inspection or comparison with other transformations. Aggregated features also need an explicit window: a count of events before prediction time differs from a count that includes future events. Interaction features represent combinations of inputs. A degree-two polynomial expansion can include the product x1 times x2, so the stated values three and four yield an interaction value of twelve. This creates an input representation; whether it improves predictions remains a separate evaluation question.