JMP Wish List

Are there any plans to integrate GAMs (Generalized Additive Models) to the predictive modeling platform. Since the procedure already exists in SAS, one would think it might be reasonably easy to port it to JMP. Many thanks, Yves P. ... View more

☑ cool new feature ☑ could help a lot of Jmp users! ☐ removes something that feels like a „bug“ ☐ nice to have ☐ nobody needs it   #myTop10_2024   What inspired this wish list request?  With the new seamless Python Integration in Jmp18 , it's now much easier to transfer small tasks to Python.   e.g.  - JSL: read a file - Python: compute new columns - JSL: make Principal Component Analysis - JSL: Plot Data in Graph builder - use Make into Data Table -> dt2 - process dt2 in Python ... - JSL: plot the result in Jmp   Such a ping pong between Jmp and Python was already possible before, option 1) Use inline Python code within the JSL code -> very hard to debug option 2) write the actual code in Python , 'import' is as a whole via JSL   new: write the main code in Python - with some JSL calls within the Python code. -> same issue as with option 1: hard to debug the inline code (slightly reduced issue as JSL is not as strict with the indentation as Python)   What is the improvement you would like to see?  Please allow Workflow Builder to accept JSL and Python code.   At the moment, the Workflow GUI asks for JSL code:   Just add an option to choose between JSL and Python (or any other code which is allowed ...)     Why is this idea important?  It will help in both directions::  - facilitates Python integration (Python can be included as an intermediate step without additional effort) - significant improvement for Workflow Builder (no limits)     more wishes from     ... View more

☐ cool new feature ☑ could help many users! ☑ removes something that feels like a „bug“ ☐ nice to have ☐ nobody needs it   What inspired this wish list request?  A task that puzzles many new Jmp user at some point: how to create a formula column with a column reference (or a constant) that is pre-defined and stored in a variable. Use for loop variable in a formula  Use expr() to replace variable column names in a formula  JSL: How to pass a variable to a column formula  New Column Formula with JSL  How to use a variable value in a formula  Need help with expressions, column references, formulas and column renaming  Creating Formula Columns in a For Loop  Apply a formula from a list  Adding Formula Columns based on Column Name List    The good news is that an experience user can choose from a range of solutions: Insert one expression into another using Eval Insert, Eval Expr, Parse, and Substitute   On the other hand, before a user gets aware of the issue, reads the manual, finds a community post or asking for help in the community, ...  he will just start with the most simple approach: use the bare column reference (or constant) within the formula.   Then Jmp will display an error, the column formula will not work - or the formula will not work anymore after a restart of JMP.   What is the improvement you would like to see?  For an experienced user, it's very easy to identify the issue and to correct it.   So, maybe, a Jmp "Copilot" could detect the issue as well and guide the user to a solution, e.g. by providing a link to Insert one expression into another using Eval Insert, Eval Expr, Parse, and Substitute   Is it possible to automatically correct the code? via right click, maybe Jmp could automatically add an  Eval(Substitute(...)) which replaces a placeholder with the variable that was defined outside of the column formula.   Why is this idea important?  New users will lose less time identifying the error + searching for a solution.   The application case of a column reference in a column formula is the most common use case, but in principle, the same Copilot could also detect and fix similar issues where variables are not evaluated before handing them over or where variables are evaluated too early before they are handed over to the next function.   more wishes by   ... View more

☐ cool new feature ☑ could help many users! ☑ feels like a „bug“ ☐ nice to have ☐ nobody needs it   Short: Remove this "bug": ... and this one:             Long: What inspired this wish list request?  If reports are open, Jmp is not able to sort a data table: https://community.jmp.com/t5/Discussions/How-to-update-table-after-sorting/m-p/659014/highlight/true#M84836    Same issue for data tables with linked subsets: sorting and concatenating data to the data table doesn't work. Similar issue if a user wants to add rows to a data table .   linked subset: sort → no add rows → no concatenate → no   open report: sort → no add rows → yes concatenate → yes   What is the improvement you would like to see?  Please remove the restrictions.   e.g. "cut the link", like it's done for linked summary tables: sort → no [why does SORT not "cut the link"?!?] add rows → yes² concatenate → yes²   ² JMP automatically cuts the link:     Why is this idea important?  It's very likely that a user opened a linked subset, a linked summary table or a report before he tries to sort a table or add new rows. Therefore, JMP users face this issue very often.       more wishes by     ... View more

☐ cool new feature ☑ could help many users! ☐ removes a „bug“ ☐ nice to have ☐ nobody needs it   What inspired this wish list request? The Query Builder in Jmp is nice to generate SQL queries via a GUI. But there are queries which cannot be generated via the GUI: Database access  With JMP 17, In the query builder, how can add "WITH UR" at the end of the SQL code?    The only solution at the moment: change to custom SQL - and at that moment lose all GUI options to make further changes to the query.   What is the improvement you would like to see?  Please improve the GUI to provide advanced SQL option: - add the functionality to "explode" entries and "index" column entries - allow the user to manually enter advanced SQL strings - which then can be added at specific positions of the main SQL query string.     Why is this idea important?  Users are not forced anymore to abandon the Query Builder when they have to add an expression to their query which is not supported by the Query Builder GUI.         more wishes submitted by   ... View more

All our data is generated in the form of stdf files.  This is a type of binary file used in the semiconductor industry.  We currently must rely on a third party add-in to convert the stdf into a JMP table.  It would be nice to have this capability integrated into JMP. ... View more

similar wish: Add CDFs to Graph Builder    ☑ cool new feature ☑ could help many users! - especially in semiconductor industry. ☐ removes a bug ☐ nice to have ☐ nobody needs it   What inspired this wish list request? Short: The summary statistics option in GraphBuilder are amazingly useful. but it could be even more powerful ...   What is the improvement you would like to see?  Please add an option for Cumulative Probabiltiy - [edit: more general maybe even a setting which allows us to specify the plotting positions:   Why is this idea important?  Other tools give the user the possibility to adjust the way the plotting positions are calculated. ... View more

☐ cool new feature ☑ could help many users! ☑ removes a „bug“ ☐ nice to have ☐ nobody needs it   #myTop10_2023 we have a workaround -> don't need it anymore.   What inspired this wish list request?  Short: Tables/Update and Tables/Concatenate destroys my source scripts. STOP THEM !!! Long: Many of the Platforms in the Tables menu provide the option Save Script to Source Table. Is is an elegant way to save the command with all the settings as a Table Script Platform_Name Script. There is even an auto-increment function which prevents Jmp from overwriting previous Table Script with the same name.   But there are two exceptions: Update and Concatenate. As all the other functions, Concatenate saves the command script as a Table Script (name: source) to the output table. Exception: If the option Append to first table is enabled, the main table is the output table - and NO script is saved (perhaps to prevent Jmp from over-writing an existing source Table script?)   For Update the main table is always used as output table. This function saves a table script with the current settings (name: source) to the main table and thereby: overwrites any existing source table script (!). Table / Update - source script collision      What is the improvement you would like to see?  Concatenate and Update should follow the naming scheme of the other Table platforms. i.e. save a script with the current settings to a Table Script with name Concatenate Script or Update Script. An auto-increment feature should be used to prevent Jmp from overwriting existing scripts.     Why is this idea important? The auto-generation of JSL source code is a great feature. But over-writing an existing source code is more ham than good . Fixing the issue will save users from losing their table source script.   The naming convention separates source scripts (name: source;  was used to generate the data table) from Platform Scripts (name: Script; can be used to act on the current data table) ... View more

☐ cool new feature ☑ could help many users! ☑ removes a „bug“ ☐ nice to have ☐ nobody needs it     To stop all formula evaluations, the user can click on "Suppress Formula Eval" in the table red triangle menu: https://community.jmp.com/t5/Discussions/stop-all-evaluations/m-p/529859/highlight/true#M75318   But sometimes, jmp is so busy to run the evaluations (stuck in a loop?) that it's almost impossible to get to the menu.   my wish: a keyboard shortcut to stop all current formula evaluations. --> the user can press it continuously till jmp gets the info end stops the evaluation (like pressing Esc continuously if a JSL code is stuck - after some while, JMP detects it and stops the code)   btw: there is a command rerun Formulas in the same red triangle menu. But this button just works if "Suppress Formula Eval" is not activated for the table. my wish:  rerun Formulas should rerun the formulas every time the user clicks on rerun Formulas - even if "Suppress Formula Eval" is activated.     more wishes submitted by   ... View more

have an input where you tell JMP what your factors and responses are and it looks at all of the data and suggests which models would be best to look at first. I've put AI in the title but it also incorporates pattern learning machine and deep learning techniques.    This is essentially joining the neural network, model comparison and all other analysis methods into one interface. It could learn which methods & algorithms are best for the work an individual usually does and how the data is displayed as plots/ graphs.  SAS uses Machine learning so the knowledge is already within the company https://www.sas.com/en_gb/insights/analytics/machine-learning.html   David ... View more

Currently depending on the size of data / data structure which I want to get the uniques from I use following: Data table column values Associative Array (if I'm lazy, but gets slow with lots of values) Summarize (a bit better, also slows down) Summary table and get values (I can get counts this way if I want to) Distribution platform and get values from Report layer (nice thing with this, is that I can get other statistics at the same time and it is fast) Lists Associative Array Insert values to table and use methods mentioned above My suggestion is to add specific function to get unique values from from data tables and lists in a list/matrix. It could be also data structure like Python's Set (and if were to be data structure  A set is an unordered collection with no duplicate elements. Basic uses include membership testing and eliminating duplicate entries. Set objects also support mathematical operations like union, intersection, difference, and symmetric difference. ... 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

I think it would be awesome if texteditbox() had the ability to have a list of values that it would search from and give a listbox (without messing up layouts) below where you could select possible options. I'm thinking like google or whatever.    something like this Names default to here(1); new window("Test", teb = texteditbox("") ); teb << Set AutoCompleter List({"face", "John", "Denver", "head", "heat"}); // I imagine it would have other flags like teb << Set AutoCompleter Match("All"|"Start"); Where if the match were all it would look like And if it were start it would look like     ... View more

What inspired this wish list request? In using the Variability Charts frequently, there are numerous issues I have in being able to customize the plots flexibly and dynamically. Often, I must settle for what's available since the customizations aren't ideal. The customizations are also hidden in many cases, limiting their potential for more casual users of the platform.   What is the improvement you would like to see? Below is an itemized list of pain points that can be improved to enhance the user experience when using the platform.   Why is this idea important? Variability Charts still get used a lot but have had less development work. They work well with many cases with nesting and many of the visually appealing features are simpler in this platform. Nesting works better and more naturally in Variability Charts than in Graph Builder.   1. The top chart with the raw data is clunky when customizing the Group Means and Connect Cell Means. You need to right-click then Customize in the white space of the graph, which is hidden for most people. Once the Group Means is found, it doesn’t really work since the reference is actually a purple line that doesn’t match what’s in the graph. It would be best if the legend in the top right could be interactive as it does in Graph Builder (Overlay, Color) or Fit Y by X (Compare Densities graph).   2. The default Std Dev chart has no separation panels. If there are at least 3 X variables and I add the Group Means for Std Dev, the grids will enter for all X variables. The grids should match the X variables shown. A snippet of this output is shown below (only Operator was selected).   3. The color of the Group Std Dev cannot be changed. There is also no customization if multiple X variables are chosen for colors, line styles, or line widths.   4. The drag-and-drop feature of the X variables in the nesting of the plots is very useful and flexible. An additional feature to consider would be to remove an X variable (likely because it seems unimportant) rather than rebuild a new plot with the variable removed. Another similar feature would be a way to add an additional X variable as well.   5. Adding a Row Legend can be an effective enhancement to visualizations, but it works best the same way the Overlay/Color functions in Graph Builder work. When applied in Variability Chart (and other platforms) it is applied globally, which is likely undesirable. If you customize the colors in the Row Legend, but then save the script, there is an error, and it will revert back to the original Row Legend values.   6. A smaller issue I have is with the variance components. The 20/40/60/80 % labels for the graph seem like a good idea, but they tend to just be smushed together and not really add clarity. You could argue that removing the label would be similar to how the Effect Summary displays the p-values in the Fit Model platform where you have hashmarks representing 0.1/0.01/0.001, etc. ... 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.  In many industrial processes, it is common to assess multiple quality characteristics simultaneously. These characteristics often exhibit correlation. Introducing multivariable process capability into JMP would be beneficial to practitioners, allowing for a more comprehensive capability analysis that considers these correlations.   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.  I propose the addition of multivariate process indices and corresponding visualizations to the JMP Quality platform. These tools would enable users to assess multivariate process capabilities more effectively. This functionality is available in StatGraphics software (documentation and screenshot attached).   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,…). Many processes require simultaneous evaluation of multiple dimensions for effective quality control. The ability to consider correlations between quality variables in capability assessments is important. Implementing multivariable process capability in JMP would offer a valuable tool for holistic process performance assessment.   @PatrickGiuliano thanks for the support!   ... View more

The current JSL log that is displayed on an error is lacking. Currently, it displays the following: What type of error was thrown What line threw the error (but not what file the line is in) The body of the JSL file that was run (the entire body, even if it is extremely long) Sometimes, a highlight in the body of the JSL file that was run indicating the line that threw the error. This does not always work.   It would be more informative to get the following debug information: What type of error was thrown A stack trace of the calling functions, with details on which line in each calling function threw the error. There's really very little value in getting a printout of the JSL file with the highlight when you can read through the file yourself and look for the erroring line. It takes up space in the log and makes me scroll past it to see the actual error that was thrown. ... View more

What inspired this wish list request?  Unnecessarily removed feature in JMP18 when compared to earlier versions...     What is the improvement you would like to see?  Bring back Clear Row States when you right click on Rows. I don't want to always Select all -> Clear Select row states. That item is still found from Rows menu, but not from right click menu   JMP18   JMP17   Why is this idea important?  Makes it easier to clear all row states like it was in earlier JMP versions     ... View more

☑ cool new feature ☑ could help many users! ☑ removes something that feels like a „bug“ ☐ nice to have ☐ nobody needs it   #myTop10_2024   Short:  Let JSL Editor show which function evaluates it's arguments and which function doesn't!   Long:   What inspired this wish list request?  There is a very powerful behavior in JSL which, on the other hand, makes it difficult for new users to get started without hiccups: Some Functions evaluate their arguments and others don't.   This is very important for functions which are used for expression handling. There is a wonderful lecture by @joseph_morgan :   on the differences, how to live with them and how to use them to develop efficient and robust applications.   ...  describing the status at that time: Jmp 14 [2018]: This doesn't exist in the documentation. This is something I figured out [ ] by reverse engineering the behavior of expression handling functions. Trust me, [ ] if you do not think of these functions in this you will never get them right.   Besides the expression handling functions listed here, the same holds for all function: if you do not think of these functions in this you will never get them right: It's highly important to know if an argument gets evaluated before the function call of not.   Does this code work or doesn't it?!? dt = Expr(current data table()); myscript = Expr(get script()); dt << myscript   Unfortunately, for the JSL scripter there is no hint how the function behaves - does it evaluate its arguments or not? Maybe it just evaluates one of the arguments? Who knows? The user has to know! ... or: reverse engineering the behavior of the respective functions.   What is the improvement you would like to see?  Please implement some syntax highlighting to indicate the different ways a function evaluates - or doesn't evaluate its arguments. Add-On: Please also indicate the difference in the Scripting index.      In JSL editor, the highlighting can be activated/deactivated via a keyboard shortcut.   The Expr(_x_^2) show kind of dilemma: the argument of Expr () doesn't get evaluated. But the two arguments of ^ would get evaluated. Maybe the highlighting reacts on the position of the mouse or cursor -  just the arguments below the branch are highlighted where the mouse/cursor is currently located.   Why is this idea important?  With the new syntax highlighting, JMP will guide the user automatically to generate the right code. The user doesn't have to run the code to get an error message - or to see the wrong result ... or to reverse engineer the function - like @JosephMorgan had to do to prepare his paper.   other wishes from  ... View more

What inspired this wish list request?  Table variables are nice place to store information which users can then access as table variable or use in formulas. Currently we are limited to text and numeric values which limits the usage and requires workarounds save matrix as table variable?    What is the improvement you would like to see? I would like that Table Variables would support all JMP data types (or at least lists, matrices and associative arrays). Currently we have to use workaround where we convert these into string and then back to the original datatype using Parse() Names Default To Here(1); dt = Open("$SAMPLE_DATA/Big Class.jmp"); dt << New Table Variable("Day_mat", Char([42 43])); m = Parse(:Day_mat);   Why is this idea important? Makes table variables more useful without the requirement to use workarounds which might or might not work.     ... View more