Shared Concepts and Topics |
Spline Effects |
This section discusses the construction of spline effects through the experimental EFFECT statement. You can also include spline effects in statistical models by other means. The TRANSREG procedure has dedicated facilities for including regression splines in your model and controlling the construction of the splines. For example, you can use the TRANSREG procedure to fit a spline function but restrict the function to be always increasing or decreasing (monotone). See the section Using Splines and Knots in Chapter 91, The TRANSREG Procedure, for more information about using splines with the TRANSREG procedure. The GAM and TPSPLINE procedures also can model the effects of regressor variables in terms of smooth functions that are generated from spline bases. For more information see Chapter 36, The GAM Procedure, and Chapter 90, The TPSPLINE Procedure.
A spline effect expands variables into spline bases whose form depends on the options that you specify. You can find details about regression splines and spline bases in the section Splines and Spline Bases. You request a spline effect with the syntax
The variables in var-list must be numeric. Design matrix columns are generated separately for each of these variables, and the set of columns is collectively referred to with the specified name. By default, the spline basis that is generated for each variable is a cubic B-spline basis with three equally spaced knots positioned between the minimum and maximum values of that variable. This yields by default seven design matrix columns for each of the variables in the SPLINE effect.
You can specify the following spline-options after a slash (/):
specifies a B-spline basis for the spline expansion. For splines of degree defined with knots, this basis consists of columns. In order to completely specify the B-spline basis, left-side boundary knots and right-side boundary knots are also required. See the suboptions KNOTMETHOD=, DATABOUNDARY=, KNOTMIN=, and KNOTMAX= for details about how to specify the positions of both the internal and boundary knots. This is the default if you do not specify the BASIS= suboption.
specifies a truncated power function basis for the spline expansion. For splines of degree defined with knots for a variable , this basis consists of an intercept, polynomials , ,, and one truncated power function for each of the knots. Unlike the B-spline basis, no boundary knots are required. See the suboption KNOTMETHOD= for details about how you can specify the position of the internal knots.
excludes the intercept column.
excludes the intercept and polynomial columns.
specifies that the extremes of the data be used as boundary knots when building a B-spline basis.
specifies the degree of the spline transformation. The degree must be a nonnegative integer. The degree is typically a small integer, such as 0, 1, 2, or 3. The default is DEGREE=3.
requests tables that show the knot locations and the knots associated with each spline basis function.
specifies that, for each variable in the EFFECT statement, the right-side boundary knots be equally spaced starting at the maximum of the variable and ending at the specified value. This option is ignored for variables whose maximum value is greater than the specified value or if the DATABOUNDARY option is also specified.
specifies that equally spaced knots be positioned between the extremes of the data. The default is . For a B-spline basis, any needed boundary knots continue to be equally spaced unless the DATABOUNDARY option has also been specified. KNOTMETHOD=EQUAL is the default if no knot-method is specified.
specifies the list of internal knots to be used in forming the spline basis columns. For a B-spline basis, the data extremes are used as boundary knots.
specifies the list of all knots that are used in forming the spline basis columns. When you use a truncated power function basis, this list is interpreted as the list of internal knots. When you use a B-spline basis of degree , then the first entries are used as left-side boundary knots and the last d entries in the list are used as right-side boundary knots.
specifies that multiple B-spline bases be generated, corresponding to sets with an increasing number of internal knots. As you increase the number of internal knots, the spline basis you generate is able to approximate features of the data at finer scales. So, by generating bases at multiple scales, you facilitate the modeling of both coarse- and fine-grained features of the data. For scale , the spline basis corresponds to equally spaced internal knots. By default, the bases for scales – are generated. For each scale, a separate spline effect is generated. The name of the constructed spline effect at scale is formed by appending _S to the effect name that you specify in the EFFECT statement. If you specify multiple variables in the EFFECT statement, then spline bases are generated separately for each variable at each scale and the name of the corresponding effect is obtained by appending the variable name followed by _S to the name in the EFFECT statement. For example, the following statement generates effects named spl_x1_S0, spl_x1_S1, spl_x1_S2, , spl_x1_S7 and spl_x2_S1, spl_x2_S2, , spl_x2_S7:
EFFECT spl = spline(x1 x2 / knotmethod=multiscale);
The MULTISCALE option is ignored if you specify the BASIS=TPF spline-option. The MULTISCALE option is not available for spline effects that are specified in the RANDOM statement of the GLIMMIX procedure.
specifies the start scale, where is a positive integer. The default is STARTSCALE=0.
specifies the end scale, where is a positive integer. The default is ENDSCALE=7.
requests that internal knots be placed at equally spaced percentiles of the variable or variables named in the EFFECT statement. For example, the following statement positions internal knots at the deciles of the variable x. For a B-spline basis, the extremes of the data are used as boundary knots:
EFFECT spl = spline(x / knotmethod=percentiles(9));
requests that internal knots be placed at each fraction of the ranges of the variables in the EFFECT statement. For example, if variable x1 ranges between 1 and 3, and variable x2 ranges between 0 and 20, then the following EFFECT statement uses internal knots 1.2, 2, and 2.5 for variable x1 and internal knots 2, 10, and 15 for variable x2:
EFFECT spl = spline(x1 x2 / knotmethod=rangefractions(.1 .5 .75));
For a B-spline basis, the data extremes are used as boundary knots.
specifies that for each variable in the EFFECT statement, the left-side boundary knots be equally spaced starting at the specified value and ending at the minimum of the variable. This option is ignored for variables whose minimum value is less than the specified value or if the DATABOUNDARY option is also specified.
specifies that when multiple variables are specified in the EFFECT statement, the spline basis for each variable be treated as a separate effect. The names of these separated effects are formed by appending an underscore followed by the name of the variable to the name that you specify in the EFFECT statement. For example, the effect names generated with the following statement are spl_x1 and spl_x2:
EFFECT spl = spline(x1 x2 / separate);
In procedures that support variable selection, such as the GLMSELECT procedure, these two effects can enter or leave the model independently during the selection process. Separated effects are not supported in the RANDOM statement of the GLIMMIX procedure.
specifies that each individual column in the design matrix that corresponds to the spline effect be treated as a separate effect that can enter or leave the model independently. Names for these split effects are generated by appending the variable name and an index for each column to the name that you specify in the EFFECT statement. For example, the effects generated for the spline effect in the following statement are spl_x1:1, spl_x1:2, ..., spl_x1:7 and spl_x2:1, spl_x2:2, ..., spl_x2:7:
EFFECT spl = spline(x1 x2 / split);
The SPLIT option is not supported in the GLIMMIX procedure.
Copyright © SAS Institute, Inc. All Rights Reserved.