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.
One of my favourite ways of visualising data is with the use of a tree map.
There are many reasons to make code re-usable. Even if you don’t want to re-use the code! I want to explore these reasons but first I need to introduce the nature of JSL syntax and the role of functions.
Convention suggests that programming languages should be introduced with a
simple trivial “Hello World” program. So I thought I would respect this convention and introduce JSL using this principle.
The Fit Model platform within JMP is incredibly powerful but can sometimes feel a little bit overwhelming when models are simultaneously being constructed for multiple responses.
When we create a custom window in JMP we basically design a layout for a variety of user interface building blocks referred to as display boxes. Most of these are quite logical – a button box displays a button, a radio box displays a radio button, a list box displays a list, and a text box displays some text.