Presentation at JMP Discovery Summit Americas 2020 on the JMP Cause and Effect diagram. Some items to add to the wish list for future enhancements of the JMP Cause and Effect platform, or a new platform for "mind mapping". Structured Problem Solving using JMP Cause and Effect Diagram, mind-mapping software, and JSL (2020-US-30MP-569)    1. Allow the option to open a closed node. Currently only closes the node and shows the ellipsis that the node is closed. Had to add JMP script to send the << Close(0) and << Close(1) messages. So know HierBox can take both messages, just add option to the right-click menu. 2. Diagram allows text to be rotated left or right. Found no option to rotate the display boxes, such as in the entire hierarchy layout. By allowing text to be rotated and display boxes to be rotated, or the entire hierarchy layout to be rotated, has the appearance of mind maps.  3. Add to the current 3 layouts: fishbone, hierarchy, nested, a new layout called something like "mind map" or "flexible map". Use the other JSL objects such as Outline Box, which allows the "node" to collapse or open, to be added to the new layout "mind map".  4. If too difficult to add to the Cause and Effect platform, maybe a new platform that would allow mind mapping. Or an enhanced journal with capabilities. Can be simple, but use the built in JMP display boxes and messages. Could see someone enter Outline Boxes, Text Boxes, but allow connectors like in the Hierarchy boxes, the Cause and Effect Diagram hierarchy layout. It might be that most of the pieces are there in JSL, but just need to be put together to allow mind maps.  ... View more

Level: Beginner   Daniel Sutton, Statistician - Innovation, Samsung Austin Semiconductor   Structured Problem Solving (SPS) tools were made available to JMP users through a JSL script center as a menu add-in. The SPS script center allowed JMP users to find useful SPS resources from within a JMP session, instead of having to search for various tools and templates in other locations. The current JMP Cause and Effect diagram platform was enhanced with JSL to allow JMP users the ability to transform tables between wide format for brainstorming and tall format for visual representation. New branches and “parking lot” ideas are also captured in the wide format before returning to the tall format for visual representation. By using JSL, access to mind-mapping files made by open source software such as Freeplane was made available to JMP users, to go back and forth between JMP and mind-mapping. This flexibility allowed users to freeform in mind maps then structure them back in JMP. Users could assign labels such as Experiment, Constant and Noise to the causes and identify what should go into the DOE platforms for root cause analysis. Further proposed enhancements to the JMP Cause and Effect Diagram are discussed.     Auto-generated transcript...   Speaker Transcript Rene and Dan Welcome to structured, problem solving, using the JMP cause and effect diagram open source mind mapping software and JSL. My name is Dan Sutton name is statistician at Samsung Austin Semiconductor where I teach statistics and statistical software such as JMP. For the outline of my talk today, I will first discuss what is structured problem solving, or SPS. I will show you what we have done at Samsung Austin Semiconductor using JMP and JSL to create a SPS script center. Next, I'll go over the current JMP cause and effect diagram and show how we at Samsung Austin Semiconductor use JSL to work with the JMP cause and effect diagram. I will then introduce you to my mapping software such as Freeplane, a free open source software. I will then return to the cause and effect diagram and show how to use the third column option of labels for marking experiment, controlled, and noise factors. I want to show you how to extend cause and effect diagrams for five why's and cause mapping and finally recommendations for the JMP cause and effect platform. Structured problem solving. So everyone has been involved with problem solving at work, school or home, but what do we mean by structured problem solving? It means taking unstructured, problem solving, such as in a brainstorming session and giving it structure and documentation as in a diagram that can be saved, manipulated and reused. Why use structured problem solving? One important reason is to avoid jumping to conclusions for more difficult problems. In the JMP Ishikawa example, there might be an increase in defects in circuit boards. Your SME, or subject matter expert, is convinced it must be the temperature controller on the folder...on the solder process again. But having a saved structure as in the causes of ...cause and effect diagram allows everyone to see the big picture and look for more clues. Maybe it is temperate control on the solder process, but a team member remembers seeing on the diagram that there was a recent change in the component insertion process and that the team should investigate In the free online training from JMP called Statistical Thinking in Industrial Problem Solving, or STIPS for short, the first module is titled statistical thinking and problem solving. Structured problem solving tools such as cause and effect diagrams and the five why's are introduced in this module. If you have not taken advantage of the free online training through STIPS, I strongly encourage you to check it out. Go to www.JMP.com/statisticalthinking. This is the cause and effect diagram shown during the first module. In this example, the team decided to focus on an experiment involving three factors. This is after creating, discussing, revisiting, and using the cause and effect diagram for the structured problem solving. Now let's look at the SPS script center that we developed at the Samsung Austin Semiconductor. At Samsung Austin Semiconductor, JMP users wanted access to SPS tools and templates from within the JMP window, instead of searching through various folders, drives, saved links or other software. A floating script center was created to allow access to SPS tools throughout the workday. Over on the right side of the script center are links to other SPS templates in Excel. On the left side of the script center are JMP scripts. It is launched from a customization of the JMP menu. Instead of putting the scripts under add ins, we chose to modify the menu to launch a variety of helpful scripts. Now let's look at the JMP cause and effect diagram. If you have never used this platform, this is what's called the cause and effect diagram looks like in JMP. The user selects a parent column and a child column. The result is the classic fishbone layout. Note the branches alternate left and right and top and bottom to make the diagram more compact for viewing on the user's screen. But the classic fishbone layout is not the only layout available. If you hover over the diagram, you can select change type and then select hierarchy. This produces a hierarchical layout that, in this example, is very wide in the x direction. To make it more compact, you do have the option to rotate the text to the left or you can rotate it to the right, as shown in here in the slides. Instead of rotating just the text, it might be nice to rotate the diagram also to left to right. In this example, the images from the previous slide were rotated in PowerPoint. To illustrate what it might look like if the user had this option in JMP. JMP developers, please take note. As you will see you later, this has more the appearnce of mind mapping software. The third layout option is called nested. This creates a nice compact diagram that may be preferred by some users. Note, you can also rotate the text in the nested option, but maybe not as desired. Did you know the JMP cause and effect diagram can include floating diagrams? For example, parking lots that can come up in a brainstorming session. If a second parent is encountered that's not used as a child, a new diagram will be created. In this example, the team is brainstorming and someone mentions, "We should buy a new machine or used equipment." Now, this idea is not part of the current discussion on causes. So the team facilitator decides to add to the JMP table as a new floating note called a parking lot, the JMP cause and effect diagram will include it. Alright, so now let's look at some examples of using JSL to manipulate the cause and effect diagram. So new scripts to manipulate the traditional JMP cause and effect diagram and associated data table were added to the floating script center. You can see examples of these to the right on this PowerPoint slide. JMP is column based and the column dialogue for the cause and effect platform requires one column for the parent and one column for the child. This table is what is called the tall format. But a wide table format might be more desired at times, such as in brainstorming sessions. With a click of a script button, our JMP users can do this to change from a tall format to a wide format. width and depth. In tall table format you would have to enter the parent each time adding that child. When done in wide format, the user can use the script button to stack the wide C&E table to tall. Another useful script in brainstorming might be taking a selected cell and creating a new category. The team realizes that it may need to add more subcategories under wrong part. A script was added to create a new column from a selected cell while in the wide table format. The facilitator can select the cell, like wrong part, then selecting this script button, a new column is created and subcauses can be entered below. you would hover over wrong part, right click, and select Insert below. You can actually enter up to 10 items. The new causes appear in the diagram. And if you don't like the layout JMP allows moving the text. For example, you can click...right click and move to the other side. JMP cause and effect diagram compacts the window using left and right, up and down, and alternate. Some users may want the classic look of the fishbone diagram, but with all bones in the same direction. By clicking on this script button, current C&E all bones to the left side, it sets them to the left and below. Likewise, you can click another script button that sets them all to the right and below. Now let's discuss mind mapping. In this section we're going to take a look at the classic JMP cause and effect diagram and see how to turn it into something that looks more like mind mapping. This is the same fishbone diagram as a mind map using Freeplane software, which is an open source software. Note the free form of this layout, yet it still provides an overview of causes for the effect. One capability of most mind mapping software is the ability to open and close notes, especially when there is a lot going on in the problem solving discussion. For example, a team might want to close notes (like components, raw card and component insertion) and focus just on the solder process and inspection branches. In Freeplane, closed nodes are represented by circles, where the user can click to open them again. The JMP cause and effect diagram already has the ability to close a note. Once closed though, it is indicated by three dots or three periods or ellipses. In the current versions of JMP, there's actually no options to open it again. So what was our solution? We included a floating window that will open and close any parent column category. So over on the right, you can see alignment, component insertion, components, etc., are all included as all the parent nodes. By clicking on the checkbox, you can close a node and then clicking again will open it. For addtion, the script also highlights the text in red when closed. One reason for using open source mind mapping software like Freeplane is that the source file can be accessed by anyone. And it's not a proprietary format like other mind mapping software. You can actually access it through any kind of text editor. Okay, the entire map can be loaded by using JSL commands that access texts strings. Use JSL to look for XML attributes to get the names of each node. A discussion of XML is beyond the scope of this presentation, but see the JMP Community for additional help and examples. And users at Samsung Austin Semiconductor would click on Make JMP table from a Freeplane.mm file. At this time, we do not have a straight JMP to Freeplane script. It's a little more complicated, but Freeplane does allow users to import text from a clipboard using spaces to knit the nodes. So by placing the text in the journal, the example here is on the left side at this slide, the user can then copy and paste into Freeplane and you would see the Freeplane diagram on the, on the right. Now let's look at adding labels of experiment, controlled, and noise to a cause and effect diagram. Another use of cause and effect diagrams is to categories...categorize specific causes for investigation or improvements. These are often category...categorize as controlled or constant (C), noise or (N) or experiment might be called X or E. For those who we're taught SPC Excel by Air Academy Associates, you might have used or still use the CE/CNX template. So to be able to do this in JMP, to add these characters, we would need to revisit the underlying script. When you actually use the optional third label column...the third column label is used. When a JMP user adds a label columln in the script, it changes the text edit box to a vertical list box with two new horizontal center boxes containing the two... two text edit boxes, one with the original child, and now one with the value from the label column. It actually has a default font color of gray and is applied as illustrated here in this slide. Our solution using JSL was to add a floating window with all the children values specified. Whatever was checked could be updated for E, C or N and added to the table and the diagram. And in fact, different colors could be specified by the script by changing the font color option as shown in the slide. JMP cause and effect diagram for five why's and mind mapping causes. While exploring the cause and effect diagram, another use as a five why's or cause mapping was discovered. Although these SPS tools do not display well on the default fish bone layout, hierarchy layout is ideal for this type of mapping. The parent and child become the why and because statements, and the label column can be used to add numbering for your why's. Sometimes there can be more and this is what it looks like on the right side. Sometimes there can be more than one reason for a why and JMP cause and effect diagram can handle it. This branching or cause mapping can be seen over here on the right. Even the nested layout can be used for a five why. In this example, you can also set up a script to set the text wrap width, so the users do not have to do each box one at a time. Or you can make your own interactive diagram using JSL. Here I'm just showing some example images of what that might look like. You might prompt the user in a window dialogue for their why's and then fill in the table and a diagram for the user. Once again, using the cause and effect diagram as over on the left side of the slide. Conclusions and recommendations. All right. In conclusion, the JMP cause and effect diagram has many excellent built in features already for structured problem solving. The current JMP cause and effect diagram was augmented using JSL scripts to add more options when being used for structured problem solving at Samsung Austin Semiconductor. JSL scripts were also used to make the cause and effect diagram act more like mind mapping software. So, what would be my recommendations? fishbone, hierarchy, nested, which use different types of display boxes in JSL. How about a fourth type of layout? How about mind map that will allow more flexible mind map layout? I'm going to add this to the wish list. And then finally, how about even a total mind map platform? That would be even a bigger wish. Thank you for your time and thank you to Samsung Austin Semiconductor and JMP for this opportunity to participate in the JMP Discovery Summit 2020 online. Thank you.   ... View more

Under Tables > Stack, the option for "multiple series stack" is  very helpful in some data situations. Would it be possible when "multiple series stack" is selected to have a preview box to show where the columns would go for the two options: (1) every nth column vs (2) n columns in a row (contiguous)? If Number of Series is used, preview panel box would show which columns would go in 2, 3, ... n groups, or highlight the first of the series in the upper column dialog. So if 3 was entered, the 1st, 4th, 7th, etc column selected would be highlighted above to safe space. If Contiguous is checked, would show which columns in how many groups of contiguous columns are being stacked.   From the JMP on Air topic: https://community.jmp.com/t5/JMP-On-Air/The-Tables-Menu/m-p/261014#U261014    ... View more

Just watched the JMP on Air segment on Statistics Index, The Statistics Index. I like to tell new JMP users about it in JMP classes.   Would like to suggest adding a filter like in the Scripting Index or Preferences. Right now in the Statistics Index you can start typing in the menu to find something, but it is a first character look-up. I search for Steel-Dwass and find it, but if I only remembered something like "Dwass", then it will not show. Or say you want to find any topic on "design", it is scattered throughout the index like "experimental design", "factorial design", "fractional factorial...", etc. ... View more

A low priority request, but could help new JMP users. The term "Kruskal-Wallis" only shows up when you hover over the term "Wilcoxon" in the Fit Y by X for nonparametric, or after you run the analysis. After running, it shows "Wilcoxon/ Kruskal-Wallis Tests (Rank Sums)".   In preferences, when you search the term "Kruskal", it does highlight the Oneway platform and the Wilcoxon term.   Other software shows "ANOVA" and "Kruskal-Wallis" side by side. When teaching the workforce which test to use, in other software can point to the Kruskal-Wallis as a menu item, but in JMP, have to remind them it is the Wilcoxon menu item, and can see it will be the Kruskal-Wallis test for more than 2 items.   Could the actual term "Kruskal-Wallis" be shown in the menu item? Such as "Wilcoxon/Kruskal-Wallis" as the menu item under the nonparametric tests?   This is similar to having "Wilcoxon Each Pair" vs "Steel-Dwass All Pairs" clearly shown in the nonparametric multiple comparisons. ... View more

  Is anyone else bothered by the orientation of the contingency table and mosaic plot? I do not use it, but one of our JMP users wanted to flip the orientation of the table so that it matches the mosaic plot. Found out that if you swap X and Y, both the table and mosaic plot update. See script below to run an example and compare them side-by-side. It seems you would want the numbers in the table to line up with the cells in the mosaic plot for easier viewing and referencing. I could not find any previous discussions. It appears the contingency table cannot be changed, it is a CrossTabBox, which does not lend itself to changing anything. The script below has in the top part the work around, which is to make a clone of the table made when switching the x and y, and then appending that to the mosaic plot. Also had to do a little with Value Ordering to get it to line up. Will add to the JMP wishlist. I did discuss at JMP Discovery Summit 2018 with the EA lab and the developers.     Found some posts on R language, where you can use the dir() argument and specify the horizontal and vertical, while the "count" output in RStudio stays the same for the orientation. # R Mosaic Plot Example - Changing Direction getwd() employee <- read.csv("Products.csv", TRUE, sep = ",",                      na.strings = TRUE) count <- table(employee$EnglishCountryRegionName,                employee$Color) count mosaicplot(count, main = "Countries Mosaic Plot",            sub = "Product Colors by Country",            xlab = "Colors",            ylab = "Countries",            las = 1,            dir = c("h", "v"),            color = "skyblue2",            border = "chocolate") // For a contingency table report, swap the x and y // currently can swap the mosaic plot only Names Default to Here(1); dt = Open( "$SAMPLE_DATA/Big Class.jmp" ); myr = Contingency( Y( :Age ), X( :sex ) ); // Have to have a Contingency Analysis report open // Can add test to make sure it is open in the future myr = Current Report(); // taking apart CrossTabBox was easier using XML than JSL mys = myr["Contingency Table"][CrossTabBox(1)] << Get XML; // get current X role or rows of contingency table start = Contains(mys,"<CrosstabBoxRowsLabel>")+22; end = Contains(mys,"</CrosstabBoxRowsLabel>"); newY = Substr(mys,start,end-start); // get current Y role or cols of contingency table start = Contains(mys,"<CrosstabBoxColsLabel>")+22; end = Contains(mys,"</CrosstabBoxColsLabel>"); newX = Substr(mys,start,end-start); // Recreate same contingency table but with X and Y flipped // also temporarily use Value Order to match the Mosaic Plot myValueLabels = Reverse(Associative Array(Column(dt,newX)) << Get Keys); Column(dt,newX) << Set Property("Value Ordering",myValueLabels); tempCont = Contingency( Y(Column(dt,newY) ), X(Column(dt,newX) ), Contingency Table ); tempContr = tempCont << Report; mycopy = tempContr["Contingency Table"][CrossTabBox(1)] << Clone Box; tempCont << Close Window; Column(dt,newX) << Delete Property("Value Ordering"); // remove the original contingency table and replace with transpose myr["Contingency Table"][CrossTabBox(1)] << Delete; myr["Contingency Table"] << Append(mycopy); // show original side by side obj = Contingency( Y( :Age ), X( :sex ) ); Report(obj)["Contingency Table"] << Set Title("Contingency Table - Current output"); myr["Contingency Table"] << Set Title("Contingency Table - Wish List for JMP16");   ... View more

Level: Intermediate   Daniel Sutton, Statistician - Innovation, Samsung Austin Semiconductor       The CUSUM Control Chart has been shown to be sensitive to small shifts compared to standard WECO (Western Electric Co) rules and Nelson rules, in particular Rule 2: “9 points in a row on a single side of the center line” [1]. Some examples of CUSUM control charts show the CUSUM technique will pick up a signal in a sequence of 9 or more points, where just one point is barely on the other side of the center line, and so Rule 2 is not triggered in that particular sequence. Question: is the SPC chart missing the signal because we do not allow for the one point on the other side of the center line? The alternative for Rule 2 of “n out of n+k points” is re-visited. Control charts in JMP and other software are hard-coded for Rule 2 “n points in a row on a single side of the center line”. This might require updating the Control Chart Builder options for Customize Tests to allow this configuration for the user, so that one platform, the Control Chart Builder, can continue to be used for all SPC analysis.      Utilizing JMP software’s built in reports of Process Screening, Control Chart Builder, and CUSUM, JMP scripts were created that could quickly generate random normal data and example signals, analyze combinations of varying k and n for the “n out of n+k” rule, and at the same time compare to traditional tests and CUSUM. The scripts extracted when tests were triggered, determined how many signals were detected, and how many false positives and false negatives occurred. Examples for different scenarios were compared.      The results show that CUSUM is better for both false positives and detects small shifts faster than even “n out of n+k” rules. Rules 1,2,5,6 do better for short duration signals. A drawback of the CUSUM chart is that it does not display the actual data points. It is recommended that the CUSUM chart be added to Control Chart Builder, as an option along side the standard SPC charts, for graphical interpretation in a single window for the user. If the CUSUM chart cannot be easily added to the Control Chart Builder, the alternative of adding a user configurable “n out of n+k” rule is also recommended for the Control Chart Builder platform. ... View more

For future Control Chart Builder enhancements in JMP15 or beyond. New drop zones for columns that contain multiple LSL, LCL, target, UCL, USL values.   Some users have to track multiple spec limits and control limits in a relational database, so columns are stored for LSL, LCL, target, UCL, USL. Would be nice to have drop zones on Control Chart Builder for these columns, instead of relying on the static Column Properties for Spec Limits and Control Limits. For example, in Graph Builder, we can drag these columns to the right axis, and change these to lines, while keeping the raw data on the left axis as points, which mimics a control chart with changing spec limits or control limits. Or if different limits, can use these drop zones and use the By button to plot by what changes, like process or product. In Control Chart Builder, can somewhat mimic by using the Phase drop zone for a column like target, if it changes, and then use a script to add the other lines.   These drop zones would have to override any Column Properties if there are conflicts, or make a warning. And you could not save these to the column properties, since they change vs. sequence. ... View more

For each version of JMP, having to turn on in preferences the VIF column for Parameter Estimates in Fit Least Squares. I teach the Regression class in JMP, and always have to show new users that you have to right-click over Parameter Estimates table in the report to select VIF from the columns that are not displayed by default. I then have to show the class how to turn this on in the Preferences. One suggestion would be to allow this to be shown with a drop down menu item. From the Least Squares Fit Inverted Red Triangle:    Under menu item Regression Reports, the Parameter Estimates can be turned on or off. (on by default)    But also under this menu, selecting the "Show All Confidence Limits" turns these two columns on in Parameter Estimates, and in Expanded Estimates (but not a column available in Sorted Estimates). So can "Show VIF" be added to this menu just like "Show All Confidence Limits"? It would be easier to find instead of hidden in a right-click on the table in the report. Saw this question a couple of times in JMP community as well. Wish list for JMP15. ... View more

// For a contingency table report, swap the x and y // currently can swap the mosaic plot only Names Default to Here(1); dt = Open( "$SAMPLE_DATA/Big Class.jmp" ); myr = Contingency( Y( :Age ), X( :sex ) ); // Have to have a Contingency Analysis report open // Can add test to make sure it is open in the future myr = Current Report(); // taking apart CrossTabBox was easier using XML than JSL mys = myr["Contingency Table"][CrossTabBox(1)] << Get XML; // get current X role or rows of contingency table start = Contains(mys,"<CrosstabBoxRowsLabel>")+22; end = Contains(mys,"</CrosstabBoxRowsLabel>"); newY = Substr(mys,start,end-start); // get current Y role or cols of contingency table start = Contains(mys,"<CrosstabBoxColsLabel>")+22; end = Contains(mys,"</CrosstabBoxColsLabel>"); newX = Substr(mys,start,end-start); // Recreate same contingency table but with X and Y flipped // also temporarily use Value Order to match the Mosaic Plot myValueLabels = Reverse(Associative Array(Column(dt,newX)) << Get Keys); Column(dt,newX) << Set Property("Value Ordering",myValueLabels); tempCont = Contingency( Y(Column(dt,newY) ), X(Column(dt,newX) ), Contingency Table ); tempContr = tempCont << Report; mycopy = tempContr["Contingency Table"][CrossTabBox(1)] << Clone Box; tempCont << Close Window; Column(dt,newX) << Delete Property("Value Ordering"); // remove the original contingency table and replace with transpose myr["Contingency Table"][CrossTabBox(1)] << Delete; myr["Contingency Table"] << Append(mycopy); // show original side by side obj = Contingency( Y( :Age ), X( :sex ) ); Report(obj)["Contingency Table"] << Set Title("Contingency Table - Current output"); myr["Contingency Table"] << Set Title("Contingency Table - Wish List for JMP15"); Is anyone else bothered by the orientation of the contingency table and mosaic plot? I do not use it, but one of our JMP users wanted to flip the orientation of the table so that it matches the mosaic plot. Found out that if you swap X and Y, both the table and mosaic plot update. See script below to run an example and compare them side-by-side. It seems you would want the numbers in the table to line up with the cells in the mosaic plot for easier viewing and referencing. I could not find any previous discussions. It appears the contingency table cannot be changed, it is a CrossTabBox, which does not lend itself to changing anything. The script below has in the top part the work around, which is to make a clone of the table made when switching the x and y, and then appending that to the mosaic plot. Also had to do a little with Value Ordering to get it to line up. Will add to the JMP15 wishlist. I did discuss at JMP Discovery Summit with the EA lab and the developers.     Found some posts on R language, where you can use the dir() argument and specify the horizontal and vertical, while the "count" output in RStudio stays the same for the orientation. # R Mosaic Plot Example - Changing Direction getwd() employee <- read.csv("Products.csv", TRUE, sep = ",",                      na.strings = TRUE) count <- table(employee$EnglishCountryRegionName,                employee$Color) count mosaicplot(count, main = "Countries Mosaic Plot",            sub = "Product Colors by Country",            xlab = "Colors",            ylab = "Countries",            las = 1,            dir = c("h", "v"),            color = "skyblue2",            border = "chocolate") ... View more

Would be nice to have more flexible column properties for spec limits and control limits. Current column properties allow only one spec limit or control limit. But many SPC users will have changing control limits and spec limits over time. Currently Control Chart Builder can use a Phase column to separate calculated control limits. Saving to a table it will show the _LCL, _Mean, _UCL, etc. for each phase, with phase as an additional column. Could spec limits and control limits work in this manner? The ability to use a table to pull in the requirements, or save from Control Chart Builder to the Column and not just the table? See wish list requests for more flexible Value Ordering and Value Labels column properties that may interact with JMP tables. Not sure how it would work with all platforms, such as Process Screening. Currently have to write scripts to add changing control limits or spec limits to charts and other platforms. ... View more

Currently in the Fit Least Squares platform, you can "Show Prediction Expression" under "Estimates". It is shown using coded levels, and harder to interpret for many users for coefficients. Currently our users are told to "Save Columns" >  "Prediction Formula" to a column, then select the formula, and use the menu item "Simplify" to undo coded levels and show as typical coefficients for the model. Any way to add the "Simplify" function to the Prediction Expression when shown in the Fit Least Squares report? (By the way, the "simplify" in the Formula Editor was an awesome addition). Example from the Custom DOE class:   "210 + 186* ( (Thickness - 5)/2.5)"  becomes "-162 + 74.4 * Thickness" using Simplify   The Y intercept of 210 is where the coded level of -1 to +1 is 0, so a positive 210 based on coded levels. But when using Fit Y by X, the equation is -162+74.4*Thickness, which has a negative value for Y intercept when Thickness is zero. ... View more

dt:mycol << Value Labels(mylist) << Use Value Labels( 1 ); For platforms such as Control Chart Builder, JMP allows importing and exporting spec limits, control limits, etc, from a JMP file. Would like to replicate this kind of function for Column Properties such as Value Labels, Value Ordering, etc. Currently have to manually type it in. We have created JSL snippets to export and import from a JMP table frequently used ones like Value Labels. The table has columns named "Values" and "Labels", so if the user is always having to do Value Labels, can use the same. Adding a new Value Label manually, can then save and update that table. Could follow the spec limit approach and use "_Values" and "_Labels" for the column names. Would be nice to do it from the Column Properties menu, but could also be under Column Utilities. Spec limits and Control Limits under Column Properties could also be upgraded if able to do it from the Column Properties user interface. For JMP15 Wish List.   ... View more

 Metrology on semiconductor wafers is necessary to understand process targeting and sources of variation. For new device introduction and initial volume production, wafer metrology may use a large number of sites for establishing targets, setting up APC (Automated Process Control), and determine sources of variation across the wafer. However, ongoing metrology on production is often viewed as non-value added. As manufacturing volume increases and the process is maturing, the question arises: what is the purpose of the continuing metrology in relation to the number of sites? Can the number of sites be reduced to increase throughput at metrology? In the past, sites may have been removed based on current maps with reduced sites on other production, and the impact of the new map analyzed with the current site data. Utilizing the built in JSL function NChooseKMatrix(n,k) which generates all possible combinations for Choose K sites from N sites, and the Prediction Profiler, JMP scripts were created that could quickly analyze and weigh all combinations of varying K, and allow the user to pick the best reduced site map based on various requirements. Examples for different scenarios will be shown.   ... View more

Hi JMP users. When using the JMP Query Builder, we have fast response for SQL servers using "ODBC Driver 11 for SQL Server", but slow response on some Oracle servers using "Oracle in OraClient11g", on the order of 2 to 3 minutes. We discovered by accident that it works just fine using the Custom SQL() argument in the New SQL Query() function in the script, instead of using the generated script from JMP Query Builder.   Has anyone else seen slow response from Oracle ODBC?   Part of the problem as I understand it is that our log in account for this Oracle database does not allow viewing some tables in some schemas on the server, so the query builder takes time when first loading up to by-pass them. You may not be able to replicate if your database access includes all schemas and tables. Submitting direct Custom SQL bypasses this scanning of the schemas and tables?   In the example below, using Query Builder, selected columns and a filter. Took 147 seconds to run for a million rows. Now from Query Builder, select the SQL from the SQL tab, or use the "Convert to custom SQL" menu item and copy the Custom SQL (or run the query from the Custom SQL window), and paste it in as the argument for Custom SQL(), and it took only 7 to 8 seconds for a million rows. // this is the JSL script generated by JMP Query Builder and saved to the datatable // takes ~ 147 seconds to run t1 = Tick Seconds(); New SQL Query( Version( 130 ), Connection(mycon), QueryName( "Test1_147s" ), Select( Column( "X1", "t1" ), Column( "X2", "t1" ), Column( "X3", "t1" ), Column( "X4", "t1" ), Column( "LAST_UPDATE_DATE", "t1", Numeric Format( "m/d/y h:m:s", "0", "NO", "" ) ) ), From( Table( "MY_DATABASE_TABLE", Schema( "SCHEMA" ), Alias( "t1" ) ) ), Where(EQ(Column( "X2", "t1" ),"AAAA",UI( Comparison( Base( "Categorical" ) ) ))) ) << Run foreground; t2 = Tick Seconds(); t2-t1; // 147 seconds // Now just copy the SQL code and put into the CustomSQL argument // takes ~ 8 seconds to run t1 = Tick Seconds(); New SQL Query( Connection(mycon), QueryName( "Test2_8s" ), CustomSQL( "SELECT t1.X1, t1.X2, t1.X3, t1.X4, t1.LAST_UPDATE_DATE FROM SCHEMA.MY_DATABASE_TABLE t1 WHERE ( ( ( t1.X2 = 'AAAA' ) ) )" ) ) << Run foreground; t2 = Tick Seconds(); t2-t1; // 8 seconds   For our JMP Query Builder best practices, will now have to show how to run and save the query and datatable from the Custom SQL window for Oracle databases. ... View more