[ibis-macro] Re: Task List update
- From: Ambrish Varma <ambrishv@xxxxxxxxxxx>
- To: IBIS-ATM <ibis-macro@xxxxxxxxxxxxx>
- Date: Fri, 15 Apr 2011 05:43:48 -0700
Arpad,
Regarding Row 51, I think we should include AMI_parameters_in as well - those
are optional as well - but not specified anywhere. And we have to clarify what
string needs to be returned when there are no Model_Specific parameters in the
.ami file.
Thanks,
Ambrish.
[cid:image002.gif@01CBFB49.3A2C5780]
Ambrish Varma | Member of Consulting Staff
P: 978.262.6431 www.cadence.com<http://www.cadence.com>
________________________________
From: ibis-macro-bounce@xxxxxxxxxxxxx [mailto:ibis-macro-bounce@xxxxxxxxxxxxx]
On Behalf Of Muranyi, Arpad
Sent: Thursday, April 14, 2011 4:51 PM
To: IBIS-ATM
Subject: [ibis-macro] Task List update
Hello everyone,
I would like to use this email to take another look at our
Task List spreadsheet (attached) so we can concentrate on
how to complete our goals of fixing up the IBIS-AMI
specification for v5.1.
The good news is that there are only few items left on it.
These are as follows:
Row 22 Table syntax (Ambrish)
Row 23 Updating Tables 1-3 in the specification text (Bob)
Row 25 Define relationship between Table and Format (Ambrish)
Row 35 Define how impulse response is generated
Row 37 InOut/Out BIRD draft (Walter/Arpad)
All, except one of these are already being discussed with
drafts flying around. The 2nd and 3rd items on the list above
are easy ones, and basically depend on the outcome of the 1st
item.
The three major topics therefore are the Table syntax, and the
InOut/Out BIRD drafts, plus the definition of the impulse
response generation which we didn't start writing/discussing
yet.
You will see four new items on the bottom of the list in Rows
51-54. I added these as reminders which came out of some of
our discussions. Note that none of them are marked yet whether
we want to address them in 5.1 or later. I would like to discuss
that in the next meeting. Some of these may be simple topics,
yet important corrections/clarifications to the specification.
Row 51 AMI_parameters_out: optional/required Init/GetWave,
NULL pointer if nothing is returned
Row 52 What should the tool do without clock_times?
Row 53 Labels BIRD draft from Walter (from a long time ago)
Row 54 Clarify rules/interpretation on "Corner"
I would like to ask all of you to focus on all of these
remaining items in your thinking and discussions so we could
get to the end of the list soon. My target is to have all of
these topics addressed and submitted in a BIRD format to the
Open Forum by our next Summit in the US in June. I think we
should be able to achieve that.
This also implies that I would like to see a little less traffic
on topics which are enhancements to the specification. Recall,
we made a decision to fix the errors and clarify ambiguous texts
in the specification first before we start working on new
capabilities. I know, we also relaxed this decision and allowed
some discussion on new features, such as converting the Opal
features to IBIS BIRDs, but this is still a lower priority for
our Task Group at this point until we complete our main goals.
I would appreciate it very much if we could all take these
thoughts to our heart and give a final push to achieve our
goals listed in the Task List.
Having said that, I would like to see more activity on the Table
syntax (bob) and the InOut/Out clarifications BIRD drafts on our
email reflector. These are the next two main BIRDs we need to
submit to the Open Forum.
Thanks,
Arpad
====================================================================
Other related posts:
