cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Try the Materials Informatics Toolkit, which is designed to easily handle SMILES data. This and other helpful add-ins are available in the JMP® Marketplace
Choose Language Hide Translation Bar
JOE1
JOE1
Level I

Prediction profiler - Interactive html

Created: Nov 20, 2020 11:44 AM  |  Last Modified: Jun 10, 2023 1:41 PM (1270 views)

Hi,

I wanted to store an interactive html using the prediction profiler with two responses and three factors.

Unfortunately the Log file displays:

Interactive HTML: Controls are not interactive.
Interactive HTML: Embedded profilers in this platform are not interactive

And after storage receive "This feature is not interactive".

For one response it is interactive.

JOE1_0-1605890528947.png

Can you help making it work with two responses?

Thanks,

Jonathan

J.Eras
0 Kudos
2 REPLIES 2
P_Bartell
P_Bartell
Level VIII

Re: Prediction profiler - Interactive html

Nov 22, 2020 12:40 PM (1236 views)  |  Posted in reply to message from JOE1 11-20-2020

Can you share the exact workflow you used? Interactive HTML is not offered in ALL places where a profiler is present in the JMP ecosystem. Profilers are in numerous platforms...and they aren't interactive in all of them. Plus what version of JMP you are using? As JMP versions progress, in general, HTML interactivity is expanding across the JMP analysis platform architecture.

 

I just fit a simple two response model using Fit Model -> Standard Least Squares personality, running JMP Pro 15.2.1, and the profiler was interactive within the HTML output report.

josh_markwordt
josh_markwordt
Level V

Re: Prediction profiler - Interactive html

Created: Dec 4, 2020 02:00 PM  |  Last Modified: Dec 7, 2020 5:13 AM (1205 views)  |  Posted in reply to message from P_Bartell 11-22-2020

As Peter said, we would need more info on the specific platform and script that was used.  The message about embedded profilers not being supported in this platform could be true, or it could have been triggered by turning on a specific unsupported feature that we didn't know we needed to detect.  If we knew more, even if it could not be supported we should be able to add a more specific log message in this case.

 

This blog post might provide more insight into why profilers sometimes go static: Why is my Interactive HTML Profiler not interactive?