Recently, sheila.loring, marie.gaudard and I have had a discussion about how to handle sample data scripts that run JMP Pro-only features. We would like for there to be some mechanism that alerts the user running one of these scripts in standard JMP to know that the script that was run contained JMP Pro-only features and might not be producing the results advertised by the name of the script.
For example, imagine a sample that runs an Elastic Net for a binomial response (in JMP Pro). If you run the same script in standard JMP, you will end up with a Logistic model, not an Elastic Net model. We think it would be nice if the user were alerted to the fact that an Elastic Net model was not produced (because that's Pro-only) and that they got a Logistic model instead.
We've had two suggestions of how to approach this. One is to write a message to the log, which could be done by the platforms themselves or be written into the sample data scripts. The other idea is to write into the sample data scripts an alert dialog that explains what is going on.
My questions are:
1) How big of a problem do you think this is, based on customer interactions and feedback?
2) If we go ahead with tackling this problem, do you have a preference between the two approaches mentioned above? Is there a better way than either of those?
Thanks!
