JMP Wish List

GiuseppeC · ‎11-25-2020

In JMP / SAS lacks a whole part dedicated to both dynamic and static Bayesian networks. The importance of Bayesian networks and therefore of the world of machine learning is increasingly important and having the possibility of dedicated commands or packages would be very important. In R-project there is the bnlearn or bnstruct package that allow you to analyze data with repeated temporal dynamics, but in JMP and / or SAS nothing exists. In SAS there is a proc hpbnet procedure, but it generates networks with a target variable and not a network where you don't want to target, but free from constraints, as the two packages bnlearn and / or bnstruct do.

ThomasZatValcon · ‎10-14-2020

I plead that all import filters in the Open function get an option to import everything into character columns. This way, a jsl developer can control data formats in columns and not rely on luck that JMP guesses the types right - which is often not the case. Also, such an option should be really easy to implement and it will remove a lot of PAIN :)

BHarris · ‎08-04-2020

I hope this isn't taken as a form of blasphemy, but it would be very nice if users could write JMP scripts in python in addition to JSL. There would be an implied "import jmp"-type statement, and then users could do things like this: dt = jmp.getCurrentTable() dt2 = jmp.newTable() aRow = dt.row(5) aCol = dt.col(3) aCell = str( dt.cell(5,3) ) dt2.cell(1,1) = aCell newCol = dt2.newCol() newCol.formula=':Column(1)*pi()/180' dt.graphBuilder( size=(800,600), x=dt.colByName('time'), y=dt.col(3), overlay=dt.col(7), colSwitcher(dt.col(3)))

john_madden · ‎08-03-2020

In a large table with hundreds of columns, I need to have more flexibility in grouping columns. I'd like to be able to have column subgroups (group hierarchies). (Would also be nice to have table script group hierarchies.)

kom · ‎06-09-2020

It'd be great if there was a simple checkbox option to prevent a script from being accidentally deleted from a data table. I've had Operators unintentionally delete scripts in the past, and this option would have saved a little time/heartache.

eemei · ‎03-02-2020

The Summary function is not flexible enough for users to be able to calculate various statistics (for e.g. Mode) using the group-by method, making it a pain in the neck to use. Other software packages like R and Python can easily allow the function to be performed on group-by data.

vince_faller · ‎02-12-2020

I want tableboxes that use ColSpanBox to name the columns better when interacting with `<<make into data table`. Currently it just takes the lowest column name. dt = Open("$SAMPLE_DATA\Big Class.jmp"); new window("Row Borders", tblbox = tablebox( ColSpanBox("1", NumberColBox("age", dt:age << Get Values), StringColbox("Sex", dt:sex << Get Values), ), NumberColBox("Height", dt:height << Get Values) ) ); tblbox << Make into data table(); The behavior that tabulate does would be fine by me. (dt << Tabulate( Add Table( Column Table( Grouping Columns( :sex, :age ) ) ) )) << Make Into Data Table

vince_faller · ‎02-12-2020

I'd like it if I could set individual cell colors. Currently I have to make a table then color the cells then << Get as report or Journal.

ih · ‎01-31-2020

One idea: bring up the scripting index when a function the cursor is in a function name (or a function name is highlighted) in the script editor and the user presses a keyboard shortcut or function key. In RStudio pressing F1 or F2 opens the function definition or brings up a vignette with a list of arguments for that function. JMP needs this!

bobmorrane · ‎01-29-2020

When you are writing a script embedded in a data table, there are several issues compared to a stand alone script file. There is no Embedded log. If I want t o see what is in the log, I have to go through the debugger. But I don't like this option as the debugger has a strong tendency to crash JMP. Can we please have an embedded log in the datatable-dependent script windows ? Upon execution, the data table is not saved automatically. This means that when I run a script and JMP crashes (I don't know if it is just me but that happens A LOT), my work is lost if I didn't save the data table. Can we have an autosave option ?

vince_faller · ‎01-24-2020

I would really love it if we could subscript a list with a matrix and have it shape the list into a list of lists. l = {"A", "B", "C", "D", "E", "F"}; ss = [1 2, 3 4, 5 6]; l[ss]; // I want this to come out as {{"A", "B"}, {"C", "D"}, {"E", "F"}};

gerd · ‎01-15-2020

I would like a JSL command that allows me to change the Display Language in JMP - not only the check box below the language, but the language itself. Being able to check what Display Language is currently used, would also be very helpful. When using Display Language English on a German OS, I can use the checkbox below to tell JMP if decimal points (tick) or decimal commas (no tick) are expected. When using Display Language German on a German OS, the tick makes no difference in that respect. As our users have both language options it's important to know what language they're using in JMP before a common script is run on their system. Currently I can only think of a poor workaround to check the language and give a warning if they're using the wrong language for the script they want to use.

nao · ‎07-25-2019

It will be convenient if there is a function that accepts a value and a name of a color gradient and returns a color code.

ghartel · ‎07-02-2019

Contrast in Generalized Linear Model doesnt save as script and not accessible in script - so if you set up contrasts, the redo only adds the contrasts button and you have to re-enter all the contrasts. It would also be good to be able to specify the reference category. In general the parameterisation should be more controllable or at least obvious. A lot of users seem unaware that standard least squares and nominal logistic personalities use centered X's (ie mean reference category) whereas Generalized Regression and Generalized Linear Model use the reduced rank approach - ie zero'ing one of the levels like SAS does. It would be good to have control over that, ie specify which level gets zero'ed or if mean subtraction should be used. IT would be good to have the same approach and features available in all the regression procedures as far as possible and make everything JSl accessible.

nao · ‎06-19-2019

Advanced users obtain results of platforms (e.g., Fit Model) by scripts. But for this, JMP forces the user to "scrape" the report, which is painful. It will be very helpful if the analysis results are, like in R, returned in a structured way, e.g., as an Associative Array.

russ_thomas_nrc · ‎05-27-2019

Hi, Could you please implement Tukey's (Running Median) Smoothing approach in JMP. You already have a number of other EDA type tools and this one seems to be missing from JMP. Many thanks. Russ

terapin · ‎04-15-2019

Folks, Currently, the Edit | Reformat Script command does a really nice job of reformatting JSL script so that all indentations are properly aligned. However, this command is wrapping any text in a row that exceeds something in the order of 130 characters, regardless of the Wrap Text setting in Preferences. I often organize/format my JSL in ways to aid in readability and organization which results in rather long rows (I have multiple large monitors which facilitiates the proper display of these long rows of characters). Unfortunately, any time I run Edit | Reformat Script my long rows of JSL commands are wrapped in ways that makes it difficult to read and see my code structure. I would appreciate it if the underlying value in Edit | Reformat Script that limits how many characters can be on a row is increased dramatically, or even eliminated. If the character limitation was eliminated, the Wrap Text property in Preferences could handle text that extends beyond the size of a given window, regardless of monitor size. Thanks for listening!

floydfoxfb · ‎02-08-2019

As we are all aware, a good deal of the time we spend on analyzing datasets is in preparing them for the analysis (ie- cleaning, organizing, formating, etc.). Frequently I work with datasets that are updated with new data periodically and I would like to have the ability to script all the dataset preparations steps so they can be executed with the new data. JMP has the ability to script analyses and graphing but not the dataset preparation steps. I hope that other members of this community would find this fuctionality valuable. If you would like to see this implemented please add your kudo to the rest of us. Many thanks, Floyd Fox

mark_anawis · ‎01-10-2019

When using JSL, update the Make Validation Column function to accept column names for Stratified Random, Grouped Random, and Cutpoint options. I know you can use formula random and add a by(:Group) but there should be a direct way to do this. Example: current data table() << Make Validation Column( Training Set( 0.50 ), Validation Set( 0.25 ), Test Set( 0.25 ), Stratified Random ("My_Column_Name") );

DJ_Kim

What inspired this wish list request? We are currently performing various tasks using our own JMP Add-in. However, it has become increasingly difficult to respond to JMP’s annual version upgrades. Depending on the user environment, the upgraded features are often not actively used in practice, yet the version change itself can create compatibility issues that disrupt our workflows. For example, when a user updates to the latest version while the Add-in is optimized for an older version, unexpected errors or functional limitations may occur. This creates a situation where maintaining operational stability becomes challenging. What is the improvement you would like to see? We would like JMP to support downloading or installing at least two previous versions of the software, not only the latest one. This would allow users who rely on custom Add-ins or stable workflows to operate in an environment that best fits their needs. Providing access to multiple past versions—similar to other software platforms that allow users to choose their preferred stable version—would greatly reduce the burden of adjusting Add-ins and scripts every year. Why is this idea important? This improvement would minimize operational disruptions, reduce version-specific maintenance work, and allow teams to ensure stability when using custom Add-ins. It would also give users the flexibility to choose the version that best supports their actual use cases, rather than being forced into every annual upgrade. Overall, it significantly enhances ease of use and provides practical value for organizations with complex or long-running JMP workflows.

JMP Wish List

Dynamic Bayesian Networks

Import all data in character columns

Enable python as an alternative to JSL

Hierarchical column groups

Inclusion of option to LOCK a SCRIPT (to prevent accidental deletion from data table)

Allow users to add statistics like Mode to the Statistics function in Table Summary

<<makeintodatatable name better when used with colspanbox

make tablebox cells colorable

Add a quick way to get function info from script editor.

Improvements for scripting window for scripts embedded in a data table

subscripting list with 2d matrix

JSL command to Get and Set the Display Language in JMP

"Color Code()" JSL Function

Contrasts and parameterization in GLMs

Return platform results in a structured way (e.g., as an Associative Array)

Tukey's (Running Median) Smoothing Approach

Increase character length limitation in Edit | Reformat Script command

Save Data cleaning changes to script

JSL Make Validation Column argument

Request for Support of Multi-Version Downloads to Ensure Add-in Compatibility and Stable Operations