Thursday, November 19. 2009Visualization in Marlow with Stephen FewWe had good attendance at the SAS offices in Marlow. Some people even flew in from Ireland. As always, Stephen was fascinating. His insights into the presentation of quantitative information are thought-provoking. I learn something new every time I hear him. For a flavor of Stephen's style and point of view, be sure to check out his two white papers: Predictive Analytics for the Eyes and Mind and Visualizing Change. For a taste of his presentation, check out his Webcast from our Explorers Webcast Series.
Posted by Jeff Perkinson
in Biz Viz, Data Visualization, JMP - General
at
08:56
| Comments (0)
| Trackbacks (0)
Monday, November 16. 2009Statistics and Malcolm Gladwell
Did you see the cover article in yesterday's New York Times Sunday Book Review? Harvard psychologist Steven Pinker reviewed the new book by Malcolm Gladwell, who was the keynote speaker for the Innovators' Summit in Chicago.
Pinker writes that Gladwell is "a minor genius who unwittingly demonstrates the hazards of statistical reasoning and who occasionally blunders into spectacular failures." Also worth a read is the editors' note for the book review section, which points out that Gladwell says getting a graduate degree in statistics may be the best way to start a career in journalism now. The editors' note also quotes Pinker as saying statistical reasoning is the most important scientific concept that non-scientists lack. Tuesday, November 10. 2009Spreading the Word About JMP in China and Japan
While the chief architect of JMP, John Sall, remains heavily involved in the day-to-day development of our product here in Cary, North Carolina, he also travels the world to show what JMP can do for organizations of all kinds.
Sall flew to China and Japan recently with Steve Adams, JMP's Director of International Sales. In Beijing, Sall spent time with influential professors from Beijing University of Technology, Peking University, the Chinese Academy of Sciences and the Capital University of Economics and Business. He gave a JMP demo at the China Association for Quality and took part in a pharmaceutical conference hosted at the SAS Beijing offices. In Shanghai, Sall was a keynote speaker at the International Forum of Quantitative Decision-making and Continuous Process Improvement at Shanghai University. In Japan, Sall presented a demo at a users group meeting with about 70 JMP users. Attendees also had a chance to chat individually with Sall and Adams at a reception following the meeting. During his visit, Sall was interviewed by the chief editor of IT Media Enterprise, the largest online news media in Japan, which comprehensively covers IT-related topics. Scroll through the photos below for a look at some of the highlights of the trip. ![]() At the entrance to Shanghai University's main campus, John Sall (left) and Steve Adams (right) stand by a billboard for the International Forum of Quantitative Decision-making and Continuous Process Improvement, where Sall gave a keynote speech. ![]() A balloon-festooned sign outside the conference center celebrates John Sall's visit to Shanghai University. Provost and Executive Vice President of Shanghai University, Zhou Zewei (left), welcomes John Sall (right). ![]() The conference at Shanghai University took place in a circular meeting room where rows were arranged in concentric circles and each seat had a monitor in front of it. ![]() John Sall (front row, center) and Steve Adams (front row, left) and JMP Japan staff celebrate a successful JMP users group meeting in Japan. Monday, November 9. 2009Scripting Data in JMP
JMP scripting is an important part of the JMP user experience. Anyone can easily create a reusable JMP "program" with JMP Scripting Language (JSL) by running an analysis, selecting the hotspot (red triangle) at the top of the report, and choosing "Script." From there, you can save a script to a data table, a script window, a journal, or a project.
But did you know that you can also write a script that can create or modify a data table? To see a script that creates a data table, follow these steps: a) Open a data table in JMP. b) Open a script window (File->New->Script). c) In the script window, type Current Data Table() << get script; and run this script (Cntl-R or Edit->Run Script). d) Open the JMP log (View->Log). In the JMP log, the script that recreates the data table is shown. e) Copy and paste that script where you need it to go. An example screenshot of what this process produces is shown below. ![]() I tend to do this a lot, especially when I am preparing presentations using custom journals or when I need a starting version of a data table for a more complicated script. The multi-step process is tedious, so naturally, I wondered if I could write a JMP script that would automate that process. It turns out that it was a pretty simple script. The JSL is below, and the script file is available for download from the JMP File Exchange.
Wednesday, November 4. 2009Discover JMP with New Book in Documentation Set
If you have updated your copy of JMP 8 to 8.0.2, you already have access to a brand new book in the JMP documentation set called Discovering JMP -- though you may not have known it!
To find out a bit more about this new book, I sent a few questions to Jonathan Gatlin, a JMP technical writer who has written several posts for this blog. Here's what you need to know about Discovering JMP. Arati: What is the book about? Jonathan: Discovering JMP provides a general overview of JMP software. The chapters cover the following information: Chapter 1: Introducing JMP – basic concepts like what is a JMP platform, and how JMP is different from Excel. Chapter 2: Preparing, interacting with, and summarizing your data. Chapter 3: Visualizing your data – using graphics to explore your data. Chapter 4: Analyzing your data – looking at distributions, relationships, and models. Chapter 5: Customizing JMP – saving JMP results, creating JSL scripts, and setting preferences. Chapter 6: Special JMP features – connecting JMP with SAS, the automatic update feature, and showing interactive results outside of JMP. Arati: Why did you and the documentation team write it? Jonathan: We wrote this book to assist new JMP users in getting started quickly with JMP. The examples should give the user a good start on understanding navigation through JMP, as well as an introduction to analyzing data with the most commonly used JMP platforms. We also wanted to provide a general purpose quick start book for international markets. We plan to translate this book into all the supported JMP languages. Arati: How is it different from the other JMP books? Jonathan: Discovering JMP is one of five books in the JMP documentation set. The other books provide complete details on all of JMP’s platforms and features. For example, the Statistics and Graphics Guide provides a full description of all statistical and graphical features in JMP. The purpose of Discovering JMP is not to give complete details, but to introduce the user to some commonly used JMP platforms and to provide simple examples of each. Arati: Who is the intended audience for the book? Jonathan: Discovering JMP is written to introduce JMP to a new user. It assumes the reader has no knowledge of statistics or JMP. The book will be useful to anyone who needs to learn JMP, whether that person is a statistician, researcher, or business analyst. Arati: How can JMP users find the new book? Jonathan: This book is available with JMP 8.0.2, and can be found with the other books at the JMP install location, usually at C:\Program Files\SAS\JMP\8\Support Files English\Documentation. You can also download a PDF of the book from the JMP Documentation page on our Web site. Monday, November 2. 2009Can You Dig It?
A few weeks ago, my wife and my youngest son heard what appeared to be a lunatic shrieking in our backyard. They rushed out the door to find me standing in the midst of about a dozen freshly dug holes, waving my arms and yelling at our mud-covered, 10 month-old Golden Retriever.
The dog, who had obviously excavated all of the holes, was simultaneously wagging her tail and sneezing the dirt out of her nose, utterly unimpressed with my tirade. My wife and son managed to get me inside with the promise of a cold drink and a warm compress, all the while calmly listening to me carry on about ruined landscaping and holes all the way to China. Once I had calmed down and my wife had taken the dog off to the tub to wash away the evidence, my son solemnly informed me that it would be impossible for Gracie to dig a hole to China, because there were lots of rocks in the way and, besides, the center of the earth was way too hot. He also reminded me how much fun it can be to dig. He was right. It can be a lot of fun to dig. Now, I’m not talking about the back-breaking, working-on-a-chain-gang type of digging, but rather the treasure-hunting or the let’s-see-what-we-can-build type of digging. Just look at a bunch of kids at the beach or in a sandbox, and you’ll see what I mean. Old blues singers ask “Can you dig, it?” Peter, Paul and Mary tell us that they “dig” rock & roll music. Paul McCartney planned to “dig the weeds” when he turned 64 (somehow, I don’t think that ever happened.). The seven dwarves sang about “dig, dig, digging” in the mines where a million diamonds shine. The pirates of yore and modern-day archaeologists spend their days digging for buried artifacts and other treasures. Digging can be pretty cool! As genomics scientists, we also spend our days digging. Faced with a mountain of data, we dig and we sift and we dig some more, all the while looking for the clues buried in those mountains. Without the right tools, the task can be daunting; in fact, like treasure hunters without a map, we could dig forever without ever finding anything of value. Here at SAS, we make the tools that make the digging easier. For example, new features in JMP Genomics 4.1, which is due out later this year, include interactive, graphical tools that will allow you to visually evaluate and compare complex statistical results for thousands of genes and other markers across an entire genome. Once you’ve identified one or more genes of interest, other new features make it easy for you to annotate those genes and link your analysis to online data bases. These tools won’t help you dig to China, but they will help you sift through your data until you find the treasure. Excuse me, now. I have some digging to do. Thursday, October 29. 2009Just the Facts, Ma'am...
Now that JMP Genomics v4.1 has gone to production, I have found a little time to catch up on my reading. As I was perusing a recent issue of the Proceedings of the National Academy of Sciences (USA), I was struck by the fact that the traditional limit of 5 pages has been scrapped and that articles of 6 or more pages have become common. Papers have grown as investigators try to pack as much information as they can into more and more space. Even authors of Science reports, which have traditionally been limited to 2500 words, get around page limitations by regularly including links to Supporting Online Materials, web sites that contain vast amounts of additional data and descriptions. All of this information tends to overwhelm the reader.
Perhaps I’m just showing my age again, but I miss the days when you were limited to a strictly-enforced set number of words or pages and there were no Supplementary Online Materials. Authors had to ensure that all of the supporting facts and figures needed to tell a good story were included in the article. These requirements forced authors to carefully consider which pieces of data were the most important and to use the most concise language possible. Good papers were razor sharp and told you just what you needed to know. They were a pleasure to read. “Just the facts, ma’am…” On the old Dragnet TV series (I’m most definitely showing my age here!), Joe Friday used these words to cut through all the fluff and get down to the essentials. We follow the same philosophy when we write the documentation for JMP Genomics. We have divided the JMP Genomics User Guide, by theme, into nine different volumes. We describe each process in its own chapter. We tell you what the process does and what you need to run it. We then show an illustrative example and tell you how to interpret the results. Each chapter is structured in the same way; once you learn how it works for one process, you know how it works for every process. A colleague of mine, who documents a different software package, recently told me that the JMP Genomics documentation was rather simple. Rather than being insulted, I took her comment as the highest form of praise. Software documentation should not contain a lot of fluff. Instead, it should just tell you what you need to know in an easily accessible format and then it should get out of your way. The JMP Genomics User Guide is designed to do just that. Solar Panel Output Versus Temperature
The SAS Solar Farm data (available in the JMP File Exchange) has proven to be a rich topic for discussion and exploration. Besides the cool factor from green technology, the factors (such as sunlight, wind, temperature) can be understood by anyone, and yet the interactions are complex and not all linear. One issue that came up in the comments to my original post was the effect of ambient temperature on the power output. Rather than try to create an accurate model to account for sun position and solar panel angle, I tried some basic visual exploration to get a feel for the relationship of temperature and power.
A fair starting point is a basic plot of power versus temperature for the whole data set. ![]() Here, I've set the graph transparency to 0.3 to give a point cloud effect. The visual is not too helpful except to get us to think about the other factors that are conditioning the relationship between power and temperature. Factors we have in our data set include time of day, day of year and solar irradiance. Other factors we might derive or get externally include solar angle, panel temperature and weather conditions. Eschewing complex models, I tried conditioning the data on irradiance (sunlight) and time from solar noon (as a proxy for panel angle and sun position). The idea is that, say, two hours before noon and two hours after noon would have the same panel angle and sun position but likely different temperatures and power output levels. Solar noon, also called local apparent noon (LAN), is where the irradiance peaks on sunny days. We only have data in 15-minute intervals, and solar noon seems to be between 12:15 and 12:30 for the Cary, NC, area, and I chose 12:30 for my calculations. From that I calculated Minutes from LAN. Here's the power versus temperature conditioned on both Irradiance and Minutes from LAN. ![]() Most of the panels show a slight negative relationship, as expected for solar cells. Eyeballing the trends suggests about 3kW per degree Celsius, or about 1% per degree. That seems a little high from what I've read, and I think it's because the panels still contain a bit of mixing of different conditions. To go a step further, I decided to look at individual pairs of times equidistant from solar noon. With plenty of pairs to look at, I filtered it down to pairs with strong power output, a significant temperature difference (more than 4°C), a similar irradiance value and on a single array. ![]() Each line connects a matched pair of temperature/power readings for a given day and panel angle (assuming the angle is proportional to minutes from local area noon). Now we can see that most pairs exhibit a small negative relationship, though there are a few outlier slopes in both directions. What accounts for those? Using Distribution or Tabulate, we find the median slope to be about -1.2 kW/°C, which is about 0.3% per degree based on an average 350kW base. Monday, October 26. 2009They Say It's Your Birthday...
Today is a special day for a colleague. Happens every 365 days.
A good friend here is 1388534400 today. At least that's what JMP tells me when I put her birthday in one column and today's date in another and then calculate the difference. You see, JMP stores dates as the number of seconds since midnight on January 1, 1904. So today's date, October 26, 2009, is 3339360000 as far as JMP is concerned. Fortunately, JMP has a host of built-in functions to help deal with dates in this format. See the whole list in the Formula Editor under the Date Time category. One very helpful class of these functions are the In XXX() functions where XXX is a time unit. These functions return the number of seconds in the time unit specified. For example, In Minutes(1) returns 60. That is, there are 60 seconds in 1 minute. These functions come in handy for converting JMP's seconds-based dates to something more readable, like years. You do that by dividing a number of seconds by In Years(1): ![]() To save my friend's dignity, I'll let you use that formula to figure out how old she is. I hope that she has a great day. Wednesday, October 21. 2009Oil and Gas Industry Sees Value in JMP
Team members from JMP attended the Society of Petroleum Engineers 2009 Technical Conference in New Orleans, Louisiana, earlier this month.
The data visualization capabilities of JMP 8 were demoed at the event and were well-received by conference attendees representing a wide range of professions in the oil and gas industry. They saw great value in how JMP visual analytics and exploratory data analysis can help optimize efficiency and reduce costs in both the upstream exploration/extraction to downstream refining operations. The JMP team also presented real oil and gas business case examples to participants that highlighted how JMP's fast and interactive analysis can quickly find trends and then present these results to others in a visually compelling way. To learn more about how JMP can help your oil and gas business, visit our oil and gas page and consider trying our free 30-day trial of fully functional JMP 8 for yourself! Tuesday, October 20. 2009Why You Need to Know About Split-Plot Designs
Bradley Jones, Director of R&D for JMP, and Christopher Nachtsheim, Professor in the Carlson School of Management at the University of Minnesota, collaborated on a paper that was published this month in the Journal of Quality Technology. Both authors have published widely on the subject of design of experiments and are recognized as experts in the field.
Their new paper is titled “Split-Plot Designs: What, Why and How,” and in this interview with Brad, I asked him those same questions contained in the paper title. Subscribers to the Journal of Quality Technology can read the full article via the ASQ Web site. Arati: What is a split-plot design? Brad: A split-plot experiment is a statistically designed study where the experimental runs are grouped so that certain variables do not change their settings within a group. The experimenter only changes these variables or factors between groups of runs. Holding these factors constant for an entire group of runs means that the run order for these experiment is not completely random. Statisticians often recommend the use of completely randomized designs rather than split-plot designs. Arati: Why are split-plot designs important for practicing statisticians to know about? Brad: Though complete randomization avoids certain problems in the analysis and interpretation of results from experiments, it often requires substantial extra effort. In many processes, certain factors are hard to change from one processing run to the next. To change some factors is as easy as turning a dial or flipping a switch. Changing others can require making time-consuming and expensive alterations to the system. It makes sense to structure your experimental runs to take this practical constraint into account. That is, you would like to do several runs in a row only changing factors that are easy to manipulate before stopping the system to make a big change. Slavish insistence on complete randomization has sometimes resulted in operational people sorting a randomized design for logistical convenience without informing the principal investigator. This sorting makes the design a split-plot design but generally a poorly constructed one. Worse yet, the principal investigator, being unaware of the sorting, analyzes the data as though the run order was random. Since the appropriate analysis of a completely randomized design is different from that of a split-plot design, the consequence of the run-sorting subterfuge can invalidate the results and make for poor decisions. Arati: Tell me about one or two of the recent developments in designing and analyzing split-plot experiments. Brad: In the last decade, the design and analysis of split-plot experiments has been a hot topic in research literature. For my money, the most exciting developments have been the methods for design and analysis of optimal split-plot experiments. It is not really the optimality of the designs that makes this approach exciting, though optimal designs certainly have desirable properties. The real value of these methods it that they allow for much more flexible problem specification and thus much wider applicability. Arati: What was your purpose in writing this article with Professor Nachtsheim? Brad: A couple of years ago I had a conversation with two past editors of the Journal of Quality Technology. They noted the resurgence of interest in split-plot designs. They also were concerned that the mathematical complexity of some of the publications were leaving most practitioners behind. There was the fact that different researchers often recommend slightly different approaches. This can confuse practitioners who do not have the background to discriminate between competing methods. Professor Nachtsheim and I wrote the article to cover all the major research lines pursued in the last decade or so and to present even-handedly their strong and weak points. I included Professor Nachtsheim in the project because I have been an advocate for one approach, and I thought it would be more objective to include an author who had no strong prior convictions. Arati: Who is the audience for this article, and how do you hope they will use the information in it? Brad: We wrote the article for two audiences. For the statistician who is unfamiliar with the recent trend in this area, our article provides a reference list and a guide to the main lines of research. The more important audience, however, is the community of practitioners. We wanted to provide information to empower this community to use these new methods profitably. Tuesday, October 13. 2009Authors Take Statistics, JMP to Engineers and Scientists
I met José Ramírez, PhD, in Chicago at the JMP Discovery conference and Innovators’ Summit. An industrial statistician and longtime JMP and SAS user, he was quite the celebrity at the conference, where he gave a well-attended talk about designing experiments using JMP and SAS.
José told me about his new book, co-authored with his wife Brenda Ramírez, who is also an industrial statistician and expert user of JMP and SAS. The pair wrote the book, Analyzing and Interpreting Continuous Data Using JMP: A Step-by-Step Guide, over two years, on weekends and evenings. They also write a blog called Stat Insights that includes excerpts from their book and discusses “statistics as a catalyst for engineering and scientific discoveries.” Here, José and Brenda share details about the book for readers of the JMP Blog. Arati: Why did you decide to write this book? José & Brenda: A few years ago, the JMP team approached us with the idea to write a book for engineers and scientists. This seemed like a natural progression in our careers, since we have been collaborating with engineers and scientists for many years and we have developed and delivered countless hours of training in statistics and continuous improvement. In addition, we are big fans of JMP software and have been using it for a long time. So writing this book seemed like the perfect opportunity for us to consolidate the significant knowledge we have gained as practicing industrial statisticians, and share it in a way that is far-reaching and useful to this community. An additional inspiration for our book comes from the National Bureau of Standards Handbook 91 Experimental Statistics by Mary Natrella. We wanted to bring the same spirit and utility of the NBS Handbook 91 to the countless engineers, scientists and data analysts whose work requires them to transform data into actionable information. Arati: Who, specifically, will benefit from reading and using your book? And how do you hope they will use the book? Brenda: The book is primarily written for engineers and scientists who need to use statistics and JMP to make sense of data and make sound decisions based on their analyses. This includes, for example, people working in semiconductor, automotive, chemical and aerospace industries. Other professionals in these industries who will find it valuable include quality engineers, reliability engineers, Six Sigma Black Belts and statisticians. In addition to the working professional, those who are studying to become engineers, scientists or even statisticians, as well as those teaching them, should get a copy of our book. It is a great teaching aid. For those who want a reference for how to solve common problems using statistics and JMP, we walk through different case studies using a seven-step problem-solving framework, with heavy emphasis on the problem setup, interpretation, and translation of the results in the context of the problem. For those who want to learn more about the statistical techniques and concepts, we provide a practical overview of the underpinnings and provide appropriate references. Finally, for those who want to learn how to benefit from the power of JMP, we have loaded the book with many step-by-step instructions and tips and tricks. Arati: What kinds of case studies or problems do you discuss in the book? José: In Chapters 3 through 7, we start with a problem description, setting the stage for the uncertainties that need to be solved using the statistical techniques described in the chapter. All of the case studies in the book are based upon common problems that engineers or scientist will come across at some point in their careers, and the chapter headings reflect the specific application. For example, in Chapter 4, “Comparing the Measured Performance of a Material, Process, or Product to a Standard,” we use a semiconductor example involving a new three-zone vertical furnace for thin film deposition of waters to illustrate the usefulness of one-sample significance tests to qualify a new piece of equipment. In Chapter 5, “Comparing the Measured Performance of Two Materials, Processes, or Products,” we compare the performance of two mass spectrometers in an analytical laboratory using the atomic weight of silver to determine if a bias exists and to understand their measurement error. Although it is not officially a case study, we are thrilled to include in Chapter 7 the data from Albert Einstein’s first published paper. In his 1901 paper, a young Einstein used least squares to fit a model to investigate the nature of intermolecular forces. Arati: It’s pretty cool that you had Professor Douglas Montgomery write the foreword to your book. How did you make that happen? José: Ever since we were students, we have been using and following the work of Professor Montgomery, and we believe his books are excellent references for engineers and scientists. We also share a passion for industrial statistics and Doug and I have crossed paths many times over the years at various statistical conferences and events, including, more recently, at JMP conferences. When we put all of these pieces together – statistics, engineering and JMP – Professor Montgomery seemed like the perfect person to entrust with this important part of our book. So we just had to find a way to ask him if he would be willing to write the foreword to our book. Luckily for us, that opportunity arose at the Quality & Productivity Research conference in June 2008 in Madison, WI. At that event, I was able to discuss this possibility with him, and without hesitation he said, “Yes.” Arati: How will you use this book going forward in your professional career? Brenda: This book is a reflection of how we collaborate with engineers and scientists to use statistics as a catalyst for new discoveries and insights. Having the book will make it easier to share our statistical engineering philosophy with others. Arati: Where is your book sold? José: Our book is available online from the SAS Web site or Amazon.com. Both Web sites allow the reader to view the table of contents and a sample chapter from the book.
Posted by Arati Bechtel
in Discovery, Innovators' Summit, JMP - General, Statistics
at
10:36
| Comments (0)
| Trackbacks (0)
Monday, October 12. 2009Answering Your Demand for Design of Experiments
Recently, JMP has been deluged with requests for information about Design of Experiments (DOE or DOX). Was it due to atmospheric disruption when NASA hit the lunar south pole last week? Or shall we just chalk it up to a growing desire to work smart and make better use of resources in the workplace?
Never fear, JMP is responding. On October 28, author and Arizona State University professor Douglas Montgomery and JMP’s Brad Jones are offering a free seminar on DOE in Phoenix. At the seminar we will give away some copies of several books, including Montgomery’s latest edition of Design and Analysis of Experiments and a new SAS Press book by W.L. Gore employees and JMP users José and Brenda Ramírez, Analyzing and Interpreting Continuous Data Using JMP: A Step-by-Step Guide. Join Doug, Brad, Susan Glick, John Guerrero and the southwest US JMP team on Thursday, October 28. Seats are filling fast so register today.
Posted by Gail Massari
in Design of Experiments (DOE), JMP 8, Statistics
at
11:20
| Comments (0)
| Trackbacks (0)
Monday, October 5. 2009JMP Is 20 Years Old
Today is the 20th anniversary of JMP's first release, and I want to thank everyone who has helped to make JMP a success.
JMP Version 1 shipped on October 5, 1989 -- or as we claimed at the time September 35 -- so that we could say we shipped in the third quarter of 1989, our goal. JMP started as a research project in the late '80s. In the earlier part of that decade, we had spent several years rewriting SAS completely (but compatibly) to fit on personal computers. But by 1988, we felt three big forces, which can be characterized by:
As for the Vehicle, SAS was becoming a large enterprise-scale product -- a larger investment than some users, like engineers and scientists, were willing to handle. We were producing analytical trucks, but there was a market for analytical cars, i.e., something with low investment and ease of driving. We needed a more personal-scale tool, one for the desktop project rather than for the enterprise system. As for the Roles, statistics itself was seeing the opportunities in exploratory techniques, and the value of graphics and interactivity. The statistics profession had been molded as a testing discipline, a role like a lawyer whose job is to prove things that we already knew. What was missing was the exploratory role, like a detective, whose job is to discover things we didn't already know. Especially since John Tukey's Exploratory Data Analysis and the improvement of statistical graphics, statistics needed to serve in the detective role as well as the lawyer role. Graphics was the key enabler of seeing patterns, and points that don't fit patterns. As for the Technology, the graphical user interface arrived with the Macintosh, and later, Windows. It is a huge difference to just point and click rather than look up and type. Applications written for batch computing through languages were not suited for graphical interactivity. It was time for some fresh design. In response to these three forces, we formed a small group to put something together. In a year and a half, we released Version 1 of JMP. This was a very small product compared to the JMP of today, but it had all the basics of statistics and graphics, with many innovative features. We thought "jump" was a name to suggest a big step into a new future, a product that jumps in responsiveness to the mouse, and a tool that enables our customers to do the experiments and make the discoveries to take huge strides in their products and processes. In the early years, we learned important lessons. We learned that engineers and scientists were our most important customer segment. These people were smart, motivated and in a hurry -- too impatient to spend time learning languages, and eager to just point and click on their data. We had a product that was nearly as easy as walk-up-and-use with enough delights to hold their loyalty. We learned that engineers need design of experiments (DOE), quality and productivity support (Six Sigma), and reliability modeling. We made sure we got better in these areas -- particularly DOE. We thought that engineers should be able to just ask the computer to custom-make a design that fits their needs rather than attempting to find a pre-built design that works. We learned how to port to Windows. We made JMP work on Windows with release 3.1, using the Altura library. This was a quick effort. Soon we were busy rewriting the whole product in a different implementation language with a portability host-interface layer, which led to a wait of more than three years before Version 4. Version 4 not only switched languages, but also introduced a new nervous system for the product, including the JMP Scripting Language. In the last few years, JMP has matured considerably. The big driving force has been in meeting the needs of those users we talk to, who correspond with us, who sometimes invite us into their sites. We have a very dedicated group of users who keep us directed, and help us serve more and more researchers every year. Recently, I heard the group of passionate JMP users termed the “JMPerati,” analogous to Stephen Baker’s term, the “numerati.” JMP has broadened to become more versatile. JMP now supports business visualization in partnership with SAS Business Intelligence, and this in turn has encouraged us to introduce more visualization platforms, like the drag-and-drop Graph Builder in JMP 8. JMP can now handle larger problems because of work we have done to multithread many of the bottleneck methods and to implement JMP on 64-bit systems. And we now work with various SAS teams on projects in several areas, collaborating and sharing efforts. JMP is 20 years old, but it seems like it is just getting started. We are growing fast. Last year, our business grew faster than ever, and we are set up to grow even faster in the future. Happy birthday, JMP, and thank you, everyone, for your contributions to JMP's success. Friday, October 2. 2009Share Your JMP Stories (or Videos) as JMP Turns 20
The curious vintage junkie in me borrowed the 20-year-old JMP box that John Sall holds up in his 20th anniversary video.
The description of JMP on the back cover was a surprise. Why? That description still applies today, 20 years later:
Feel free to post a comment here. Or post a video response to Sall’s 20th Anniversary video or to our global thank you on the SAS YouTube Channel. You can also tweet your comment using the Twitter tag #JMP20.
(Page 1 of 17, totaling 250 entries)
» next page
|
ABOUT THIS BLOG
JMP Statistical Discovery Software from SAS
is proud to bring you this blog on all things related to
data visualization, visual Six Sigma, design of experiments
and other statistical topics.
The blog content appearing on this site does not necessarily represent the opinions of SAS. Your use of this blog is governed by the Terms of Use. CategoriesQuicksearchSyndicate This Blog |
||||

