🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

Thread View: comp.lsi.testing
5 messages
5 total messages Started by Praveen Vishakantaiah Fri, 28 Aug 1992 14:36
Rise and shine
#36
Author: Praveen Vishakantaiah
Date: Fri, 28 Aug 1992 14:36
71 lines
4352 bytes
It is very interesting to delve into the reasons why this group is having
problems getting any postings. Here are my two cents worth to motivate
test engineers to generate useful and relevant discussions even in the
midst of unencouraging number of postings in this group.

Holger> I cannot imagine that everyone is interested in design
Holger> (comp.lang.vhdl, comp.lang.verilog, comp.sys.mentor, comp.lsi*),
Holger> but nobody in testing of all the stuff produced. 

Well, isn't testing harder than designing ;-). Nobody has proved VLSI 
design to be an NP-complete problem (as far as I know)!

Also, if you look at the topics that are discussed in the design groups,
most of them are centered around the usage/bugs of a commercial design
tool or how to obtain free software. There are not as many commercial test
tools or free test software that is as widely used as design software in
order to generate postings in this category.

Allingham> Hopefully, someday all designers will realize that test needs 
Allingham> to be considered up front.

This is a very interesting point, but test engineers or project managers
cannot just hope for this to happen:-). I don't think the designers can be
forced to learn the test strategies from somewhere and expect them to 
start putting lot of man hours into incorporating test ideas as they
design. The test tools and research should be directed towards automating
the interaction between design and test and I feel that this is happening 
now. Test research and tools should not just aim at producing 100% fault 
coverage for a particular category of faults.

Harlow> Come on, Janak: you have lots of good things going on at UIUC: how
Harlow> about some timely, controversial postings from you and/or your
Harlow> group?

Although this is a very good and useful suggestion, it is very unlikely 
that researchers are ready to discuss their ideas openly due to competitive 
reasons. But, we can always discuss published work as well as get feedback
from people in the industry as to the research direction in testing which
would be useful to them.

Harlow> Suppose we had a manufacturing line whose yield was 100%...  
Harlow> would we then not need to test products? .........
Harlow> .................
Harlow> More generally speaking, how much of what we call testing is
Harlow> actually a cover for lack of design verification?

The way I would look at this question before answering it, is -
To prove that the yield was 100%, would I use design verification or 
testing? I would use testing since formal verification of designs does 
not handle manufacturing defects in the strict sense. But again, you can 
use information generated during formal verification to potentially obtain
test vectors. I would say, formal verification and testing are two sides
of the same coin. The value is the same, but they look different depending
on which side you want to look at!

Rise and shine, all you testing folks. Spend some time posting useful
discussions pertaining to VLSI testing. Don't work too hard on the testing
problem [I hope my advisor does not see this:-)]. After all, the testing
problem was NP-complete, is NP-complete and will be NP-complete!! 

Praveen Vishakantaiah.

------------------------------------------------------------------------------
-- Microelectronics and Computer Technology Corporation, | Ph : (512)338-3736|
-- 3500 W. Balcones Center Drive                         | e-mail :          |
-- Austin, TX 78759.                                     | praveen@mcc.com   |
------------------------------------------------------------------------------
-- ALSO A HARD WORKING MEMBER OF :-)
-- Computer Engineering Research Center,                 | Ph : (512)471-8013|
-- University of Texas, Austin.             e-mail : praveen@cerc.utexas.edu | 
-----------------------------------------------------------------------------
Re: Rise and shine
#41
Author: Raghu Hudli
Date: Fri, 28 Aug 1992 16:28
42 lines
2051 bytes

In article <1992Aug28.143621.1917@mcc.com>, praveen@sirius.mcc.com
(Praveen Vishakantaiah) writes:
>
>
  some stuff deleted....

An interesting posting; however it elicits a couple of comments....

> 
> Holger> I cannot imagine that everyone is interested in design
> Holger> (comp.lang.vhdl, comp.lang.verilog, comp.sys.mentor, comp.lsi*),
> Holger> but nobody in testing of all the stuff produced. 
> 
> Well, isn't testing harder than designing ;-). Nobody has proved VLSI 
> design to be an NP-complete problem (as far as I know)!
> 

  That is not true. There is a mulititude of problems that are NP-complete
in physical design of VLSI, including placement, routing, pin assignment, etc. 

> 
> Rise and shine, all you testing folks. Spend some time posting useful
> discussions pertaining to VLSI testing. Don't work too hard on the testing
> problem [I hope my advisor does not see this:-)]. After all, the testing
> problem was NP-complete, is NP-complete and will be NP-complete!! 
                                               ^^^^^^^^^^^^^^^^^^^^

   ... until the question P = NP ? remains unresolved.


> Praveen Vishakantaiah.

Raghu Hudli
-----------------------------------------------------------------------
Raghu V. Hudli                       Tel:   (914) 892-4188
IBM Corporation                      Fax:   (914) 892-4316 
E. Fishkill, NY                      email: raghu@vnet.ibm.com
------------------------------------------------------------------------
Disclaimer: The opinions/views expressed here are mine and my employer
does not necessarily concur with me.
Re: Rise and shine
#43
Author: Holger Veit
Date: Mon, 31 Aug 1992 07:35
66 lines
4173 bytes
In <1992Aug28.143621.1917@mcc.com> praveen@sirius.mcc.com (Praveen Vishakantaiah) writes:

>Holger> I cannot imagine that everyone is interested in design
>Holger> (comp.lang.vhdl, comp.lang.verilog, comp.sys.mentor, comp.lsi*),
>Holger> but nobody in testing of all the stuff produced. 

>Well, isn't testing harder than designing ;-). Nobody has proved VLSI 
>design to be an NP-complete problem (as far as I know)!

>Rise and shine, all you testing folks. Spend some time posting useful
>discussions pertaining to VLSI testing. Don't work too hard on the testing
>problem [I hope my advisor does not see this:-)]. After all, the testing
>problem was NP-complete, is NP-complete and will be NP-complete!! 

I don't think that you can rate the design process by the complexity of an 
algorithm, but even for testing, NP-completeness could have been shown for
combinational deterministic TPG (polynomial transformation to SAT problem) 
only. Sequential TPG has the additional time parameter (this might come close
to Turing's halting problem). Your opinion is quite correct. Everybody who
has put together two gates successfully, might be called a "designer"
(I am really afraid that some of the students which have heard - not learnt -
design courses here will go to industry and design some microprocessor which
will control parts of my car :-), just self-criticism, forget it), but
design verification or testing really requires some skills.

>Harlow> Come on, Janak: you have lots of good things going on at UIUC: how
>Harlow> about some timely, controversial postings from you and/or your
>Harlow> group?

>Although this is a very good and useful suggestion, it is very unlikely 
>that researchers are ready to discuss their ideas openly due to competitive 
>reasons. But, we can always discuss published work as well as get feedback
>from people in the industry as to the research direction in testing which
>would be useful to them.

This is what Nikolaus and I intended when we proposed this group. I would not
expect that for instance Janak talks about his recent improvement that he 
just put into his software, but if he contributes a paper to some conference, 
and is accepted and the date of the delivery of the final version is over 
(important!), he could talk about it, and may profit from a discussion on it.

>Harlow> Suppose we had a manufacturing line whose yield was 100%...  
>Harlow> would we then not need to test products? .........
>Harlow> .................
>Harlow> More generally speaking, how much of what we call testing is
>Harlow> actually a cover for lack of design verification?

See my reply to the original posting.

>Praveen Vishakantaiah.

>------------------------------------------------------------------------------
>-- Microelectronics and Computer Technology Corporation, | Ph : (512)338-3736|
>-- 3500 W. Balcones Center Drive                         | e-mail :          |
>-- Austin, TX 78759.                                     | praveen@mcc.com   |
>------------------------------------------------------------------------------
>-- ALSO A HARD WORKING MEMBER OF :-)
>-- Computer Engineering Research Center,                 | Ph : (512)471-8013|
>-- University of Texas, Austin.             e-mail : praveen@cerc.utexas.edu | 
>-----------------------------------------------------------------------------

-- 
|  |   / Holger Veit             | INTERNET: veit@du9ds3.uni-duisburg.de
|__|  /  University of Duisburg  | BITNET: veit%du9ds3.uni-duisburg.de@UNIDO
|  | /   Dept. of Electr. Eng.   | "No, my programs are not BUGGY, these are
|  |/    Inst. f. Dataprocessing |          just unexpected FEATURES"
Re: Rise and shine
#44
Author: Praveen Vishakantaiah
Date: Mon, 31 Aug 1992 14:51
40 lines
2400 bytes
> 
> Holger> I cannot imagine that everyone is interested in design
> Holger> (comp.lang.vhdl, comp.lang.verilog, comp.sys.mentor, comp.lsi*),
> Holger> but nobody in testing of all the stuff produced. 

> 
> Praveen> Well, isn't testing harder than designing ;-). Nobody has proved VLSI 
> Praveen> design to be an NP-complete problem (as far as I know)!
> 

> Hudli> That is not true. There is a mulititude of problems that are NP-complete
> Hudli> in physical design of VLSI, including placement, routing, pin assignment, etc. 

I should have specified it more clearly. I meant logic and functional
design. Yes, placement, routing etc. are NP-complete and are part of the
design process. But then I consider testing also to be an essential part of
VLSI design and the whole purpose of comparing design and test is lost. 

Thanks for pointing it out.

> Praveen> After all, the testing problem was NP-complete, is NP-complete 
> Praveen> and will be NP-complete!! 
               ^^^^^^^^^^^^^^^^^^^^

> Hudli>   ... until the question P = NP ? remains unresolved.

Or until the computer scientists/mathematicians give up:-) 

Praveen Vishakantaiah.

------------------------------------------------------------------------------
-- Microelectronics and Computer Technology Corporation, | Ph : (512)338-3736|
-- 3500 W. Balcones Center Drive                         | e-mail :          |
-- Austin, TX 78759.                                     | praveen@mcc.com   |
------------------------------------------------------------------------------
-- ALSO A HARD WORKING MEMBER OF :-)                     |
-- Computer Engineering Research Center,                 | Ph : (512)471-8013|
-- University of Texas, Austin.             e-mail : praveen@cerc.utexas.edu | 
-----------------------------------------------------------------------------
Re: Rise and shine
#48
Author: Kevin Karplus
Date: Tue, 01 Sep 1992 22:44
6 lines
664 bytes
Logic minimization is also NP-hard.

In fact, damn near any interesting design or testing teachnique is NP-hard (after all, that
is what makes it interesting).

Kevin
Thread Navigation

This is a paginated view of messages in the thread with full content displayed inline.

Messages are displayed in chronological order, with the original post highlighted in green.

Use pagination controls to navigate through all messages in large threads.

Back to All Threads