# Patent

## Title
Image processing architecture

## Abstract

An inspection system that receives image data corresponding to an image and processes the image data to produce a report corresponding to characteristics of the image. Interface cards receive the image data in a flow, where each interface card receives image data corresponding to a different portion of the image. Process nodes connect to the interface cards, and receive the image data from the interface cards. A host computer is connected to the process nodes, and job managers implemented in the host computer manage the flow of image data to and from the process nodes. The job managers remain operable during a crash of one of the process nodes. Process node programs are implemented in the process nodes, and analyze a portion of the image data and produce the report corresponding to the characteristics of the analyzed portion of the image data. At least one process node program is implemented in each process node. The process node programs rapidly analyze the image. The process node programs are isolated from the job managers so that a crash of a process node program does not crash the job manager.

## Background
FIELD
This application claims rights and priority on copending U.S. patent application Ser. No. 10/967,376 filed Oct. 18, 2004, U.S. Pat. No. 8,823,969 issuing Sep. 2, 2014.
This invention relates to the field of integrated circuit fabrication. More particularly, this invention relates to substrate inspection systems. This application relates to the applications listed below, all of which were filed on Oct. 18, 2004:














application Ser.
U.S. Pat.



No.
No.









10/967,388
7,149,642



10/967,397
7,076,390



10/967,419
7,181,368



10/967,542
7,555,409



10/967,375
7,379,847



10/967,838
7,024,339



10/967,500
7,440,640



10/967,376
8,823,969



10/967,832
Abandoned



10/967,420
7,382,940



10/967,418
7,602,958










BACKGROUND
Integrated circuit manufacturers use inspection systems to detect anomalies, such as defects, in substrates. Generally, an inspection system rasters the surface of the substrate with one or more optical sensors, and generates image data based on the images detected by the sensors. This image data is analyzed according to one or more of a variety of different algorithms to determine where defects might exist on the substrate. Integrated circuit manufacturers demand that such inspection systems meet several criteria. Among these criteria is that the inspection system must be extremely accurate, fast, and reliable. Further, such inspection systems should preferably be reasonably priced and relatively flexible.
Prior art inspection systems have implemented one or both of pipelined systems or computers that are networked in a switched fabric topology, which use highly customized hardware. Customized hardware has several disadvantages as compared to commercially available hardware, including higher nonrecurring engineering costs for the developer, lower reliability, longer development times, and more inflexibility in changing algorithms. Switched fabric systems have additional disadvantages, including high cost, lack of standards between manufacturers, and development lag in the components, such as the level of microprocessor that is built into such systems.
Commercial hardware, by contrast, tends to be more reliable, more versatile, and less expensive. For example, large computer manufacturers devote a tremendous amount of engineering effort to ensure that the latest technologies are implemented in their products, and that those products are brought to market as soon as possible. This large engineering effort is then factored into the price of the many, many units that they anticipate selling. Thus, the large development costs are spread quite thin as to each unit that is purchased. The development costs for customized hardware, on the other hand, must be borne on a relatively very small number of units.
Further, once a commercial product is developed, the engineering support team continually updates, improves, and bug fixes that product. Again, these costs are distributed over all of the many units that are sold by a large manufacturer. Again, the expenses of such efforts for customized hardware must be borne by a very few units. Often, the number of units makes such levels of support for customized hardware financially unreasonable to offer or to buy. Thus, prior art inspection systems, while perhaps having acceptable speed and accuracy, have been woefully lacking in the categories of flexibility, reliability, and cost.
What is needed, therefore, is a system that overcomes problems such as those described above, at least in part.
SUMMARY
The above and other needs are met by an inspection system that receives image data corresponding to an image and processes the image data to produce a report corresponding to characteristics of the image. Interface cards receive the image data in a flow, where each interface card receives image data corresponding to a different portion of the image. Process nodes connect to the interface cards, and receive the image data from the interface cards. A host computer is connected to the process nodes, and job managers implemented in the host computer manage the flow of image data to and from the process nodes. The job managers remain operable during a crash of one of the process nodes. Process node programs are implemented in the process nodes, and analyze a portion of the image data and produce the report corresponding to the characteristics of the analyzed portion of the image data. At least one process node program is implemented in each process node. The process node programs rapidly analyze the image. The process node programs are isolated from the job managers so that a crash of a process node program does not crash the job manager.
In various embodiments, the job managers are written in Java and the process node programs are written in C. In one embodiment, a shared memory is shared by the job managers and the process node programs, which transmit data between one another by reading and writing data into the shared memory. In one embodiment, the shared memory is sufficiently large to receive the data produced by both the job manager and the process node program when they both produce a maximum possible amount of data. In one embodiment, each job manager is assigned to a set of at least one process node programs, and manages the flow of data to and from the assigned set of process node programs. In one embodiment, each process node includes at least two processors for simultaneously executing two process node programs to analyze the portions of the image data. In one embodiment, the job manager loads a job queue memory with job data before the job data is needed by the process node program, and the process node program loads the report into a results queue memory before the report is needed by the job manager. In this manner, no delay is caused by the process node program waiting for job data and no delay is caused by the process node program waiting for memory space in which to write the report.



BRIEF DESCRIPTION OF THE DRAWINGS
Further advantages of the invention are apparent by reference to the detailed description when considered in conjunction with the figures, which are not to scale so as to more clearly show the details, wherein like reference numbers indicate like elements throughout the several views, and wherein:
FIG. 1 is a functional block diagram of an inspection system according to one embodiment of the invention.
FIG. 2 is a functional block diagram of an interface of a process node of the inspection system of FIG. 1, according to one embodiment of the invention.
FIG. 3 is a functional block diagram of the communication between a job manager and a process node in the inspection system of FIG. 1, according to one embodiment of the invention.



DETAILED DESCRIPTION
One advantage of the inspection system 10 described herein is that the components are readily commercially available and do not require customized design and manufacture, except perhaps an interface 22, which is relatively easily produced. This has a number of advantages. First, the reliability of the inspection system 10 is generally increased by using components for which a large engineering effort has been invested, for which upgrades and fixes are continually produced, and which have a good track record in the marketplace. In addition, with large numbers of a single component being produced by the original manufacturer, problems are generally discovered faster and fixed sooner.
Further, commercially available computers, such as the process nodes 20 and other components as described below, can run many different kinds of algorithms, whereas customized hardware, and more especially the customized and optimized hardware that is so prevalent in prior art inspection systems, tends to be extremely limited in what it can do, because the cost of adding additional functionality to such customized hardware is extremely high.
With reference now to FIG. 1, there is depicted a functional block diagram of an inspection system 10 according to one embodiment of the present invention. A general description of the inspection system 10 is first presented. Following the general description, more detailed descriptions of various aspects of the inspection system 10 are presented.
General Description
In one embodiment, the inspection system 10 is used for analyzing image data, such as that gathered from optical sensors. For example, both bright field inspection systems and dark field inspection systems use optical sensors. In various embodiments, the inspection system 10 includes a sensor array 26, which is operable for optically gathering the image data. In one embodiment, the sensor array 26 as depicted in simplified form in FIG. 1 includes functions such as those provided by a common run time alignment processor, which sends the image data out on different output streams 58.
The sensor array 26 includes sensors and handling systems for optically inspecting substrates, such as the substrates that are used in integrated circuit fabrication processes, such as semiconductor wafers, masks, reticles, and other such substrates. Thus, the inspection system 10 is particularly well adapted to the integrated circuit fabrication industry, which relies greatly upon the optical inspection of such substrates.
As the term is used herein, “integrated circuit” includes devices such as those formed on monolithic semiconducting substrates, such as those formed of group IV materials like silicon or germanium, or group III-V compounds like gallium arsenide, or mixtures of such materials. The term includes all types of devices formed, such as memory and logic, and all designs of such devices, such as MOS and bipolar. The term also comprehends applications such as flat panel displays, solar cells, and charge coupled devices.
In one embodiment, the sensors in the sensor array 26 are time domain and integration sensors. However, in other embodiments, other sensor types may also be used. In one embodiment, the substrate handling systems in the sensor array 26 are adapted to automatically unload the substrate from an input staging system, such as from a cassette, move the substrate under the sensors, such as by moving one or both of the sensors and the substrate relative to one another, and then load the substrate back into an output staging system, such as a cassette.
Thus, in some embodiments, the inspection system 10 is adapted to automatically inspect the substrate and produce image data. However, in alternate embodiments the inspection system 10 can accept image data that has been stored for later analysis, either in addition to or in place of image data that is being generated in real time.
Many different factors of the inspection 10 combine to produce a very large quantity of image data at a very fast rate. Because of the very small size of modern integrated circuits, in one embodiment, the imaging of the substrates by the inspection system 10 is performed at a very high magnification. In one embodiment, the inspection system 10 is adapted to detect anomalies on the substrate, which may be defects such as scratches, extraneous particles, voids, short circuits, open circuits, and so forth. To support the optical inspection of such very small features, in one embodiment, the pixel size for the sensors is about one tenth of a micron. This small pixel size is one of the factors in the large amount of image data that is produced, and the high rate at which it is produced.
In addition, in one embodiment, the inspection system 10 is adapted to handle relatively large substrates having a diameter of about a foot or more. Further, the substrate handling system of the sensor array 26 moves the substrate as rapidly as can be supported by the rest of the inspection system 10, so that the inspection system 10 can process as many substrates within a given length of time as possible. As introduced above, all of this combines to create a very large amount of image data that is delivered at a very fast rate.
For example, the inspection system 10 generates more than three billion pixels per second, with each pixel having eight grayscale bits. This produces an image data stream of over three gigabytes per second. Thus, the embodiments of the present invention as described in greater detail below are adapted to process large amounts of data through a variety of different means.
The inspection system 10 is under the control of a control computer 12, which provides top level control for the inspection system 10, including the storage, selection, and delivery of the recipes by which the inspection system 10 is controlled, interfacing with system operators, and receipt, storage, and delivery of information from and to other computer systems on a network.
However, because the inspection system 10 handles large amounts of data at high rates as described above, in one embodiment, there is at least one job manager 14 that performs most if not all of the detailed control aspects for the various components of the inspection system 10. The number of job managers 14 that are implemented varies according to various criteria, such as the type of inspection that is performed by the inspection system 10—be it bright field or dark field, for example.
In one embodiment, the job manager 14 is a logical structure, such as a set of Java routines that run on a host computer. In one embodiment, the job manager 14 is hosted on a separate computer that is used substantially only for that function. Such a configuration tends to isolate the job managers 14 from other computational demands that may be hosted by a commonly used computer. However, in alternate embodiments the job manager 14 is hosted on a common computing platform, such as on the control computer 12.
The job manager 14, among other things, directs the transmission of image data to the process nodes 20 for processing. Stated in other words, the job manager 14 does not actually transfer the image data to the process nodes 20, but directs other components of the inspection system 10 to do, as described in more detail below. The job manager 14 also provides instructions for the inspection of the image data to the process nodes 20. In one embodiment, the instructions define inspection parameters such as pixel size, optics mode, number of gray scales, inspection swath length, and so forth.
The control computer 12, job manager 14, and sensor array 26 are all in communication with one another through a network, such as, in one embodiment, a relatively high speed network such as gigabit Ethernet. It is appreciated that other protocols besides Ethernet could also be used, and speeds other than gigabit could also be used. However, gigabit Ethernet is used in some embodiments for this portion of the communication between the components, because it has a relatively high bandwidth that generally supports the design goals of high data throughput in the inspection system 10.
In various embodiments, the network connections 44, 46, and 48 are made through one or more network switches. Alternately, other devices such as routers or hubs could be used for this purpose. In one embodiment, all of these network connections are made through the same switch, such as switch 16 or switch 18. However, in one embodiment, these network connections are locally made through a first switch 16, so that control information that is delivered between the job manager 14, control computer 12, and sensor array 26 does not steal bandwidth from other network connections, which are described in more detail below.
In such a configuration, the first switch 16 is connected to a second switch 18, such as via a network connection 54. Other network connections are also made to the second switch 18, as described in more detail below. In one embodiment, the job manager 14 is connected to both the first switch 16, so as to communicate lower priority instructions to the elements of the inspection system 10 as described above, and also to the second switch 18, so as to communicate higher priority instructions to other elements of the inspection system 10, as describe in more detail below.
The analysis of the image data is accomplished by a node array 60 of the inspection system 10. The node array 60 in one embodiment is an array of process nodes 20, which can be thought of as being disposed in rows 28, 30, 32, and 34 and columns 36, 38, 40, and 42. The number of rows and column as depicted in the node array 60 of FIG. 1 is by way of example only, and is determined by factors that are described in more detail below. In one embodiment, the process nodes 20 receive image data on lines 58 of a high speed network, such as a fiber optic network. Although a different protocol may be used for the high speed network 58, such as gigabit Ethernet, Firewire, high speed USB, or fast wide ultra SCSI, fiber optic tends to have greater bandwidth when used in combination with the other components of the inspection system 10 than these other options.
The portion of the image data that is delivered on the network 58 to a single column of process nodes 36, 38, 40, or 42 comes from a given portion of the sensors in the sensor array 26. For example, the first column 36 may receive image data from a first quarter portion of a time delay and integration sensor, the second column 38 may receive image data from a second quarter portion of the sensor, the third column 40 from a third quarter portion, and the fourth column 42 from a fourth quarter portion. The process nodes 20 in a given column are preferable connected to the network 58 in a daisy chain topology, as described in more detail hereafter.
In one embodiment, each of the process nodes 20 is a dual processor G5 PowerMac computer running OS X, as manufactured by Apple Computer, Inc. of Cupertino Calif., operating at a clock speed of at least about two gigahertz. In one embodiment, the inspection system 10 includes at least twelve of the process nodes 20, which are most disposed in four logical columns of three rows each. However, the same computational capacity might also be provided in other embodiments with a total of eight different three gigahertz, dual processor computers, which are disposed in four columns of two rows each. It is appreciated that the selection, number, and arrangement of the process nodes 20 in the inspection system 10 is adjustable as necessary to handle the desired throughput of image data.
It is appreciated that other computers besides PowerMac computers may be used in the inspection system 10. For example, Opteron based computers, as manufactured by Advanced Micro Devices, Inc. of Sunnyvale Calif., having similar speeds and memory capacity could also be used with the Linux operating system. However, because of the interdependencies of the computations being performed by each of the process nodes 20, all of the process nodes 20 in a given inspection system 10 are of the same type and configuration, in one embodiment. In one embodiment, each of the process nodes 20 includes at least about three gigabytes of memory. The computer hosting the job managers 14 is of a similar class, with some differences. Speed is also important for the job manager 14, but data buffering is less so and storage space is more so than for the process nodes 20. Thus, while the process nodes 20 have lots of memory and no hard drive, the job manager 14 has less memory and at least one hard drive.
The process nodes 20 receive the image data through an interface 22 that is installed in each process node 20, which interface 22 is adapted to receive the image data on the high speed network 58, and provide it to the process node 20 at a speed that is at least as fast as the speed at which a given process node 20 can process the image data. In one embodiment, this speed is no less than about eight hundred megabits per second. However, in embodiments where a greater number of process nodes 20 can be used, each process node 20 does not need to accept the image data at such a high rate of speed. However, by maximizing the image data delivery rate to the process nodes 20, fewer process nodes 20 are required, and the overall cost of the inspection system 10 is generally reduced. In one embodiment, the interface 22 performs some amount of processing on the image data that it receives, such as verifying checksums, stripping off packet headers, and re-ordering the bits to more fully optimize the image data stream for processing by the process node 20.
The process nodes 20 analyze the image data that is sent to them, and generate reports on the image data that they have analyzed. The reports from the process nodes 20 are delivered to the job manager 14. In one embodiment, the process nodes 20 communicate with the job manager, and other elements of the inspection system 10 as may be desired, through the network connections 56. In one embodiment, the network 56 is again a gigabit Ethernet network, and the connections 56 are made to the second switch 18. However, in other embodiments, other protocols and topologies can also be used, as described above.
The processing of the image data by the process nodes 20 is accomplished with relatively high speed routines, such as those written in a programming language such as C. Communication between the process nodes 20 and other components, such as the job manager 14, is accomplished with a low overhead routine, such as those written in a programming language such as Java, and in one embodiment, using the remote method invocation protocol.
Because the process nodes 20 receive image data at an extremely high rate, they tend to generate the reports at a high rate. However, because the reports do not contain as much data as the image data, a relatively slower network can be used to communicate the reports to the job manager 14 than is used to communicate the image data to the process nodes 20. Therefore, in one embodiment, high speed fiber 58 is used for the image data, and relatively slower gigabit Ethernet 56 is used for reporting. It is appreciated that the network 56 may run at a slower speed than gigabit, such as one or more of the automatic fallback rates of one hundred megabits per second and ten megabits per second, as supported by the gigabit Ethernet protocol.
In one embodiment, the network 56 also carries instructions from the job manager 14 to the process nodes 20. These instructions include information such as set up data and processing instructions that are to be performed on the image data. Because the process nodes 20 are operating under a relatively heavy computational load, and thus may require such instructions at a fairly rapid rate, and also because the reports delivered by the process nodes 20 are sent at a relatively high rate, in one embodiment the job manager 14 has a second network connection 52 to the second switch 18, through which such higher priority communication is accomplished.
Various aspects of the inspection system 10 are now presented in greater detail in the following sections.
Image Data Interface
As introduced above, in one embodiment, the image data delivered to the process nodes 20 is divided into four streams, with each stream representing a one-quarter portion of an inspection swath on the substrate that is about five hundred and twelve pixels wide. One of each of these four image data streams is delivered to one of each of the four columns 36, 38, 40, and 42 of the process nodes 20. As mentioned above, the number of columns and the segmentation of the image data stream can be set at other values besides four. In one embodiment, the fiber optic network 58 delivers the image data at a rate of about eight hundred megabytes per second. In one embodiment, the fiber network 58 implements a serial, full duplex data transfer architecture.
In the embodiment of FIG. 1, the image data is received by the interface 22, which is installed in each process node 20. In one embodiment, the interfaces 22 are input data adapter cards having serial fiber optic inputs, such as transceivers 100, which convert the fiber optic image data received on the fiber network 58 into electrical image data, and deliver the image data to a pre processor, such as a field programmable gate array 102, all as depicted in FIG. 2. The transceivers 100 support a bandwidth of about two and a half gigabits per second. In one embodiment, each of the interfaces 22 has four such transceivers 100, with each of the transceivers 100 in each process node 20 of a given column 36, 38, 40, and 42 independently daisy chained to the corresponding transceivers 100 in each of the other process nodes 20 within the column 36, 38, 40, or 42 of the node array 60. Thus, the network 58 provides four connections to each column of process nodes 20 in the node array 60. Three of these four connections are depicted as stubs in FIG. 1, so as to not unduly burden the figure with detail.
In some embodiments, the gate array 102 provides some image data processing functions, such as segmented auto thresholding histogramming. The gate array 102 is additionally adapted to handle input tracking, input processing, PCI-X interface, and memory interface processes. The interface 22 includes at least about one to two gigabytes of buffer memory 104, which is used to buffer the image data as necessary prior to transferring it to the memory in the process node 22. If the process node 20 can keep up with the flow of image data received on the network 58, then no buffering is needed. However, if the process node 20 cannot sustain that rate of data flow, such as for intermittent periods of time, then the backlog of image data is buffered in the memory 104. The interface 22 communicates with the process node 20 through a PCI-X slot 106, although interface protocols with similar bandwidth capabilities of at least about eight hundred megabits per second could also be used.
Memory Load Balancing
As described above, the process nodes 20 are adapted to store a portion of the image data that they receive, such as within the buffer 104 of the interface 22. Thus, the process nodes 20 have a sufficient amount of memory to continue receiving image data even if the rate of analysis of the image data within the process node 20 falls below the rate of data acquisition by the process node 20. In this manner, the inspection system 10 can readily handle a peak load of image data without slowing down image data acquisition and analysis.
For example, at a standard load of delivery of the image data, a given process node 20 may be able to process the image data at a faster rater than it is delivered. In such a situation, the buffer memory 104 is generally not used to buffer any significant amount of the image data, because there is no need to relieve the computational load on the process node 20. However, for various reasons, such as the scanning of particularly complex portion of the substrate that is being inspected, a relatively large amount of image data may be delivered within a brief period of time, or the process node 20 may take a longer period of time to process the image data that it has already received.
If the additional image data load extends beyond that which the process node 20 is capable of processing on the fly, the additional image data load is buffered, such as in the memory 104 in a first in, first out process. Then, when the image data load ebbs again, the process node 20 receives the buffered image data, and starts receiving the image data without it building up a load within the buffer 104. Such control of the delivery of the image data is, in one embodiment, under the control of the gate array 102, as explained in more detail elsewhere herein.
With the buffer 104 configuration as described above, the software requirement for the inspection system 10 is significantly less than that for prior art inspection systems. For example, the job manager 14 in one embodiment does not provide dynamic load balancing between the process nodes 20, because the process nodes 20 are assigned to a segmented stream of the image data from the sensor array 26, and have sufficient memory and speed for handling the peak loads of the image data stream. Thus, no complex and expensive switched fabric topology is needed, as is commonly employed in prior art systems. Further, the number of process nodes 20 used in the node array 60 can be kept at a number that is less than that which would otherwise be required to handle a peak load of image data, resulting in a lower overall cost for the inspection system 10, without compromising the throughput of the inspection system 10.
Status Polling
As introduced above, the image data is moved from the interface 22 to the process node 20 via direct memory access. As the process node 20 is able to accommodate more image data, the interface 22 delivers the image data through the PCI-X interface 106, and when the process node 20 cannot handle more image data, the interface 22 buffers the image data in the buffer memory 104.
In prior art designs, an interrupt is used as a signal when more data can be delivered via a direct memory access process. However, interrupts are typically handled by the central processing unit of the host, which in this case is the process node 20. As described at length above, the process node 20 is under a severe computational load, and various aspects of the inspection system 10 are designed to keep the process node 20 processing image data as fast as it can. Thus, any additional computation load on the process node 20 is unwelcome.
Therefore, the inspection system 10 according to some embodiments of the invention does not use interrupts to signal when additional image data can be delivered via direct memory access to the process node 20. Rather, a polling method is used. In one embodiment, the gate array 102 polls a register or some other memory location to determine the status of the register. When the register is in a first status, then the process node 20 will accept more image data via direct memory access, and when the register is in a second status, then the process node 20 will not accept more image data via direct memory access. In this manner, the image data is delivered in a smooth manner via direct memory access, without losing the processing cycles on the process node 20 that would otherwise be required to handle an interrupt.
Daisy Chain Topology
The benefits of disposing the process nodes 20 into columns 36, 38, 40, and 42 have been generally described above. Some of the benefits of disposing the process nodes 20 into different rows 34, 32, 30, and 28 are now described. In addition to load leveling the computational demands of the inspection system 10 by increasing the memory capacity of the process nodes 20 and providing buffer memory 104 in the interface 22, the architecture of the node array 60 also both increases the capacity and levels the computational load of the inspection system 10.
For example, with reference to FIG. 1, first swaths or portions of the image data stream are sent out on the network 58. Because the four process nodes 20 in row 34 of the node array 60 are not working on anything else at the time that the first portion of the image data is delivered, they accept the first portion of the image data, and the process nodes 20 in row 34 begin processing the first portions of the image data. While the process nodes 20 in row 34 are still processing the first portions of the image data, second portions of the image data stream are sent out on the network 58. However, this time the four process nodes 20 in row 34 of the node array 60 are busy processing the first portion of the image data stream, and thus they do not accept the second portion of the data stream.
Instead, the transceivers 100 of the interfaces 22 reflect the second portions of the image data stream back out onto the network 58, to be received by the four process nodes 20 in row 32 of the node array 60. Because the four process nodes 20 in row 32 of the node array 60 are not doing anything else at the time, they accept the second portions of the image data, and the process nodes 20 in row 32 begin processing the second portions of the image data. By the time third portions of the image data stream are provided by the sensor array 26 on the network 58, and one or more of various different options can be implemented.
In a first example, the process nodes 20 in row 34 of the node array 60 have completed processing the first portions of the image data stream, and thus they can receive and process the third portions of the image data stream. If the process nodes 20 in row 34 of the node array 60 have not as yet completed processing the first portions of the image data stream, then the third portions of the image data stream can optionally still be sent to the process nodes 20 in row 34, to be buffered in memory, such as the memory 104, before being processed by the process nodes 20, because each of the process nodes 20 has enough memory to hold at least two such portions of image data. In this manner, as long as no one of the process nodes 20 within a row of the node array 60 does not get too far behind in computation, the inspection system 10 will not stall.
Alternately, additional rows 30 and 28 of process nodes 20 may be implemented in the node array 60. In this manner, either the memory requirements for each of the process nodes 20 may be reduced, or the speed at which image data is delivered to the inspection system 10 may be increased, or additional processing of each portion of the image data may be accomplished by each process node 20. In one embodiment, the control of such decisions is specified at the job manager 14, and implemented within the gate array 102, which determines whether it will or will not accept the image data.
This bumping of the successive portions of the image data is enabled, at least in part, by the daisy chain topology of the network 58. In one embodiment, under the control of the gate array 102, portions of the image data are bumped to rows of process nodes 20 that are deeper within the node 60, when the shallower process nodes 20 are busy. In one embodiment, if one of the process nodes 20 within a row of the node array 60 is not able to accept an image data portion, then none of the process nodes 20 within the row of the node array 60 accepts the image data portion, and the image data portion is bumped via the network 58 to the next deeper row of process nodes 20 within the node array 60. In alternate embodiments, the different columns of process nodes 20 within a given row are more independent, and bumping occurs within a given column from one row to another based only upon the load of the shallower process nodes 20 within that column.
In alternate embodiments, this daisy chain topology as implemented in the fiber network 58 can be implemented in other network protocols, such as gigabit Ethernet. However, fiber network 58 is used in one embodiment because of the generally greater bandwidth which it affords.
The number of rows and columns in the node array 60 and the processing capabilities of the process nodes 20 are all interrelated. In one embodiment, it is preferred to send image data to the node array 60 on the network 58 as fast as it can be generated by the sensor array 26. Thus, it would also be preferred in some embodiments to process the image data with the node array 60 as fast as it can be sent by the network 58. By increasing the number of column within the node array 60 and dividing the swath of image data into a number of different segments that corresponds to that number of columns, the computational requirements of each process node 20 in the node array 60 generally decreases for a given level of image data delivery. By increasing the number of rows within the node array 60, the computational requirements of each process node 20 in the node array 60 further generally decreases for a given level of image data delivery.
By selecting process nodes 20 with as high a computational capacity as is practical, the number of rows and columns in the node array 60 can generally be reduced for a given level of image data delivery. Thus, process nodes 60 with relatively high computational capacities are selected. The number of rows and columns in the node array 60 is then set so that the node array 60 can process an amount of image data that represents the faster average amount that can be delivered by the sensor array 26 on the network 58. Memory is added to either the process node 20 or the interface 22 as described above to handle any additional, intermittent computational load that might be required, as described above. In this manner, the inspection system 10 does not specify either too few or too many process nodes 20.
Full Swath Analysis
In the embodiments described above, the image data for a single swath has been segmented as delivered from the sensor array 26, such as into four quarter portions. It is appreciated that other segmentations could also be used. However, in some embodiments, no segmentation of the image data is desirable. Such an embodiment would, for example, allow for a greater portion of the imaged substrate to be used for detection of anomalies, such as defects. Such segmentation can be specified, for example, by the job manager 14, and implemented in one or more of the various components that are generally referred to as the sensor array 26 herein.
As described elsewhere above, the process nodes 20 in one embodiment contain sufficient memory, either within themselves or within the buffer memory 104, to enable continued acquisition of image data even if the rate of analysis of the image data in the process node 20 falls behind the rate of image data acquisition. The process nodes 20 may also contain sufficient memory so that an entire swath width of the image data may be sent to a single column 36, 38, 40, or 42 of process nodes 20, without segmenting the image data.
The architecture of the inspection system 10 would not need to change from that as depicted in FIG. 1. Rather, the job manager 14 could instruct the appropriate elements of the sensor array 26 to provide the entire swath of the image data along a single output of network 58 to a single column of the node array 60. Alternately, the architecture of the node array 60 could be changed to a single column. However, accomplishing the image data delivery as described in this section by using instructions to the sensor array 26 rather than altering the architecture of the node array 60 provides for a much more adaptable inspection system 10.
To implement such an embodiment, each process node 20 would have about six gigabytes of memory, which could either be resident in the process node 20 itself, or within the buffer memory 104.
Mirror Node Verification
One goal of inspection system 10 is to maintain consistent and uniform processing by each of the process nodes 20. Each process node 20 in the node array 60 produces a report that is substantially similar to the report that would be generated by any other process node 20 in the node array 60. Ensuring that this condition is met is of particular concern when new hardware or software is introduced into the inspection system 10.
In one embodiment, a new process node 20 is configured to mirror one of the existing process nodes 20 within the node array 60. The job manager 14 is configured to send instructions to both the existing process node 20 and the mirror node. In one embodiment, the instructions are redundant in the case of the mirror node, so that the results from the mirror node can be compared to the results from the existing process node 20. The mirror node is programmed by the job manager 14 to produce the output that the process node 20 produces, including information such as defect results, images, histograms, and projections.
The mirror node can exist in various logical positions within the inspection system 10. for example, the mirror node may be disposed within the node array 60, such as on one of the deeper rows 28 or 30, so that it resides within a row that can be turned off in regard to normal image data processing, without substantially effecting the throughput of the inspection system 10. Alternately, the mirror node can be on the network 56, such as through the switch 18, but be logically outside of the node array 60, in that it does not reduce the computational ability of the node array 60 in any manner.
In yet another embodiment, the mirror node can be placed anywhere within the node array 60, but the job manager 14 instructs the inspection system 10 to always have the process node 20 that is one row deeper within the same column of the node array 60 to also process the image data that is received by the mirror node. This is accomplished such as by the interface 22 reflecting all of the image data that is received by the mirror node back out along the network 58 to be received by the next deeper process node 20, which is connected to the network 58 in the daisy chain topology, as described in more detail elsewhere herein.
The job manager 14 verifies whether the mirror node and the process node 20 produce results that are in agreement within an allowable tolerance. If they are not, then there is a problem with one or more of the mirror node and the process node 20, and the job manager 14 reports this condition. The job manager 14 is programmed to not reject an inspected substrate based upon either a bad report from the mirror node or a discrepancy between the mirror node and the process node 20.
If a discrepancy of too great a size exists between the mirror node and the process node 20, it may be an indication that the mirror node is unacceptable, or alternately, it may be an indication that the process node 20 is faltering. In this manner, the mirror node can be used as a check of the various process nodes 20 within the node array 60. Further yet, a discrepancy may be an indication that both the mirror node and the process node 20 are faulty.
In some embodiments, the mirror node is a candidate computer that is of unknown performance, and the purpose of connecting the mirror node to the inspection system 10 is to determine whether the mirror node is acceptable. In alternate embodiments the mirror node is known to be acceptable, and the purpose of connecting the mirror node to the inspection system 10 is to verify that the process node 20, which may be of unknown performance, is equivalent to the mirror node. In these embodiments the mirror node is a known good computer.
If the mirror node is a candidate computer and the report from the mirror node is unacceptably different from the report provided by the process node 20, then the mirror node is judged to not be acceptable. If the mirror node is a known good computer and the report from the mirror node is unacceptably different from the report provided by the process node 20, then that process node is judged to not be acceptable, and the job manager 14 identifies it as a failed process node 20. Under such circumstances, the reports from the mirror node may be substituted for the reports from the failed process node 20, until the failed process node 20 can be replaced.
In some embodiments, the job manager 14 cyclically transmits the common portion of the image data to the mirror node and the process node 20 for which the reports are being compared. In some embodiments involving cyclical transmission, a regression analysis is performed on the test results to determine differences among some or all of the process nodes 20, and between the process node 20 and the mirror node.
Image Processing Architecture
In one embodiment, each process node 20 implements a proxy bridge. The proxy bridge performs remote calls via the remote messaging interface protocol. Not having to explicitly handle the details of remote procedure calls tends to simplify implementation of the process node 20, and offload additional computational loads.
One embodiment of the software structure of each process node 20 is depicted in FIG. 3. Each process node 20 includes a first programming environment 210 in which the housekeeping work is handled, as described elsewhere herein, such as the implementation of the proxy bridge. In one embodiment, the first programming environment 210 is relatively stable, in comparison to a second programming environment 226 and 228 that is described below. In most programming environments, the desire for stability tends to come at the expense of speed. Although a relatively slow speed is not a design goal for the first programming environment 210, an extreme amount of speed is not particularly needed for the first programming environment 210. Therefore, the trade off of some speed for stability is preferred in some embodiments, for the first programming environment 210.
It is further desired that the first programming environment 210 be processor and operating system independent. With these criteria, one option for the first programming environment 210 is Java. It is appreciated that other programming environments other than Java could also meet the design criteria as both specified above and generally elsewhere herein.
In one embodiment, routines within the first programming environment 210 launch routines within a second programming environment 226 and 228 that is relatively fast, in comparison to the first programming environment 210 that is described above. As introduced above, in most programming environments, the desire for speed tends to come at the expense of stability. Although relative instability is not a design goal for the second programming environment 226 and 228, an extreme amount of stability is not particularly needed for the second programming environment 226 and 228, because of the isolation of those environments. Therefore, the trade off of some stability for speed is preferred in some embodiments for the second programming environment 226 and 228.
It is further desired that the second programming environment 226 and 228 be processor dependent, which tends to optimize the second programming environment 226 and 228 even further for speed. With these criteria, one option for the second programming environment 226 and 228 is some variant of C. It is appreciated that programming environments other than C could also meet the design criteria as both specified above and generally elsewhere herein.
In alternate embodiments, both the first programming environment 210 and the second programming environment 226 and 228 are implemented in the same programming environment, which in one embodiment is both sufficiently stable and sufficiently fast to perform the function in the manner described herein. However, in such a case the operating system environment provides sufficient isolation between the routines of the first programming environment 210 and the second programming environment 226 and 228 that the failure of any one does not effect the efficient operation of the others.
In addition to the housekeeping chores, two additional routines are launched within the first programming environment 210, which are job dispatch threads 218 and 220. Two job dispatch threads are launched because the process nodes 20 are dual processor machines. If additional processors are available within the process nodes 20, then additional job dispatch threads 218 and 220 are implemented. As depicted in FIG. 3, routines within the first programming environment 210 also direct the driver 230 for the interface card 22 to appropriately provide the image data to the threads 230 and 232, as described elsewhere herein.
The job dispatch threads 218 and 220 communicate with the job manager 14 through a shared memory 212, which both the job manager 14 and the job dispatch threads 218 and 220 can both read and write, as described in more detail elsewhere herein. In one embodiment, the shared memory 212 includes both a job queue 214 and a report queue 216. The job queue 214 primarily receives job control information from the job manager 14, which directs the operation of the process node 20. The job dispatch thread 218 and 220 read the job queue 214 from the shared memory 212, so as to understand what the process node 20 is supposed to do. The report queue 216 primarily receives reports from the job dispatch threads 218 and 220, which informs the job manager 14 of the results of the processing accomplished by the process node 20. The job manager 14 reads the report queue 216 from the shared memory 212.
As introduced above, in one embodiment, the second programming environment 226 and 228 implements the routines 230 and 232 that are used to analyze the image data. Because the process nodes 20 have dual processors, two such threads 230 and 232 are implemented in each process node 20. Job data, or in other words instructions from the job manager 14 as to how to process the image data, is delivered to the threads 230 and 232 within the second programming environment 226 and 228 via shared memories 222 and 224, respectively. In one embodiment, one such shared memory 222 or 224 is provide for each thread that is implemented in a processor within the process node 20. The shared memories 222 and 224 receive job instructions from the job dispatch threads 218 and 220, which are intended for the evaluation threads 230 and 232, respectively. The shared memories 222 and 224 also receive reports from the evaluation thread 230 and 232, respectively, that are intended for the job dispatch threads 218 and 220, respectively, and ultimately for the job manager 14.
The infrastructure 210 and the evaluation threads 230 and 232 are separated so to enhance both system reliability of the process node 20, and, because the evaluation threads 230 and 232 have not been explicitly designed to be re-entrant, running two copies of the evaluation threads 230 and 232 within the same address space would fail.
In one embodiment, the evaluation threads 230 and 232 never need to request more image data from the interface 22, or more instructions from the job manager 14, or wait for space within a memory to open up in which to write the reports. Instead, the job manager 14 keeps sufficient amounts of image data coming through the interface card 22, such that the evaluation threads 230 and 232 substantially never run out of image data to process, as describe elsewhere herein in more detail, until a job is completely finished. Similarly, the evaluation threads in one embodiment do not need to wait for the shared memories 222 and 224 to clear out so that reports can be delivered.
In one embodiment, the shared memories 222 and 224 are large enough to handle both the largest amount of job data and the largest amount of report data that could be generated. In one embodiment, about ninety megabytes of shared memory is sufficient for each shared memory 222 and 224. The shared memories 222 and 224 are divided in one embodiment into three areas, such as about ten megabytes for job data, about eighty megabytes for reports, although it is probably rare that eighty megabytes of reports come back from a single job, and about one megabyte for logging data, if logging is enabled.
To achieve high throughput, careful attention could be paid to the way in which the elements as described above interact. The following general principles can be used to keep the inspection system 10 running efficiently. First, the housekeeping is performed between jobs to reduce the performance degradation that arises from context switching, and to avoid disturbing the caches when they are in use by the evaluation threads 230 and 232. Housekeeping can alternately be performed between swaths, to queue up the jobs and return the reports. Latency can be masked by getting job data to the process nodes 20 before it is needed, and memory can be used to implement deep queues, which enable data send and receive operations to be scheduled between swaths.
The job-to-job flow within a swath is the first dynamic view to consider. Because there are two processors per process node 20, there are two independent threads 230 and 232 running at any one time. Each thread 230 and 232 can be viewed in isolation as depicted in FIG. 3.
The inter-job housekeeping may require about four hundredths of a millisecond per job, with a typical job taking about twenty milliseconds. Thus, the inter-job housekeeping adds about two tenths of a percent in overhead. Almost all of this overhead is needed because of the task switches that both increase reliability and address non-reentrancy.
Some housekeeping tasks tend to take more than microseconds, and are accomplished either between swaths, or at the beginning of a swath when the entire length of the swath is then available to catch up. The swath-to-swath flow looks similar to the job-to-job flow, but there is only one thread to this flow, rather than one thread per processor. The inter-swath housekeeping tasks include items such as sending queued reports to the job manager 14, receiving new jobs from the job manager 14, returning the log output data to the job manager 14 if logging is enabled, and receiving the go command from the job manager 14.
FIG. 3 also depicts how the two job dispatch threads 218 and 220 in the infrastructure 210 work with two evaluation thread 230 and 232. The combination of one job dispatch thread 218 or 220 with its associated evaluation thread 230 or 232 works as a unit. In many embodiments, only one of the threads from each pair is running at any one given time, and thus they can be thought of as a single logical thread that spans process boundaries. Because in some embodiments there are only one of these logical threads for each of the two processors in the process node 20, contention for the processors is reduced, and thus additional thread switching overhead is also reduced, and adverse cache effects from threads contending for the processors is likewise reduced.
In one embodiment, the reports are sent back between swaths. To reduce task switching, the interface 22 does very little during swathing that involves the processors. Specifically, and as mentioned elsewhere herein, there are no interrupts delivered from the interface 22 during normal operation. The interface 22 is adapted to perform direct memory access transfers, using polling and not interrupts, and then leave the processors alone. When performed in this manner, direct memory accesses do not require processor attention, and thus do not contend for use of the processor.
The foregoing description of embodiments for this invention has been presented for purposes of illustration and description. It is not intended to be exhaustive or to limit the invention to the precise form disclosed. Obvious modifications or variations are possible in light of the above teachings. The embodiments are chosen and described in an effort to provide the best illustrations of the principles of the invention and its practical application, and to thereby enable one of ordinary skill in the art to utilize the invention in various embodiments and with various modifications as is suited to the particular use contemplated. All such modifications and variations are within the scope of the invention as determined by the appended claims when interpreted in accordance with the breadth to which they are fairly, legally, and equitably entitled.

## Claims

1. An inspection system that receives image data corresponding to an image and processes the image data to produce a report corresponding to characteristics of the image, the inspection system comprising:
network interface cards that receive the image data in a flow, where each interface card receives image data corresponding to a different portion of the image,
process node computers connected to the interface cards that receive the image data from the interface cards,
a host computer connected to the process nodes,
job manager programs stored in a non-transient memory and implemented in the host computer that manage the flow of image data to and from the process nodes, the job managers adapted to remain operable during a crash of one of the process nodes, and
process node programs stored in a non-transient memory and implemented in the process nodes that analyze a portion of the image data and produce the report corresponding to the characteristics of the analyzed portion of the image data, at least one process node program implemented in each process node, where the process node programs rapidly analyze the image, the process node programs being isolated from the job managers so that a crash of a process node program does not crash the job manager.

2. The inspection system of claim 1 wherein the job managers are written in Java and the process node programs are written in C.

3. The inspection system of claim 1 further comprising a shared memory that is shared by the job managers and the process node programs, wherein the job managers and the process node programs transmit data between one another by reading and writing data into the shared memory.

4. The inspection system of claim 3 wherein the shared memory is sufficiently large to receive the data produced by both the job manager and the process node program during a worst case scenario in which both the job manager and the process node program produce a maximum possible amount of data.

5. The inspection system of claim 1 wherein each job manager is assigned to a set of at least one process node programs and manages the flow of data to and from the assigned set of process node programs.

6. The inspection system of claim 1 wherein each process node includes at least two processors for simultaneously executing two process node programs to analyze the portion of the image data.

7. The inspection system of claim 1 further comprising a job queue memory, where the job manager loads the job queue memory with job data before the job data is needed by the process node program.

8. The inspection system of claim 1 further comprising a report queue memory, where the process node program loads the report into the results queue memory before the report is needed by the job manager.

9. The inspection system of claim 1 further comprising a job queue memory and a report queue memory, where the job manager loads the job queue memory with data before the data is needed by the process node program, and the process node program produces loads the report into the results queue memory before the report is needed by the job manager, so that no delay is caused by the process node program waiting for job data and no delay is caused by the process node program waiting for memory space in which to write the report.

10. An inspection system that receives image data corresponding to an image and processes the image data to produce a report corresponding to characteristics of the image, the inspection system comprising:
network interface cards that receive the image data in a flow, where each interface card receives image data corresponding to a different portion of the image,
process node computers connected to the interface cards that receive the image data from the interface cards,
a host computer connected to the process nodes,
job manager programs stored in a non-transient memory and implemented in the host computer that manage the flow of image data to and from the process nodes, where the job managers remain operable during a crash of one of the process nodes,
process node programs stored in a non-transient memory and implemented in the process nodes that analyze a portion of the image data and produce the report corresponding to the characteristics of the analyzed portion of the image data, at least one process node program implemented in each process node, where the process node programs rapidly analyze the image, and
a shared memory that is shared by both the job managers and the process node programs, where the job managers and the process node programs send and receive data between each other by writing the data into the shared memory.

11. The inspection system of claim 10 wherein the shared memory is sufficiently large to receive the data produced by both the job manager and the process node program during a worst case scenario in which both the job manager and the process node program produce a maximum possible amount of data.

12. The inspection system of claim 10 wherein each job manager is assigned to a set of at least one process node programs and manages the flow of data to and from the assigned set of process node programs.

13. The inspection system of claim 10 wherein each process node includes at least two processors for simultaneously executing two process node programs to analyze the portion of the image data.

14. The inspection system of claim 10 further comprising a job queue memory and a report queue memory, where the job manager loads the job queue memory with data before the data is needed by the process node program, and the process node program produces loads the report into the results queue memory before the report is needed by the job manager, so that no delay is caused by the process node program waiting for job data and no delay is caused by the process node program waiting for memory space in which to write the report.

15. The inspection system of claim 10 wherein the job managers are written in a relatively slow and stable programming environment and the process node programs are written in a relatively fast and instable programming environment, and the process node programs are isolated from the job managers so that a crash of a process node program does not crash the job manager.

16. A method of processing image data corresponding to an image to produce a report corresponding to characteristics of the image, the method comprising the steps of:
receiving the image data in a flow with network interface cards, where each interface card receives image data corresponding to a different portion of the image,
receiving the image data from the interface cards with process node computers connected to the interface cards,
managing the flow of image data to and from the process nodes with job manager programs stored in a non-transient memory and implemented in a host computer that is connected to the process nodes, where the job managers remain operable during a crash of one of the process nodes, and
analyzing a portion of the image data with process node programs stored in a non-transient memory and implemented in the process nodes and producing the report corresponding to the characteristics of the analyzed portion of the image data, at least one process node program implemented in each process node, where the process node programs rapidly analyze the image, the process node programs being isolated from the job managers so that a crash of a process node program does not crash the job manager.