文档库 最新最全的文档下载
当前位置:文档库 › JMP和Minitab的比较(二):简单回归分析

JMP和Minitab的比较(二):简单回归分析

JMP和Minitab的比较(二):简单回归分析
JMP和Minitab的比较(二):简单回归分析

JMP和Minitab的比较(二):简单回归分析

ZDNet 企业管理软件频道更新时间:2008-08-14 作者:来源:

本文关键词:统计JMP

上次看到有人以“基本统计分析”的应用为出发点对JMP和Minitab进行了真刀真枪的大PK,并且得出JMP在统计专业性和整体易用性方面远胜于Minitab的结论。笔者对该作者实事求是的风格颇认同,在此继续遵循这一原则,从另外一个常用统计“简单回归分析”的应用来再次比较JMP和Minitab到底孰优孰劣。

将相同的两列数据“X”和“Y”分别输入到最新版的JMP7和Minitab15中,想得到线性回归方程、含回归直线的散点图、回归检验报告以及回归直线的预测区间。

对比项目一:操作的便捷性。

JMP的操作路径为:主菜单Analyze > Fit Y By X,初始报告弹出菜单中的Fit Line,以及Linear Fit弹出报告中的Confid Curve Fit和Confid Curve Indiv等相关选项,得到的报表如图一所示;Minitab的操作路径为:主菜单Stat > Regression > Fitted Line Plot,Options中选择Display confidence interval和Display prediction interval,得到的报告和图形经整合后如图二所示。操作实现的时间没有明显的差异,但JMP的操作模式让人意识到操作步骤之间层层递进的关系,逻辑性强,而Minitab的操作则纯粹是靠用户用记忆力连接起来的一组相对独立的机械动作。

对比项目二:输出报表的整体效果。

JMP将统计分析结果和相关图形天然地整合在一起,用户查阅起来一目了然。而Minitab的统计分析结果显示在Session窗口,而相关图形又显示在另一个独立的Graph窗口中,查阅起来平添了几分麻烦。如果分析的数据、内容、次数一多,这种麻烦就更难忍受了。

对比项目三:统计分析的具体内容。

无论是回归方程的系数,还是R2、显著性检验P值等等,JMP和Minitab的输出结果都是一致的,这说明两种软件背后所遵循的统计原理其实都是一样的。如果观察得更仔细一些,你会发现JMP中的小数位保留得比Minitab更多,而且可以自定义,显得更精确、更专业一些。

图二Minitab的输出结果

对比项目四:统计图形的效果。

在回归分析的早期,只需要观察最基本的散点图,JMP和Minitab的图形效果差不多。但是到了回归模型的预测应用阶段,置信区间的显示至关重要,JMP可以通过“区间阴影化”的方式加深用户对预测模型的理解。相比之下,Minitab就相形见拙了。

如果要比较边际图的效果,两者的差距就更大了。JMP只需在原有的报表基础上再选择Histogram Borders就能完成,结果如图三所示。它既保留了原先预测区间的特征,又能实现其中散点图与直方图之间的动态链接,Minitab则要重新从主菜单中选择Graph > Marginal Plot,重新在一个新的Graph窗口才能完成,结果如图四所示。而且可惜的是,原先预测区间的特征消失了,图形之间动态链接的效果更是从来都无法体现的。

图三JMP的边际图

图四Minitab的边际图

对比项目五:统计分析的拓展性。

JMP和Minitab都考虑到了这一点,但无论是广度,还是深度来看,两者之间的差异都很明显。先看广度,除了两者都具备的功能外,JMP的回归报表中还整合了非参数拟合、样条拟合、分组拟合、特殊拟合和椭圆密度等丰富实用的内容,令Minitab望尘莫及。

即使是双方都涉及的内容,我们也可以挖掘其涉及的深度来观察两者的差别。以多项式回归为例,JMP最高可支持六次项,Minitab则仅为三次项。以保存数据为例,JMP不仅能够保存残差值和预测值,而且能够保存预测公式,Minitab则不具备保存公式的功能。诸如此类,举不胜举。唯一可以让Minitab挽回一些脸面的是它在进行残差分析的时候会比JMP稍快一些。

总结以上五项对比内容的结果,所有真正理解回归的人都会得到一个一致的结论:JMP在“简单回归分析”方面远胜于Minitab。这个结论的正确性在我们做一些简单的工作时可能会体会不深,但是随着分析问题的深入,这种感觉会越来越强烈地让人感受到。

同样,笔者愿以此文抛砖引玉,希望有更多真正理解统计、需要统计来进行质量管理、六西格玛项目的爱好者来交流切磋,共同提高。

k-折交叉验证(K-fold cross-validation)是指将样本集分为k份,其中k-1份作为训练数据集,而另外的1份作为验证数据集。用验证集来验证所得分类器或者回归的错误码率。一般需要循环k次,直到所有k份数据全部被选择一遍为止。

Cross Validation

Cross validation is a model evaluation method that is better than residuals. The problem with residual evaluations is that they do not give an indication of how well the learner will do when it is asked to make new predictions for data it has not already seen. One way to overcome this problem is to not use the entire data set when training a learner. Some of the data is removed before training begins. Then when training is done, the data that was removed can be used to test the performance of the learned model on ``new'' data. This is the basic idea for a whole class of model evaluation methods called cross validation.

The holdout method is the simplest kind of cross validation. The data set is separated into two sets, called the training set and the testing set. The function approximator fits a function using the training set only. Then the function approximator is asked to predict the output values for the data in the testing set (it has never seen these output values before). The errors it makes are accumulated as before to give the mean absolute test set error, which is used to evaluate the model. The advantage of this method is that it is usually preferable to the residual method and takes no longer to compute. However, its evaluation can have a high variance. The evaluation may depend heavily on which data points end up in the training set and which end up in the test set, and thus the evaluation may be significantly different depending on how the division is made.

K-fold cross validation is one way to improve over the holdout method. The data set is divided into k subsets, and the holdout method is repeated k times. Each time, one of the k subsets is used as the test set and the other k-1 subsets are put together to form a training set. Then the average error across all k trials is computed. The advantage of this method is that it matters less how the data gets divided. Every data point gets to be in a test set exactly once, and gets to be in a training set k-1 times. The variance of the resulting estimate is reduced as k is increased. The disadvantage of this method is that the training algorithm has to be rerun from scratch k times, which means it takes k times as much computation to make an evaluation. A variant of this method is to randomly divide the data into a test and training set k different times. The advantage of doing this is that you can independently choose how large each test set is and how many trials you average over.

Leave-one-out cross validation is K-fold cross validation taken to its logical extreme, with K equal to N, the number of data points in the set. That means that N separate times, the function approximator is trained on all the data except for one point and a prediction is made for that point. As before the average error is computed and used to evaluate the model. The evaluation given by leave-one-out cross validation error (LOO-XVE) is good, but at first pass it seems very expensive to compute. Fortunately, locally weighted learners can make LOO predictions just as easily as they make regular predictions. That means computing the LOO-XVE takes no more time than computing the residual error and it is a much better way to evaluate models. We will see shortly that Vizier relies heavily on LOO-XVE to choose its metacodes.

Figure 26: Cross validation checks how well a model generalizes to new data

Fig. 26 shows an example of cross validation performing better than residual error. The data set in the top two graphs is a simple underlying function with significant noise. Cross validation tells us that broad smoothing is best. The data set in the bottom two graphs is a complex underlying function with no noise. Cross validation tells us that very little smoothing is best for this data set.

Now we return to the question of choosing a good metacode for data set a1.mbl:

File -> Open -> a1.mbl

Edit -> Metacode -> A90:9

Model -> LOOPredict

Edit -> Metacode -> L90:9

Model -> LOOPredict

Edit -> Metacode -> L10:9

Model -> LOOPredict

LOOPredict goes through the entire data set and makes LOO predictions for each point. At the bottom of the page it shows the summary statistics including Mean LOO error, RMS LOO error, and information about the data point with the largest error. The mean absolute LOO-XVEs for the three metacodes given above (the same three used to generate the graphs in fig. 25), are 2.98, 1.23, and 1.80. Those values show that global linear regression is the best metacode of those three, which agrees with our intuitive feeling from looking at the plots in fig. 25. If you repeat the above operation on data set b1.mbl you'll get the values 4.83, 4.45, and 0.39, which also agrees with our observations.

What are cross-validation and bootstrapping?

--------------------------------------------------------------------------------

Cross-validation and bootstrapping are both methods for estimating generalization error based on "resampling" (Weiss and Kulikowski 1991; Efron and Tibshirani 1993; Hjorth 1994; Plutowski, Sakata, and White 1994; Shao and Tu 1995). The resulting estimates of generalization error are often used for choosing among various models, such as different network architectures.

Cross-validation

++++++++++++++++

In k-fold cross-validation, you divide the data into k subsets of (approximately) equal size. You train the net k times, each time leaving out one of the subsets from training, but using only the omitted subset to compute whatever error criterion interests you. If k equals the sample size, this is called "leave-one-out" cross-validation. "Leave-v-out" is a more elaborate and expensive version of cross-validation that involves leaving out all possible subsets of v cases.

Note that cross-validation is quite different from the "split-sample" or "hold-out" method that is commonly used for early stopping in NNs. In the split-sample method, only a single subset (the validation set) is used to estimate the generalization error, instead of k different subsets; i.e., there is no "crossing". While various people have suggested that cross-validation be applied to early stopping, the proper way of doing so is not obvious.

The distinction between cross-validation and split-sample validation is extremely important because cross-validation is markedly superior for small data sets; this fact is demonstrated dramatically by Goutte (1997) in a reply to Zhu and Rohwer (1996). For an insightful discussion of the limitations of cross-validatory choice among several learning methods, see Stone (1977).

Jackknifing

+++++++++++

Leave-one-out cross-validation is also easily confused with jackknifing. Both involve omitting each training case in turn and

retraining the network on the remaining subset. But cross-validation is used to estimate generalization error, while the jackknife is used to estimate the bias of a statistic. In the jackknife, you compute some statistic of interest in each subset of the data. The average of these subset statistics is compared with the corresponding statistic computed from the entire sample in order to estimate the bias of the latter. You can also get a jackknife estimate of the standard error of a statistic. Jackknifing can be used to estimate the bias of the training error and hence to estimate the generalization error, but this process is more complicated than leave-one-out cross-validation (Efron, 1982; Ripley, 1996, p. 73).

Choice of cross-validation method

+++++++++++++++++++++++++++++++++

Cross-validation can be used simply to estimate the generalization error of a given model, or it can be used for model selection by choosing one of several models that has the smallest estimated generalization error. For example, you might use cross-validation to choose the number of hidden units, or you could use cross-validation to choose a subset of the inputs (subset selection). A subset that contains all relevant inputs will be called a "good" subsets, while the subset that contains all relevant inputs but no others will be called the "best" subset. Note that subsets are "good" and "best" in an asymptotic sense (as the number of training cases goes to infinity). With a small training set, it is possible that a subset that is smaller than the "best" subset may provide better generalization error.

Leave-one-out cross-validation often works well for estimating generalization error for continuous error functions such as the mean squared error, but it may perform poorly for discontinuous error functions such as the number of misclassified cases. In the latter case, k-fold

cross-validation is preferred. But if k gets too small, the error estimate is pessimistically biased because of the difference in training-set size between the full-sample analysis and the cross-validation analyses. (For model-selection purposes, this bias can actually help; see the discussion below of Shao, 1993.) A value of 10 for k is popular for estimating generalization error.

Leave-one-out cross-validation can also run into trouble with various model-selection methods. Again, one problem is lack of continuity--a small change in the data can cause a large change in the model selected (Breiman, 1996). For choosing subsets of inputs in linear regression, Breiman and Spector (1992) found 10-fold and 5-fold cross-validation to work better than leave-one-out. Kohavi (1995) also obtained good results for 10-fold cross-validation with empirical decision trees (C4.5). Values of k as small as 5 or even 2 may work even better if you analyze several different random k-way splits of the data to reduce the variability of the cross-validation estimate.

Leave-one-out cross-validation also has more subtle deficiencies for model selection. Shao (1995) showed that in linear models, leave-one-out cross-validation is asymptotically equivalent to AIC (and Mallows' C_p), but leave-v-out cross-validation is asymptotically equivalent to Schwarz's Bayesian criterion (called SBC or BIC) when v = n[1-1/(log(n)-1)], where n is the number of training cases. SBC provides consistent subset-selection, while AIC does not. That is, SBC will choose the "best" subset with probability approaching one as the size of the training set goes to infinity. AIC has an asymptotic probability of one of choosing a "good" subset, but less than one of choosing the "best" subset (Stone, 1979). Many simulation studies have also found that AIC overfits badly in small samples, and that SBC works well (e.g., Hurvich and Tsai, 1989; Shao and Tu, 1995). Hence, these results suggest that leave-one-out cross-validation should overfit in small samples, but leave-v-out cross-validation with appropriate v should do better. However, when true models have an infinite number of parameters, SBC is not efficient, and other criteria that are asymptotically efficient but not consistent for model selection may produce better generalization (Hurvich and Tsai, 1989).

Shao (1993) obtained the surprising result that for selecting subsets of inputs in a linear regression, the probability of selecting the "best" does not converge to 1 (as the sample size n goes to infinity) for leave-v-out cross-validation unless the proportion v/n approaches 1. At first glance, Shao's result seems inconsistent with the analysis by Kearns (1997) of split-sample validation, which shows that the best generalization is obtained with v/n strictly between 0 and 1, with little sensitivity to the precise value of v/n for large data sets. But the apparent conflict is due to the fundamentally different

properties of cross-validation and split-sample validation.

To obtain an intuitive understanding of Shao (1993), let's review some background material on generalization error. Generalization error can be broken down into three additive parts, noise variance + estimation variance + squared estimation bias. Noise variance is the same for all subsets of inputs. Bias is nonzero for subsets that are not "good", but it's zero for all "good" subsets, since we are assuming that the function to be learned is linear. Hence the generalization error of "good" subsets will differ only in the estimation variance. The estimation variance is (2p/t)s^2 where p is the number of inputs in the subset, t is the training set size, and s^2 is the noise variance. The "best" subset is better than other "good" subsets only because the "best" subset has (by definition) the smallest value of p. But the t in the denominator means that differences in generalization error among the "good" subsets will all go to zero as t goes to infinity. Therefore it is difficult to guess which subset is "best" based on the generalization error even when t is very large. It is well known that unbiased estimates of the generalization error, such as those based on AIC, FPE, and C_p, do not produce consistent estimates of the "best" subset (e.g., see Stone, 1979).

In leave-v-out cross-validation, t=n-v. The differences of the cross-validation estimates of generalization error among the "good" subsets contain a factor 1/t, not 1/n. Therefore by making t small enough (and thereby making each regression based on t cases bad enough), we can make the differences of the cross-validation estimates large enough to detect. It turns out that to make t small enough to guess the "best" subset consistently, we have to have t/n go to 0 as n goes to infinity.

The crucial distinction between cross-validation and split-sample validation is that with cross-validation, after guessing the "best" subset, we train the linear regression model for that subset using all n cases, but with split-sample validation, only t cases are ever used for training. If our main purpose were really to choose the "best" subset, I suspect we would still have to have t/n go to 0 even for split-sample validation. But choosing the "best" subset is not the same thing as getting the best generalization. If we are more interested in getting good generalization than in choosing the "best" subset, we do not want to make our regression estimate based on only t cases as bad as we do in cross-validation, because in split-sample validation that bad regression estimate is what we're stuck with. So there is no conflict between Shao and Kearns, but there is a conflict between the two goals of choosing the "best" subset and getting the best generalization in split-sample validation.

Bootstrapping

+++++++++++++

Bootstrapping seems to work better than cross-validation in many cases (Efron, 1983). In the simplest form of bootstrapping, instead of repeatedly analyzing subsets of the data, you repeatedly analyze subsamples of the data. Each subsample is a random sample with replacement from the full sample. Depending on what you want to do, anywhere from 50 to 2000 subsamples might be used. There are many more sophisticated bootstrap methods that can be used not only for estimating generalization error but also for estimating confidence bounds for network outputs (Efron and Tibshirani 1993). For estimating generalization error in classification problems, the .632+ bootstrap (an improvement on the popular .632 bootstrap) is one of the currently favored methods that has the advantage of performing well even when there is severe overfitting. Use of bootstrapping for NNs is described in Baxt and White (1995), Tibshirani (1996), and Masters (1995). However, the results obtained so far are not very thorough, and it is known that bootstrapping does not work well for some other methodologies such as empirical decision trees (Breiman, Friedman, Olshen, and Stone, 1984; Kohavi, 1995), for which it can be excessively optimistic.

For further information

+++++++++++++++++++++++

Cross-validation and bootstrapping become considerably more complicated for time series data; see Hjorth (1994) and Snijders (1988).

More information on jackknife and bootstrap confidence intervals is available at ftp://https://www.wendangku.net/doc/99694023.html,/pub/neural/jackboot.sas (this is a plain-text file).

References:

Baxt, W.G. and White, H. (1995) "Bootstrapping confidence intervals for

clinical input variable effects in a network trained to identify the

presence of acute myocardial infarction", Neural Computation, 7, 624-638.

Breiman, L. (1996), "Heuristics of instability and stabilization in model

selection," Annals of Statistics, 24, 2350-2383.

Breiman, L., Friedman, J.H., Olshen, R.A. and Stone, C.J. (1984),

Classification and Regression Trees, Belmont, CA: Wadsworth.

Breiman, L., and Spector, P. (1992), "Submodel selection and evaluation

in regression: The X-random case," International Statistical Review, 60,

291-319.

Dijkstra, T.K., ed. (1988), On Model Uncertainty and Its Statistical

Implications, Proceedings of a workshop held in Groningen, The

Netherlands, September 25-26, 1986, Berlin: Springer-Verlag.

Efron, B. (1982) The Jackknife, the Bootstrap and Other Resampling

Plans, Philadelphia: SIAM.

Efron, B. (1983), "Estimating the error rate of a prediction rule:

Improvement on cross-validation," J. of the American Statistical

Association, 78, 316-331.

Efron, B. and Tibshirani, R.J. (1993), An Introduction to the Bootstrap,

London: Chapman & Hall.

Efron, B. and Tibshirani, R.J. (1997), "Improvements on cross-validation:

The .632+ bootstrap method," J. of the American Statistical Association,

92, 548-560.

Goutte, C. (1997), "Note on free lunches and cross-validation," Neural

Computation, 9, 1211-1215,

ftp://eivind.imm.dtu.dk/dist/1997/goutte.nflcv.ps.gz.

Hjorth, J.S.U. (1994), Computer Intensive Statistical Methods Validation,

Model Selection, and Bootstrap, London: Chapman & Hall.

Hurvich, C.M., and Tsai, C.-L. (1989), "Regression and time series model

selection in small samples," Biometrika, 76, 297-307.

Kearns, M. (1997), "A bound on the error of cross validation using the

approximation and estimation rates, with consequences for the training-test split," Neural Computation, 9, 1143-1161.

Kohavi, R. (1995), "A study of cross-validation and bootstrap for accuracy estimation and model selection," International Joint Conference on Artificial Intelligence (IJCAI), pp. ?,

https://www.wendangku.net/doc/99694023.html,/users/ronnyk/

Masters, T. (1995) Advanced Algorithms for Neural Networks: A C++ Sourcebook, NY: John Wiley and Sons, ISBN 0-471-10588-0

Plutowski, M., Sakata, S., and White, H. (1994), "Cross-validation estimates IMSE," in Cowan, J.D., Tesauro, G., and Alspector, J. (eds.) Advances in Neural Information Processing Systems 6, San Mateo, CA: Morgan Kaufman, pp. 391-398.

Ripley, B.D. (1996) Pattern Recognition and Neural Networks, Cambridge: Cambridge University Press.

Shao, J. (1993), "Linear model selection by cross-validation," J. of the American Statistical Association, 88, 486-494.

Shao, J. (1995), "An asymptotic theory for linear model selection," Statistica Sinica ?.

Shao, J. and Tu, D. (1995), The Jackknife and Bootstrap, New York: Springer-Verlag.

Snijders, T.A.B. (1988), "On cross-validation for predictor evaluation in time series," in Dijkstra (1988), pp. 56-69.

Stone, M. (1977), "Asymptotics for and against cross-validation," Biometrika, 64, 29-35.

Stone, M. (1979), "Comments on model selection criteria of Akaike and Schwarz," J. of the Royal Statistical Society, Series B, 41, 276-278.

Tibshirani, R. (1996), "A comparison of some error estimates for neural network models," Neural Computation, 8, 152-163.

Weiss, S.M. and Kulikowski, C.A. (1991), Computer Systems That Learn, Morgan Kaufmann.

Zhu, H., and Rohwer, R. (1996), "No free lunch for cross-validation," Neural Computation, 8, 1421-1426.

相关文档