JMP Wish List

ThomasDickel · ‎07-03-2023

What inspired this wish list request? We want to store log and debug messages of our addin-ins in a local database which can be used later for debugging purposes and we have seen that JMP has an internal SQLite support meaning that there does not need an ODBC driver to be installed. Currently in JMP 16, 17 and 18 EA2 the internal support for SQLite is only for read (=SELECT) operations and the internal SQLIte operation has an over 8 year old version 3.8.11.1. Neither of both limitations are documented in the JMP documentation or can be found somewhere else. E.g. the following command opens a SQLite database file in JMP: obj = New SQL Query( Connection("SQLite:Database=<path>\data.db"), Custom SQL("SELECT sqlite_version(), sqlite_source_id() FROM table1") ) << Run Foreground(); BTW this command returns the version of the internally used SQLite implementation of JMP 16/17/18EA2: sqlite_version sqlite_source_id 3.8.11.1 2015-07-29 20:00:57 cf538e2783e468bbc25e7cb2a9ee64d3e0e80b2f But the next INSERT- or UPDATE-command results in an error: "deleted object reference[]" obj = New SQL Query( Connection("SQLite:Database=<path>\data.db"), Custom SQL("INSERT INTO table1 (id, name, data) VALUES (1, \!"test\!", sqlite_version());") ) << Run Foreground(); What is the improvement you would like to see? - Allow the SQLite implementation to execute UPDATE- and INSERT-statements to store data gathered while executing a JMP add-in. - Update the internal SQLite driver so that a more recent version of the driver can be used - current version is 3.42.0 Why is this idea important? This idea allows storage small data for debugging or logging purposes into the SQLite database files - this format is better, more flexible and more usable than using plain text, JSON or XML files. @martindemel

vince_faller · ‎05-08-2019

I would love if in User Defined funcitons we could use keyword arguments in the calls so I can do Names default to here(1); f = function({x, y=2, z=3}, show(x, y, z); ); print("What I'd like to do"); f(1, z=2); //I want it to be 1, 2, 2 //instead of having to do f = function({x, kwargs={}}, {DEFAULT LOCAL}, // optional y = 2; z = 3; evallist(kwargs); show(x, y, z); ); print("Using List"); f(1, {z=2}); Someone mentioned it here, but it was 8 years ago, so figured I'd bring it up again.

DavidLeber · ‎10-05-2018

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.

cnattrass · ‎02-19-2020

Several other programming languages default to the local namespace/environment rather than a global environment. JMP Experts say the NamesDefaultToHere(1) is the BKM whenever scripting as typically the local namespace is appropriate for new scripts to avoid clashing with other JMP scripts. It would be more convenient to define NamesDefaultToHere(0) when you want a script to be in the global namespace rather than defining every script with the "true" argument

john_madden · ‎07-17-2019

I have diurnal data (time-of-day data for a daily recurring process). I'd like to have access to some plots and techniques from the realm of so-called circular (directional) statistics (see Pewsey A, Neuhauser, M Ruxton G. Circular Statistics in R. Oxford, OUP. 2013). I was thinking that since there is an R package for circular statistics, I could probably access some of these functions by calling R from JSL. But it would be nice to have JMP built-ins. Even just the basic graphics (circular plots, rose diagrams, etc.).

bayesfactor1 · ‎10-15-2021

The problem statement is I want to be able to compare 2 populations' survival and give a confidence interval around the point estimate. JMP can plot a simultaneous or pairwise confidence interval around any given population, but cannot give a confidence interval around the difference. Therefore, I suggest to everyone in my company to use R or python to do survival analysis, because the point of comparing survival is to quantify the difference, and the uncertainty in the difference. RMST is one way to compare survival across 2 populations and derive confidence intervals. https://cran.r-project.org/web/packages/survRM2/vignettes/survRM2-vignette3-2.html I suggest JMP impelement RMST.

nao · ‎06-19-2019

We get frustrated when we find JMP frozen after starting a script that takes a long time. But even in most such situations, only one CPU thread is active. JMP should be able to take advantage of today's multicore processors and keep working even while a heavy script is running.

john_madden · ‎10-20-2018

I would really appreciate a "Replace & Find Next" button in the Find dialog box, so I don't have to keep alternating between the Find button and the Replace button when I am trying to step through replacements in a long script. For example, BBEdit has this, together with a few other convenient enhancements relative to JSL FInd dialog: Don't mean to steal their ideas, but…actually…I guess I do. Maybe you could ask their permission…

StarfruitBob · ‎04-28-2023

What inspired this wish list request? More intelligible table names when the option "Subset by" is used. Consecutive numerical naming, along with the deletion of the Subset by column creates datasets that have had data deleted and can be difficult to name properly. What is the improvement you would like to see? An option to append the data that has been appended into the subset name. For example: If I have a data table that includes a column :Fruit of fruit names and I want to create a subset for each fruit (given the output name of "Fruit"), right now I'd use --> subset > Subset by :Fruit. This would output data tables that have the name "Fruit 1", "Fruit 2", etc. The data of which fruit each data table has been created for has been lost, since the column with this information has been deleted in this process. I'm suggesting the following: If I have a data table that includes a column :Fruit of fruit names and I want to create a subset for each fruit (given the output name of "Fruit"), right now I'd use --> subset > Subset by :Fruit. This would output data tables that have the name "Fruit Apple", "Fruit Orange", etc. Why is this idea important? This would help keep information, rather than deleting it, creating predictable output tables names for calling later in scripting for further processing.

ttreynor · ‎09-05-2018

Based on details in the discussion below, this idea is amended to request that a "Source" or "Make Combined Data Table" script be written to the table resulting from Make Combined Data Table in a report when there is a By column/variable. --------------------------------------------- "Make Combined Data Table" is one of JMP's most powerful features, yet one of its most challenging to script. No matter how many times I use this feature when exploring my data, I nearly always fail repeatedly when I try to incorporate it into a longer JMP-scripted data analytical pipeline. (I suspect I'm not the only one who has pinged support@jmp.com repeatedly on this same issue.) When users run any of the platforms accessible from the Table menu the table that gets created is automatically created with a "Source" script that can be copied and pasted into a larger script in such a way that only minor and relatively obvious tweaking is needed to get the table script working in its new context. Yet when users request "Make Combined Data Table", usually no source script gets written automatically to the newly created table. This seems like a glaring and important gap in JMP's feature set that I hope can be filled with the next release. Intriguingly, when users request "Make Combined Data Table" for a report table that occurs only once within the report, a script called "Make Combined Data Table" is in fact saved to the data table. But it is relatively non-obvious (to me) what kind of tweaking is needed to adapt the saved script to the situation where there are actually multiple tables that I very much need to combine. I suspect there are many of us who would benefit if a functioning "Source" script were automatically saved to the newly created table every time "Make Combined Data Table" is requested -- especially when there are actually multiple tables to combine.

fzellinger · ‎04-03-2023

What inspired this wish list request? Even though various platforms (Fit Y by X Group->OneWay) have many options in File->Preferences->Platforms, there will always be some additional features users want (or default features users want to have removed). A post-generation script preference would allow for arbitrary customization (anything that can be scripted) by the user. What is the improvement you would like to see? In File->Preferences->Platforms->{any platform} please add a "post-generation script" feature (text/script box, or pointer to script file). For each instance of the platform executed, a reference to the instantiated platform object would be passed (or be made available via default variable) to this script. The end-user can put whatever they need into this script to customize the platform (or take other related actions). Why is this idea important? In JMP 17.0 (and other versions) certain platform features have been introduced "by default" with no way for the user to control them. And, there was no platform preferences setting to control the feature. The response from JMP support was "here is a script which can be run against the platform after it is generated, which will make it behave the way you want". The only problem was that there was no way for the user to have it automatically run, other than to re-script all of their workflows (assuming that their workflows were scripted in the first place, which they were not). In addition to this 'platform post-generation script' (needs a better name?) feature allowing users to affect/revert platform default behaviours, it will also open the door for some VERY interesting additional user interactions and usage of JMP as a multi-tiered analysis solution.

StarfruitBob · ‎03-31-2023

What inspired this wish list request? I've generated a map of a product I help to analyze in the graph builder platform. This map has local data filters and column switcher enabled. To see the entire area of the product map, I've set the x & y axis to the appropriate range, then used lock scale(1) in the script to make sure they don't change between filter selections. Lock scale also locks the scale of the legend, which is unfortunate when different metrics need to be looked at, and different areas of the product. What is the improvement you would like to see? Implementation of different locks for axis and legends. Why is this idea important? The purpose of legends is to add further information to a visualization. When it's locked into a range, the purpose becomes defeated because it cannot be fulfilled.

txnelson · ‎05-30-2018

I would like to see a JSL message that retrieves the color of a cell. It would need to have optional arguments of Cell Color, Value Colors, Gradient Color and Display. Cell Color, the color value from a << Color Cells Value Colors, the color value from the Value Color column property Gradient Color, the color value from the Color Gradient Display, the color currently being displayed in the table The message needs to return a list of lists. The message needs to be applicable to individual cells or to the column.

dale_lehman · ‎11-10-2018

In the Predictive Modeling platform, it would be nice to have options, similar to the alternative confusion matrix cutoffs, to change various tuning parameters for a number of iterative steps of values. For example, in a partition, vary the minimum split size between 3 and 10 in increments of 1 (similarly for the other paramters). I realize this is not difficult to accomplish with a loop in a script, but it would be nice if it was as easy as with the confusion matrix cutoff example, or the way it works to put a variable in the By box when doing an analysis. It would then be easy to examine how various performance measures change as the tuning parameters vary. It has been my experience that most of the default parameters in JMP work quite well, but it becomes tedious to test whether or not this is true. This suggestion would automate this testing and make it easier to determine whether or not to override the defaults.

jthi · ‎03-30-2022

Currently JMP's DDL capabilities allow array being only used with double. This will prevent users from directly using some .dll as those require to be able to pass back other values than doubles. One such DLL has been discussed here (in fact the same I was working on) Re: Does anyone know about TDMS format data converting into JMP? The NI TDMS File Format

nathan-clark · ‎05-18-2021

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!

blackeneth · ‎03-11-2022

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.

nikles · ‎08-08-2018

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.

msharp · ‎08-01-2018

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.

ErraticAttack · ‎02-16-2023

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.

JMP Wish List

SQLite support in JMP should be enabled to allow write-operations UPDATE/INSERT

Keyword arguments for functions

Improved JSL Stack Trace in Log on Error

Names Default to Here(1) as the default namespace

Support for Circular (Directional) Statistics

Confidnece interval around difference in survival

Run time-consuming taks in the background

Replace & Find Next

Subsetting using "Subset by" naming option

automatically write "Source" script when "Make Combined Data Table" is used in report with By column

Platforms post-generation script preference

Axis vs legend lock scale()

<< get cell color

Parameter tuning in Predictive Modeling

Extend the support of arrays in JMP's DLL capabilities beyond double

JSL Map Bar Scroll Option

Work with Julia Language

Hyperlinks for Function and Expression calls in the script editor

JSL to JSON

Fix Selected States being drawn above all other possible elements in a graph