JMP Wish List

I really like the new feature in JMP 15 showing the distributions below the headers. Yet, for time series (sensor data), distributions are not enough.   It will be great if we can also add spark-lines (Excel and many other software have them). ... View more

What inspired this wish list request?     What is the improvement you would like to see?              <<Visibility("private") <<Visibility("invisible"/"hidden") <<Visibility("visible")       Why is this idea important?      ... View more

I would like to suggest the ability to force MFI to combine files together, even if it finds differences.   Use Case: I am combining data from two instrument platforms where the data is set up identically, but the differences are enough that MFI separates the data into two tables if I have both instrument platforms. I am aware of all pertinent differences, and just want to leverage MFI for high quality, quick combination. I would like a radio button to 'force into one file' along with "Stack Similar Files" and "One Table for Each File".   While JMP does an amazing job most of the time, sometimes I know better than JMP ;) ... View more

Exactly the same line up box we have now, except that we fix the number of rows and let the number of columns adjust based from data input.   It will be populated per column. I.e, Fill 1st column first from top to bottom, then create 2nd column and fill from top to bottom, repeat added all elements. ... View more

Many DOE's need to be peformed over several days so considering and separation of random time variation in DOE analysis is an issue. As stated by Goos & Jones Randomized blocks in DOE are very useful to absorb random variation so fixed effects can be precisely estimated. However in the JMP forward stepwise parameter selection module random effects can't be included; all blocks, also random time effect blocks, need to be treated as fixed effects. In forward selection it would be a major imporvement to also allow random effects so the old cumbersome backward selection can be avoided. ... View more

What inspired this wish list request?  Currently, within the Concatenate function, columns to be concatenated have to have exactly the same header (including case). Frequently, there are small differences or typos which JMP interprets as being a different column. This can be rather frustrating and slows things down.   What is the improvement you would like to see?  The concatenate function to have an extra window where the user can state which columns are matches for each other (I'm thinking it could be something similar to the Group function within Recode)- for each file you're concatenating you could have a list of columns and you could select your columns to match and click a "match" button. If JMP could suggest matches (and show its suggested matches) before producing the new data table that would be useful too (and help catch the odd typo)   Why is this idea important?    It smooths out the Concatenate process and saves you time instead of having to change all your column headers to exactly match.   ... View more

This would fall under a small "quality of life" improvement but the legend for a stacked bar chart is always in the opposite order of what one would intuitively expect when going scanning from top to bottom (the top item in the legend is the bottom item in the stacked bar) . If that isn't changed it would be nice to have a "reverse" order button in the legend settings box, similar to what is available when changing the Value Ordering property for a column. ... View more

Similar to this: https://community.jmp.com/t5/Discussions/Automatically-shows-Show-filter-option-in-every-window/td-p/186559   Would want this in at least the formula view and the graph builder view.    ... View more

Fit model allows the user to set up and launch an analysis but not close the launch window.  This is useful when iterating through many versions of a model.  Add this check box (but leave it unchecked by default) to every platform. ... View more

There are a lot of forum posts about how to get results from reports.  This could be made easier by adding some attributes to the display tree and defining two new functions that would do most of the work for the user.  I propose this syntax:   platform = Fit Model( ... ); platform << Get Result( "BIC", fit("NormalLassoAICValidation") ); //returns [0.683248] Display Tree Attributes Define a set of result types that is standard across all platforms. This will be a big list, but if two platform both report an adjusted R2, they should both use the same result type. Add the result type to an attribute in the display tree for the column, cell, and/or anywhere else it is displayed, similar to the helpKey attribute for some platform outlineboxes. Display the result type somewhere in the platform GUI, maybe in a hover label for everywhere it is displayed Do something similar to flag outline boxes containing a fit created by the model (think '...fit with 6 components' in PLS or 'Normal Lasso with AICc Validation').  Here the attribute would be specific to the platform. Functions Create functions to get The result values The report element containing the result The report element of the fit The scriptable object of a fit Call them like this platform << Get Result("AdjustedRSquared") //Matrix or list of all Adjusted R Squared values platform << Get Result("AdjustedRSquared", fit("NIPALS_1")) //Matrix or list of all Adjusted R Squared values in fits with NIPALS_1 platform << Get Result("AdjustedRSquared", fit("NIPALS_1"), fitnumber(1)) // Matrix or list of all Adjusted R Squared values in the first fit with NIPALS_1, should be exactly one value platform << Get Fit("NIPALS_1") //returns the scriptable object platform << Get Fit("NIPALS_1","object") //same platform << Get Fit("NormalLassoAICValidation","report",fitnumber(1)) //returns the report from the first fit with NormalLassoAICValidation These functions these could be variations of wrappers around XPath: platform << XPath("//NumberColBoxItem[@ResultType='AdjustedRSquared']") platform << XPath("//OutlineBox[@Fit='NIPALS_1']") platform << XPath("//OutlineBox[@Fit='NIPALS_1']") << Get Scriptable Object fm << XPath("//OutlineBox[@fit='NIPALS_1']//NumberColBoxItem[@ResultType='AdjustedRSquared']")   ... View more

What inspired this wish list request?  JMP version 17.1 PRO I have a problem with the scale of the prediction profiler. The scale of "H" should be between 0.3 and 0.7. Suddenly it moves its target to 1.5 when I remove "h". The problem happens when I remove "h". Before "h" was removed, the profiler was "normal". The profiler seems to get confused by "h" and "H".     What is the improvement you would like to see?  I would like some warning when two columns names are simuilar like "H" and "h" there could be problems when using them as a factor in a model. Or better the problem fixed.   Why is this idea important?  I used a lot of time testing what is problem was.   ... View more

☐ cool new feature ☑ could help many users! ☑ removes a „bug“ ☐ nice to have ☐ nobody needs it   #myTop10_2022 ➜ Jmp18 :)     Get rows where is extremely slow if the column is referenced with a varible (here i=5 ) i = 5; dt << get rows where( As Column( dt, i ) == 999 ); instead of a direct reference like in dt << get rows where( As Column( dt, 5 ) == 999 ); My wishes: Is it possible to "fix this issue in the background"? e.g. by a setting in the preferences: "hereby I confirm that JMP is allows to pre-evaluate variables to speed up code execution - accepting that this could lead to unintended/unusual behavior" (I am not good enough in JSL programming to predict all the collateral effects - would such a mode make sense?) If fixing the issue in the background is not possible, could you please implement a warning function in JSL such that the user gets informed about the bad performance due to non-pre-evaluated variables. Then he can adjust the code, with substitute Should you Loop through a data table or use Recode, or use Get Rows Where to change values in a data table  or Eval: https://community.jmp.com/t5/Discussions/Should-you-Loop-through-a-data-table-or-use-Recode-or-use-Get/m-p/580751/highlight/true#M78769        more wishes submitted by   ... View more

What inspired this wish list request?  Displaying tables with decimal numbers can be confusing when there is a large number of digits.   What is the improvement you would like to see?      Possibility of setting the default number of decimal places displayed in the table (for example, limit the default to 2) in the preferences. It will avoid us to do it for each table or desired columns (even if the « Standardize Attributes » helps)   Why is this idea important?    Help readability in JMP tables;     ... View more

In JMP 13.2.1, JSL script "Open Database("DSN=mysql", sql)" is much slower than running the same "select" sql query on MySQL workbench or at mysql command line on same pc.  DSN points to MySQL ODBC driver installed locally in my win10 pc, (mysql-connector-odbc-5.3.7-winx64.msi).  The loading speed difference is very noticeable when "select" would return many lines such as 1 million line of data.  Wish JMP would improve this data connection and loading speed in next release. ... View more

I would like to see an option for formulas to ignore excluded rows without having to build this into the formula using the "exclude state" formula function.  I think the easiet way for this to be implemented is to have it as a column property option in the formula column property option box So just one more check box here that would say "treat excluded rows as missing"   Thanks for considering this request.   Steve ... View more

What inspired this wish list request?  Multiple file import and open functions are able to save a list of files they open in a list. I'd like to see something similar with functions that can generate multiple columns from one, mainly text to columns    What is the improvement you would like to see?    saving text to column to a variable saves a list of column names generated to a list.   Example: A dt containing a column of numbers separated by commas new_cols_list = dt << Text to Columns( columns( :Numbers column ), Delimiters( "," ) );   Why is this idea important?  This would allow more compact identification of generated columns, and therefore more streamlined, and less error-prone way of working with these columns, if needed   ... View more

We need access to a much larger library of functions to choose from for the hidden layers of a neural network. It would also be great to be able to input custom functions and their derivatives. ... View more

☐ cool new feature ☐ could help many users! ☐ removes a „bug“ ☑ nice to have ☐ nobody needs it     If columns have to be visible all-time, independent of the actual position in the data table. one can lock them on the left. To do so, one has to select the columns and click on Scroll Lock/Unlock in the Col menu. https://community.jmp.com/t5/Discussions/Collection-of-quot-funny-quot-JSL-newbie-questions/m-p/575687/highlight/true#M78385   my wish: Could you please add this command also to the context menu which is opened by selecting columns and right-clicking. here the command can be found much easier.   ... View more

Is it possible to add an open text field to the Define tab in Easy DoE, so that the problem you are trying to solve can be stated? Perhaps this also could be included on the top of the report tab? This would make it possible to connect the designs to different projects, teams, purposes or other reasons. ... View more