Prediction profiler prediction values do not match with the actual dataHello,
Please allow me to ask a stupid question.
I just realized that prediction profiler Y-axis values do not match with the actual data.
I ran factorial analysis with actual data and had prediction profilers.
When I compared actual data with the prediction values, the values are different.
For example, I have actual data 5% for 100 g of A, 50 g of B, and 100 ug of C condition. However, on the prediction profilers with the same condition, the value is 20%.
In this case how I can analyze and utilize prediction profilers? and is my prediction profilers are reliable?
My apologies for the lack of examples or screen shots. I am not allow to share my data.
Happy New Year!
AnalyticsData TableDOERe: Prediction profiler prediction values do not match with the actual dataThe prediction profiler is based on a model, either the current model in one of the fitting platforms or on a model that was saved as a column formula. Do you mean by 'factorial analysis' that you used the Fit Least Squares fitting platform and opened the prediction profiler in that platform?
Assuming that your answer is "yes," then two thoughts:
- The predictions rarely match the observed values because the observation includes statistical error (individual) and the prediction is the expected mean response.
- if the difference seems unusually large, then perhaps your model is biased or the estimates of the parameters are biased. Are you modeling percent response versus continuous factors A, B, and C, or are you treating them as categorical factors? Is there an interaction or non-linear effect on the response that is not modeled?
Re: Prediction profiler prediction values do not match with the actual dataYes it's the Fit Lease Squares. My apologies for the confusion.
Yes I'm looking at percent response (whether how much % of cells are live or dead) after continuous factors of A, B, and C.
There are synergistic effects of drugs but we don't know the effects are linear or non-linear correlations
I have follow up questions
1. Even if I do the prediction profilers with the observed data, the prediction profilers would be different? (The profilers shows really small confidential intervals but the observed values are out of the range)
2. I want to know how I can fix this profilers. Could you please advise me how to do that?
Regards,
Re: Prediction profiler prediction values do not match with the actual dataYou might try to apply the Logit transform in the Fit Model launch dialog to the response. Be sure that the actual numerical data values are 0 to 1, not 0% to 100%. You can enter 0 to 1 values and then change the format (select Cols > Column Info > Format > Percent) to see 0% to 100%.
The Logit function should make the linear regression happy (it assumes that -infinity < Y < infinity) but the back transform will be limited to 0 to 1.
Re: Prediction profiler prediction values do not match with the actual dataThank you! I tried different transformation as well. Weirdly, reciprocal transformation shows prediction values close to the observed values.
I checked each equation but reciprocal does not make sense to drug toxicity data.
Does this mean my prediction profilers would not be applicable for the future experimental data?
I leave the link for JMP help for Transformation columns for the future reference
https://www.jmp.com/support/help/en/15.2/?os=win&source=application&utm_source=helpmenu&utm_medium=application#page/jmp/transform-columns.shtml
.
Re: Prediction profiler prediction values do not match with the actual dataI would like to chime in here on something that you mentioned earlier. You wanted to use the profiler on "actual data." To be clear, that is not really possible. Think of this simple example:
X Y
10 90
10 94
20 70
20 74
At what value of Y should the profiler be at when X=10? The logical choice is 92, but that is the expected mean for the response based on a model. Similarly, what would should the Y value be when X=15? No way to get that without a model.
So the proper abbreviated process, at a very high level, is to:
1) Collect your data (there should be many steps ahead of this to ensure the proper data is collected in the proper fashion, etc.).
2) Fit a model to your data (the model will be based on step #1 and all of your assumptions and issues discussed prior to step 1),
3) Assess the fit of your model. If the model does not fit well, you should not be using the profiler because it will not be accurate.
4) If the model does fit well, use the profiler to generate some predictions.
5) **** VERY IMPORTANT STEP ***** VERIFY that the model is predicting the future data. Your model may fit the data used to build the model -- it should based on step #3. But will it predict future observations? Don't know until you verify it. There are several possible approaches to doing this depending on situation and circumstance, but those would be topics covered in many books on predictive modeling.