A column of a JMP table acts as the primary source of data for most types of analysis within JMP. That is evident by the fact that the first task you perform when you launch a platform is to assign columns to roles:
A string variable is created by enclosing a text sequence within double quotes:
str = "this is a string";
If the string needs to contain special characters, including the double quote character itself, the special characters are prefixed with an escape sequence consisting of a backslash (\) following by an exclamation mark (!).
With a little effort you can create some stunning interfaces to front-end your JSL scripts. The individual elements of the user interface are known as display boxes. They can be used to add content to a window and to control alignment.
Often we only need trivial amounts ofJSL to perform a particular task.
In an earlier post I discussed how we can reuse code by creating our own user-defined JSL functions. The most common reason I hear for not creating user-defined functions is that the code is only being used once, hence there is no requirement for reuse. But there are many benefits to creating our own functions – far beyond code reuse. In this post I’m going to explore some of those benefits.
If you want to interactively build graphs in JMP then the graph builder platform is great.
I use it a lot when I’m not so familiar with a set of data, and I’m not quite sure how I want to plot the data. The graph builder allows me to rapidly evaluate different graphical representations.
Here is a data table that I have created. It happens to contain data
that is the result of a designed experiment. I know that, but JMP doesn’t.