Learn how to build custom Python data connectors and further customize JMP’s Data Connector Framework with the Python Data Connector Demo, available now in the JMP Marketplace!
See how to create experiments to support product design and ID useful product features. Register for June 12 webinar, 2pm US Eastern Time.
Hi @andrewtkarl, you can set the distributions and std deviations via JSL. Can you please provide more information on the change(s) you'd like to see? Thanks!
Thanks, Mia. I am going to do my best to recall the things I was hoping to see:
First, a more general Profiler() wish is to have a way to retrieve the current predictions at each response in the profiler (given the current factor settings). Ideally returned as something easy to parse such as a list of response names and a list of values. We can use
<<get factor settings
to see the factor settings (and that returns a syntax that is sort of challengign to parse) but surprisingly there is not a corresponding <<get response values
For a simulator object, I belive I was hoping to see a richer vesion of <<get factor settings that would also return information about the current simulator setup for each factor (distribution and range). This was for a script that was automatically working with a table script containing a simulator and I needed to access that information and instead was having to do a lot of parsing instead of just being able to message the simulator object to <<get factor simulator settings.
I also think I was hoping to have a simpler syntax to change the distribution of the factors in the simulator. For example, if we had a richer <<Get factor simulator settings message where we could loop over the factors in the simulator and send a message to each if we wanted to change the distribution (just using the default distribution parameters). By simpler I mean something that would allow us to specify the name as a string instead of having to parse the name into the correct format with :"[name]"\n delimiters needed when there are special characters.
has added a <<get responses message for Profiler. But in my first bullet point I was thinking of the need to have a <<get response names message to get a list of the responsese those values correspond to.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.