JMP Wish List

☑ cool new feature ☑ could help many users! ☐ removes a „bug“ ☐ nice to have ☐ nobody needs it   What inspired this wish list request?  The Group By concept in Jmp is sooo useful! You can find it everywhere. e.g. in Graph builder one can use X/Y groups to generate split graphs - and summary statistics will automatically give the correct results for every single graph. In Platform menus, there is a By option - which splits the data into groups and every group is analyzed separately. Under the porcellain layer, there are more group by options, like the Col aggregation functions (e.g. Col Median(:height, :sex)) which automatically return separate aggregated values for groups of rows.   What is the improvement you would like to see?  Please use such Group By options wherever it is possible. let's see if other users find more places where Group By could be useful ...   here I want to focus on a Col Grouped Interpolate function which can be used in a Column Formula like New Column("interpolated", Formula(Col Interpolate(:newX, :height, :weight, by(:sex)))) It should generate an interpolation for :weight by :height - split by subgroups M/F in :sex - and use the interpolation to calculate values @ x values :newX.   In a similar way, the existing Interpolate function could be lifted to a new level by providing an argument  BY() which can be used to interpolate subgroups [for this case, I think an additional argument for()is needed to specify the groups of interest and their order] Grouped Interpolate    Interpolate(myheight, :height, :weight, by(:sex), for({"F","M"}))   Definitely worth to have it - which can be seen by the fact that users invested the time to program their own grouped Interpolate to get the results: https://community.jmp.com/t5/Discussions/Grouped-Interpolate/m-p/692358/highlight/true#M87807    Why is this idea important?  Group By is one of the concepts which makes Jmp a million times more useful for exploratory data analysis  than Excel . use this concept at as many locations in the program as possible.         more wishes submitted by   ... View more

☑ cool new feature ☑ could help many users! ☐ removes a „bug“ ☐ nice to have ☐ nobody needs it   #myTop10_2022   Please add this functionality to JSL editor:   When a user Double-Clicks a bracket, the code inside the brackets is analyed, clustered ind highlighted with differnet colors. Example for "if": - conditions are highlighted green to separate the code blocks in-between - else code is highlighted red to separate is from the other code https://community.jmp.com/t5/Discussions/JSL-if-else-gt-find-the-commas/m-p/573510/highlight/true#M78251   Similar highlighting could also be applied to many  other functions: Match: highlight each match to separate the code blocks. Substitute: highlight the search patterns to separate the replacement blocks ...     more wishes submitted by   ... View more

What inspired this wish list request? A change was noticed in upgrade from JMP 17 to JMP 18 where all table column names are automatically alphabetized rather than following programmed order.     What is the improvement you would like to see? Return to previous setting where the table column order is how the table was built.     Why is this idea important? Increased burden on large tables to reorder.      ... View more

☑ cool new feature ☐ could help many users! ☐ removes a „bug“ ☐ nice to have ☐ nobody needs it   What inspired this wish list request?  edit: first part shifted to Expression Indexing: How to climb the Expression Tree?  Thanks @jthi for providing a solution: Via  Extract expr a user has the possibility to search and extract parts of Expressions. The function provides a pattern search and returns the first match.   Even Wildcards are possible :)   What is the improvement you would like to see?    A mixture of Display Tree Indexing and Data Table Indexing - just for expressions:   A more precise read access via: dt = Open( "$SAMPLE_DATA/Big Class.jmp" ); myExpr=Expr(gb = dt << Graph Builder( Size( 437, 413 ), Graph Spacing( 4 ), Variables( X( :height ), Y( :weight ), Y(:height), Overlay( :sex ) ), Elements( Points( X, Y, Legend( 1 ) ), Smoother( X, Y, Legend( 2 ) ) ) )); //instead of: Arg(Arg(Arg(Arg(Arg(myExpr,2),2),3),3),1) // I want to use: myExpr[2][2]["Variables"]["Y"(2)][1] //assign // send // Graph Builder // Variables // or like it's possible for Display Trees: myExpr["Variables"]["Y"(2)][1]   Where it gets really cool: write access similar to what's is possible via Data Table Indexing: myExpr["Variables"]["Y"(2)][1] = Expr(:height); Like Substitute - but in a different dimension! [edit] And maybe the best application of Expression Indexing:  Insert Into , e.g.: Insert Into ( myExpr["Variables"], Expr(Y(:age))) Why is this idea important?  With the Power of Expression Indexing, Expression Handling in Jmp will get easier :)         more wishes submitted by   ... View more

Hi,   Could it be possible to implement a new function for encrypt and decrypt multiple files ? A way to encrypt or decrypt multiple files which have the same password. Could be very interesting.   Thanks Regards Guillaume ... View more

What inspired this wish list request?Managing a large number of jmp installations can be complicated when it comes to updating and /or harmonizing versions within a company.   What is the improvement you would like to see? On major release installation, it will be fine if InstallShield could ask this question: An older jmp version was detected, would you like to install the new version (and keep the old one) or update jmp?   and something that will be good too, keep the users preferences on major update from old to new release.     Why is this idea important? Facilitating the deployment of jmp in companies where the software is managed ... View more

☑ cool new feature ☐ could help many users! ☐ removes a „bug“ ☐ nice to have ☐ nobody needs it   #myTop10_2022   If a column is set to "multiple response", there are cool options available in the data filter menu: These allow the user to get much more power out of the data filter. Most of them rely on the fact that there are "multiple responses" in the column - and the user can select which combination he wants. There is also an option "none". It has the same effect as the "inverse" - but the difference is that "inverse" just inverts the current selection, but "none" is a setting which is applied in the background. With "none" fancy Data filters are possible along the idea: THIS, but not THAT: https://community.jmp.com/t5/Discussions/Conditional-Data-Filter-for-modeling-type-Multiple-Response/m-p/556062#M77004   Unfortunately, for standard columns, there is no "none": https://community.jmp.com/t5/Discussions/advanced-data-filter-arithmetic-just-available-if-the-column-is/m-p/556682   Every Jmp user who worked with the cool functionalities of multiple response columns (esp. the availability of "not") feels an incredible lack of functionality when working with standard columns.   my wish: Add "not" also for standard data filters.     more wishes submitted by   ... 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?  In JSL there are functions like  is control key() to get the current status of modifier keys,   unfortunately,  This function does not return the current state of the control key but rather the state of the control key at the start of another event like mouse click or key press.  Checking for modifier keys (ctrl, alt, shift) in script without mouse trapping      What is the improvement you would like to see?  As  JMP does have an internal function to get the modified key state at any time but this is not exposed via JSL. Checking for modifier keys (ctrl, alt, shift) in script without mouse trapping  ... could you please provide a JSL function to expose the current status of a modifier key :)     Why is this idea important?  This will allow JSL programmers to generate Toolbars and commands in the menu on a completely new level: depending on the status of a modifier key, different actions could be triggered (!!!)   similar add-on functionality could also boost standard platforms: - A user could specify a DEFAULT action in the preferences. If a user clicks on Subset, Summary, Tabulate, Graph Builder - holding SHIFT - the DEFAULT action is executed ... without any need to manually enter the settings. - with a control key, the action could be triggered with the RECALL settings.   other wishes from  ... View more

It would be great if you added in SVM modelling capability to the JMP Pro predictive analytics platform.  I would prefer to run this directly in JMP rather than having to use R add ins, etc.  Even a JSL scripted add in would be helpful. ... View more

Most of my other editors allow Ctrl Shift Z to be a redo.  When I do Ctrl+Shift+Z in JMP, I get some weird      Definitely not ideal as it just wipes out my redo stack.   I can't edit it through toolbar customizations using the builtin edit:redo, but I do have a workaround with JSL   mainmenu("edit:redo");   Possible to add undo/redo shortcut buttons to toolbar? reminded me of this.         ... View more

With omics datasets becoming the norm, JMP needs a straightforward way to visualize high-dimensional data... Tsne and UMAP are becoming the norm for this purpose, PC analysis just won't cut it for publication. The availability of Tsne and UMAP as native tools in JMP would make a world of difference for those of us who don't want/know how to work with R or Python!!!  Thank you for your attention L.   ... View more

Our company is now using automated scripts in JMP connecting to our Laboratory management system, LIMS, to pull data for SQC reports.  These need to be reviewed for 'bad data' prior to sending to customers.  Samples undergo multiple tests which need to be arranged in columns - 1 row per sample.  Most of the 'bad data' relates to a single test (maybe a typo or a measurement special cause) so we don't want to exclude the whole suite of testing just to remove that single point. JMP's row structure to data currently means the only way this is possible is to exclude values in column properties or delete the value from the cell.   ... View more

☐ cool new feature ☑ could help many users! ☑ removes a „bug“ ☐ nice to have ☐ nobody needs it   #myTop10_2023 we have a workaround -> I 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

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

☑ 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 a „bug“ ☑ nice to have ☐ nobody needs it   What inspired this wish list request?  How does one perform Bitwise operations in JMP formulas?  How do I perform bitwise xor operations between columns with 44-bit binary data?    What is the improvement you would like to see?  Native function for bit operations like XOR, shift bits, split bits, get bit, set bit.   Why is this idea important?  could help users who want to do bit operations in Jmp.   more wishes submitted by       ... View more

This would help for example when making numeric encoding for character values. Dense Rank (wikipedia) or calculating orders For example scipy.stats.rankdata offers average, min, max, dense and ordinal ... View more

I have tried to use different state handlers JMP provides, but the more I use them the more I notice issues with them. There are many reasons why I would like to use them and maybe even more reasons for me to avoid them. Biggest issue is usually that they seem to trigger too many times and value returned is not that helpful.   Subscribe To Data Table List() is fairly good example on how most of these should work. You can add different functions to different events (sometimes it is a hassle though). You can imagine how well Subscribe To Data Table List() would work if it would trigger every time something happens to data table list (add, remove, rename) and it would return only data table name for example (or number of data tables changed...) and nothing more.   Below are some problems and suggestions: Hover Label Problem Seems to get triggered when you move close to the point you want to hover over. This causes multiple triggers and slows down JMP unnecessarily and sometimes this slow-down is quite big. Also triggers immediately when you hover over point -> if you move mouse fast over multiple elements it will trigger multiple times. Also triggers multiple times on hover over (could be related to all of the things mentioned earlier) Suggestions Make it more accurate when hover label triggers. Add possibility for "delay" when to trigger event, for example I would like to be able to trigger hover label after user has hovered over same element for 0.2s. Also allow selection of "safe-zone" to determine when hover label should even trigger.   Row State Handler Problem Triggers too many times and all events. Has a bug where you remove row, the row state handler seems to get removed. Suggestions Most likely would be enough if there was a way to capture only specific row state changes (and fix the bug).   Filter State Handler Problem Triggers too many times. One example is that if you even look at the filter the state handler will trigger. Suggestions Remove unnecessary triggers from Filter State Handler or give possibility to choose which states should trigger which function.   Scheduler Problem Can have only one scheduler at the time and you cannot hide the scheduler window. Suggestions Allow creation of private schedulers (currently I hide the window and hope that user won't close it) and multiple different schedulers at the same time. ... View more