JMP Wish List

Currently when you export a Profiler to Interactive HTML the confidence intervals are not displayed.    Please add support for these confidence intervals for Profilers in interactive HTML.   This issue was raised in a recent discussion: Sharing model profiler results within company   Compare the report in JMP vs. interactive HTML shown below.   Profiler in JMP w/Confidence Intervals Profiler in interactive HTML ... View more

I know there is a lot that can be done with two layers, but being limited with two layers even in JMP Pro is not a good idea. As a customer, I can get any layer in a free package of Python and I don't know why I should not be able to get the same with JMP Pro. Number of layers in the best option would be selective, otherwise, at least provide three layers (Input, middle, output layers). ... View more

☑ cool new feature ☐ could help many users! ☐ removes a „bug“ ☐ nice to have ☐ nobody needs it     Adjusting gradient settings is very time consuming because the menu has to be closed to get the changes applied. Often, the settings have to be tried and optimized iteratively. A "live view" could help:   alternative: direct mouse control of the gradient scaling settings: https://community.jmp.com/t5/JMP-Wish-List/mouse-control-for-color-gradient/idi-p/486588 ... View more

☐ cool new feature ☑ could help many users! ☐ removes a „bug“ ☐ nice to have ☐ nobody needs it     In the NewFormulaColumn/Transform menu there are many useful functions, but "modulo" is missing:     more wishes submitted by   ... View more

☐  cool new feature ☑ could help many users! ☐ removes a „bug“ ☐ nice to have ☐ nobody needs it     sometimes it's hard to find the right column again and again.   some suggestions to make it easier:       - define special colors for special columns (or groups):   - make the vertical line between groups thicker     more wishes submitted by   ... View more

I'd like to suggest the ability to only lock one side of an axis range (the min or the max).  This would allow the user to lock the range at zero (min) and then allow the max setting to vary with the data range.  This would mimic the way the axis setting works in a popular program that rhymes with "terrel".   Thanks for considering this request.   Steve ... View more

What inspired this wish list request? Due to a change in default for JMP17. Previously in JMP16, the jitter default looks like this:   But the JMP17 default is now something like this:    We see in the Fit Y by X platform and its preferences you can only use a boolean to turn jitter on/off. Oneway( Y( :Data ), X( :Levels ), X Axis Proportional( 0 ), Points Jittered( 1 ), We did discover by doing a right-click and select Customize > Marker, that the option to change the jitter is shown Oneway( Y( :Data ), X( :Levels ), Means( 1 ), Box Plots( 1 ), Mean Diamonds( 1 ), X Axis Proportional( 0 ), Points Jittered( 1 ), SendToReport( Dispatch( {}, "Oneway Plot", FrameBox, {Frame Size( 607, 243 ), DispatchSeg( Marker Seg( 1 ), Set Jitter( "Random Uniform", "X", 1, 0, 355 )   What is the improvement you would like to see? We would like the option to set the type of jitter in the Fit Y by X platform similar to the Graph Builder jitter options. To also allow this in the Preferences for the platform. Graph Builder( Size( 526, 448 ), Show Control Panel( 0 ), Variables( X( :Levels ), Y( :Data ), Color( :Levels ) ), Elements( Points( X, Y, Legend( 7 ), Jitter( "Random Uniform" ), Jitter Limit( 0.4381 ) ) ) );   Why is this idea important? To standarize reports for viewers preferences, instead of having to change each time, or run a script that adjusts the elements of the Fit Y by X, should allow this platform to change as a preference and a menu option in the Fit Y by X platform.     ... View more

What inspired this wish list request? @scott_allen has developed an add-in that allows tuning of NN parameters,     What is the improvement you would like to see? Adding more layers to the NN platform will allow faster and better model building and exploration using the NN-add-in.     Why is this idea important? NN models are subject to a lot of parameter tuning and a transparent and efficient DOE based approach has a lot of advantages in robustness and also accuracy   ... View more

When I am using the Fit Model platform with Standard Least Squares, I can effectively save the prediction formula and standard errors to a separate column. When I do this for multiple responses, I can effectively use the Graph -> Profiler menu to overlay those models. This is very helpful, as each response may have a different set of meaningful predictors in it. Here is a reference to such a thread on the topic:   https://community.jmp.com/t5/Discussions/Confidence-Interval-in-prediction-profiler/td-p/10817   However, if I have a generalized linear model (GLM) such as a logistic regression, I have no such luck. Within the single model for fitting the GLM Personality, the results in that platform have confidence intervals on them. However, I am only able to export the prediction formula. If my most 2 important responses contains one normal response with Standard Least Squares, and one binomial response with a GLM logistic regression model, I cannot create a joint Prediction Profiler with effective predictions and confidence intervals. I am optimistic this can be done because we already have evidence that the confidence intervals can be created for GLMs. You just have to work out what the StdErr Pred Formula column would look like.   I brought this up as a ticket with JMP as well. The following series of responses from JMP support certainly brought attention to the issue, but perhaps if others find value in this enhancement, then it is more likely to be completed.   "Unfortunately, at the moment, I do not see a way to get a confidence interval around the predicted probability for the binary response in the combined standalone profiler."   "I see what you mean about the inability to save Standard Error Formulas for GLM's or for Least Squares models containing nested terms. I am not aware of any particular reason why this is the case. I will pass these items on to JMP R&D for their consideration in a future version of JMP."   ... View more

What inspired this wish list request?  There is a plethora of posts in the Jmp Community concerning Date and Time data curation, e.g.  Manipulating Timestamp  Unix Timestamp to Real Date & time  Changing Date Format  Date-Time Format Problem  Date Format help please  change date format    There are some tools which help a lot - but any improvement will help :)   For time & date columns the user can select from a long list of standard settings and even specify a custom pattern. BuiltIn presets can be concatenate to construct the desired pattern.   Unfortunately, every time the user has to construct a pattern he has to start from scratch.   What is the improvement you would like to see?  Please add a history to the custom date/time pattern dialog window.     Why is this idea important? If a user uses a pattern once, there is a large chance that he will use it again. With the history aavailable in the dialog window, it will be much easier to use the Format Pattern window: Invest the time once to generate the pattern and enjoy it for the rest of your live.           more wishes submitted by   ... View more

☐ cool new feature ☐ could help many users! ☑ feels like a bug ☐ nice to have ☐ nobody needs it   What inspired this wish list request?  code that is generated via << save script will generate JSL code to reproduce the same behavior - in combination with the settings in the preferences. So far so good.   But the same code - in combination with (other) settings on another system can generate a completely different behavior. One could say: so far so good - the user on the other system might have some idea why he adjusted the settings.   But things get funny when the code was generated on a system with adjusted settings in the preferences. Then - (most *) setting which fit to the current (non-standard) settings in the preferences will NOT be saved in the JSL script - and now when such code will be executed on a standard system such non-standard standard settings will be missing in the code → leading to a different behavior on a standard system. - (other **) settings which fit to the standard settings will NOT be saved in the JSL script - and therefore when being executed again on the same system (with non-standard settings) will be missing.   *) like color gradients: it's not possible to specify a gradient for a plot in JSL  (via << save script) which equals the gradient in the preferences    **) like Conditional settings of the Data filter: on a system with Conditional enabled in the preferences, it's not possible to generate a JSL code (via << save script()) for a non-conditional data filter   collateral effects: With there are CHANGED settings in the preferences, a user loses the chance to use Dashboard Builder to generate Dashboards which opens platforms on his system with STANDARD settings :( Do you use the preferences?    The only workaround: Open the source script of the Dashboard and add the respective code manually.   What is the improvement you would like to see?  Although current behavior is as designed - it is not always as expected by the users. Please optimize the behavior in a future version of Jmp.   Why is this idea important?  If a user changes settings in the preferences he should still have the chance to generate Dashboards which use the standard settings.   more wishes submitted by   ... View more

What inspired this wish list request?  I have been adding table scripts to our standardized data and telling user what they do just based on the name is starting to get a bit difficult.    What is the improvement you would like to see? I would like to be able to provide users with tip/tooltip when they hover over over table script (in similar manner as Notes works for Column Properties).   Why is this idea important?  Makes it easier to indicate user what the script is doing IF just the name isn't enough without them having to open the script and understand it (or read a comment in script). ... View more

Dear all, we use Box Plots a lot, and the new features in JMP 16 (notched ...) are great, but it would be quite helpful to be able to control these features already in preference settings.   So I would vote for including features like  Box Style( "Solid" ), Notched( 1 ), Fences( 1 ), Name( "5 Number Summary" )(1) in preferences to not need to specify them in each plot again.   See script and screenshot for illustration. Thanks,     Names Default To Here( 1 ); // styled Box Plot with notch and colos dt = Open( "$SAMPLE_DATA/Big Class.jmp" ); dlg = Column Dialog( xCols = Col List( "X, Factors", Min Col( 1 ), Max Col( 1 ), Modeling Type( "Categorical" ) ), yCols = Col List( "Y, Response", Min Col( 1 ), Max Col( 1 ), Modeling Type( "Continuous" ) ) ); gb = Graph Builder( Show Control Panel( 0 ), Variables( X( dlg["xCols"][1] ), Y( dlg["yCols"][1] ), Color( dlg["xCols"][1] ) ), Elements( Box Plot( X, Y, Legend( 3 ), Box Style( "Solid" ), Notched( 1 ), Fences( 1 ), Name( "5 Number Summary" )(1) ) ) ); ... View more

☐ cool new feature ☐ could help many users! ☑ feels like a „bug“ ☐ nice to have ☐ nobody needs it   What inspired this wish list request?  The Regex search in Jmp is restricted because the user is not allowed to set all flags which are officially available for regex searches.   vs. what is possible in Jmp for Regex():   What is the improvement you would like to see?  Please add options to enable/disable all flags.   Please start with standard behavior which matches other tools.   Why is this idea important?  At the moment, with singleline option enabled, the result of a Regex search in Jmp differs from what the user expects after debugging the Regex search outside of Jmp (unfortunately, there is no Test system in Jmp which can be used to debug Regex searches): Regex: disable singleline option  So, it will be highly beneficial once  - Jmp behaves the same as the other tools. - Jmp allows all options which the user finds in other tools.         more wishes submitted by   ... View more

https://community.jmp.com/t5/Discussions/linked-data-table-how-to-cut-the-quot-link-quot/m-p/573180#M78213   Summary Tables and Subsets have an option to "link" the new table to the original data table. "Data views" have such a link enabled by default.   Cool: Row Selections and changes to the values are automatically linked between the tables.   But sometimes one needs to remove such a link  - to add additional rows to the main table - edit entries in the columns which were used for summary grouping - to rename columns of the linked table ...   my wish:  remove the link via right click on  and click on a command like "cut the link".   workarounds: - generate a (100%) subset of the linked table and delete the linked table itself - a Links cannot be saved, so, one can save the tables, close both tables and open the "linked" table again - without the link.   more wishes submitted by   ... View more

I would like a button in Graph Builder that opens a table, like shown below, that allows me to change all of the major font settings in Graph Builder without having to go into each axis separately or even into the main Preferences.   I like the CTRL - SHIFT - +/- functionality, but that doesn't solve everything (especially as it enlarges everything in JMP which I often don't want).       Maybe there could be more subgroups than shown in my table for which to change all settings at once. ... View more

Please implement native Polar plot platform. Also called Radar Plot, Star Plot etc. There are some work arounds that you can find, for instance a cylindrical 3D plots add-in from Mr. Brady Brady (@brady_brady), but a native platform with all the usual controls over lines, markers, colors, point selections etc. would be much better. Something like this: or this (this one is from Mr. Xam Gregg's blog post):   This is actually, an illustration how would reference range look on this kind of plot:   If something like that already exists, I apologize and please help me find it. ... View more

What inspired this wish list request? This is inspired because JMP classes have special REPR functions ( _to string_ and _show_ ) that are quite nice.  I work with many namespaces that exist hierarchically -- as it, they refer to each other via child / parent relationships -- and if I accidentally cause one to be printed to the log then JMP will effectively crash as it attempts to write tens of billions of lines to the log (a few times I waited many hours to avoid lost work).   What is the improvement you would like to see? If namespaces had a REPR override then it would be very nice!  If I have either the name _show_ or _to string_ within the namespace, I'd like it to use those names just like classes use.     Why is this idea important? For me it is important because I use namespaces extensively, and primarily when errors are throws if I could easily print the current namespace and have it show a descriptive REPR that I've implemented that would be awesome, but mostly I don't want JMP to effectively crash when I accidentally print the raw namespace (again, because it circularly refers to many dozens / hundreds of other namespaces)   ... View more