JMP Wish List

☑ cool new feature ☑ could help many users! ☑ removes something that feels like a „bug“ ☐ nice to have ☐ nobody needs it   #myTop10_2024   What inspired this wish list request?  short: In Jmp it's quite complicated to generate a plot like this! Inclusive values will fix the issue ...   long: During the Semiconductor Lunch meeting @ Discovery Summit 2024 Europe, we found out that many of us have a similar problem:   GraphBuilder Plots with missing data.   examples: - date with missing month, day, year ( A way to show a date with no data in graph builder ) - wafer lists with missing wafer (for 25 wafers in a 5x5 grid generated via Wrap, wafer #20 should always be at the same position, independent of how many wafers < 20 are in the data / missing) - wafermaps with missing dies - pass / fail - bins with pre-defined categories (0 occurences for a specific bin) ... Motivation via date:  at first glance, nobody will notice that the data for Tuesday is missing - there is not even a label on the axis.   To make the missing day appear, one can add a dummy row, Day of Week = Tue, all other entries of the row: missing.   ... till somebody uses a data filter - then Tue is gone:   The only way to make it work: a dummy row for EVERY (!!!) item in the data filter. And if the user has a chance to change the column for the data filter: for EVERY item in ANY column the user may pick. Ouch !!!   What is the improvement you would like to see?  Please add a column property for inclusive values *) - values which should always show up on the axis. For days of week: all days of the week :) For 25 "wafers" in a lot: all numbers from 1 to 25. For pass/fail : pass and fail . Such that one day when there is a lot with 0 fails the plot will say: fails = 0. Instead of: not showing any number of fails.   Besides usage for axes, also X/Y Group & Wrap should react on the new setting. The same for Overlay and Color.   *) "inclusive"? what is the best name for the property?  - "default value" sounds like  - additional, auxiliary, supplemental suggest that the value is no actual value of the column - after some discussion, Copilot suggested "inclusive" values - values which should be included, if missing.   Why is this idea important?  With the new column property INCLUSIVE VALUES, - missing value information gets visible (!!!) - the plots can be generated MUCH easier - the generated plots are "robust" (example with Data Filter!)   other wishes from  ... View more

☑ cool new feature ☐ could help many users! ☐ removes a „bug“ ☐ nice to have ☐ nobody needs it   #myTop10_2022   If a column is set to "multiple response", there are cool options available in the data filter menu: These allow the user to get much more power out of the data filter. Most of them rely on the fact that there are "multiple responses" in the column - and the user can select which combination he wants. There is also an option "none". It has the same effect as the "inverse" - but the difference is that "inverse" just inverts the current selection, but "none" is a setting which is applied in the background. With "none" fancy Data filters are possible along the idea: THIS, but not THAT: https://community.jmp.com/t5/Discussions/Conditional-Data-Filter-for-modeling-type-Multiple-Response/m-p/556062#M77004   Unfortunately, for standard columns, there is no "none": https://community.jmp.com/t5/Discussions/advanced-data-filter-arithmetic-just-available-if-the-column-is/m-p/556682   Every Jmp user who worked with the cool functionalities of multiple response columns (esp. the availability of "not") feels an incredible lack of functionality when working with standard columns.   my wish: Add "not" also for standard data filters.     more wishes submitted by   ... View more

What inspired this wish list request?  Can the listbox have a select all command, at the moment you can only select one by one. Use lb<<set selected(1)   What is the improvement you would like to see?  listbox has a command to select all elements at once.   Why is this idea important?  Many commands have this, but listbox does not; for example, checkbox   ... View more

☐ cool new feature ☑ could help many users! ☐ removes a „bug“ ☐ nice to have ☐ nobody needs it   Indexing/Slicing of Matrices just works with indices which count from the start of the matrix: What is the JSL Matrix?    counting from the back or leaving the start or end open doesn't seem to work: Collection of "funny" Jmp newbie questions    my wish: add the missing functionality such that indexing like this is also possible: mat[1::-1]; mat[1::]; mat[::-1]; mat[::]; mat[::, x] is already possible as mat[0,x]   more wishes submitted by     ... View more

Many DOE's need to be peformed over several days so considering and separation of random time variation in DOE analysis is an issue. As stated by Goos & Jones Randomized blocks in DOE are very useful to absorb random variation so fixed effects can be precisely estimated. However in the JMP forward stepwise parameter selection module random effects can't be included; all blocks, also random time effect blocks, need to be treated as fixed effects. In forward selection it would be a major imporvement to also allow random effects so the old cumbersome backward selection can be avoided. ... View more

There are a lot of forum posts about how to get results from reports.  This could be made easier by adding some attributes to the display tree and defining two new functions that would do most of the work for the user.  I propose this syntax:   platform = Fit Model( ... ); platform << Get Result( "BIC", fit("NormalLassoAICValidation") ); //returns [0.683248] Display Tree Attributes Define a set of result types that is standard across all platforms. This will be a big list, but if two platform both report an adjusted R2, they should both use the same result type. Add the result type to an attribute in the display tree for the column, cell, and/or anywhere else it is displayed, similar to the helpKey attribute for some platform outlineboxes. Display the result type somewhere in the platform GUI, maybe in a hover label for everywhere it is displayed Do something similar to flag outline boxes containing a fit created by the model (think '...fit with 6 components' in PLS or 'Normal Lasso with AICc Validation').  Here the attribute would be specific to the platform. Functions Create functions to get The result values The report element containing the result The report element of the fit The scriptable object of a fit Call them like this platform << Get Result("AdjustedRSquared") //Matrix or list of all Adjusted R Squared values platform << Get Result("AdjustedRSquared", fit("NIPALS_1")) //Matrix or list of all Adjusted R Squared values in fits with NIPALS_1 platform << Get Result("AdjustedRSquared", fit("NIPALS_1"), fitnumber(1)) // Matrix or list of all Adjusted R Squared values in the first fit with NIPALS_1, should be exactly one value platform << Get Fit("NIPALS_1") //returns the scriptable object platform << Get Fit("NIPALS_1","object") //same platform << Get Fit("NormalLassoAICValidation","report",fitnumber(1)) //returns the report from the first fit with NormalLassoAICValidation These functions these could be variations of wrappers around XPath: platform << XPath("//NumberColBoxItem[@ResultType='AdjustedRSquared']") platform << XPath("//OutlineBox[@Fit='NIPALS_1']") platform << XPath("//OutlineBox[@Fit='NIPALS_1']") << Get Scriptable Object fm << XPath("//OutlineBox[@fit='NIPALS_1']//NumberColBoxItem[@ResultType='AdjustedRSquared']")   ... View more

☑ missing function ☑ could help many users! ☐ removes a „bug“ ☐ nice to have ☐ nobody needs it   #myTop10_2022   Add-In Manager is a really great Add-In to manage and distribute Jmp Add-Ins in the company. Add-In Manager  Please include it in Jmp and fix some bugs:   - functionality to add and handle Toolbars (not: delete toolbar entries) https://community.jmp.com/t5/JMP-Add-Ins/Add-In-Manager/tac-p/575008/highlight/true#M1667   - option: "insert after" to place commands after a specific existing command (e.g. self-made plotting command below GraphBuilder) https://community.jmp.com/t5/JMP-Add-Ins/Add-In-Manager/tac-p/567196/highlight/true#M1646   - add Meta data directory option for TEST - to enable auto-update also for TEST repository: https://community.jmp.com/t5/JMP-Add-Ins/Add-In-Manager/tac-p/424276/highlight/true#M1379   - provide @Justin_Chilton the bandwidth to work on these topics: https://community.jmp.com/t5/JMP-Add-Ins/Add-In-Manager/tac-p/452189/highlight/true#M1420     more wishes submitted by   ... View more

It would be really nice to have the ability to use proportions/attribute data in the Process Screening platform, i.e., be able to select P or NP chart behavior for the platform. I work a lot with process yield data, and haven't yet found a statistically appropriate method for screening a long list of processes this way. ... View more

I like to use the import wizard to get Excel data into JMP (version 16.2 Pro); this works fine for files stored on LAN but I don't seem to be able to use the wizard to open files stored in Teams/SharePoint. Can this functionality please be added? ... View more

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

It would be exceptionally great if JMP would allow frame boxes to have a sample-and-hold type of display.  Specifically, they should be rendered once and only re-rendered for such things as resize events, row-state changes (for any marker seg's that are linked to a table's row-state) or by sending the <<Inval or <<Dirty message.   What I'd like to see is for the below example script to not print any number more than once while scrolling -- during the initial render and that's it (this would also apply to marker segs if present).   The main reason for this is that if I'm plotting many graphs with millions of data points, I don't mind waiting several seconds for the initial render (that is expected) but it is unacceptable that every scroll event requires multiple seconds of rendering -- render only once and just repaint the bitmap at a different location when scrolling.   NOTE:  If the devs are worried about the memory consumption of holding bitmaps in ram -- DO NOT WORRY.  Let the user worry about that when setting up the boxes.  For example, if I try to create a plot that would be 1,000,000,000 x 1,000,000,000 pixels to render then let me attempt it and crash JMP.  You shouldn't prevent us from having the necessary feature simply for the reason that it might allow us to crash JMP under stupid circumstances.  Allow it to be opt-in only (i.e., only by calling the  <<Lazy method will this new feature be invoked).   Just to reiterate, it would be great if a FrameBox had a method (such as <<Lazy) that would do the absolute minimum number of renders possible to keep the painted bitmap current and no more -- thus allowing scrolling to be fluid and fast for FrameBoxes with either very complicated Graphics Scripts or millions of data points or both.   Here is an example of the bad behavior currently -- the numbers are printed multiple times indicating that the rendering pass happens each scroll event:   Names Default to Here( 1 ); New Window( "Test", V Scroll Box( vlb = V List Box() ) ); For( i = 1, i <= 100, i++, Eval( Eval Expr( vlb << Append( Graph Box( X Scale( 0, 1 ), Y Scale( 0, 1 ), Pen Color( "Blue" ); Line( [1 0], [0 1] ); Print( Expr( i ) ) ) ) ) ) )     Here is an example of the unacceptable wait-time associated with this "re-render-at-every-scroll-event" / "re-render at every possible opportunity" (just try scrolling through here...)   Names Default to Here( 1 ); ns = New Namespace(); ns:table = New Table( "TEST", New Column( "X", "Numeric", <<Formula( Random Normal() ) ), New Column( "Y", "Numeric", <<Formula( Random Normal() ) ), <<Add Rows( 100000 ) ); ns:func = Function( {_i}, Print( _i ) ); Eval( Eval Expr( New Window( "Test", <<On Close( ns = Namespace( Expr( ns << Get Name ) ); Close( ns:table, No Save ); ns << Delete Namespace; ) , V Scroll Box( vlb = V List Box() ) ) ) ); For( i = 1, i <= 100, i++, Eval( Eval Expr( vlb << Append( box = Outline Box( "", Graph Box( Frame Size( 300, 300 ), Y Scale( -3, 3 ), X Scale( -3, 3 ), Marker Seg( Expr( ns:table:X << Get Values ), Expr( ns:table:Y << Get Values ), Row States( Expr( ns:table ) ) ); ) ) ); seg = box[Frame Box( 1 )] << Find Seg( "Marker Seg" ); seg << Transparency( 0.4 ); box[Frame Box( 1 )] << Add Graphics Script( Local( {ns = Namespace( Expr( ns << Get Name ) )}, ns:func( Expr( i ) ) ) ); ) ); )       ... View more

Hello,   Can the following be added to the rules table of the AA report?   - Support for condition and consequent? - PS and IS Measures (see attached)?   Thanks and regards Mehul Shroff ... View more

☐ cool new feature ☑ could help many users! ☐ removes a „bug“ ☐ nice to have ☐ nobody needs it #myTop10_2022   There is a set of posts with questions how to restrict the Col ... aggregation functions to a specific subset. Compute Column Mean while restricting observations used  JMP10: Col Max() and Col Min() functions returned the data from excluded row  Col Functions and Row States  How do I use the Col Maximum Formula with a "where" condition  Exclude data in formula    Application cases: excluded rows from the aggregation: Col Max(if(not(excluded()), :weight,.),: sex) or even shorter (if one doesn't need values in the excluded rows); Col Max(:weight, :sex, :excluded()) Benchmark some data with a reference data set (country A in this post)  :data / Col Maximum(if(:country="A", :data,.))   calculate relative performance over time (divide all values at time t>=t0  by values at t=t0) (here the Col Mean is actually to get the value for :time=0 to the other rows.:) : data / Col Mean(if(:time=0, :data, 0) :batch, :sampleID)   As one can see in the examples above, the easy solution is an If statement inside the Col xyz aggreagtion:   col Mean( if(:sex=="M", :weight,.), :age); col Mean( if(not(excluded()), :weight,.), :age)     The problem: The approach is EXTREMELY slow - if the subset if-condition contains a  string comparison: How-do-I-use-the-Col-Maximum-Formula-with-a-where/M78599 Then the time scales quadratically with the number of rows and even for small data sets with just a few 1000 entries the calculation takes seconds. For data sets with some million entries it would take months (!!!) - but will be stopped by a timeout and an error message pops up. Not nice!   My wish:  fix the bug   Even better: Provide an additonal where option for Col xyz aggreagtions which fixes the timing problem automatically: first restricts the data set, then applys the aggregation (--> much faster, even if the cool "col..." speedup has a  bug) which  make subset definitions easier, instead of (*), you just need:   col Mean(:weight, :age, where(:sex=="M")) col Mean(:weight, :age, where(not(excluded())))     timing examples, copied from here corrected version - in a prev. version the screenshot showed [ms] instead of [s]   more wishes submitted by   ... View more

I'd like to see the columns that are causing the error to show up in this error message:   right now it is quite tedious to find out which columns to remove to get past this error.  Note: this was while using the BSF platform.   ... View more