Additional information¶
Alternative ID (Local Manufacturer SN)¶
The alternative ID (local manufacturer SN) for wafer is a required and unique property of the wafer and sensor component and must be filled in as: VX-WWWWWW for wafer and VX-WWWWWW-D-NNN for sensor or test structure tiles as specified in (ii). If you try to register a wafer/sensor tile with the same alternative ID as one already in the PDB, you will get an error.
This alternative ID (local manufacturer SN) should NOT be confused with the production database serial number, which is the SN automatically generated by the user selection in the GUI based on the SN specification in the form: 20UXXYYNNNNNNN.
- Example: If you register a parent wafer with Local Manufacturer SN V4-000023, this will be the wafer identified by the vendor as number 23.
If it has 4 children sensor tiles, with position 1-4, they must be registered with the alternative ID:
V4-2-000023-3-001
V4-2-000023-3-002
V4-2-000023-3-003
V4-2-000023-3-004
Here, the -3-
indicates the tiles to be sensors and not test structures, -001
to -004
indicates the position the sensor has on the wafer (see wafer map).
The scrip will use the alternative ID of the sensor tile to find the parent wafer and connect it to it.
Wafer Maps¶
Wafer maps are .json
files that can be found in the directory "WaferMap". These files contain the positions and types of all the sensor tiles connected to a wafer from a given vendor.
After successfully registering a wafer, you will get prompt with a question in the terminal if you want to automatically register the children sensor tiles connected to your wafer by using a wafer map.
If you type in "yes", the code will run trough wafer map file in a for loop and register and attach all the sensor tiles to the (parent) wafer. This method was specially meant for institutes that had ~20-30 dices on their wafer and would save time by not having to register the sensor tiles manually one by one.
This method, however, is just an optional shortcut for registering all the sensors tiles on a wafer right after registering the wafer itself. But you also need to know which vendor number (V1-V6 in the new SN schema) this wafer map should be connected too.
You can add or change your wafer map in inside the "Wafermap" directory. However, the position number of the sensor tile is standardized (changing this would also mean to change the for loop in the "RegisterComponent.py" script.
- Example on Wafer map:
Let's say you have a wafer with children sensor type code: "OUTER_PIXEL_QUAD_SENSOR_TILE" (see terminal json-file display for finding the codes easily), from vendor 4 with 6 sensor tiles on it. The wafer PDF map will then look like this:
And the corresponding json-file for this wafer map should look like this:
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 |
|
In the tile
section different sensor or test structure types are assigned their corresponding codes in the PDB.
The Map
section indicates whether each physical tile is a test structure "halfmoon" or a sensor tile.
The Halfmoon
section details the test structure layout, including the test structure type indicator and name, on each of the halfmoons.
- The number inside the 2D array element decides the sensor or test structure type (2nd classification digit), like 1 is single, 2 test structure halfmoon, and 3 is quad etc. More information on the sensor type numbers can be found in the SN specifications.
- Here the script will first register 6 quad sensors with position (1-6), and then the 4 test structure halfmoons.
- Due to the large number of test structures per wafer, the registered test structure halfmoons will only have empty slots for test structures until a test is registered for a test structure.