- JMP User Community
- :
- JMP Wish List : Top Ideas
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
JMP Wish List
We want to hear your ideas for improving JMP. Share them here.We want to hear your ideas for improving JMP software
We know that you have many valuable ideas on potential new features, or enhancements to existing features. You can use this Wish List to share your ideas, and discuss how to improve JMP, with other users across the globe.
Here's how to participate:
- Search: Please search for an existing idea first before submitting a new idea.
- Kudo & Comment Kudo ideas you like, and comment to add to an idea.
- Subscribe: Follow the status of ideas you like. Refer to status definitions to understand where an idea is in its lifecycle. (You are automatically subscribed to ideas you've submitted or commented on.)
- Submit: Post your new idea using the Suggest an Idea button. Please submit one actionable idea per post rather than a single post with multiple ideas.
We can’t implement everything, so please include the following to help JMP Product Management evaluate your ideas for consideration:
- What inspired this wish list request? Please describe the current issue that needs improvement or the problem to be solved that is not easy or possible right now, with an example use case.
- What is the improvement you would like to see? Please describe the idea for improving JMP. Please include mock-ups, wireframes, screenshots, scripts, other documents or examples from other software that help describe the change you would like to see.
- Why is this idea important? Please describe the value to you and/or other users if the idea is implemented (for example, ease of use, must have,…).
What inspired this wish list request? The search bar in the Data Filter clears any previous selections. This makes multiple selections from long lists of many levels really tedious; you have to scroll through the entire list to make your selections. What is the improvement you would like to see? The search bar in the Data Filter should not clear your previous selections. Why is this idea important? This feature would enable easy & fast multiple selections from long lists. I'd like to use it to select ingredients from a standardized list of all of our raw materials that would feed a DOE factors table. This way, scientists are all using the same names/identifiers for ingredients in their DOEs. Without this feature, I'd have to build a bespoke tool & JSL scripts to do this.
... View more
See more ideas labeled with:
What inspired this wish list request? I was working on a dataset with thousands of rows and hundreds of columns, and I saved dozens & dozens of scripts to document my exploratory data analysis and model development process. I organized the scripts in the script window by grouping them together. Whenever I received new columns of data, I joined the new data to the large dataset, and the resulting table inherited the scripts from the primary table but the script groupings disappeared. I had to redo the script groupings each time (or copy/paste the new columns into the primary table which is error prone). What is the improvement you would like to see? Table operations create new tables that inherit the primary table's scripts and the script groups. Why is this idea important? Maintain script organization as datasets and analyses grow in complexity. Not all data comes back at the same time, and new questions can be raised over time.
... View more
See more ideas labeled with:
Status:
Archived
Submitted on
10-11-2018
10:27 PM
Submitted by
uday_guntupalli
on
10-11-2018
10:27 PM
In the current version of JMP, while the ability to drag and drop and build an application builder and in turn a dashboard is amazing, the ability to script an equivalent or manage the script that is generated is terribly hard. I would request that the application builder and dashboard scripting be overhauled to make it a more easier to script/manage feature.
... View more
See more ideas labeled with:
Status:
Acknowledged
Submitted on
07-19-2024
09:40 AM
Submitted by
guillaumebugnon
on
07-19-2024
09:40 AM
What inspired this wish list request? Today, Process screening plateform assume only normal distribution.
What is the improvement you would like to see? Integrate all others calculation (percentiles) for non normal distribution.
Why is this idea important? To have a better plateform.
... View more
See more ideas labeled with:
☑ cool new feature ☑ could help many users! ☑ users can remove bugs on their on ☐ nice to have ☐ nobody needs it What inspired this wish list request? Via a user can edit the main menu and [on windows systems] the toolbars. Other menus cannot be edited. Unfortunately, some of the implemented functions have bugs - and some functions are missing. What is the improvement you would like to see? Please add the possibility to remove items from any right click / red triangle / ... menu and the possibility to add user defined items. This will allow us to fix tiny issues which won't make it into a future version of JMP - or just in many years. e.g. - Allow us to perform more actions when right clicking on column name on columns panel - Paste Column has a bug and should be replaced with a version without bug: JMP jumps Is it possible to customize the Add Formula Column menu to include customize functions? yes and no: - a user can not add user-Defined mini GUIs , e.g. to add Modulo to the portfolio. - Existing functions cannot be added to the menu by name. (TS-00152405) Why is this idea important? Less pressure on JMP developers to bugfix and fine-tune the GUI. Users don't have to wait for version N+2. -> Users will be able to bugfix and tweak the GUI on their own. other wishes from
... View more
See more ideas labeled with:
What inspired this wish list request?
Resetting preferences when changing JMP versions is problematic because pre-existing preferences often get removed. The JSL Set Platform Preferences() command does not run if missing preferences are listed. Additionally, the alert only gives a few messages at a time, so multiple iterations have to be run to work through the list.
What is the improvement you would like to see?
Is there a way to only generate the list of preferences set/modified by the user? The command currently seems to publish all preferences (unchanged/default and user set/modified). I primarily only care about the former.
Is there a way to have the JSL commands ignore missing preferences?
Is there a way to get a full list of missing preferences in one alert?
Can JMP provide detailed documentation on which preferences ihave been removed for a major version change?
Why is this idea important?
This will enable aster changeover to and adoption of new versions of JMP.
... View more
See more ideas labeled with:
What inspired this wish list request?
Working with data tables with hundreds or thousands of columns.
What is the improvement you would like to see?
Browsing columns pane is fast and it can be filtered down quickly and you cannot do that with column headers (or with the table). I would like to be able to perform more actions we can perform from columns header from columns pane. Especially copying/pasting/inserting but I wouldn't mind if I had all the possible options under some new drop-down menu.
One possible mock-up of the idea (there are some options which shouldn't be included and some are duplicated)
Why is this idea important?
Makes it easier to work with very wide tables.
... View more
See more ideas labeled with:
What inspired this wish list request? When automating repetitive work I often manually perform the steps and check the Log to see what the equivalent JSL is. What is the improvement you would like to see? I would like to see the Log show the equivalent JSL message when I change an axis label name. Why is this idea important? This will allow users to automate and write JSL without google searching.
... View more
See more ideas labeled with:
What inspired this wish list request?
The limitation of column switcher, that we cannot have same column used in multiple roles without running in all sorts of issues.
What is the improvement you would like to see?
I would like to see new switcher which would allow me to change the columns used in Roles instead of columns. You define which role in your report you wish to modify selections for, you select which columns include in that switcher and then it would work in similar manner as column switcher WITHOUT the worry that there would be collisions as those would be allowed.
Why is this idea important?
It would allow us to swap columns used for different roles without worry that the column is already used in other role at the same time.
This could maybe be combined with New filter "Column Filter" a combination of Local Data Filter and Column Switcher (better name for that suggestion could be for example Role Switcher or Column Quick Swapper like I did rename the add-in)
... View more
See more ideas labeled with:
What inspired this wish list request? When you click on a report various things happen including that a datatable associated with it may become current. I recently experienced some cases where I would like a different data table to be current in that case but I can't currently specify anything to happen when a report is clicked on. What is the improvement you would like to see? An OnActivate ability for a new window that would be similar to OnClose, OnOpen or OnValidate. This would be for when a window gets focus and comes to the top as happens when a user clicks the title bar. JMP does things in this case and this OnActivate would happen after those things. That way OnActivate could override what table JMP decided to make current and would generally have the last word on what happens. Why is this idea important? The cases I noticed were for reports with live plots where more than one table was involved or where the tables involved were private tables that can't themselves be made current. JMP support encouraged me to make this wish list request (case number below). Through my case with them I learned some of what JMP will do when a report is clicked on the upshot was that for complex reports with multiple tables involved it can be complicated and may be difficult to guarantee that it will make a particular choice. I also think there may be other useful things one might want to do "OnActivate" (maybe there are displays that could be refreshed in that case for example, and it just seems like a logical extension of the available functions.
... View more
See more ideas labeled with:
☐ cool new feature ☑ could help many users! ☑ removes something that feels like a „bug“ ☐ nice to have ☐ nobody needs it What inspired this wish list request? Insert Into automatically "flattens" the expression if the Head of the first and second argument are the same - causing some JMP Expr() weirdness . For lists the automatic flattening might be OK ... let's say for 60% of the use cases - but it "hurts" for the remaining ones. And for all the other (non-list) cases it's actually NOT what the user wants. What is the improvement you would like to see? Please add an option flatten(0|1) to Insert Into. Why is this idea important? less JSL weirdness → happy users : ) other wishes from
... View more
See more ideas labeled with:
What inspired this wish list request? I was trying to model some data as a Rice distribution, which uses a Bessel function in the PDF. What is the improvement you would like to see? I would like if JMP supported Bessel Functions, specifically Bessel Function of the first kind Jα(x) Bessel Function of the second kind Yα(X) Modified Bessel Function of the first kind Iα(X) Modified Bessel Function of the Second kind Kα(X) Why is this idea important? Bessel functions are used to describe the PDF of the Rice distribution, as well as engineering applications (heat transfer, wave propagation). They are currently supported in some other programs, such as SAS, Excel, MATLAB, and R.
... View more
See more ideas labeled with:
I would like to be able to use my JMP Pro License either on my laptop/desktop or in Amazon Web Services, rather than buying two separate licenses.
... View more
See more ideas labeled with:
What inspired this wish list request? As a reliability engineer, I frequently use the Life Distribution platform for its distribution plotting and fitting capabilities. These plots are important not only for internal topics but also for critical customer communications. Unfortunately, the method of plotting data points in this platform changed in JMP 17 in a way that is less desirable. These plots are often used to demonstrate the quality of fit of a distribution model to data. Such demonstrations can be crucial in obtaining acceptance. The Kaplan-Meier / Turnbull estimates used in JMP 16 were appropriate for this, as a good MLE distribution fit often came close to the estimates. For example, see the Weibull MLE fits below (same data table, different versions). Both MLE Weibull fits are identical, however JMP 17 points are significantly below the fit. This change to the default behavior is troubling - now I must question which version of JMP was used when reviewing plots. JMP 16 – “great fit!” JMP 17 – “not such a great fit?” (same fit!) In JMP 17 the user can select Points (black, default) / Step Function (red) / Both / None. Both selected below: However there are a some issues with this: User has no customization options for the red markers (which are what should be default). Need ability to adjust color, marker, size, etc. just like regular markers. Buggy behavior: selecting Step Function does not work when going from one of the other options. It works when the platform is first launched if selected as platform default in preferences, however when toggling from Points back to Step Function it once again shows nothing. Even if selected as default in preferences, once the “Nonparametric” distribution is deselected the red markers disappear and can only be recalled if “Both” selected. What is the improvement you would like to see? The default point positions should be the “step function” points (Kaplan-Meier / Turnbull estimates) to be consistent with previous versions. It would still be nice to be able to select midpoints, however each option should have full marker customizability. Why is this idea important? These plots are often used to demonstrate the quality of fit of a maximum likelihood distribution model to data. Such demonstrations can be crucial in obtaining acceptance. The previous default Kaplan-Meier / Turnbull estimates were appropriate for this, as a good MLE distribution fit often came close to the estimates. Deviating from this now with JMP 17 causes confusion and is inconsistent with previous versions.
... View more
See more ideas labeled with:
What inspired this wish list request?
Writing scripts and finally this post How to supress script dump in log upon closing a chart?
What is the improvement you would like to see?
1. Message / argument to prevent report snapshot from single report
I would like to see a message we can use to prevent a platform from being recorded when it is being closed which we could use when scripting. The message could be something similar as the preference we have
<< Report Snapshot On Close(0)
and of course it should be possible to use this as an argument in JMP Platforms.
2. A function which would change how snapshot behaves in current script
Being able to disable all snapshots created from a script could also be useful. The setting could work in similar manner as Names Default To Here(1); and maybe it could be called something like
Disable Snapshot On Close(1);
Why is this idea important?
When writing and using custom scripts it can get quite annoying when your log is being spammed with report snapshots. This can be already prevented by modifying preferences but I would like to keep preferences as they are as I like that snapshots are saved when I'm using JMP interactively and just prevent these snapshots from my scripts. There is also at least one workaround which works from time to time but this is very clunky to start adding to every report
Names Default To Here(1);
dt = open("$SAMPLE_DATA/Big Class.jmp");
nw = New Window("", gb = dt << Graph Builder(
Variables(X(:weight), Y(:height), Overlay(:sex)),
Elements(Points(X, Y, Legend(9)), Line Of Fit(X, Y, Legend(11)))
));
nw << on close(
gb << close window;
);
... View more
See more ideas labeled with:
What inspired this wish list request? I have a table that is already sorted in a specific manner and I can't resort it. I need to do a Column Statistic, but not a standard statistic. I can build JSL in the column formula to go through the whole table to create a matrix "by" the categories of interest, but for this larger table, the JSL layer would be pretty slow and inefficient. JMPs canned columns statistics already gather these matricies - and quite fast - so I would like to leverage that. What is the improvement you would like to see? I would like to see a column function that is more generic... so like ColMean(column, by1, by2, by3) returns the mean of a matrix of values by 'by1', 'by2' and 'by3' .... I would like a function that just returns the matrix of values prior to any math being done. Why is this idea important? As mentioned in the first section, coding this in the column formula would be very inefficient. Coding this in a separate script (a table script, perhaps) could be faster, but then not as 'live' as a formula in a column. With JMPs base infrastructure already existing, being able to leverage it further would be ideal.
... View more
See more ideas labeled with:
What inspired this wish list request? In other stat packages I have used I can get 95% confidence intervals for various MSA outputs, such as % tolerance, StDev, 6xSD, and % Study Variation. What is the improvement you would like to see? I would like to see the option of showing 95% confidence intervals for the following outputs: Both EMP and Variation Platforms: All possible output columns need CI's Variation Platform: Variance and % of Total need CI's, EMP: % of total only as Var Component is there already. Why is this idea important? CI are important for MSA studies as they help an investigator know if there is enough data in the study to be a useful result. I've seen people get a % tolerance of 25% and pat themselves on the back but the CI's are basically from 9% to 95% so you really have no confidence with the amount of data you collected. JMP 17.2 Pro
... View more
See more ideas labeled with:
☐ cool new feature ☐ could help many users! ☑ removes something that feels like a „bug“ ☑ nice to have ☐ nobody needs it What inspired this wish list request? For some of the settings in Preferences, A user can read: Get Platform Preferences( Bivariate( Fit Line ), DOE ); Get Preferences( Graph marker size ); and even change the settings via JSL: Platform Preferences( Bivariate( Fit Line( 1 ) ) );
Preferences( Graph marker size( "Large" ) ); Surprisingly, there are other settings in the preferences which cannot be accessed via JSL. Who defined which settings are available and which are not ? At the moment, I need JSL access to the graphics export settings - but according to Jmp support this is not possible. What is the improvement you would like to see? Please provide JSL read/write access to all settings in the preferences. Why is this idea important? "important"? no, it isn't. more wishes submitted by
... View more
See more ideas labeled with:
What inspired this wish list request? Multivariate platform's Outlier Analysis allows you to save Mahalanobis Distances, Jackknife Distances, etc to a column. It will plot these and show a calculated Upper control limit on those for current alpha - very useful for using the distances to assess whether a point is an outlier. JMP puts a single value (ie Jackknife Value) into the column properties (ie on the Jackknife Distances column) that is this UCL. However, if there was a By group, there are distinct UCL values for every group (based on number of non-missing points in the group) and this single value in the column properties appears to just be for the last group. One might think you could extract them from the platform's report but it doesn't seem like it - they are in Frameboxes, not textboxes in the report and I don't see a way to extract those values. What is the improvement you would like to see? In my use case, with a By Group I'd like the UCLs in a column as well. But what I'd like to see is maybe an ability to ask the platform for those, maybe similar to the way you can ask a fit in Fit Model for various calculated values using <<GetEstimates, and get a list of those for all the by groups. Related: it would be nice if in cases like this there were a good way to <<Get what the groups are in order to use that list of values better? At least I'm not sure how to do that without parsing it out of the outlinebox names on the report. Would be nice to get a handy list in same order as the values in what you get from <<getestimates so you know for sure what group each is for. It has come to my attention that different platforms vary in terms of what groups they will include in their report (or skip due to inadequate data) and the order groups will be in may not be as obvious as it used to be now that JMP will user "numerical ordering" in some cases. Why is this idea important? I think it's clear why the UCLs are useful - it's what you'd compare the distance to in order to see if it's a large distance, for a given confidence? Here's a community post where someone wanted this value, they just weren't using a By I guess because were happy with the single value in column properties:Solved: Jackknife Predicted Values - JMP User Community
... View more
See more ideas labeled with:
What inspired this wish list request?
I was trying to make some errors easily visible in wafermaps and started playing around with Fill Selection Modes. I managed to make my graphs visual enough (but there is no "perfect" option), but I could make it even more visual if I could combine multiple modes (at least two). Also changing and trying out different options requires me to go through multiple menus using mouse.
What is the improvement you would like to see?
I have few suggestions regarding Fill Selection Mode in JMP graphs to make JMP visuals provide more information quicker. There are a lot of different situations where JMPs default option of Selected Patterned isn't really that helpful. I will use Wafer Stacked.jmp as an example dataset for most of these with this starting situation (stacked wafermaps and Defects mean used as color) and I have selected some random areas. There are a lot of other situations where diffee
Not very easy to see QUICKLY what has been selected if I'm using default option "Selected Patterned".
1. Let us combine multiple Fill Selection Modes OR provide new options which have these combinations predefined
Depending what you are trying to present, you might want to highlight your graphs in different ways. In this case I would like to quickly highlight the specific areas of wafermap. Few selection modes work quite well
Selected Darkened
Selected Outlined
Unselected Faded (best for this case in my opinion with current options)
And finally Selected Same Color (otherwise good but it is difficult to change the color AND I will lose information on the graph, so I wouldn't use this in this case)
But what I would like to do is to combine these (at minimum two) or at least have few new options. I would like to combine at least Selected Outlined+Unselected Faded or Selected Darkened + Unselected Faded.
Demonstration of Selected Outlined + Unselected Faded
And in this case maybe better option Selected Darkened + Unselected Faded
2. Let us easily change the Fill Selection Mode without always going though the hassle of right-clicking the graph
Drop-down menu toolbar could be one idea, similar to data table list in Script Editor (of course dropdown wouldn't work unless they are checkboxes if we can make our own combinations). I will most likely write my own add-in which will let user to go to next selection by pressing a button (or shortcut key) for now.
3. Let us easily change the "Fill Selection Color" from somewhere else than JMP Preferences or make the color choice somehow smarter.
Currently I don't know if this color can be changed anywhere else than preferences and depending what I'm doing, the preference color might be very bad.
4. Maybe nice to have in some cases let us define which Pattern to use when using Selected Patterned
Sometimes different pattern could solve a lot of visual issues. We do have a lot of different patterns already available, they are just "never" used
Why is this idea important?
Makes JMPs visuals more visual, quicker and more easy to use.
Other
Other a bit similar suggestion for just graph builder and marker selections: Graph Builder: Marker Selection mode -> multiple selections!
... View more
See more ideas labeled with:
-
Data Exploration and Visualization
548 -
Automation and Scripting
439 -
Mass Customization
325 -
Data Access
235 -
Basic Data Analysis and Modeling
229 -
Data Blending and Cleanup
221 -
Content Organization
176 -
Sharing and Communicating Results
164 -
Advanced Statistical Modeling
140 -
Quality and Process Engineering
117 -
Predictive Modeling and Machine Learning
104 -
Design of Experiments
89 -
Reliability Analysis
58 -
Consumer and Market Research
41
- © 2024 JMP Statistical Discovery LLC. All Rights Reserved.
- Terms of Use
- Privacy Statement
- About JMP
- JMP Software
- JMP User Community
- Contact