Bug: Evaluate design not working for Orthogonal blocks CCD by default

[Victor_G]

What inspired this wish list request? Answering to the topic Re: How do orthogonal axis values change with the number of center points? - JMP User Community, I have created several orthogonal blocks CCD. However, when I try to run the "Evaluate design" script from the design table, the script does nothing. When using the Evaluate design platform, I have an error message :

So evaluation of orthogonal blocks CCD is by default facing an error/bug when the design table is created. 

What is the improvement you would like to see? The fix was quite easy to found: for the block factor, the value of the column property "RunsPerBlock" is set to 0 by default, which makes the Evaluate design platform bug. When setting the value to the value displayed during design creation (in the screenshot 6), then the script 'Evaluate design" from the design table and the Evaluate design platform can work normally:

 
Creating the Orthogonal Blocks CCD for 3 factors and Block size = 6

In the block factor column, RunsPerBlock is set by default to 0, hence the bug. When I change the value to 6, the script "Evaluate design" works normally:

Why is this idea important? I haven't tested extensively all orthogonal blocks CCDs to check if this bug was always present, but it's present for at least Orthogonal Blocks CCD from 2 to 5 factors. Fixing this bug should not be a big issue, the fix is easy to find.

[jszarka]

I will try to add on to the great catch by @Victor_G  as I tested this out and noticed some additional issues.

I ran the same 3-factor blocked CCD as him using the default Axial Value that is Orthogonal. The Design Evaluation in the RSM platform is very unreliable for multiple reasons. In the snippet below, you will see a very strange power of 0.05 for the Block effect. The platform in general is unreliable for updating Design Evaluation (e.g., say I change the axial from 1.633 to 1.5 as it gives 'rounder' values that are easier for operators to implement) the values in the Design Evaluation will not update appropriately. This will happen in other scenarios as well (e.g., the number of center points are adjusted, different radio buttons for axial values are chosen, replicates added). The Design Evaluation can only be trusted after you Make Table and use the Evaluate Design script (except of course, for what was just shown).

A further issue is that after hitting Make Table, the default orthogonal axial value of 1.633 is not used in the table, it is actually 1.82574185835055. Because the axial value has changed, all of the powers will shift as a result. But you can see that after making the RunsPerBlock fix, the power for the Block effect gives a more sensible value.