JMP Wish List

Several other programming languages default to the local namespace/environment rather than a global environment. JMP Experts say the NamesDefaultToHere(1) is the BKM whenever scripting as typically the local namespace is appropriate for new scripts to avoid clashing with other JMP scripts. It would be more convenient to define NamesDefaultToHere(0) when you want a script to be in the global namespace rather than defining every script with the "true" argument ... View more

If you want your software to be used in the social sciences, esp. psychology, I recommend two critical features - the first involving simple slopes and the second involving hierarchical regression.     In general, the ability to follow up an interaction involving a continuous variable to conduct a "simple slopes" or "simple effects" analysis in which, at a minimum, the user can either probe the slope of a line at different values of another predictor (and obtain slopes with SEs) and even better, provide contrasts between these slopes. The other predictor may be continuous (and thus the ability to plot plus or minus 1 SE would be necessary) or categorical.     A second very common technique in psych is hiearchical regression in which two models are compared with one nested within the other.  The only way I can do this using JMP is to run both models, extract the model dfs and SS values and MSE, compute an F, and then look up the F in a table (or compute the associated p-value using a JMP Formula).  Very clunky.  This is super simple in R, SPSS, and even Jamovi.     ... View more

Recently ran across this problem.  Needed to fit an exponential growth model to a set of data where the curve must pass/start at the origin. Most of the exponential growth models in Fit Curve don't allow you to constrain the model parameters so that the curve will go through the origin.  So I wasnt' able to do what I needed in Fit Curve.  I was able to do this in Non-linear by building the model I wanted, but that is rather technical and above the level of the typical user who wants to use Fit Curve.  Many chemical and physical kinetic processes y(t) start with y(0)=0.  Currently only Weibull Growth &  One Compartmental Oral Dose have that property.     Could either: a) Allow for fixing and constraining parameters in Fit Curve so that you could get y(0)=0, or b) Adding exponential growth models that go through the origin.  For example, these models would be nice to have y(t) = a(1-exp(-bt))   y(t) = a(1-exp(-bt)) + c(1-exp(-dt))       ... View more

JMP's Log is one of its most helpful features. However, I think it would be nice and productive if its position can be customizable. Currently when a user selects the "Show Embedded Log", the log is always snapped to the bottom of the screen. It would be nice to allow the user to dock it where ever the user likes.  ... View more

Currently if I open any non-modal window while inside of a project, it gets added to the project.  I'd love some way to make a new window NOT open in the project.   ... View more

Would be nice to have more flexible column properties for spec limits and control limits. Current column properties allow only one spec limit or control limit. But many SPC users will have changing control limits and spec limits over time. Currently Control Chart Builder can use a Phase column to separate calculated control limits. Saving to a table it will show the _LCL, _Mean, _UCL, etc. for each phase, with phase as an additional column. Could spec limits and control limits work in this manner? The ability to use a table to pull in the requirements, or save from Control Chart Builder to the Column and not just the table? See wish list requests for more flexible Value Ordering and Value Labels column properties that may interact with JMP tables. Not sure how it would work with all platforms, such as Process Screening. Currently have to write scripts to add changing control limits or spec limits to charts and other platforms. ... View more

Currently in the Fit Least Squares platform, you can "Show Prediction Expression" under "Estimates". It is shown using coded levels, and harder to interpret for many users for coefficients. Currently our users are told to "Save Columns" >  "Prediction Formula" to a column, then select the formula, and use the menu item "Simplify" to undo coded levels and show as typical coefficients for the model. Any way to add the "Simplify" function to the Prediction Expression when shown in the Fit Least Squares report? (By the way, the "simplify" in the Formula Editor was an awesome addition). Example from the Custom DOE class:   "210 + 186* ( (Thickness - 5)/2.5)"  becomes "-162 + 74.4 * Thickness" using Simplify   The Y intercept of 210 is where the coded level of -1 to +1 is 0, so a positive 210 based on coded levels. But when using Fit Y by X, the equation is -162+74.4*Thickness, which has a negative value for Y intercept when Thickness is zero. ... View more

What inspired this wish list request? Please describe the current issue that needs improvement or the problem to be solved that is not easy or possible right now, with an example use case. The variable importance analysis employs a Monte Carlo simulation, therefore each time you perform a specific analysis the importance report changes somewhat, and the results are therefore not exactly reproducible.  One can manually add a random seed command to the Profiler script to make the importance report reproducible in the future. However, it would be nice to be able to set a random seed while performing the analysess.     What is the improvement you would like to see? Please describe the idea for improving JMP. Please include mock-ups, wireframes, screenshots, scripts, other documents or examples from other software that help describe the change you would like to see.  Exact reproducibility of variable importance results   Why is this idea important? Please describe the value to you and/or other users if the idea is implemented (for example, ease of use, must have,…). When scientists observe that the variable importance reports are not exactly the same each time the analysis is performed, they tend to become skeptical of the approach.  Also, these variable importance reports are sometimes used as supporting documentation for critical process parameter identification in FDA filings, so it is important they be exactly reproducible.   ... View more

What inspired this wish list request?  Accessing the Text to Columns utility from the main Cols menu is cumbersome and inefficient.   What is the improvement you would like to see?  Enable Text to Columns Utility to be accessed by riht-clicking the column and from the Column manager. Potentially also allow the utility to be simultaneously operated on multiple columns.     Why is this idea important?  Increased efficiency and ease of use.   ... View more

What inspired this wish list request? Managing jmp licenses can be tedious if we have a lot of licenses and employees resign or arrive. Corporate user management systems (like Active Directory or other SSOs) always need to be up to date, so if we can have an API to add or remove users on my.jmp.com, that would be very useful.   What is the improvement you would like to see? All actions that we can do manually in the my.jmp.com console should be possible with API and be documented.   Why is this idea important? Manage jmp automatically and not manually. ... View more

What inspired this wish list request? Please describe the current issue that needs improvement or the problem to be solved that is not easy or possible right now, with an example use case. The Analyze tab in the Easy DOE platform gives a cool plot of the model terms included in the chosen model along with associated confidence intervals. Easy DOE is better for newer users, but more intermediate/advanced users could benefit from this graphical display as well. The full reference to the plot is found here - Analyze (jmp.com).   What is the improvement you would like to see? Please describe the idea for improving JMP. Please include mock-ups, wireframes, screenshots, scripts, other documents or examples from other software that help describe the change you would like to see. Implementing this in either the Fit Least Squares or Generalized Regression platforms (it would look good potentially as an option near the Solution Path graphs).   Why is this idea important? Please describe the value to you and/or other users if the idea is implemented (for example, ease of use, must have,…). Being able to harmonize output across platforms can be important to the user experience. A newer engineer leveraging Easy DOE can make a nice plot that a more experienced engineer that is using standard menus such as Fit Model are unable to reproduce. Easy DOE is also more of a front-to-back, end-to-end bundle of content for a DOE, so it is difficult to just get a singular extraction from the platform. It would be simpler to implement the Effect Plot in other model-fitting platforms.     ... View more

What inspired this wish list request? I use multi-layer "Group X" in graph builder often to look efficiently at multiple categorical outputs (and especially nice when I want to bin continuous outputs).  However, if I have a lot of levels then the Group X axis can smash the data up too much.   What is the improvement you would like to see? I would like to be able to stack another column under the column used in the "Wrap" view in Graph builder. So go from this: to this:         Why is this idea important? This allows more the Group X axis to be more useful when looking at two columns you'd like to stack in the axis (and frees up even more drilling down possibilities since now Overlay can be used for a third column)   Thanks Steve     ... View more

Hi.  I would like to have the ability to set the USL equal to the LSL.  I'm currently using JMP Pro 17.2.0.  If I try to set the limits equal to each other in the Column Properties window, I get an error "USL must be greater than LSL and the target".  Similar error if I try it using the Manage Limits platform.   Please see this thread for original discussion: https://community.jmp.com/t5/Discussions/Setting-Spec-Limits-with-USL-LSL/m-p/717822#M89952    What inspired this wish list request?  If I try to set limits equal to each other in the Column Properties window or Manage Limits platform, I get an error.  I can programmatically set the limits to be equal using the << Set Property message, but I cannot read them back using Manage Limits.  This script helps to illustrate:   Names Default to Here(1); dt = Open("$SAMPLE_DATA/Big Class.jmp"); dt:Height << Set Property("Spec Limits", USL(1), LSL(1)); //I can set USL=LSL in a script //I can confirm they've been set by manually opening the Column Properties window. //At some later date I need to reopen the table and get the limits to evaluate yield: msl = dt << Manage Limits(Process Variables(:Height)); //The limits are now missing. dtlim = msl << Save to Tall Limits Table; Sometimes I also see a small window popup saying something to the effect of "Inconsistent Limits" with all the offending columns listed, but I haven't figured out yet how to reproduce this.     What is the improvement you would like to see?  I would like the ability to set limits equal to each other in the Column Properties and Manage Limits windows.  I want to continue preventing USL < LSL though.   Why is this idea important?  Our data contains 1000s of columns.  Some (but not all) columns represent codes (integers), where only one value means "ok" and all others indicate a different type of failure.  For example, a "1" is passing, a "0" = did not test, and values 2 or greater indicate some other error.  We wish to compute yields and other analyses on these data using scripts.  But we're finding that these columns where USL=LSL are not getting checked because when the script reads back the limits using Manage Limits, they're missing.     Things we've considered:  1. Set the limits to (x-0.1, x+0.1) instead of (x,x).  Cannot do bc that would require modifying hundreds of limits multiplied by several manufacturing steps multiplied by several programs, and would affect many other orgs in our company. 2. Set just the LSL for these columns, leaving the USL missing.  Then, in our yield analysis script, add a clause that checks the column name against a list of columns whose values are "coded", and if matching, just check if the value matches the LSL instead of checking if the value lies between LSL-USL.  Problematic bc it would require us to hardcode which columns need to be checked one way vs another within the script, constantly updating scripts as the list of names changes throughout development.  Plus, there would have to be separate lists maintained for each manufacturing step and each program, as they don't share the same tests.  Also problematic bc others are using different analysis scripts on the data, that may not be aware if we have deleted the USL and kept only the LSL. 3. Set the limits programmatically as in the script above.  Then when we wish to read them back from the data table at a later date, use the << Get Property message instead of the Manage Limits.  I'm still working on a script to try this, but I already have misgivings about this tact.  First, it would need a For loop to read and parse each column's specs, which might take awhile for 10k+ columns.  Second, I'm having difficulty parsing out the limits from the << Get Property("Spec Limits") message.  (1) It just returns USL(1) (no quotes) and it's unclear to me how to extract the number from this.  (2) it does not seem to return the LSL, even though I confirmed in the Column Properties window that it was also set to 1.  The script below illustrates: Names Default to Here(1); dt = Open("$SAMPLE_DATA/Big Class.jmp"); dt:Height << Set Property("Spec Limits", USL(1), LSL(1)); //confirm limits set in col props window. specs = dt:Height << Get Property( "Spec Limits" ); //returns USL(1) only lsl = specs["LSL"]; //returns . usl = specs["USL"]; //returns .   Apologies in advance if there are other obvious solutions I haven't thought of (or forgot to mention).  Also apologies if I've glossed over some crucial detail.  I've been working on this for awhile now, so I'm pretty deep in the weeds.     Thanks for considering.       ... View more

What inspired this wish list request?  The need to compare the model built from a DOE ran in a simulation software with the model from the exact same DOE ran in an experiment in the lab.    What is the improvement you would like to see?  Overlay in the profiler if two different models in the same row. For more detail please look at the post below https://community.jmp.com/t5/Discussions/Overlay-profiler-from-two-different-models/m-p/708222#M89253   Why is this idea important?  It helps to see the mismatch between the simulation and the experimental DOE results and helps calibrate the simulation software model better and design better DOEs in the next experiments.   ... View more

☐ cool new feature ☑ could help many users! ☐ removes a „bug“ ☑ nice to have ☐ nobody needs it   What inspired this wish list request?  Freq and Weight can have different effects.   Jmp documentation makes it difficult to understand the differences: https://www.jmp.com/support/help/en/17.0/index.shtml#page/jmp/summary-launch-window.shtml#ww272136    SAS provides an application note  Distinction between the WEIGHT and FREQ statements  and an explanatory article about the differences: The difference between frequencies and weights in regression analysis    Jmp uses Freq differently from SAS: https://community.jmp.com/t5/Discussions/Not-sure-how-to-use-amp-quot-Weight-amp-quot-in-amp-quot-Analyze/m-p/684790/highlight/true#M87072      If the user wants to weight different values differently in a Median calculation (weights: 0-1), he has to use Freq: https://community.jmp.com/t5/Discussions/Not-sure-how-to-use-amp-quot-Weight-amp-quot-in-amp-quot-Analyze/m-p/684839/highlight/true#M87083  ...  and he is allowed to use Freq (in Jmp)   What is the improvement you would like to see?  Please add some explanatory text to the documentation - perhaps: some simple example which explains the difference between Weight and Freq and guides the user to pick the right one.   Why is this idea important?  To generate meaningful analysis a user has to understands the meaning of entries in the GUI. Best: via documentation - not via trial and error :)         more wishes submitted by   ... View more

    Say you do the following, slightly modified from the scripting index: Names Default To Here( 1 ); dt = Open( "$SAMPLE_DATA/Semiconductor Capability.jmp" ); obj = dt << Process Screening( Grouping( :Site, :lot_id ), Process Variables( Eval( 5 :: 132 ) ), automaticrecalc(1) ); You'll get a report like this with rows for the different combinations of values from the Grouping() columns: And those rows act as a gateway to various plots.  For example,  you can get Process Capability or Control Charts that are pretty much as if you had used these grouping() columns as a By() on those platforms.  But you won't get a row for a grouping where any of the Grouping column values were missing or, if character, whitespace.  So if you replace a lot_id value with blank or a SITE with missing you don't see that appear on the report so you don't know there was some data that was like that, maybe needing attention.   When I discussed this with JMP support I was told that this is consistent with other JMP platforms, for example how X values that are blank don't show up on the X axis of a Oneway.  But my perspective is that Grouping() is a lot more like a By() in this case (which does make plots for the by groups with values of missing or blank).  The situation with Grouping() is also similar to summary/summarize which would recognize those groups and produce a row. I appreciate that Process Screening has a By() and Grouping() is not it, but I think there would be value in showing up these groups and providing access to the same plots you'd see from a by()  (ie if you ran Control Chart() with a by() on the same columns you would see a report for a missing SITE):     The upshot is that I was encouraged to after all make a Wish List item on this so this perspective could be considered.    I think it would at least be worthwhile as an option.   Why is this idea important?  The main issue/value is how starting from Process Screening as your gateway to the various other reports lets you miss some of your data or problems in your data.  This came to my attention while working with a customer with a large amount of data in many groupings with many levels per grouping and with data that comes from machine sources.  To some degree the Process Screening is advertised at letting you sift through lots and lots of processes and so it's a situation where the possibility that some data is defective - and that that could go unnoticed - is heightened.  This platform could even go so far as to highlight such groupings, let alone include them. ... View more

What inspired this wish list request?  I've experienced migrating scripts & add-in from JMP 15 to JMP 16 to JMP 17 which consume a lot of my engineering time to debug. We never know how many more versions JMP plan to release in the future. I foresee we will keep repeating this process, which really holding us back to fully automate the decision-making flow in operation. Imagine, if I have 10 scripts saved at 5 computers for machine learning which may contain >100 lines of code. Every time JMP release new version that is not compatible with old versions, I need to re-edit my scripts & test at all computers to ensure no disruption to the operation.   What is the improvement you would like to see?  -Create "add-in script converter" between versions. Maybe start with JMP 17 --> if user want to upgrade to JMP 18 license, this feature propose a new script or verify the old version code to see if it compatible.  -Maybe add this feature in "add-in manager" feature highlighted by other users. https://community.jmp.com/t5/JMP-Add-Ins/Add-In-Manager/ta-p/43736#U43736 https://community.jmp.com/t5/JMP-Wish-List/Integrate-Add-In-Manager-in-Jmp/idi-p/575114     Why is this idea important?  1. We can save a lot of time & do something else in JMP rather than keep re-edit our released scripts. 2. Easy for me to justify investment to buy more JMP license.   ... View more

What inspired this wish list request?  I have to export tabulate results to Excel and reformat it.  Waste of time.     What is the improvement you would like to see?  Add conditional formatting.     Why is this idea important?  Saves time.     ... View more

Now, Expanded Estimates are available only for basic regression models. It would be great to have them for models that are less standard, like logistic regression, ordinal regression, ... ... View more