Three layout TIPS for JMP Software

[@gilbertomoreno9392]

Excellent💯 video thank you for sharing!!

[@steffenbugge4736]

So simple, yet so powerful! I will never look at a fit model the same way again! Thanks for sharing!

[@markchahl6408]

Thank you, David! This 30 year JMP user continues to learn from you.

[@PegaAnalytics]

Thanks for your feedback Mark.

[@statslikejazz]

Great content #PegaAnalytics! Never thought of using arrange in rows in the fit model platform! When would you not use fit separatly?

[@PegaAnalytics]

Hi, thanks for your feedback. I can't think of a good reason to not use the 'fit separately' option. Perhaps I might use it if I am doing a demonstration and want to focus on model visualisation and interpretation without dwelling on the details of model building. But in a real-world scenario, I would always want to spend my time building the best model I can for each response, and for that I would use 'fit separately'. The 'fit separately' option allows you to refine model terms individually for each response, whereas if not selected you refine model terms en-masse across the responses. Prior to version 14 this was the only way of handling multiple responses - apart from running Fit Model separately for each model. And the benefit of specifying multiple responses rather than running multiple Fit Models, is that you can view all the models simultaneously in the prediction profiler and contour profiler, as well as perform numerical optimisations that take account of all the responses.