Hello everyone,
I have the problem that I like to use the control chart builder and the Lot numbers I put in the x-axis do not stay as set, when I save it as script to use again, once my data table is refreshed. I got four control charts save in the script and usually the first one has the set right, but the other three don't. So every time I start the script I have to set the last three control chart again. A bit of a hassle it is.
"Charge",
{Min (113), Max (147.5), Inc (1), Minor Ticks (0)}
),>
That's the code for the first box, but for the others it is the same:
"Charge",
{Min (113), Max (147.5), Inc (1), Minor Ticks (0)}
),>
and so on.
So where is my error? I just set all the control charts and the saved it as a script. So I guessed JMP will provide all the right details for it.
Hope someone can help me out!
see you
Jan
JMP is pretty good, but on rare occasions the saved script can be incomplete.Cases that are confirmed as such should be reported via support@jmp.com. If you are able to post your script here, I'm sure someone would take a look. Change the column names used if they are sensitive.
Thanks Ian for your help so here is my full script. Maybe someone finds what I am missing. See you!
Jan
Control Chart Builder(
Size( 522, 452 ),
Show Two Shewhart Charts( 0 ),
Show Control Panel( 0 ),
Show Capability( 0 ),
Variables(
Subgroup( :Charge ),
Y(
:Name( "HCP-E [mg/L] Ernte" ),
:Name( "HCP-E [mg/L] MF" ),
:Name( "HCP-E [mg/L]UF/DF" ),
:Name( "HCP-E [mg/L]Capture" )
),
Phase( :Filter )
),
Chart( Points( Statistic( "Individual" ) ), Limits( Sigma( "Moving Range" ) ) ),
Local Data Filter( Close Outline( 1 ) ),
SendToReport(
Dispatch(
{},
"Charge",
ScaleBox,
{Min( 113 ), Max( 147.5 ), Inc( 1 ), Minor Ticks( 0 )}
),
Dispatch(
{"Übersicht Grenzen HCP-E [mg/L] Ernte"},
"LCL",
NumberColBox,
{Visibility( "Collapse" )}
),
Dispatch(
{"Übersicht Grenzen HCP-E [mg/L] Ernte"},
"UCL",
NumberColBox,
{Visibility( "Collapse" )}
),
Dispatch(
{"Übersicht Grenzen HCP-E [mg/L] Ernte"},
"Limits Sigma",
StringColBox,
{Visibility( "Collapse" )}
),
Dispatch(
{"Übersicht Grenzen HCP-E [mg/L] Ernte"},
"Subgroup Size",
NumberColBox,
{Visibility( "Collapse" )}
),
Dispatch(
{},
"Charge",
ScaleBox( 2 ),
{Min( 113 ), Max( 147.5 ), Inc( 1 ), Minor Ticks( 0 )}
),
Dispatch(
{"Übersicht Grenzen HCP-E [mg/L] MF"},
"LCL",
NumberColBox,
{Visibility( "Collapse" )}
),
Dispatch(
{"Übersicht Grenzen HCP-E [mg/L] MF"},
"UCL",
NumberColBox,
{Visibility( "Collapse" )}
),
Dispatch(
{"Übersicht Grenzen HCP-E [mg/L] MF"},
"Limits Sigma",
StringColBox,
{Visibility( "Collapse" )}
),
Dispatch(
{"Übersicht Grenzen HCP-E [mg/L] MF"},
"Subgroup Size",
NumberColBox,
{Visibility( "Collapse" )}
),
Dispatch(
{},
"Charge",
ScaleBox( 3 ),
{Min( 113 ), Max( 147.5 ), Inc( 1 ), Minor Ticks( 0 )}
),
Dispatch(
{"Übersicht Grenzen HCP-E [mg/L]UF/DF"},
"LCL",
NumberColBox,
{Visibility( "Collapse" )}
),
Dispatch(
{"Übersicht Grenzen HCP-E [mg/L]UF/DF"},
"UCL",
NumberColBox,
{Visibility( "Collapse" )}
),
Dispatch(
{"Übersicht Grenzen HCP-E [mg/L]UF/DF"},
"Limits Sigma",
StringColBox,
{Visibility( "Collapse" )}
),
Dispatch(
{"Übersicht Grenzen HCP-E [mg/L]UF/DF"},
"Subgroup Size",
NumberColBox,
{Visibility( "Collapse" )}
),
Dispatch(
{},
"Charge",
ScaleBox( 4 ),
{Min( 113 ), Max( 147.5 ), Inc( 1 ), Minor Ticks( 0 )}
),
Dispatch(
{"Übersicht Grenzen HCP-E [mg/L]Capture"},
"LCL",
NumberColBox,
{Visibility( "Collapse" )}
),
Dispatch(
{"Übersicht Grenzen HCP-E [mg/L]Capture"},
"UCL",
NumberColBox,
{Visibility( "Collapse" )}
),
Dispatch(
{"Übersicht Grenzen HCP-E [mg/L]Capture"},
"Limits Sigma",
StringColBox,
{Visibility( "Collapse" )}
),
Dispatch(
{"Übersicht Grenzen HCP-E [mg/L]Capture"},
"Subgroup Size",
NumberColBox,
{Visibility( "Collapse" )}
)
)
)I took a look, and the 'Dispatch()' commands that modify the report seem OK. But the Control Chart Builder report is complicated, particularly with multiple 'Y' variables. Just do a right click on the topmost outline node, then 'Edit > Show Tree Structure'!
It's difficult to go further without the data, but I would recommend bringing this thread to the attention of support@jmp.com. Then you will be 'in the system' and are guaranteed a response . . .
My guess is that you are using an older version of JMP. I ran similar code in 14.2 and saw the problem you were seeing. I ran the same code in 15.2.1 and it worked as expected. There was a bug that was fixed at some point.