cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Try the Materials Informatics Toolkit, which is designed to easily handle SMILES data. This and other helpful add-ins are available in the JMPĀ® Marketplace
Choose Language Hide Translation Bar

Capability Index Plot Shade levels

Hello Community,

I want to use the capability index plot for my process capability report. Therefore I need to change the shade levels (yellow and green area). The capability line is 1.0 which is still ok. Now I want to change the yellow borderline to 1.33. Is this change possible? I haven't found a possibility to change this line.

 

JMP version:16.2

 

Do you have an idea @Jonas_Rinne

 

Thanks for your help! 

 

David_Hanslian_0-1669214623551.png

Here is the part of my session script for the report:

 

 

Capability Index Plot( 1, Capability Lines( 1 ), Shade Levels( 1 ) ),
	Process Performance Plot( 0 ),
	Automatic Recalc( 1 ),
	SendToReport(
		Dispatch(
			{"Overall Sigma Capability Summary Report"},
			"",
			TableBox,
			{Sort By Column( 13, 0 )}
		),
		Dispatch(
			{"Capability Index Plot"},
			"2",
			ScaleBox,
			{Min( -0.0316605834674102 ), Max( 3.56546171869086 ), Inc( 1 ),
			Minor Ticks( 0 )}

 

1 ACCEPTED SOLUTION

Accepted Solutions

Re: Capability Index Plot Shade levels

Hi David,

 

The "Shade Levels" option for the Capability Index Plot automatically shades the levels based on the Ppk slider on the right: Less than the slider value = red; up to 2x the slider value = yellow; more than 2x the slider value is green. This behavior can't be changed, but there's a workaround.

 

If you uncheck the "Shade Levels," then right-click on the Ppk axis and select Axis Settings..., you can create custom shaded zones to your liking. Example script below:

open ("$SAMPLE_DATA\Cities.jmp");

Process Capability(
	Process Variables( :OZONE, :CO, :SO2, :NO ),
	Spec Limits(
		:OZONE( LSL( 0 ), Target( 0.05 ), USL( 0.1 ) ),
		:CO( LSL( 5 ), Target( 10 ), USL( 20 ) ),
		:SO2( LSL( 0 ), Target( 0.03 ), USL( 0.08 ) ),
		:NO( LSL( 0 ), Target( 0.025 ), USL( 0.6 ) )
	),
	Moving Range Method( Average of Moving Ranges ),
	Capability Box Plots( 0 ),
	Goal Plot( 0, Shade Levels( 1 ) ),
	Capability Index Plot( 1 ),
	Process Performance Plot( 0 ),
	SendToReport(
		Dispatch(
			{"Capability Index Plot"},
			"2",
			ScaleBox,
			{Add Ref Line( {-1, 1}, "Solid", "Red", "", 1, 0.25 ),
			Add Ref Line( {1, 1.33}, "Solid", "Yellow", "", 1, 0.25 ),
			Add Ref Line( {1.33, 3}, "Solid", "Green", "", 1, 0.25 )}
		)
	)
);

View solution in original post

3 REPLIES 3

Re: Capability Index Plot Shade levels

Hi David,

 

The "Shade Levels" option for the Capability Index Plot automatically shades the levels based on the Ppk slider on the right: Less than the slider value = red; up to 2x the slider value = yellow; more than 2x the slider value is green. This behavior can't be changed, but there's a workaround.

 

If you uncheck the "Shade Levels," then right-click on the Ppk axis and select Axis Settings..., you can create custom shaded zones to your liking. Example script below:

open ("$SAMPLE_DATA\Cities.jmp");

Process Capability(
	Process Variables( :OZONE, :CO, :SO2, :NO ),
	Spec Limits(
		:OZONE( LSL( 0 ), Target( 0.05 ), USL( 0.1 ) ),
		:CO( LSL( 5 ), Target( 10 ), USL( 20 ) ),
		:SO2( LSL( 0 ), Target( 0.03 ), USL( 0.08 ) ),
		:NO( LSL( 0 ), Target( 0.025 ), USL( 0.6 ) )
	),
	Moving Range Method( Average of Moving Ranges ),
	Capability Box Plots( 0 ),
	Goal Plot( 0, Shade Levels( 1 ) ),
	Capability Index Plot( 1 ),
	Process Performance Plot( 0 ),
	SendToReport(
		Dispatch(
			{"Capability Index Plot"},
			"2",
			ScaleBox,
			{Add Ref Line( {-1, 1}, "Solid", "Red", "", 1, 0.25 ),
			Add Ref Line( {1, 1.33}, "Solid", "Yellow", "", 1, 0.25 ),
			Add Ref Line( {1.33, 3}, "Solid", "Green", "", 1, 0.25 )}
		)
	)
);

Re: Capability Index Plot Shade levels

Thanks for the fast answer and the work around, Jed.

 

I checked all the options and did not find a direct solution.  

Re: Capability Index Plot Shade levels

Hi Jed, 

 

thanks a lot for your solution. It was easy for me to implement it

 

David_Hanslian_0-1669373716463.png