RE: [sv-ac] Call to vote. Due August 30

Hi Scott,

I tried to explain the importance of sampling in checkers in my response to Tom. Please, see there. I don't think that there is a big difference from the sampling point of view whether the assignments to checker variables occur in the NBA or in the Re-NBA, at least for design variables. The main reason why the checker variable assignments are performed in the Re-NBA is to enable expressions of the form sequence.triggered in their RHS.

It would help if you can send an abstracted use case of procedural assertions with modeling code. Note, that current definition in the LRM does not address this issue properly.

Thanks,
Dmitry

From: Little Scott-B11206 [mailto:B11206@freescale.com]
Sent: Monday, August 30, 2010 11:47 PM
To: Korchemny, Dmitry; sv-ac@eda.org
Subject: RE: [sv-ac] Call to vote. Due August 30

John and I discussed this mantis earlier today. I tend to agree with his thoughts although maybe not as strongly. Part of my problem with knowing how to vote on this item is understanding why it is important that the design variables are sampled in a checker. I think that if I could be given some intuition as to why/when this is important it would help me understand the "goodness criteria" for the proposed solution. I do understand that it is related to the fact that checker NBAs occur in re-NBA, but I haven't thought about the problem long enough to understand why this causes problems.

One use case I had kicking around in my head is this: I already have some modeling code and procedural concurrent assertions in a design. I would like to take those and encapsulate them in a checker for reuse. How hard is this to do? What issues might I have with sampling?

 I know these are very basic questions with regard to checkers in general, but it seems like an example along this line might also help others.
---------------------------------------------------------------------
Intel Israel (74) Limited

This e-mail and any attachments may contain confidential material for
the sole use of the intended recipient(s). Any review or distribution
by others is strictly prohibited. If you are not the intended
recipient, please contact the sender and delete all copies.

-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.