cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Browse apps to extend the software in the new JMP Marketplace
Test Time Optimization
mzwald
Staff

If you work in the semiconductor industry (or any industry where extensive testing is performed on products), then reducing test time is a major component to reducing operational costs for manufacturing. Semiconductor test time is expensive, and projected to increase, contributing a significant amount to the total manufacturing cost of a semiconductor device. Reducing test time will translate into large savings, especially for high volume and complex products.

While there is specialized software available to accomplish this task, I wanted to demonstrate how it could be performed in JMP using a custom add-in.  Add-ins allow users to extend the functionality of what JMP can do out of the box into custom applications. This is accomplished through JMP scripting and with it, you can create any type of customized functionality. To install this add-in, download the .jmpaddin file along with the two sample .jmp files and open the .jmpaddin file with JMP (File > Open). Opening the .jmpaddin file with JMP will install it and the add-in will be accessible from JMP's Add-Ins menu.

 

This add-in requires two sets of data: run-on-error (ROE) test data and test time data in the .jmp data table format. Run-on-error is required so that the optimizer add-in can determine which tests have overlapping test coverage, and use that, combined with the test times, to determine the optimal test order. This optimization will not work with stop-on-fail test data. The attached .jmp files to this blog are examples of the format required for the ROE and test time data tables. (Note: the ROE data needs to have values of 1 representing a test fail and 0 representing a test pass and each row is a different unit being tested).

 

Read my Test Time Optimization blog to see how I used the .jmp files with the add-in. If you have questions about the test time optimizer add-in, please comment below or contact me through email (mark.zwald@jmp.com).

Comments
drotshil1

Hi Mark,

First of all, I would like to feedback that this is a great Tool for TTR. 

I think it can be very useful.

I tired it first using your example data set and it was working just fine. 

I then tried it using my own data set and found few issues. for example, it shows me that full test time is 89s while it is actually 49s...

Not sure if it is a fair request, but it would be great if you could take a look? ( Unfortunately I can't debug it on my own as I don't have the JSL script itself).

Of course I can add my data set ( ROE file and Test Time file)

  

mzwald

Hi @drotshil1 ,

I would be happy to take a look at your use case.  If you could send me anonymized versions of the bin results and test times (similar format to the files I've attached in this blog), then I can follow up with you in a video call.

I can be reached at mark.zwald at jmp dot com.

drotshil1

Hi @mzwald ,

thanks a lot, I'll send you an email with the JMP files I was using and it would be great to have a video call. 

appreciate your help! 

 

mzwald

A bug was found in the original add-in. 

v1.1 fixes it which is attached to the blog post.

Thanks to @drotshil1 for helping identify it!

Recommended Articles