JMP Wish List

☑ cool new feature ☑ could help many users! ☑ removes a "feels like bug“ ☐ nice to have ☐ nobody needs it   What inspired this wish list request? With the Subgroup option in Table/Summary one can split group statistics by subgroups - several columns can be used as subgroups to get even more details.   At the moment, when several columns are selected as subgroups, all possible combinations are hierarchically listed. For the example here: Table summary - Subgroups every single day of the week X every single day of the month gets a subgroup, ending up with 7 * 31 = 271 subgroups (dom, dow)   Sometimes, the user just wants to generate a fast overview with subgroups from several columns. Therefore, subgroups should not be listed hierarchically, but just put next to each other (side-by-side subgroups *): This is not possible yet in Table/Summary and the cool intersection feature feels more like a "bug" :)   As a workaround, the user can use the Tabulate Platform: https://community.jmp.com/t5/Discussions/Table-summary-Subgroups/m-p/589647/highlight/true#M79432  Tabulate gives the user all the flexibility to choose between hierarchical listing of (sub)groups and putting (sub)groups side-by-side  (actually: groups ... below each other :) But Tabulate has several disadvantages: - Tabulate doesn't provide interactive linking to the source table - Tabulate doesn't provide sorting (right?) - Tabulate doesn't support columns with modeling type multiple response   What is the improvement you would like to see?  For the Table/Summary Platform, please add an option that allows the user to chose if several (Sub)group Categories should be intersected or just put next to each other.   Why is this idea important? The click effort to generate a  summary with side-by-side (sub)groups (*) can be significantly reduced. e.g. for the example in Table summary - Subgroups  from ~ 17 clicks/dragNdrops to 5 clicks/dragNdrops.         more wishes submitted by   ... 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

JMP17 has new function called New Formula Column. It would be nice if it were to return the references to the newly created columns in a list, in similar manner as << New Column does for single column. This would make using this function easier   Names Default To Here(1); dt = Open("$SAMPLE_DATA/Big Class.jmp"); new_col = dt << New Column("Log2[height]", Numeric, Continuous, Formula( Log(:height, 2) )); new_cols = dt << New Formula Column(Operation("Log 2"), Columns(:height, :weight)); Show(new_col, new_cols); ... View more

Currently Action Recorder creates fairly non-robust code by using table names and such. New Workflow Builder is able to offer reference replacements but I would like to go a bit further and have an option in which Action Recorder would use variable names. These should be configurable by user. Also namespace should be used in this case, either some specific one or here (add Names Default To Here(1); to top of script)   Below is fairly simple example created using Big Class and Enhanced Log /*: // Open Data Table: Big Class.jmp // → Data Table("Big Class") Open("/C:/Program Files/SAS/JMPPRO/16/Samples/Data/Big Class.jmp"); // New formula column: Log[weight+1] Data Table("Big Class") << New Formula Column( Operation(Category("Log"), "Log x+1"), Columns(:weight) ); // New formula column: Random Uniform Data Table("Big Class") << New Formula Column( Operation(Category("Random"), "Random Uniform"), Columns(:sex, :height) ); // Report snapshot: Big Class - Graph Builder Data Table("Big Class") << Graph Builder( Size(528, 448), Show Control Panel(0), Variables(X(:sex), Y(:"Log[weight+1]"n)), Elements(Points(X, Y, Legend(4))) ); It would be nice if this could be written in log as (this won't work as it seems like << New Formula Column doesn't return reference to the column like << New Column does, but the idea is still the same) // Open Data Table: Big Class.jmp // → Data Table("Big Class") dt_1 = Open("/C:/Program Files/SAS/JMPPRO/16/Samples/Data/Big Class.jmp"); // New formula column: Log[weight+1] col_1 = dt_1 << New Formula Column( Operation(Category("Log"), "Log x+1"), Columns(:weight) ); // New formula column: Random Uniform col_2 = dt_1 << New Formula Column( Operation(Category("Random"), "Random Uniform"), Columns(:sex, :height) ); // Report snapshot: Big Class - Graph Builder rep_1 = dt_1 << Graph Builder( Size(528, 448), Show Control Panel(0), Variables(X(:sex), Y(col_1)), Elements(Points(X, Y, Legend(4))) ); And in this example dt_, col_ and rep_ are the variable name prefixes user has chosen for these specific object types.   This should make auto-generated scripts a bit more robust ... 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

What inspired this wish list request?      What is the improvement you would like to see?      Why is this idea important?      ... View more

What inspired this wish list request?  Default opening:  Would like this to be the default:       What is the improvement you would like to see?      Why is this idea important? It keeps the full efficiency gain of using toolbars   ... View more

What inspired this wish list request?  We currently run a very long JSL script. We'd like the ability to save the time each line of code takes once the Time Profiler runs so we can use it to find speed improvements over time. Currently, we have to run every script with the Time Profiler & look for time differences by making a change & then re-running the Time Profiler   What is the improvement you would like to see?  The ability to save the amount of time each line of code takes into a text file would be helpful to compare scripts over time. This way, there wouldn't be a need to re-run scripts when asked about a specific function or statement, the data would already be accessible.   Why is this idea important?  Data is constantly increasing & with it, scripts take longer to run. The ability to identify code blocks that are causing slowdowns are critical to maintain efficiency.    I'm currently using JMP 17.0.0.   ... View more

What inspired this wish list request?  I saw that in JMP 17 we can now change the value order of a variable in Graph Builder, and it will save that property back to the column.   What is the improvement you would like to see?  I would like to see this same feature applied to the Tabulate platform.  I often build summary tables and this is where I frequently become aware that I need to fix the values in a particular order other than their occurrence or alphabetically.  Being able to do this right from the Tabulate page would be great.   Why is this idea important?  It's efficient and consistent with other platforms.   ... View more

What inspired this wish list request? I haven't really used JMP's Dashboards because Tab Page Boxes they use take too much space and because of this I always write my own UI using New Window(). I could see myself almost using Dashboards (at least as a starting point) now that JMP17 provides quite clean script if I didn't have to clean the code to remove Tab Page Boxes. This isn't as big of an issue in Dashboard view but more on the created script, though I would also like to be able to have dashboard without the "title boxes"   What is the improvement you would like to see?  Provide an option to not add the Tab Page Boxes. Below is fairly simple example with one graph builder and one distribution (script taken with  from Dashboard above): I have basically three mostly useless Tab Page Boxes there, I already know this is a dashboard, I already know I have a Graph Builder and Distribution , I don't need the Tab Page Boxes to tell me that (I also have Outline Boxes telling me this). I would like to be able to have Dashboard which look more like this:   Why is this idea important?  Allows easier creation of compact UI's. Especially with JMP17 change in which the Dashboard script isn't a huge mess anymore (! ... View more

WHAT'S GOOD ABOUT JMP JSL (JMP Scripting Language) is a great tool to ensure reproducibility of your analysis. While it requires some learning for you to be fluent, fortunately, JMP lets you do some analysis with GUI and get a script to reproduce it by clicking the "Get Script" option. This is essential for both learning JSL and making efficient use of it. JSL offers multiple ways to achieve a single task.   THE PROBLEM "Get Script" of most platforms gives you a kind of JSL that's not very popular, the one with "SendToReport" and "Dispatch". For example, the following is a script suggested in "Scripting Platforms" Chapter of the Scripting Guide:   Open( "$SAMPLE_Data/Big Class.jmp" ); // I added this line   oneObj = Oneway(   Y( :height ),   X( :age ),   Each Pair( 1 ),   Means( 1 ),   Mean Diamonds( 1 ) ); oneObj << Unequal Variances( 1 );   rep = Report( oneObj ); rep["Oneway Anova"] << Close( 1 ); rep["Means Comparisons"] << Close( 1 );   Running this script, you will get a Oneway platform with a nice graph. Now, you select "Get Script" from the red triangle menu of the report and get the below: Oneway(   Y( :height ),   X( :age ),   Each Pair( 1 ),   All Graphs( 0 ),   Means( 1 ),   Unequal Variances( 1 ),   Composition of Densities( 1 ),   Mean Diamonds( 1 ),   Std Dev Lines( 1 ),   SendToReport(     Dispatch( {}, "Oneway Anova", OutlineBox, {Close( 1 )} ),     Dispatch( {}, "Means Comparisons", OutlineBox, {Close( 1 )} )   ) );   This is completely different from the one suggested in the Scripting Guide, and is generally less easy to master.   SUGGESTED IMPROVEMENT I wish JMP allows the user to choose the type of JSL to be produced. For those who regularly use "Save Script" for reproducible analysis, this would be a tremendous time saver. ... View more

What inspired this wish list request?  Suche nach der Möglichkeit des Einbettens eines interaktiven Analysediagramms direkt in Powerpoint,  vorheriger Weg über .SWF Export inzwischen nicht mehr möglich     What is the improvement you would like to see?  Mögliches Einbetten von interaktiven Analysediagrammen etc. direkt in Powerpoint     Why is this idea important?  Aufzeigen von Ergebnissen/Analysen in Powerpoint-Präsentationen     ... View more

What inspired this wish list request?  HTM-Export eines Analysediagramm: Y-Skala anders als zuvor dargestellt und nicht per grab veränderbar     What is the improvement you would like to see?  Veränderbare Y-Skala im HTM-Export des Analysediagramms per grab, auch die Bezeichnungen tragen sehr unschöne Umbrüche, welche nicht veränderbar sind   Why is this idea important?  Bisher Darstellungsprobleme und keine Möglichkeit der Änderung der Y-Achse im HTM-Export     ... View more

What inspired this wish list request?  Vergleich mehrere Einstellungen/Zustände in einem Analysediagramm     What is the improvement you would like to see?  "Festhalten" der Einstellungen/Zustände und Einfluss auf die Zielgröße und weiterer Regler für andere Einstellungen/Zustände mit EInfluss auf die Zielgröße, um die Unterschiede dieser Einstellungen/Zustände erkennen zu können     Why is this idea important?  Vergleich mehrerer Zustände im Analysediagramm und Ableitung der Aussagen     ... View more

What inspired this wish list request?  Vergleich zweier Zielgrößen im Analysediagramm   What is the improvement you would like to see?  zwei Zielgrößen in einem (!) Graphen im Analysediagramm   Why is this idea important?  bei zwei konkurrierenden Zielgrößen ist ein Vergleich der Differenz/Delta bzw. Schnittpunkt sinnvoll   ... View more

I think it might be practical and valuable for some users, if it would be possible to save the data from a distribution histogram into a table. The table would then contain two columns where one is the undersize value (i.e. the upper bin limit), that increases with the bin width that was set in the x-Axis settings of the histogram, and the other column contains N of the respective bin (and/or, or in a third column, the respective recalculated frequency).   Currently, it is possible to get the proposed table, but only using a work-around: One can save the level numbers of the histogram of interest (the levels also scale with the set bin size in the histogram's x-scale) into the original data table. Then one can organize the date e.g. using the command (as described in How to get the table of values after constructing a histogram? - JMP User Community). However, one then still has to manually adjust the levels to the actual x-axis scale that was used in the histogram.   Since there is already the option of saving different data directly out of the histogram under the distribution dialogue menu via (like the levels described) above), it might be relatively simple to implement another option, where the above proposed table is directly created. Especially since the data must already somewhere be stored in JMP in order to create the histogram graph.   This feature might for example come in handy, when particle size distributions have to be recalculated from a number based distribution into a volume based distribution or vice versa. With the new feature, the data of the histogram can directly be manipulated and/or recalculated.   Currently using JMP 16. ... View more

What inspired this wish list request?  Currently when user want's to modify the slider value for example in Graph Builder, it is very difficult to do it based on exact value as you cannot see the value easily and you have to use slider.   Example below: No idea what those values currently are unless I hover over and if I change the value I cannot see it while using the slider. And even if I could see the values, I cannot move the slider accurately enough to get the value I would like to have.   For example Fit Y by X offers this type of controls And with Profiler you can click the value and modify it   What is the improvement you would like to see?  I would like to see the values all the time and have a possibility to write the values I want to use in addition to using sliders. Number Edit Box is one option how it could be handled, maybe combination of how fit y by x and profiler do it in the images above.   Why is this idea important? This would make it much easier to use those controls accurately. Currently I think the easiest way is to move all the sliders randomly somewhere and then take the script. Then you can accurately edit the values and run the graph again. Or you could write your own add-in which allows changing slider values with Number Edit Box. ... View more

What inspired this wish list request?      What is the improvement you would like to see?      Why is this idea important?      ... View more

What inspired this wish list request? I use the data table filter often (especially as a selection tool vs a filter) so I will minimize it.  To find it again I have to go to the home window or window list table as it does not show up in the Windows taskbar (it does show up if not minimized) or on the bottom of the data table window list panel.     What is the improvement you would like to see?  I would like to see data the table filter window to show up the same way as all windows do on the task bar and the data tables.   Why is this idea important? It will improve the user experience as there will be less searching for the filter window and will improve user efficiency. ... View more