JMP Wish List

On a few occasions I had to extract tables from pdf files. Now, I used online converters of pdf tables to Excel, and then went from Excel to JMP. It is probably not too complex to allow users to open pdf files containing tables staight away in JMP? If free online website can offer that service, I'd expect that JMP should be capable as well! ... View more

    What inspired this wish list request? Currently, outliers detection techniques are available in different menus : Some univariate and multivariate outliers detection techniques are available in "Screening" -> "Explore Outliers", Some multivariate techniques are available in "Multivariate Methods" -> "Multivariate" and different from the other detection techniques from the Screening platforms.   Finally, some techniques or models used in litterature (Isolation Tree/Forest, One-Class SVM, k-Nearest Neigbors...) are not directly available in JMP.   What is the improvement you would like to see?  Following the idea of the Python library pyOD (pyod 1.0.7 documentation) and other libraries/packages, it would be great to have only one single JMP menu dedicated to outliers detection, using several methods combined like in the "Model Screening" platform, where several options would be available : If a response is present in the dataset and used in the "Y, column" dialog, the emphasis and techniques used would be supervised (semi or fully supervised). If no response is added in the "Y, column" dialog menu, then the techniques used could be unsupervised. In the same way as "Model Screening" platform is proposing several models in a auto-ML way, it would be great if JMP user could choose all, several or only one methods among those proposed. In order to help the user have more visibility on the different techniques, it could be perhaps helpful to group some techniques behind group, like for the type of anomaly there could be several groups of methods for local, global, dependency and clustered types of anomalies. Under each group, the user could select or deselect any of the techniques, to have more freedom and flexibility. Finally, when the different outliers detection techniques are used, it could be great to have results in a "macro" and "micro" view : "Micro" view : For each detection techniques, being able to know which points were detected as outliers, in order to compare the techniques and see the agreements/disagreements between the methods, "Macro" view : For the ensemble of detection techniques, instead of "hard voting" or binary result like outlier vs. normal, it could be great to have instead a continuous "anomaly score" from ensembling the different models (ranging from 0: never detected as outlier with all selected techniques to 1: always detected as outlier), in order to use it in a transformed way (perhaps in a "reciprocal" transformation: 1/anomaly score) in other modeling platforms as a "Frequency" or "Weight" variable, in order to create "weighted models" that take into account outliers, but reduce their importance.     Why is this idea important?  Two points are motivating this request : Unify and group the different outliers detection techniques in a single platform could help user be aware of the different techniques proposed, It could be a great starting point to add new models to the JMP platform focused on this outlier detection aspect. ... View more

I do some editing in editors other than the packaged JSL editor and have come to love the scroll feature in many of them. It's the map bar for quick scrolling through code where the code is miniaturized and you can quickly jump through large areas of code quickly. Below is a screen shot of an example. It would be awesome if the native JSL editor had this option. Thanks!   ... View more

Julia is a fast, dynamic, composable, general purpose programming language well suited to statistical data analysis, machine learning, automatic differentiation, other numerical modeling, as well as more general purpose programs. It feels like a scripting language, but runs compiled -- using Just-In-Time (JIT) compiler technology to compile code on the fly. It was designed from the ground up to support multi-threading, multiprocessing, and distributed multiprocessing. Julia solves the "two language" problem -- you don't need one language for ease-of-use prototyping, and a second language for speed -- as Julia is already easy to use and fast. You can write your high performance code in Julia itself.    This proposal would be to support Julia similar to how Python is currently supported.    Data types are highly compatible between the two languages   JMP Data Type Julia Data Type Boolean Boolean Data Table DataFrames.jl Associative Array Dictionary Numeric Float64 Matrix Float64 Matrix List tuple String Unicode string   One advantage of Julia over Python is that there is no Numpy -- that functionality is just built-in.  In addition, instead of telling users what packages they need to install, JMP could use PackageCompiler.jl to create a stand-alone binary of Julia with all of the packages that JMP requires and distribute that with JMP.  Julia integration would work right out of the box (or "after the install program finishes"). Advanced Julia users would have the option of replacing it, but for everyone else, it just works.    Julia is an exciting, rapidly growing language in statistical, machine learning, and scientific computing. See The unreasonable effectiveness of the Julia programming language, by Lee Phillips (10/9/2020).    Adding support for Julia would also users to drop some state-of-the-art tools and coding into their JSL scripts.  ... View more

I've been a big fan of equivalence tests in JMP. For a one-sample scenario in the Distribution platform I like the output because it has a nice graphical representation of the equivalence bounds overlaid with the confidence intervals on the mean. You also get a deliberate interpretation statement at the bottom.   In a multi-sample scenario in the Fit Y by X platform it's less interpretable. I was in a meeting with a few engineers, and they had no idea how to interpret the two normal distributions and indicated they definitely prefer the one-sample case.   My proposal would be to create similar output in Fit Y by X as to what you see in the Distribution platform. For the example above, the equivalence bounds of [-6, +6] can be easily shown with a red confidence interval based on the actual output (centered around 3.02). ... View more

Two items for review: I would like to suggest that on the Process Screener platform, you add two options to the red arrow drop down: "select out of spec rows" and "select out of control rows".  When selected they would highlight the corresponding out of spec or out of control rows per the process screener analysis.  If both were selected it would be if it is out of control or out of spec the row would be selected.  The select out of spec option is currently available in the capability platform. I would like to suggest that the "select out of control rows" option be added to the red arrow drop down for the control chart builder platform Thanks for considering these   Steve     ... View more

☑ cool new feature ☑ could help many users! ☐ removes a „bug“ ☐ nice to have ☐ nobody needs it An everyday problem in daily jmp data handling is how to get updated data sets efficiently into jmp: You add some lines to an excel file - perhaps also some columns - and want to check the graphs that you just have generated in jmp.   When importing csv or excel files, a "source" script is added atomatically - and one could run it again to get an updated version of the data into jmp. But the new data is imported as a second data set - independent of the first one. So, if there are already dozens of graphs, analysis windows and dashboards linked to the original table, it's quite some effort to update everything.   I'd love to have a universal "update" button that copies any update of the input (e.g. Excel) data to the jmp table: - adds new rows - deletes removed rows - adds new columns (keeps previous columns, even if they were deleted  - just in case :) like the "reread" button in Cornerstone.   A first step in this direction and very helpful is Martin's "update from Excel" script: https://community.jmp.com/t5/Martin-Demel-s-Blog/Updating-a-JMP-data-table-from-a-spreadsheet-made-easy-Part-1/ba-p/266323 ... but some of the above functions are missing. And:  The script should be added automatically - like the "source" script, right?     ... View more

Please add a columns filter for the columns in the main table view. Also add the filter as default to all column selectors (or as an optional preference) ... View more

In the script editor, would it be possible to make all calls of user-defined functions or expressions be hyperlinks?  For instance, I would like to be able to click on an instance of "myfunc" somewhere in my script, and have the editor immediately take me to the location in the script where myfunc is defined.  And of course, I'd like to have a "back" button as well to take me back to where I was initially in the script.  Same goes for expressions. ... View more

It is common to have a recently opened files and be able to pin items on this list. Why not extend this idea to the JMP menu/toolbar items?   How about a sidebar (with oversize icons?) where 'favourite' menu/toolbar items appear and can be pinned. The number of items that appear on this list could also be customised.   I could create a favourites menu/toolbar manually but that would require keeping a mental note of which menu/toolbar items I use most. Being able to expose the usage statistics to the end user might also prove enlightening? ... View more

What inspired this wish list request?  I have been building quite a few custom user-interfaces and there are some features I would really like to have and this is one of the (I would like them be even visible with Filter Col Selector and Col List Selector, but they aren't yet visible even with column (More icons to column listing )). I would like to be able to show user the column properties in the selectors especially notes would be helpful.   What is the improvement you would like to see?  Below is an example how it could look like. names has notes column property set, so I would like to see it on hover over. Age as label set so I would like to see it Also if this make columns more distinct gets implemented, it would be great to have colors also visible   Why is this idea important?  This idea further improves upon JMPs interactivity and visualization capabilities. Also it makes column properties more visible and useful (in the end I would like to be able to store instructions/metadata/information to column properties which would be easy to access, this is one step closer to it). ... View more

With the latest JMP 14 JSON Features: Parse JSON(); JSON To Data Table(); and JSON To List(); it would be really great if we could reverse this process.  I would like to turn a JSL Associative Array into a JSON string.  I realize there's a work around to turn a Data Table into a JSON string, but the most important of these features would be turning an AA into a JSON string. ... View more

What inspired this wish list request?  (edit) Apparently the template drops a bunch of text here.  The inspiration is that selected rows are drawn above EVERY custom user-generated graphics script, regardless of the draw order given.   I understand that the devs were trying to fix the issue of un-selected data points being drawn above selected data points, but they took the lazy fix and just clobbered any hope of having the user determine the draw order.  Now selected points are drawn above everything else.  I'm almost surprised that the mouse is drawn above selected data points.     What is the improvement you would like to see?  (edit as this form dropped my previous response) I would like to see JMP adhere to the draw order given in the graph customizations list.  If a users attaches a graphics script AFTER the marker seg, then any elements drawn by that script should be drawn on top of all markers,  Period.  End of story.     Why is this idea important?  (edit, as this form dropped my first response)  This is clearly important.  Extremely important.  To the point that my org is putting serious resources into alternatives such as Python or online with JS.  There is a large number of work-flows that now cannot be done in JMP14 or 16, full stop.   Consider this graph: Here I might want to highlight a specific item by selecting it in the legend.  When I do, the dense data points completely obscure EVERY SPLINE, even though the splines are drawn as separate scripts AFTER the marker segs.   This is just one example.  In my org it is common to have many thousands or even hundreds of thousands of data points.  Drawing some sort of custom summary graphic above the data points (whether it's splines, goal lines, confidence intervals, or any other such custom graphic) is needed for properly consuming the data.  With JMP14 and beyond, this becomes totally useless for interactivity, since selecting items (and the associated data points) completely obscures EVERY and ALL other graphics drawn on the graph.   And while my org is slow to update to new JMP versions (as many are still using JMP12), I'm left telling people that it's impossible with the new versions of JMP to have the same workflow as before.  Instead of being faster with better features, we're left with something completely useless.   And while I do understand that a user can simply deselect the rows (say by clicking a single data point), this type of work-around to a fundamentally bad design decision by the JMP devs should not be necessary, and is not always acceptable (and also changes the visual story / significance):   From my perspective this is so egregiously bad that JMP should provide a hot-fix and patch all users systems in JMP14 and beyond, not wait till JMP18 to fix.   ... View more

Can we have JMP display a path diagram for exploratory factor analysis (EFA) in the multivariate platform?  Even though the loading matrix displays similar information, the path diagram will be a very powerful visulaization of the factor model by displaying the most dominant item connected to each factor.  There could be an option to display the number of items for each factor (e.g., 3) to control the complexity fo the diagram.  The diagram should contain the values of the loadings, and also the correlation among factors for non-orthogonal rotations. ... View more

Hello JMP team, I'd like to suggest the following for the column options: On the columns list located on the left side of a data table, can you add the options for standardized attribute, column properties, formula, recode, and new formula column when you right click on the column? On the main column titles, can you make it so that by clicking on the column and holing the alt key that it will move that column into view on the column list at the left of the datatable? On the columns list located on the left side of a data table, can you add an option to filter by modeling and data type? Thanks for considering these options. Steve ... View more

What inspired this wish list request?  I quite commonly have to create labelling columns depending on the row values on one column. For example I might have ERROR_DESCRIPTION column and when it has a value it means error happened else test was ok. So I would like to have FAILURE labels formula :ERRORDESCRIPTION != "" -> "1" else "0".  And I would like to be able to do this with New Formula Colum and as Transform columns from Filter Col Selectors in different platforms.   What is the improvement you would like to see?  I would like to see possibility to create new formula column (and transform column) to create such labellings based on row values.   This example does combine two types into one, but idea would be that depending on the Data Type of column, different selections should be available. UI can be made more user friendly fairly easy (and should be), for example by disabling selections until Row Value has been selected. And maybe if column modelling type is continuous the combo box could be slider box and in this case created columns would be something like this: dt << New Column("Compare[age]", Character, Nominal, Formula( If(:age >= 14, 1, 0 ) )); dt << New Column("Compare[name]", Character, Nominal, Formula( If(:name == "ALFRED", "1", :name == "CAROL", "2", "0" ) )); Demo UI script: Names Default To Here(1); dt = Open("$SAMPLE_DATA/Big Class.jmp"); Summarize(dt, col_options_num = By(:age)); Insert Into(col_options_num, "<SELECT>", 1); numeric_options = {"==", ">=", ">", "<=", "<"}; Summarize(dt, col_options_char = By(:name)); Insert Into(col_options_char, "<SELECT>", 1); character_options = {"==", "!="}; lub_expr_numeric = Expr(Lineup Box(N Col(3), Combo Box(col_options_num, << Set Function(function({this}, If(this << get selected != "<SELECT>", ((this << parent) << parent) << Append(lub_expr_numeric); ); ))), Combo Box(numeric_options), Number Edit Box(.) )); lub_expr_character = Expr(Lineup Box(N Col(3), Combo Box(col_options_char, << Set Function(function({this}, If(this << get selected != "<SELECT>", ((this << parent) << parent) << Append(lub_expr_character); ); ))), Combo Box(character_options), Text Edit Box("") )); // could also be built with Table Box nw = New Window("Demo", << modal, H List Box( Panel Box("Numeric - age", Lineup Ruler Box( Widths({100,70,50}), Lineup Box(N Col(3), Text Box("Row Value"), Text Box("Compare"), Text Box("Value") ), V List Box( lub_expr_numeric, ), Text Box("..."), Lineup Box(N Col(3), Text Box("Else"), Combo Box({""}, << Enabled(0)), Number Edit Box(.) ) ) ), Spacer Box(Size(50,0)), Panel Box("Character - name", Lineup Ruler Box( Widths({100,70,50}), Lineup Box(N Col(3), Text Box("Row Value"), Text Box("Compare"), Text Box("Value") ), V List Box( lub_expr_character, ), Text Box("..."), Lineup Box(N Col(3), Text Box("Else"), Combo Box({""}, << Enabled(0)), Text Edit Box("") ) ) ), Panel Box("Actions", Button Box("OK", num_vals = . ), Button Box("Cancel") ) ) ); Why is this idea important?  Would make it much faster to create transform labelling columns which are not dependent on selections but rather on row values in the column.     ... View more

If you have several position to evaluate, which have different specification limits it is not possible to set them by variable/grade.   So idea would be to not only define, or put in the numbers, instead also be possible to say in which column the LSL and USL and Target is stored.   best regards Splerin ... View more

One thing that I have been looking for JMP to implement is to be able to add an annotation to individual values in a data file.  There are often occasions when you may need to identify that there is something special about a specific data point (e.g. you may have inserted a mean to replace a missing value) and you want to retain that information with the data file.  If this annotation was implemented as a property of the data value then you would be able to interrogate individual data points in a graph that could then pop up the annotation (if they existed for that point).  It could even be used in the reverse order where you identify an unusual data point in a graph and then link back into the data table to add an annotation to it for future reference? ... View more

Being an ecologist, I routinely switch back and forth between JMP and PRIMER, but, with each update of JMP, I can do more in JMP (and therefore less need for PRIMER). However, PRIMER has a multivariate, distance matrix-based algorithm called "distance-based linear modeling" (DistLM) that essentially works like stepwise regression (model selection by minimizing BIC/AICc) though with a distance matrix as the input. It is great for those looking to find the best model to explain similarity and differences between samples in a multivariate framework. I feel like JMP already has distance matrix capacity AND stepwise regression, and, although I know this is much more complicated than univariate stepwise regression, I think it should be possible to develop this technique in JMP (as well as the more commonly used PERMANOVA). Actually, it doesn't need to be DistLM, just any multivariate incarnation of stepwise regression. Pleassssssseeeeee.  ... View more