JMP Wish List

☐ cool new feature ☐ could help many users! ☑ removes a „bug“ ☐ nice to have ☐ nobody needs it   What inspired this wish list request?  this community discussion : Graph Builder: Unclear statistics when using multiple response columns    @gnu23 wrote: I think the discussion boils down to the question, if statistics on multiple response columns should generally either use the number of responses (standard now in JMP) or the number of rows as 'n'. In my opinion the second option would make more sense for many use cases and an option to switch between these two values for 'n' would increase the (already very nice) functionality of multiple response columns.     The default statistics in Graph Builder for counts and percentage, is (*):  "one row counts one - Ntotal (denominator for percentages) is the number of rows". [This statistics can be adjusted via the Freq/Weight drop zone.]   Surprising: If a column with modeling type "multiple response" is used ANYWHERE in the graph, the statistics changes to "one response counts one [OK] Ntotal (denominator for percentages) is number of responses" [maybe: not OK].   So, to generate meaningful bar charts on the porcelain layer, it seems that on the plumbing layer Jmp  stacks the individual responses, creating additional "rows", and then applies the standard logic (*) For simple bar charts, this might be reasonable, but for Ntotal and the calculated percentages it leads to funny/strange effects.   What is the improvement you would like to see?  Please provide a more meaningful statistics for Multiple Response (e.g. as an alternative to the current version): "one response counts one But: denominator for percentages (Ntotal) is the number of rows contributing to the plot - like in standard Graph Builder"   on the plumbing layer one might think of: Any column with multiple responses is split into "indicator columns", representing each response - the number of rows stays constant. This approach is much closer to the default Statistics in Graph Builder. As a side effect, this alternative approach will also fix a bug which shows up if multiple columns with modelling type "multiple response" are used in one graph: https://community.jmp.com/t5/Discussions/Graph-Builder-Unclear-statistics-when-using-multiple-response/m-p/754313/highlight/true#M93647    Why is this idea important?  a) Meaningful statistics. b) no misleading statistics anymore for users who don't "notice"      other wishes from  ... View more

Suggestion:  Please treat missing data (and missing value code data) for ordinal X/Factor variables the same as continuous X/Factor variables when the informative missing option is selected.  That is, test to see if missing is better grouped "high" or "low".  Right now, it appears to be treat the missing value (or missing value code) as an ordinal value and assign it accordingly.  ... View more

☐ cool new feature ☑ could help many Jmp users! ☐ removes something that feels like a „bug“ ☐nice to have ☐ nobody needs it      What inspired this wish list request?  In a Data Filter there is a hidden feature to include / not include rows with missing values in a column with modelling type continuous:   If the red triangle menu is closed, the user cannot see if the option is on or off.     What is the improvement you would like to see?    1) In the main display box of the Data Filter, please add an indicator that shows if "select missing" is on or off.   2) In the main display box of the Data Filter please add a function to activate/deactivate "select missing".   Why is this idea important?  Missing Data is extremely dangerous - especially if the user doesn't know/see how Jmp handles this data.   more wishes from     ... View more

☐ cool new feature ☐ could help a lot of Jmp users! ☑ removes something that feels like a „bug“ ☐ nice to have ☐ nobody needs it   What inspired this wish list request?  The Column Switcher is very useful - but it has one major drawback:    The user can only specify which column to replace - but not WHERE in the graph. If a column appears in multiple places in the graph, ALL of them are replaced with the new column selected in the Column Switcher. So Column Switcher feels a bit like "Column Switcher light".   A great add-in that solves the problem:  Column Quick Swapper - easily change multiple Y and X-axis columns in Graph Builder    What remains is the opposite issue:  A column is only replaced by Column Switcher, if it appears directly in GraphBuilder. If a column is used in a Transform Column, Column Switcher ignores it.   What is the improvement you would like to see?  Please add an  option to Column Switcher to replace columns in Transform columns as well.   Why is this idea important?  Column Switcher is cool  - Transform columns are essential for certain use cases. Column Switcher + Transform Columns is a nightmare.    With the new functionality, Column Switcher + Transform Columns will become a dream team :)   more wishes from       ... View more

☐cool new feature ☑ could help many users! ☑ removes a „bug“ ☐ nice to have ☐ nobody needs it   What inspired this wish list request?  short: some remaining BUGS how Jmp handles dates and times. long: With Jmp 16, the import of date and time formats got a bit easier: How do I apply Custom Date (and Duration) Formats in JMP?    It's like a GUI version of Informat and provides features which before were just available via Date Formula Writer / Data Table Tools Add-in @brady_brady    But still, there are some time formats which cannot be imported correctly, like - Monday, March 22, 2023 5:06:07 +0100 - 2023-12-31T01:02:03.099Z     What is the improvement you would like to see?    Please optimize the functionality of the Input_Format option:   - add an autodetect button. One doesn't need AI to see that 2023-12-31 is YYYY-MM-DD          ... maybe the user just has to specify the meaning of +0100 - add a placeholder to read in the correct time zone offset (+0100) - add a placeholder to read in infos like CET, ET, ... - add a non-greedy placeholder - to tell Jmp to ignore all strings in front of the comma, like Monday, - or Montag, - add a history: Custom Time/Date Format Pattern: history  - add a way to specify default values: Input Format Pattern - default values  - add a display box and shot the first entry of the column -- like it's available in Date Formula Writer / Data Table Tools Add-in @brady_brady  - add support for ms time codes: https://community.jmp.com/t5/JMP-Wish-List/Date-Format-Pattern-additional-functionality/idc-p/736976/highlight/true#M5354    - <DayofWeek>, <Month>, <MMM> should be UNIVERSAL - please don't restrict the input to the local values. Actually similar to </> which produces a well defined output, but is very open with the input: ".",  "/" ... alternative: in InputFormat,  please provide a possibility to specify the regional settings e.g. in my system with german regional setting, I can read in "Freitag, März 20",  but not "Friday, March 20 " ! Please note that "Freitag" is replaced with "Sonntag" anyways  - so, even more frustrating that "Friday" is not allowed.   Why is this idea important?  Date and Time format import is one of THE annoying thing which users are frightened of. Jmp already provides some features which help a lot. But they feel like a Light version of Date Formula Writer / Data Table Tools Add-in from @brady_brady ...     other wishes from  ... View more

☐ cool new feature ☐ could help many users! ☑ feels like a bug ☐ nice to have ☐ nobody needs it   What inspired this wish list request?  In Jmp, there are 2 approaches to generate Transform Columns. 1) by talking to a data table: - the transform column is generated with Table Scope - so, the Transform Column "lives" outside the context of the platform it is generated for. - there is a Replace option: either a pre-existing Transform Column is replaced (setting: 1) or the name of the new Transform Column is adjusted (setting: 0) - The Transform Column is easily accessible, e.g. by using the return value of the command = handle for the generated transform column 2) by talking to a report 2b)  via platform << Transform Column() - this Transform column is generated in the scope of the platform - and will we deleted once the platform is closed -> very useful :) This is why this is the default approach how Transform Columns are used in Graph Builder, Summary and all the other platforms. - unfortunately, there is no replace option. If there is a Transform Column with the same name, the command is ignored (!) and the exiting Transform Column is used instead. -  unfortunately, Transform Columns which are generated by a platform are very hard to access: how to reference a Transform Column?  e.g. how to remove a Transform Column? What is the improvement you would like to see?  Although it works like designed, it definitely feels like a bug. It's hard for a user to understand that there are several tasks doable via the GUI which are not accessible via JSL.   Please improve the functionality of Transform Columns which are generated in the context of a Platform: return a handle for the column - - analogous to the one of the first kind of Transform columns add a replace option - analogous to the one of the first kind of Transform columns   Why is this idea important?  GraphBuilder has cool features to aggregate data via Summary Statistics - but important functions are missing, like CDF . Transform Columns provide a possibility to close such gaps - but the limited functionality of Transform Columns in the context of a platform make it difficult.   Example: If a user changes the selection in a Local Data Filter - how to update a Transform Column to account for the changes?         more wishes submitted by   ... View more

What inspired this wish list request?  I often find myself with new data tables that are almost identical to old ones.  I need to pull the plotting scripts from the old tables into the new ones.   What is the improvement you would like to see?  When I drag a script from the top-left pane of a data table window to another window, it looks like it's accepting it, but then nothing happens.  I would like to be able to copy a bunch of scripts from one data table into another via drag-and-drop.   Why is this idea important?   The script drag-and-drop is an intuitive action that seems to work, and it's frustrating that it doesn't.   (JMP v17, Windows and Mac)   ... View more

Dear Sir/Madam,   I've been dealing with information (eg yield table) from different subcons, on same product.  However, the tables may contain slightly different column names but they're meant to be on the same column.  Hence merging the tables from all subcons is a nightmare!     I have attached a simple table to illustrate what I need to accomplish.   If you could help to develop a command to merge tables with similar column names, that would help me (and JMP community) alot!     Thank you in advance!   Best regards, Voon Yean Ten An engineer from Broadcom   ... View more

What inspired this wish list request?  In this Heatmap plot, the cells 1-3 are a mixture of 100 red with tiny amounts of green - but they are quite transparent and quite green. Heatmap Plot - mixing colors  Seems that the transparency levels are mixed before colors are mixed, instead of mixing the colors with the respective transparency levels.   What is the improvement you would like to see?  Please adjust the code for color mixing such that 100% red + some green gives something close the red.   Option 1: Please add different blend options to control how colors are mixed, like (from paint.net)   Why is this idea important?  fewer bugs -> happier users :) ... View more

What inspired this wish list request?  Testing results very often include non-numeric entries such as "N/A" or "Nil" in columns consisting of otherwise continuous numeric data. This causes JMP to class it as "Character" data, resulting in the need to recode and then reclassify the column.   What is the improvement you would like to see?  I'd like JMP to be able to bring up an error message to say: "Column X's data is continuous and numeric apart from rows 35 ("N/A") and 37 ("Nil"). Would you like to change these to numeric entries?" "Yes" would then bring up a window where I could recode these two rows and it would automatically be classified as continuous numeric.   Why is this idea important?  It's easy to stick to rules for data recording if you're generating and doing the recording yourself, but if you're contracting out or getting help from others, these errors can sneak in (and I suspect they're pretty common!). This sorts of studies tend to have large data sets and to be able to work with the data without having to recode would be ideal.   ... View more

Hello, When porting the output data from Matched Pairs to a (combined) data table, the various parameters are split into multiple columns. This makes the data cumbersome to use. It would be preferable for the various parameters (Mean Difference, DF, t-ratio, Prob > |t|, etc.) to be put into separate columns (with the appropriate column headers). Alternatively, they should be tabulated as stacked, with the headers in a Label column and values in a Data column. Once the data is available in one way or the other, it can be handled more easily. With the current approach, it's neither here nor there.   Regards Mehul Shroff ... View more

What inspired this wish list request?  The new Data Preview in the Tables Platforms are extremely useful. The same holds for the Recall button.   Unfortunately, there is a conflict between both functions: After a click on the Recall Button, the GUI interface is filled with the stored values - step by step for every single entry. And every single GUI update triggers a Auto-Update of the Data Preview. No big issue - but as Replace Column Values is set to All by default (?!?!), there are cases where a Replace doesn't work - and Jmp throws an Alert - step by step with every single update of an entry. In total: 10 error messages.   What is the improvement you would like to see?  Please disable the auto-update of the Preview till all GUI items got updated by the Recall button   Why is this idea important? With the proposed improvement, the user will see the Alert just once - not 10 times.     ... View more

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.   ... View more

Hello,   I would like to request a function to be added to the Rows menu to delete duplicate rows based on a matching cell except for the first (or selected) one. Currently, one has to first select matching cells, unselect the first occurence, and then delete the remaining. In a large dataset with several unique sets of duplicates, this can be extremely cumbersome.   Thanks and regards Mehul Shroff ... View more

From time to time I come across situation where I would like to quickly check if two columns have exactly same results in rows. I usually do this by writing new column with :COL1 == COL2 for example. It would be nice to have this as an New Formula option in right click menu (and hopefully support more than 2 columns). ... View more

What inspired this wish list request?  When writing jsl scripts that update large tables it is cumbersome to add a <<begin data update() and <<end data update() on either side of the for each row().   What is the improvement you would like to see?  I would like to see some functionality for <<begin data update() and <<end data update() embedded in the for each row() function.   Why is this idea important?  This will make code more readable and faster if users write all for each row() using the new functionality. May improve GUI speed as table updates will be faster.   I am using JMP 16.2   ... 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 New Formula column submenu in the column right click context menu is very useful to quickly generate new formula columns. But: Often a user just wants to get a column with the values, without the need of a formula column. compare the options of Recode:     What is the improvement you would like to see?  Please add an option to the New Formula right click context menu, allowing the user to toggle between - Formula Column and - New Column (just calculate). A third option could be: - Formula Column (1x) like it is implemented in the Normalize Function of the QuickSelect Toolbar  : This way a Formula Column is added to the table, but the evaluation is disabled after a first calculation.     Why is this idea important? With the additional option available, a user can generate "pre-calculated" columns as easy as he can generate formula culumns. The third option would allow the user to generate a pre-calculated (non updating column) with the additional benefit that the calculation is stored/freezed - ideal for documentation, and with the possibility to reactivate it.         more wishes submitted by     ... View more

What inspired this wish list request?  The New Formula column submenu in the column right click context menu is very useful to quickly generate new formula columns. But the user is somehow "lost" if the desired function is not available or if he want to generate a special function. Then he has to generate a new column, and add a formula manually manually.   No big issue ... But let's look at the Filter Col Selector right click context menu, e.g. by right clicking on a column entry in the Summarize Dialog. There is an additional entry: Formula ... which allows the user to create a "draft" new formula column, just starting with the identity formula and waiting for further user input.     What is the improvement you would like to see?  Add such a Formula ... entry also to the New Formula Column submenu of the column right click context menu. The new column should be called orignalColumn 2 - Transform[originalColumn] (like in the Filter Col Selector) is too long :)   Why is this idea important? It gets much easier to generate a new formula column. The identity function is an ideal starting point.         more wishes submitted by   ... View more

☐ cool new feature ☐ could help many users! ☐ feels like a „bug“ ☑ nice to have ☐ nobody needs it   Surprising, especially for new users of Jmp: A local data filter doesn't exclude items, which are already excluded by a global data filter. Data Filter: exclude excluded rows    For users who work with Jmp for many years, this can be a quite logical thing. But if you think about it objectively, it's completely unnecessary, right? So, why?!    In the example from the link above, a data filter which could look like this actually looks like this (excluded, unnecessary items marked red): A user who selects age = 13, 15,17 will not see any update in the graph; could be that he wonders what's wrong.   There is a functionality to exclude data from a graph - why not use the same functionality to exclude the items from the data filter lists? It's already possible to apply such an exclusion manually, bu "conditional" data filters and an additional column with formula excluded(). But this requires some effort.   My proposal: a checkbox in the context menu of the local data filter: don't show data points which are excluded by the global data filter  Then the user can decide if he wants that excluded rows are listed in the data filter (checkmark = 0) or if they should be removed (1) ...   Hm .. actually I can't think of any application case where a user intentionally decides to get excluded items listed. But definitely, there will be some special cases ... Can anybody give an example?         more wishes submitted by   ... View more