From: Don Organ
Sent: Tuesday, March 18, 2003 10:32
AM
To: STIL. 4 (E-mail)
Subject: stds-1450.4: Teleconference
minutes 3/18/2003
Ernie
Wahl
Jim
O'Reilly
Don
Organ
Dave
Dowding
Jim
Mosley
Jim sent out use
case #2.
Jim has established
a WebEx session for today's meeting.
------------------------------------------------------------------------------------
Regarding use-case
#2.
Jim O'Reilly: The
main flow goes clock-wise from upper left. A number of the flownodes are
actually flow groups (2nd, 4th, etc). The 2nd (continuity) is shown in the 2nd
diagram on the first page. Also, notice a couple of stand-alone flow-groups on
the left (2nd row). The 3rd is flow-node which contains a test-method - is
a "flownode onto itself" (doesn't represent any subflows). In the GUI tool,
double-clicking on it would bring-up the appropriate tool.
Regarding the
Continuity flow-group - the first node (initial) could have just as easily been
put immediately after the "GO" icon in the top-level flow-group. The decision to
avoid re-initialization on the 2nd-Nth execution is handled in the user code.
Note that the 3rd diagram (the overhead flow-group) is that the INSTALL
flow-group must be run first, followed by the INITIAL, before the other stuff
can be executed. The flowgroups whose names begin with "_" are system provided.
The user provided flow-nodes ("ask_pac", "menu_op", "compute") ask the operator
for some information, and then process it. Down on the bottom row (of Overhead
flow-group) are a bunch of stand-alone flow-nodes / flow-groups. Used for
powering-down, for prober interfacing (planarization and probe height). The
flownodes/flow-groups are called by the work-cell
controller.
Ernie: Why have
stand-alone flownodes, since a flownodes purpose is just to connect in the flow?
Why not just have the test object?
Jim: The answer
probably has to do with the specifics of the underlying system, and the user's
desire to see them in the tool.
lbrd_menu - has some
functions for dealing with load-board calibration. This is intended to be
invoked manually from the flow-tool.
Also note in the
Continuity flow-group is that only one set of 4 flow-nodes is used at a time.
The difference is the underlying instrument to be used (per-pin PMU versus
high-accuracy central PMU). Wanted to allow the test engineer to
chose.
The flow-group
concept is really just associated with the editor/tool. There is no semantic
significance.
The high-voltage
speed test flow-group - a composite - contains a number of flownodes. A number
of functional tests, interspersed with searches (performed with user-code - i.e.
C code).
We can examine some
of the specific source code next week.
---------------------------------------------------------------------------------
Don
Organ
Inovys Corporation
---------------------------------------------------------------------------------