Attendees:

0000000000000001000010111100000000 Qamar Alam
1111111111111111111010111111101111 Himyanshu Anand
0111111110011111101110100011111111 Kenneth Bakalar
1111101010110110111011000011100011 Prabal Bhattacharya
0000000000000011000010100100001001 Sri Chandra
0111101111111111110110101111101111 Eduard Cerny
1110111000010110101110111110111111 Scott Cranston
0000000000000001000000000000000100 Dave Cronauer
0000000000001100000000011111100111 Dejan Nickovic
1101110111100100000000000000000000 Mike Demler
0000000000000000000000000000000000 Surrendra Dudani
1110000000111111111111001101111111 John Havlicek
1110001100100000000000000000000000 Kevin Jones (RGG Leader)
0000000111111111101110111111111111 Jim Lear
0000000000001110111000000000000000 Top Lertpanyavit
1111110110111111111111111011111111 Scott Little
0000000000000100000000000000000000 Erik Seligman
1010000000000000000000000000000000 David Sharrit
0000000100000000000000000000000000 Murtaza
0000000100000000000101100110000001 Martin O'Leary

---

Decisions:

1. Voting on ASVA requirements complete.

---

Action Items:

---

Details:

HA: Lets go through the various items voted upon and have a discussion on those.

KB: KB1 failed, minimize the changes.

ED: We don't need this. We can always decide whether this is required.

SC: KB3 assumes that SV will be a host language.

KB: The point was just productions.

SC: What is the definition of the host language.

KB: Names, functions.

SC: If KB3 does not restrict to SV then do not object to it.

KB: KB4 is agreed upon.

KB: KB5, All in agreement, ASVA as a superset of SVA and it should mean the same in both SV and ASVA.

HA: Formula should not mean different things in ASVA (SV) and ASVA (VAMS). If they are different that's a recipe of disaster.

KB: KB6,

PB: Do we need a continous time, rather than a digital time?

KB: The notation does not refer to simulator synchronization or interpolation.

PB: The time refers to the time in analog solver?

KB: No, it refers to the system being modeled.

DN: I strongly agree with Ken. We will have assertions without explicit reference to time.

PB: If it is meant that ASVA will be able to refer to time, but not impact the way the digital simulator works. We believe should be refered but that time should be extracted from the analog solver. It is possible from digital solver to force an exact point in analog solver.

KB: In general there is no construct in VAMS that forces a time point.

PB: Are you refering to be able to refer to that time in requirement KB6.

DN: We need to specifically define what we mean by events in the language.

KB: KB7, all agreed.

KB: KB8, all agreed.

KB: KB9, there was discussion about post-processing a wave form as opposed to online (on-the-fly). The expressions would be applicable to both forms of processing.

DN: "As soon as the simulation...". I don't think that timing will be able to always meet this guarantee. The best you can say, is that you answer the question as close to the data point as possible.

KB: You are making the same mistake about interpolation and synchronization.

KB: We are not producing a "post-processing language"

KB: KB10, I agree with SNPS and CDNS as well. Disagree in-principle with FSL. We need to be modest in our proposal and not expansive.

JH: JH1, There has been some reflection on modules and checkers and whether we really need checkers. It may reduce checkers requirements.

KB: Since all the ports the input ports, the expressions will be all in VAMS context. The elaborator will be in the SV.

ED: The body of the checker is expanded in the context. They are not the same as module.

JH: Checkers allow events to be hooked up. Modules do have event ports, they are hooked up by reference.

ED: They cannot be expressions.

JH: JH2, If the SV module/checker is instantiated in VAMS. The main intention was that if we are hooking up SV the port connection actual could be something be a part of SV in the mixed language model. We want to avoid the situation where disassembly/assembly is required.

KB: My suggestion was to use a different model of connection.

ED: Does it not depend on how you deal with two heirarchies. If its unified, then why can you not solve it.

KB: The VAMS parser needs to understand that.

ED: What if the two parsers are closely integrated?

KB: Yes, it could be done. But that's a large job to do that.

JH: It will be more productive to craft some details and re-evaluate it.

KB: If its not a legal VAMS connect expression. You have to tell me how to read it.

ML: There is some disagreement on this. It sounds like we need to get some more technical details and discuss this later.

JH: JH3, no disagreement. This was the motivating capability to bring the checkers.

JH: JH4, Suppose the actual is an integral in SV and that is legal in VAMS. But the formal is not a VAMS type but is legal in SV but they are assignment compatible.

KB: It may be an in-port or out-port. If its an in-port the assignment belongs to SV if its out-port then it belongs to VAMS.

ED: Are we not restricting everything to input only?

KB: I don't think so. But we could. That yes, most of us are thinking about inputs.

JH: Even if there is an ouput, SV will do the assignment compatible. And the values that come out will be interpreted by VAMS.

KB: Is everything packed? Arrays?

JH: The syntax matches for packed arrays with unpacked arrays?

KB: VAMS has no notion of packed/unpacked.

JH: If they are packed they are compatible.

JH: JH6, Vector of wreal will be interesting.

SC: Does this mean we have to add wreal to SV? Is that a bad thing?

JL: Yes, that's a bad thing.

JL: JL1, Wanted an ability to force a time point in VAMS from SV.

ML: Why is it required?

KB: The analog simulator gives the value at the time, how it goes about getting the point is upto the simulator.

JL: The level of accuracy based on the heuristics is never satisfactory. You
always have to force a time point, particularly for a FFT.

-- AnandHimyanshu - 2009-11-03