JMP Wish List

Hi, I'm looking at the Profiler red triangle, under Optimization and Desirability -> Set Desirabilities. Several of our newer users get confused when they have multiple y variables because JMP pops up a separate modal box to set desirability for each response one at a time. The astute ones notice that each box is for a different response, but others don't notice the subtle change. Any way we could replace this interface with a single window? Use a List Box or a Combo Box or a Tab Box to arrange the different responses. Then the user can go to "Set Desirabilities", see all the responses in one window, and potentially set all of them from the same window. Or, with flexibility to choose which responses need to be set, having a "select the response to change" property allows the user to skip over two or three responses that don't need to be changed in the first place. Icing on the cake: allow some sort of "Standardize Desirabilities" option from the Profiler as well. Sure, you can standardize attributes from the data table and set the Response Limits property, but when you're in the middle of a Profiler that isn't intuitive. ... View more

With the "New Formula Column", a Log can be easy made. it would be a nice feature to transform spec and control limits, axis settings ect.too. ... View more

Most of the tables that JMP uses have the magic JMP Home Button icon bottom right of the table which takes you back to the Home Window . I use the Query builder a lot and if I have a number of JMP applications open it can be quite tricky to find which one contains the query as well as any other tables I'm using.   Can the JMP Home window button be added to the Query Builder ( as well as any others not currently having it)?   David   ... View more

  Ability to use table or local variables from formula editor to control some values in axis, platforms, … ... View more

When updating a target table that includes columns with a List Check property, the update on that column fails silently if the update source table contains items that are not in the target table's List Check.   I agree that the update should fail, but it should fail with a warning and an option to (a) remove the List Check before proceeding or (b) abort the update. ... View more

In  case there are named ranges in Excel sheets it would be good if those could be accessed when importing data into JMP. I have workbooks containing data in named ranges and want to automate data import. The only way i have so far is to script some "search algorithm" to find the boundaries of the named range or using additional software tools like R or Excel-VBA.   ... View more

I would like to be able to import selected images from a folder into a new or existing Data Table with the option to either match names of images with names in an existing column or to have the names of the images written in a separate column (see attached illustration).   It should be possible to specify a name for the Expression column ("Process Result Pic" in the illustration) and a name for the ID column (if used, "Serial Number" in the illustration), or if names of images should be matched with entries in an existing column, then the name of the existing column must be specified. It would be very handy if file sizes could be reduced (on import) down to a max of x Mbyte, and to a maximum width or height (as in the Column Property "Expression Role").   I'm aware that there is a community entry by M_Anderson with supplied jsl code that goes in a very similar direction, but with the expectation that a column with pic names already exists. I couldn't get this to work (probably I misinterpreted sth there).  It would be nice to have an official tool for this with more options. https://community.jmp.com/t5/JMP-Scripts/Adding-Images-to-A-Data-Table-From-a-Directory/ta-p/40341 ... View more

Autosaving data tables should have an option to rename and retain the existing file as "table.jmp.bak" before saving the new version as "table.jmp".  The reason is to prevent autosave unintentionally overwriting a "good" copy of a table with a (mis-)edited version.   An even better option is be able to designate a backup folder where N previous versions of the file can be optionally retained. ... View more

See the attached journal.  This is a simple example of a variability/gauge plot. from one of the sample datasets. I do a lot of beginning JMP user training, and I always show them the variability chart because it is so useful for visulaizing the effects of different X factors on a Y response all on one plot. I would like to be able to do more statistical analysis off this platform. I am looking for the same analysis that is on the fit Y by X platform. For instance in this case an Anova/Tukey means comparison by Gender. And/or a T test comparing gender by each drug. ... View more

Expose as many as possible GUI features through JSL. Specifically, in this case, 'new formula column'. ... View more

For factorial combinations (in Fit Model), LSMeans tables (also "Connecting Letter Report" tables) should present level names as separate strings in separate columns. That will allow to alternate group order by sorting these tables by level of one factor ("Level i") or by the second factor ("Level j"), regardless the factors' order in the data table. ... View more

Since version 12, "Preferences" allows to set the default Summary Statistics in the output of "Distribution". This option should be effective to all platforms. ... View more

In the current version of "Create Excel Workbook", JMP requires the data to be exported to only be a data table . It would be nice and useful to expand this to Matrices and Lists as well  ... View more

Other places where you are picking a column have a little red triangle (lrt) that allows me to select things that "contains" or such.   When I put ~100 (ish) columns in, and want to reduce them in the effect summary, it would be so much nicer if I could limit the shown columns to those containing or not containing some piece of text in the name. ... View more

What inspired this wish list request?      What is the improvement you would like to see?      Why is this idea important?      ... View more

What inspired this wish list request?  Posts such as this: Item Wrap and Max Items - Default Legend Settings and basically the limited options we have through JMP Preferences.   What is the improvement you would like to see?  I would like to be able to define which Preset to use as a default when launching a platform. This of course means that not all of the settings can be taken into account when platform is still fairly "clean" but some of them could definitely be already there. Or optionally (maybe even better) create separate Presets which are supposed to be used only once during platform launch. For scripting, this should generally NOT be reflected (by default) as "using preset..." as it will mess up sharing of scripts, but rather just create the proper script (this is already happening sometimes with JMP Preferences).    Why is this idea important?  Lets user customize newly launcher platforms more freely without relying on, sometimes, very lacking JMP Preferences.   ... View more

What inspired this wish list request?    I am trying to perform non-linear fits of my data to a custom equation in a column. In the non-linear fit platform, I have to manually scroll down nearly 100 separate fits to manually press the 'go' button for the iteration to fit the equation to the data for each variable in the 'by' grouping. It's so tedious, and could be solved by a button in the top triangle menu which says something like 'fit all'.    What is the improvement you would like to see?    A way of automating the process - a single click that works through each set of fits and runs the iteration for each.  It would also be awesome to have the ability to do other 'global' operations like set bounds for parameters across the whole set rather than having to type the same numbers time and time again. Alternatively, it would be extremely helpful if the ability to add custom functions to the function library could be done so that they could utilise the 'grouped' fitting capability available in the 'fit curve' analysis platform.    Why is this idea important?    Currently we are limiting the number of fits that can be performed sequentially to the use ... View more

What inspired this wish list request?  I have a lot of functions that take a data tables as input, then do calculations from it and returns a new table. To keep my functions pure, i usually start by cloning the table.   What is the improvement you would like to see?  The "<< Clone" message should have options to specify the visibility settings for the cloned window. Something like Visibiliy("Keep"|"Visible"|"Invisible"|"Private")   If there are other settings for datatables it would also be nice to have options for those.   Why is this idea important?  JMP seem to run a lot faster when tables are not shown, can massively speed up scripts From a user pov it also nice to not see a million windows flash when running scripts.     ... View more

What inspired this wish list request?  I would like to run clustering where the cluster centers (medoids) are restricted to be rows in the data table (different from kmeans where the mean may not be a row in the table and satisfy constraints).     What is the improvement you would like to see?  Perhaps add this somewhere in the Analyze > Clustering menu. Here is some example R code. library(cluster) n <- 200 X <- data.frame( x1 = rnorm(n), x2 = runif(n, 0, 10), f1 = factor(sample(letters[1:3], n, TRUE)), f2 = factor(sample(c("lo","mid","hi"), n, TRUE)) ) d <- daisy(X, metric = "gower") fit <- pam(d, k = 5, diss = TRUE) cl <- fit$clustering medoid_rows <- fit$id.med cat("Medoid row indices:", medoid_rows, "\n\n") cat("Medoid rows (one per cluster):\n") print(X[medoid_rows, ], row.names = FALSE) cat("\nCluster sizes:\n") print(table(cl)) > cat("Medoid row indices:", medoid_rows, "\n\n") Medoid row indices: 170 111 191 200 68 > cat("Medoid rows (one per cluster):\n") Medoid rows (one per cluster): > print(X[medoid_rows, ], row.names = FALSE) x1 x2 f1 f2 -0.42460961 4.116528 b mid -0.08807738 7.593479 b hi -0.32078302 2.121084 c lo 0.28653902 4.962979 c mid 0.30942313 2.652641 a lo > cat("\nCluster sizes:\n") Cluster sizes: > print(table(cl)) cl 1 2 3 4 5 33 43 43 35 46 Why is this idea important?  I want to use this on tables produced by Output Random Table in Profiler to downselect a subset of different highly desirable factor settings, and need this instead of k-means for when mixture or other constraints are present.   ... View more