JMP Wish List

What inspired this wish list request: In my field, electronic notebooks (ELN) seem to be everywhere. While they bring critical benefits, the few that I've used don't seem well set up for experimentally designed projects. It's very much "what did you do" first, and data second. With a DoE, to use the lab notebook correctly, depending on what software you have, you might have to do a whole new entry for each experiment, an entirely unwieldy premise that deters one from using ELNs correctly.   On the flip side, especially with projects, JMP invites you to include all of your data because it is so straight-forward. However, one of the lackings is that while I want to store as much info as I can in JMP, I can't store my non-numerical data, not easily at least. Currently I'm sitting on hundreds of photos that I took of different steps in my experiment. I could put them in the data table, but that would become cumbersome extremely fast. Aside from the annoyance of having to deal with even more columns than the 200+ I already have, during some experiments I took one picture for a given step, while during others I took 5. Given that there's no organizational principle to how I took the pictures, some picture columns would be sparse, while others dense: an underutilization of JMP's great column functionality.   Additionally, and maybe more importantly, there is the general problem of proper transfer of knowledge, especially in academia where there is high turnover of students. Many of the lessons learned come not from the data, but seeing what was noted at the time of experimentation. However, with lab notebooks, just going through the lab notebook from some random person you never met from years ago on a project you don't know can be both daunting, and sometimes counterproductive. In my experience, it almost never happens. ELNs can make this process much easier because of their search features, uniformity of input, etc. However, the problems with ELNs stated before remain, especially in that they are often optimized for "what did you do" rather than the data and analysis. JMP has virtually no way to do this, except to upload a picture of a lab notebook into a project file, which would be as likely looked at as the physical pages in the lab notebook.   What is the improvement you would like to see: I think a few things would be very useful for researchers: Associate photos with rows and columns: Allow a set of pictures to be associated with a particular column or set of columns, each picture being assigned to a row (or set of rows if the same setup use used for multiple experiments, such as in a split-plot experiment). Notation and maybe even image markup (e.g. drawing an arrow to an important part of an instrument, or, in the case of an image associated with multiple columns, assigning parts of the image to different columns) would also make sense here. Quick access of the experimental photos: This is rather self-explanatory, but I'm not sure the best way. Perhaps have a view mode that draws small outlines of the regions that are associated with a particular image? This wouldn't work though with tons of overlapping regions if there were any. And then possibly a persistent hover window of the photos that you are interested in that you x out of, can drag around, resize, and scroll through that you could access from clicking on a cell, column, or row, with the option to do a pop-up or new file if using JMP projects. Save images of notebook pages with metadata: Have images of notebook pages stored in a way that relevant sections can be accessed while browsing data. Something like NVivo would be overkill, but a simple click and drag a box, polygon, or freeform line around the important area of a lab notebook and associate with individual/set-of cells/rows/columns. I'm envisioning something like this: I'm looking at the JMP table for some experiment, see some weird outlier in row x, click some button or press a hotkey, the lab notebook page pops up, and I can read what was written when the experiment was performed, and ah! that was the day before we found the clog in instrument Y, which was used in this experiment. Now I have reason to suspect this outlier is due to instrument failure rather than a true outlier. Could this be done by re-reading the physical lab-notebooks? Sure! Would it be a thousand times easier to not have to go back and forth between the physical copy, which may have pertinent info across multiple pages, and the computer screen, but rather have associated sections available next to the data on screen? YES! Related Idea One of the issues with JMP is when you have a gagillion columns. Lots of rows is manageable, but tons of columns can get confusing fast. And while column grouping is very helpful, a more general overview would fit well into what I've said above. A common tool, especially in business, is a process map. In STEM, a process map could summarize a variety of things: a manufacturing process, a mechanism, an experimental procedure. If process mapping were implemented, then a very complex JMP table could be given an overview, where different columns are associated with different steps in the map. For example, if the map represents an experimental procedure for a chemical reaction, the concentrations, temperature/pressure, reaction vessel size, etc could be associated with one step, while the crystallization condition columns could be associated with step two, and the final yield could be associated with the third (analysis) step. In my mind, I'm envisioning zooming out from the data table, and a process map fading in, with associated column names listed under each step in the map and maybe even pre-scripted analyses, but I'm sure there's a better way to do it. Because process mapping is a "related idea" and not the main one, I'll put the "why this idea is important" here: While JMP journals and dashboards have some aspects that touch on these ideas, having an overview of a process, experimental procedure, in a graphical, interactive format that's connected to the data, either in the data table or in a journal, would be very helpful for both the experimentalist's brain-space, especially with many-column'd tables, as well as in communication of results, especially with people in a meeting or conference unfamilliar with a process.   Why is this idea important: Because of its easy-to-use and feature-rich, JMP (rightly!) invites the user to make JMP the hub for data exploration and analysis. However, the process of experimentation and collecting data is just as important as the data itself, because a poor experiment will generate poor data. Poor communication of what you did will also lead others to have poor experiments.... leading to poor data. Adding functionality to store your non-numerical experimental info in an easily referencable way would very much help organization, analysis, and tech transfer.   Note: There are a couple of related wish-list items that readers should go upvote: Process Mapping: https://community.jmp.com/t5/JMP-Wish-List/Process-Map-Value-Stream-Map/idi-p/564386 Mark-up Notes: https://community.jmp.com/t5/JMP-Wish-List/Mark-up-notes/idi-p/394570 ... View more

☐ 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?  In general, Jmp doesn't distinguish between upper and lower case - and Jmp ignores white spaces in Symbol names. So, :age can refer to the same column as :A G E  But :age and  :A G E can be also different columns. check if column exists?    JSL ignores white-spacing for names, most people don't take advantage of this!    Let's take the Concatenate platform as an example. This platform is very picky with column names. If Table A has a column :age and table B has a column :A G E,the combined table will contain 2 columns! In general this is a nice feature: better split the columns, the user can merge them later.   But for user who lived the carefree life of "difference don't matter" - the first collision with Concatenate can be traumatic.   What is the improvement you would like to see?  In Concatenate (and other platforms?) please provide an option "Column Names: Exact match". If the option is on, Concatenate is as picky as now, if it's off, Concatenate follows the usual rules of JMP/JSL when comparing column names.   Why is this idea important?  - The option will give the user more possibilities.   - The presence of the option will generate awareness!   - The idea is related to the option Exact Match (1 |0) of   dt << has column(), which will be introduced with Jmp18: data table : message column exists(colname)?    more wishes by   ... View more

☑ cool new feature ☑ could help many users! ☑ removes a „bug“ ☐ nice to have ☐ nobody needs it   @myTop10_2024 What inspired this wish list request?  For Line Graphs in Graph Builder, there is a cool feature row order. If it's selected, the line doesn't connect data points from left to right in the graph - but along the order in which they appear in the data table.   Instead of this graph: the user gets this graph: Much better ...   But unfortunately, there are those nasty jumps "back" to the next curve. Of course, for simple graphs, you can use a column (here "Station") as an overlay to produce 3 separate curves, without the zigzag. But already with slightly more complicated graphs like this one here: Graph Builder. Combine Smoother and Line - how? the user reaches the limits of current Graph Builder (v17, v18).       What is the improvement you would like to see?     With sorted data in the data table, a step from right to left indicates a new curve. So, with row order enabled, there could be an additional option to draw lines  "only left -> right". If this option is enabled, line for steps from higher to lower values will disappear -> the jump back-lines are gone : ) Fallback:  Rows with missing y value could be used to add a break in line graphs (even somewhere in the center of the graph - cool, right?) ... if there was an option: *)   Why is this idea important?  a tiny change of the program - a  tremendous improvement for the users: dt =Open( "$SAMPLE_DATA/Functional Data/Weekly Weather Data.jmp" ); dt << New Column( "group",Character,"Nominal",Formula( Substr( :STATION, 8, 1 ) )); Graph Builder( Size( 523, 407 ), Summary Statistic( "Median" ), Graph Spacing( 4 ), Variables( X( :DATE ), Y( :TAVG ), Overlay( :group ), Color( :group ) ), Elements( Line( X, Y, Legend( 31 ), Row order( 1 ) ) ), Local Data Filter( Add Filter( columns( :STATION ), Where( :STATION == {"USW00003195", "USW00003868", "USW00003949"} ), Display( :STATION, N Items( 15 ) ) ) ) )   more wishes by   ... View more

What inspired this wish list request? Managing jmp licenses can be tedious if we have a lot of licenses and employees resign or arrive. Corporate user management systems (like Active Directory or other SSOs) always need to be up to date, so if we can have an API to add or remove users on my.jmp.com, that would be very useful.   What is the improvement you would like to see? All actions that we can do manually in the my.jmp.com console should be possible with API and be documented.   Why is this idea important? Manage jmp automatically and not manually. ... View more

JMP does an amazing job of chugging along so even long analyses get done eventually (unless there are hardware limitations). However, sometimes these long processes are kicked off on accident or without realizing how long they will actually take.   I would like to suggest a way to kill the current process so the single thing I started stops, but I don't have to force close all of JMP and lose any other work I have going on. I know myself, and many colleagues, have done these things - from an accidental click to a botched while loop - so a way to save JMP from this 'killer process' would be greatly appreciated! ... View more

What inspired this wish list request?  Trying to move my preferences between few PCs and running into issues when ALL preferences were exported instead of just changed. For example I'm not really sure if I would really like to set incorrect CPUID as it seems to be included in Get Preferences()   What is the improvement you would like to see?  Add << Changed option to Get Preferences(). It can already be found from Get Platform Preferences() Utility Functions (jmp.com) . With this we could get the list of the preferences user has changed. You could also provide function such as "Get Default Preferences" so we could always check the default preferences JMP uses.   Why is this idea important?  Makes it easier to take backups or move JMP preferences between different laptops when not ALL preferences are copied over. ... View more

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. The Analyze tab in the Easy DOE platform gives a cool plot of the model terms included in the chosen model along with associated confidence intervals. Easy DOE is better for newer users, but more intermediate/advanced users could benefit from this graphical display as well. The full reference to the plot is found here - Analyze (jmp.com).   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. Implementing this in either the Fit Least Squares or Generalized Regression platforms (it would look good potentially as an option near the Solution Path graphs).   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,…). Being able to harmonize output across platforms can be important to the user experience. A newer engineer leveraging Easy DOE can make a nice plot that a more experienced engineer that is using standard menus such as Fit Model are unable to reproduce. Easy DOE is also more of a front-to-back, end-to-end bundle of content for a DOE, so it is difficult to just get a singular extraction from the platform. It would be simpler to implement the Effect Plot in other model-fitting platforms.     ... View more

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

☐ cool new feature ☐ could help many users! ☐ removes a „bug“ ☑ nice to have ☐ nobody needs it   What inspired this wish list request?  I want to clean up a data table with a few hundred columns. A few columns are used in formulas and have to be replaced by new columns. The remaining columns can be deleted. When deleting the old columns, it is difficult to identify the columns which are used in column formulas.   What is the improvement you would like to see?  1) Please display a symbol next to columns that are used in Formulas.   2) Please provide a functionality to generate a formula lookup map. a) The map should list all formula columns with the columns used in the respective formula. b) In addition the Window should provide a list of all columns which are used in any Formula column.   e.g.    ratio = height / weight myequation= (height - weight)^sex   a) - ratio: height, weight - myequation: height, weight , sex   b)  - height - weight - sex   Part a) is useful to get an overview and to work on specific formulas,  Part b) is useful for batch-replace:  A right click menu should be available which allows to replace the specific column in ALL column formulas with a replacement column.   Why is this idea important?  Will help to edit column formulas after changes of the input column names.   more wishes by   ... View more

The main data source for new JMP users will always be Excel. These can be messy, and probably used as database with manual input for KPI tracking, for example. However, neither the Excel add-in, nor the Excel wizard provide a simple way to update file from its source. This is a common request that can be found in this forum, multiple times, and all of them require scripting (see examples below). You can see the understandable response of beginners, that are drag into a complex solution to a simple request. Updating columns, adding new rows, adding new columns, all of these are complex concepts that require several steps and getting into automation via JSL or Automation Builder. JMP needs to include a wizard to automatically generate a script that reads and updates the current data table in place. https://community.jmp.com/t5/Discussions/Automatically-update-quot-source-quot-file/td-p/324299 https://community.jmp.com/t5/Virtual-JMP-Users-Group/How-to-update-a-JMP-data-table-to-reflect-Excel-updates/td-p/228625 https://community.jmp.com/t5/Discussions/How-do-I-automatically-update-JMP-data-table-while-populating/td-p/247303 ... View more

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

What inspired this wish list request? The need to automate JSL encryption     What is the improvement you would like to see? 1) A way to get around the login requirements when running tasks without direct user interaction. 2) A stand-alone package (DLL, etc) that can be called outside JMP completely but which can encrypt the file with JMPs proprietary encryption algorithm -- this would also make it easier to encrypt as an automated deployment of tools without the need of stand alone computers.   Why is this idea important? I have desktop computer I use to run some automated tasks in JMP with - typically with windows scheduler. With the new method of logins with JMP 18, if I log into another PC (assuming the desktop is the 2nd one currently logged into) I will have to re-log into the desktop or the scheduled tasks will fail. JMP 18 is also the first version where the JSL encryption function works correctly so that automated encryption is possible. Why does it need to be automated? It's part of the deployment of JMP addins from github where the code is created in github but when packaged it would be encrypted so the end user wouldn't have access.   ... View more

In manufacturing is very common to handle datasets with more than a hundred columns, each corresponding to a sensor. Manufacturing systems have a tree hierarchy that is defined in PI AF (also used in JMP 17 and PI to find the sensor names).   This information is lost when moved to a JMP table.  We open-sourced an add-in to reorganize columns (see image and code here)   However, JMP only allows two levels (parent group and child), which is very limiting in terms of organization and analysis. For manufacturing data, multiple grouping levels are a must-have or users won't be able to use JMP for their daily tasks in manufacturing (too much information to handle).   Please have a look at PI AF to understand how engineers are used to finding data. This information can be coded into a column property. This metadata can eventually allow users to swap analysis between assets. ... View more

What inspired this wish list request?  There are many platforms where you can be asked to input a value, sometime the input box is pre loaded (such as in gauge R&R where a spec limit has been assigned to the column) or other where you have to enter it for each analysis (such as an equivalence level in Distributions).  However, you cannot broadcast these settings which means you can be set up for having to click the "okay" button a bunch of times to get the analysis to run.  A specific example is trying to broadcast turning on a GR&R analysis in the Variability Platform.  Here I entered the Meta data spec tolerance range but when I held down control and clicked the Gauge R&R button in the menu I then had to click through this menu pop up 10 times (as I have 5 responses for two different codes in the "By" factor)         What is the improvement you would like to see? I would like to see the ability to broadcast the value of a manual input across all input boxes or use the input of the meta data without having to click okay on each box.   Why is this idea important? This would align the expected results of using the broadcast function and also save the user from having to sit there and click dozens (if not hundreds) of input boxes to process the analysis. ... View more

☐ cool new feature ☐ could help many users! ☐ removes a bug ☑ nice to have ☐ nobody needs it   What inspired this wish list request?  - The analysis options in Life Distribution are wonderful. - Graph Builder is great for generating condensed Trellis Plots. How to combine both of them? https://community.jmp.com/t5/JMP-Wish-List/Add-CDFs-to-Graph-Builder/idc-p/773025/highlight/true#M5793 TorP ‎07-15-2024 12:46 PM Distribution graphs are the main reason we still use Minitab in our department. Currently it still produces such graphs faster and easier than jmp. (Minitab has much less evaluation options in the reports, but that's secondary if you first need the distribution graphs.)   Example w/ data from Big class.jmp Minitab: Automatic settings, 3 clicks in dialogue window     jmp (no JSL, just std. options) 1. Graph Builder Automatic settings       y-axis manually set to Probability Normal and adjusted to 0.01 and 0.99     2. Lifetime Distribution Automatic settings. Nice graphics, but - No panel option - No info about distribution type (Normal, Weibull,...) and CI - Legend missing when copied w/ "Copy Graph" (available in original report)   Summary: Such graphs in the graph builder w/ the above issues fixed would really be appreciated. And it seems like most pieces are already available, but in diff. places/platforms? It's unlikely that Graph Builder will be enhanced with all the functionality which is available via Life Distribution   What is the improvement you would like to see?  For Life Distribution, add an one page overview graph with all plots: (best)           with the nice fits from Life Distribution (also OK)     as a GraphBuilder Plot without fit curves   maybe with a)  info about the underlying fit (like in Minitab) b)  button for single click copy to clipboard (incl.info from a) and the legend) c)  options to globally change the fitting settings.   Why is this idea important?  not "important"     other wishes from  ... View more

☐ cool new feature ☑ could help many users! ☑ feels like a „bug“ ☐ nice to have ☐ nobody needs it   Short: Remove this "bug": ... and this one:             Long: What inspired this wish list request?  If reports are open, Jmp is not able to sort a data table: https://community.jmp.com/t5/Discussions/How-to-update-table-after-sorting/m-p/659014/highlight/true#M84836    Same issue for data tables with linked subsets: sorting and concatenating data to the data table doesn't work. Similar issue if a user wants to add rows to a data table .   linked subset: sort → no add rows → no concatenate → no   open report: sort → no add rows → yes concatenate → yes   What is the improvement you would like to see?  Please remove the restrictions.   e.g. "cut the link", like it's done for linked summary tables: sort → no [why does SORT not "cut the link"?!?] add rows → yes² concatenate → yes²   ² JMP automatically cuts the link:     Why is this idea important?  It's very likely that a user opened a linked subset, a linked summary table or a report before he tries to sort a table or add new rows. Therefore, JMP users face this issue very often.       more wishes by     ... View more

What inspired this wish list request? I use multi-layer "Group X" in graph builder often to look efficiently at multiple categorical outputs (and especially nice when I want to bin continuous outputs).  However, if I have a lot of levels then the Group X axis can smash the data up too much.   What is the improvement you would like to see? I would like to be able to stack another column under the column used in the "Wrap" view in Graph builder. So go from this: to this:         Why is this idea important? This allows more the Group X axis to be more useful when looking at two columns you'd like to stack in the axis (and frees up even more drilling down possibilities since now Overlay can be used for a third column)   Thanks Steve     ... View more

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

DUPLICATE OF Allow secondary or alternate column names  ☑ cool new feature ☑ could help many users! ☐ removes a „bug“ ☐ nice to have ☐ nobody needs it #myTop10_2024   What inspired this wish list request?  Often incoming data is quite cryptic and some data curation is needed. Jmp already provides nice solutions, which help the user to curate the data "on the fly", like recode.   Many of the curation steps are "persistent" - such that no further curation is needed when the data table gets updated with the latest data: - formula columns - column property: Value Label - ...   A special issue are column names: Ho to handle cryptic Column names?  Here there is a clear trade-off between human-readability and compatibility to incoming data.   - The user might rename a column -  but then the data table cannot be updated anymore. - the user might add an additional column with the correct name and link it to the original column by a column formula - but this approach is just useful for a few column names. - possibility to give columns different names in different languages - save the alternative name as a new column parameter + Script to toggle between original and alternative column names.   https://community.jmp.com/t5/Discussions/Ho-to-handle-cryptic-Column-names/m-p/722751/highlight/true#M90501    I guess everyone has found their own workaround to deal with the problem. Surprisingly, there is no "official" solution, like column alias   What is the improvement you would like to see?  Please add a new column property: Column alias If a column alias is defined, - the alias column name replaces the column name in the table header, all lists, reports, plots and views. - the alias column name can be used alternatively in filters (so the user can search with the original and the alternative name) - it can be used in Table operations like update and concatenate - as an alternative to the original column name     Why is this idea important?  Significant simplification of data curation :) more wishes submitted by   ... View more