JMP Wish List

JMP Windows Specific preferences does offer "Dock the Window List in maximized windows" option which is from time to time great. What I would like to have, is to be able to quick hide that window list in maximized windows. This could be implemented in similar manner as Hide/Close Left Panels in data table.   Why? This is because the Window list takes quite a bit space if it is set in usable size and I would like to hide it when I have no need for it BUT get it back when I need it again. ... 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

What inspired this wish list request? I am trying to automate (JSL code) the redundant admin tasks that consume too much time. My company uses Sharepoint, Teams, and Outlook and having JSL code "easily" communicate with these programs would make life much easier.     What is the improvement you would like to see? Sharepoint and Teams - be able to pull import data easily. Outlook - be able to send emails and meeting invites via script (maybe without having to hit the "allow" button for each email).     Why is this idea important? save time and have less errors     ... View more

☐ cool new feature ☑ could help many users! ☐ removes a „bug“ ☐ nice to have ☐ nobody needs it   What inspired this wish list request?  If users want to access display boxes in reports they always have the problem to get the correct code. Is it ListBoxBox # 3 or #5 nad with an intermediate step to the Panel Box, it then #2 or #1? With Jmp 17 it got a bit better, because a direct code for the display box can be generated by the properties menu. So far so good.    But just try to get a robust code to access the list box in the center of the Update menu - robust even if the user changes the Replace Column setting!   A wonderful trick from Using Display Boxes     : select and deselect the node to check if you selected the right one.   This approach could be optimized by a tiny new feature, implemented in the right click context menu of the JSL editor:   What is the improvement you would like to see?  If a user selects the code of a display box, please add a select/deselect command to the right click context menu. When the user clicks on the command Jmp should send a select command to the display box: myWindow[Panel Box( 3 )][ListBoxBox( 3 )] << select If possible: read the current select state of the display box and toggle it (select -> unselect -> select ...)       Why is this idea important?  The trick from the JSL course is so helpful - but the user always has to write the code, change the code, delete it again. With the new command in the right click context menu, it will be much more fun to find the right code to address a Display Box :)   ... View more

What inspired this wish list request?  When making a new data table I frequently use code dt = new data table() but this throws an error since only new table() works.  Tables are frequently called data tables in documentation and other functions and would be good to support new data table() as an alias for new table().   What is the improvement you would like to see?  Please make a function "New Data Table()" as alias for "New Table()"   Why is this idea important?  Would remove a frequent error when coding in JSL.   I am using JMP 16.2 ... View more

☐ cool new feature ☑ could help many users! ☑ removes a „bug“ ☐ nice to have ☐ nobody needs it   #myTop10_2023 we have a workaround -> I don't need it anymore.   What inspired this wish list request?  Short: Tables/Update and Tables/Concatenate destroys my source scripts. STOP THEM !!! Long: Many of the Platforms in the Tables menu provide the option Save Script to Source Table. Is is an elegant way to save the command with all the settings as a Table Script Platform_Name Script. There is even an auto-increment function which prevents Jmp from overwriting previous Table Script with the same name.   But there are two exceptions: Update and Concatenate. As all the other functions, Concatenate saves the command script as a Table Script (name: source) to the output table. Exception: If the option Append to first table is enabled, the main table is the output table - and NO script is saved (perhaps to prevent Jmp from over-writing an existing source Table script?)   For Update the main table is always used as output table. This function saves a table script with the current settings (name: source) to the main table and thereby: overwrites any existing source table script (!). Table / Update - source script collision      What is the improvement you would like to see?  Concatenate and Update should follow the naming scheme of the other Table platforms. i.e. save a script with the current settings to a Table Script with name Concatenate Script or Update Script. An auto-increment feature should be used to prevent Jmp from overwriting existing scripts.     Why is this idea important? The auto-generation of JSL source code is a great feature. But over-writing an existing source code is more ham than good . Fixing the issue will save users from losing their table source script.   The naming convention separates source scripts (name: source;  was used to generate the data table) from Platform Scripts (name: Script; can be used to act on the current data table) ... View more

It would be really helpful to have a Peak Deconvolution add-in into JMP. This will help users who frequently are analyzing data from instruments like FTIR, XPS etc.       ... View more

Quite a few text editors provide positional information in status bar. I would like to have these also in JMP's Script Editor.   Image from notepad++: Visual studio code: ... View more

いつも大変お世話になっています。 掲題の件、ウィシャート分布(Wishart distribution）における期待値と分散を算出したく、投稿致しました。 ウィシャート分布（Wishart distribution）は、連続型の確率分布です。ウィシャート分布はカイ２乗分布を多次元に拡張したものとして知られています。 website:ウィシャート分布 | 初心者からはじめる統計学 (develop-chronos.com)   (1)この分布の期待値と分散を算出する、JMPのサンプルデータやサンプルコードのデモ作成をお願い致します。 (2)これらを通じて、「ウィシャート分布と線形関数」や、「分割行列とウィシャート分布」の関係を、JMPを通じて学びたいと思っています。   現在は、JMP®  15.2を利用しています。 よろしくご検討の程、お願い申し上げます。吉池     ... View more

Add new function which would return values in a list (or matrix if numeric calculation) based on column calculations. We can calculate values with Formula() and << Set Each Value, but we have to place the values in Data Table. It would be nice to be able to just calculate values based on the data table's columns WITHOUT adding new columns which you will have to later remove.   One idea for usage could be something like this (Big Class.jmp) result = dt << Calculate Values(:Height / :Weight); and this would then return me a matrix with :Height/:Weight calculated for each row.   Other example with characters could be result = dt << Calculate Values(:sex ||"_"||Char(:age)); and this would return me a list of each row concatenated with :sex and :age.   ... View more

This would help for example when making numeric encoding for character values. Dense Rank (wikipedia) or calculating orders For example scipy.stats.rankdata offers average, min, max, dense and ordinal ... View more

What inspired this wish list request?  It has been some time since I did use SAS Viya, but I think it did allow me to "easily" create calculated columns which will reflect the columns used in visualization (this feature might be called scoping in aggregated measures).   What is the improvement you would like to see?  I would like to be able to create formulas in Graph Builder (maybe to the data table?). This image is from some Viya video (https://video.sas.com/detail/video/4027587158001/creating-visualizations:-creating-new-derived-data-items  Other video which demonstrates the idea https://www.youtube.com/watch?v=LBgiHVJTx78   Why is this idea important?  This would allow user to create even more dynamic visualizations without using too much complicated scripting ... 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?  Unlike plots and reports, column formulas don't use the information: which rows are excluded? - by default. If the user doesn't pay attention, this leads to erroneous, Max, Min Rank etc. values.   The workaround: The user has to specify explicitly that excluded rows have to be excluded form the analysis. Therefore some kind of Excluded() has to be added to the formulas as soon as rows are excluded: Col Functions and Row States    The problem: The user has to know about the problem.   What is the improvement you would like to see?  Please provide a shortcut button to add excluded()to the formula; The button could be placed between the columns list and the constants/variables menu. alternative: For new users, please add Excluded() from Function List /Row States to the functions favorites - to present it nicely visible at the top of the functions list.   Why is this idea important? a) With the new button (or function favorite)  a user can quickly add an excluded() expressions to his formula.   b) A new Jmp user doesn't expect that such expressions have to be added to the formula. The availability of the button (or function favorite) will make him think, dig deeper and find out.         more wishes submitted by   ... View more

☑ 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