nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

61060_en-US

liliconcom

Profiler and Constraint Property

Hi,

I put this in the main JMP community (not wish list) a month or so ago, as I wasn't sure whether there was a simple fix. https://community.jmp.com/t5/Discussions/Profiler-and-Constraint-Property/m-p/57146

Basically, constraints don't work if the Constraint property refers to any variables that are not currently in the equation(s) being profiled. This is undesirable for me. I can think of a couple solutions that might work. One is to have multiple Constraint properties and the ability to tell Fit Model (or Profiler) which one to use. The other is for JMP to be able to ignore variables when they are not used in the models being profiled.

Thanks,

Michael

Graphics

Re: Profiler and Constraint Property - Status changed to: Delivered

@mjoner I think this is delivered now with profiler extrapolation control. If not please let me know.

Comments

There are no comments yet