22 Oct 2002Tracker Week - Bonding WGSalvatore Costa - Catania Status of Database Interface for...

22 Oct 2002Tracker Week - Bonding WGSalvatore Costa - Catania

Status of Database Interface for Status of Database Interface for Bonding Data Bonding Data

Salvatore Costa

University and INFN – Catania

22 Oct 2002Tracker Week - Bonding WG 2 Salvatore Costa - Catania

News

• Version 0.2 released on 17 Oct 2002 (eventually!)• DEMO, but with same interactive look-and-feel of

future real version for the User• Takes into account all comments to previous v 0.1

(example: VIEW requires pw, so data are visible only within CENTER)

[if not: complain]• 11,000 lines of code (HTML, pl, XML)


Functional Description

if

op

su

man

ENTER

UPDATEVIEW

SEARCH

VALIDATE

CREATE new file

front page

User’s Guide

(in new window)

data

indb

results

ID_oper.dat

ID_oper.dat ID_oper.xml

BigBrowser

ID_oper.xml.indb

ParSet….xml.indb TrackerDBTrackerDB

ParSet…dat ParSet...xml


Work in Progress on v0.2

• Fix bugs [already fixed some]

• Soften bg colors (OK on LCD monitors, too bright on CRT)

• Add “defaults” to Forms for some CENTERS


Center “DB Readiness”

Center DB Responsible Form Defaults

Aachen Wolfgang Braunschweig MISSING

Bari Valeria Radicci OK

Catania Salvatore Costa OK

CERN Alan Honma OK

FNAL Bill Kahl OK

Florence Simone Paoletti OK

Karlsruhe Hans-Jürgen Simonis IN PROGRESS

Padova Maurizio Loreti MISSING

Pisa Andrey Starodoumov IN PROGRESS

Santa Barbara Bill Kahl OK

Strasbourg Pierre Juillot OK

Torino Ernesto Migliore OK

Vienna Thomas Bergauer OK

Zurigo Klaus Freudenreich OK


Work to do for v 1.0

• Write User’s Guide

• Develop Installation proceduredir designation and naming (results and indb must

coincide with those declared when installing BigBrowser)• BigBrowser on same machine or in machine mounting same dir

Web server configuration• Authentication (pw)

• Authorizations (dir ownership and protection)

• Make it “Talk” to TrackerDB

• Extend to Hybrid Bonding…


“Talk” to TrackerDB…

…to get List of Channels not-to-be bonded

• Sought solution: Download when entering Pre-BondingTry “Relay” application to query TrackerDB from User’s program

• Backup solution: Use BigBrowser to download SENSOR Tables, then filter list with script (Andrey Starodoumov helping)

Will be documented in User’s Guide



…to upload our dataNo Relay application, AFAIKUsing a button in BigBrowser

Will be documented in User’s Guide

I need to determine exact XML file contents


<?xml version="1.0" encoding="UTF-8" ?><DBFile xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"><xsi:noNamespaceSchemaLocation="calibration.xsd"><object id="111" /><action><action_description name="PREBOND" version="1" object_name="MOD" object_type=“TIB4"

input_id="123" /><result name="centre_name" value="SANTA BARBARA" /><result name="tool_id" value="2" /><result name="tdate" value="2002-10-17T18:16:37" /><result name="INSPECTOR" value="Susanne Kyre" /><result name="RECV_TIME" value="2002-10-17T18:16:00" /><result name="UNPACK" value="None" /><result name="STATUS" value="Good" /><result name="QUICK_TEST" value="No comment" /><result name="STORAGE" value="None" /><result name="SHIP_TIME" value="2002-10-17T18:16:00" /><result name="READY_FOR_BOND" value="yes" /><result name="status" value="valid" /><result name="tcomment" value="nocomment" /></action></DBFile>…

XML file contents



…to pass List of Channels not bonded from Bonding Center to Bonding Repair Center

• In DEMO Bond Repair forms look in file created by Bond Forms

In v 1.0 must dowload from TrackerDB since Repair Center may be different than Bonding Center, just as has to be done for the list of channels not-to-be-bonded


Hybrid Bonding

• “8th Section” in Interface?, such as Hybrid Bonding

Enter Data Add or Change Data Validate Data

• Added to the “Bonding” Forms?

Most depends on when Hybrid bonding occurs, after Module is assembled or before?

To which OBJECT (as registered in TrackerDB) should we attach the info: MOD or HYB or...?


The 9 Bonding Tables

PREBOND POSTBOND

BONDREP PULL

“BOND” Composite

BONDMACHINE BONDWIRE

BONDLOG BONDSTATUS

BONDPARAM


“PREBOND” Table

Description Name Data Type Entry Mode

Pre-bonding Inspector name INSPECTOR VARCHAR(128) PULL-DOWN LIST WITH AUTOMATIC DEFAULT

Receiving date& time

(By Pre-Bonding Inspector)

RECV_TIME DATE PULL-DOWN LISTS WITH AUTOMATIC DEFAULTS

Unpacking info UNPACK VARCHAR(128) TYPE-IN

Status found in pre-bonding inspection

STATUS VARCHAR(384) TYPE-IN

Comment on quick readout test QUICK_TEST VARCHAR(384) TYPE-IN

Storage info STORAGE VARCHAR(128) TYPE-IN

Release date & time

(by Pre-Bonding inspector)

SHIP_TIME DATE PULL-DOWN LISTS WITH AUTOMATIC DEFAULTS

Ready-for-Bonding status READY_FOR_BOND VARCHAR(64) RADIO BUTTON (default: NO)


“BONDMACHINE” Table


Manufacturer & Model MFTMOD VARCHAR(128) PULL-DOWN LIST WITH AUTOMATIC DEFAULT

ID (seq n. to uniquely identify same-model machines)

ID INT PULL-DOWN LIST WITH AUTOMATIC DEFAULT

Tool Manufacturer TOOL_MFT VARCHAR(128) PULL-DOWN LIST WITH AUTOMATIC DEFAULT

Tool Type TOOL_TYPE VARCHAR(128) PULL-DOWN LIST WITH AUTOMATIC DEFAULT

Jig number JIG_NUM INT PULL-DOWN LIST WITH AUTOMATIC DEFAULT

Machine-specific Parameter Filename

PARAM_FILENAME VARCHAR(128) TYPE-IN WITH AUTOMATIC DEFAULT

Name of Program PROGRAM VARCHAR(128) TYPE-IN (default: “manual”)


“BONDWIRE” Table


Manufacturer MFT VARCHAR(128) PULL-DOWN LIST WITH AUTOMATIC DEFAULT

Type TYPE VARCHAR(128) PULL-DOWN LIST WITH AUTOMATIC DEFAULT

Thickness (µm) THICKNESS_UM FLOAT PULL-DOWN LIST WITH AUTOMATIC DEFAULT

ID ID VARCHAR(128) PULL-DOWN LIST WITH AUTOMATIC DEFAULT

Date of fabrication FAB_DATE DATE TYPE-IN

Date of first usage FU_DATE DATE TYPE-IN


“BONDLOG” Table


Bonding operator name OPERATOR VARCHAR(128) PULL-DOWN LIST WITH AUTOMATIC DEFAULT


(by Bonding operator)


Ambient Temperature TEMP_C FLOAT TYPE-IN

Ambient Relative Humidity REL_HUMI_PERC FLOAT TYPE-IN

# bonds with tool thus far N_BONDS INT TYPE-IN

# repaired failures during bonding

N_REPAIRED INT TYPE-IN

Release date & time

(by Bonding Operator)


Recommended repairs RECOM_REPAIRS VARCHAR(1024) TYPE-IN

Ready-for-Post-Bonding Inspection status

READY_FOR_POSTBOND STRING(64) RADIO BUTTON (default: NO)


“BONDSTATUS” Table


Channels not bonded

(PA to SEN)

PA2SEN_NOT_BONDED VARCHAR(4000) CLICK CHECKBOXES

Channels not bonded

(SEN to SEN)

SEN2SEN_NOT_BONDED VARCHAR(4000) CLICK CHECKBOXES


“POSTBOND” Table


Post-bonding Inspector name INSPECTOR VARCHAR(128) PULL-DOWN LIST WITH AUTOMATIC DEFAULT


(by Post-Bonding Inspector)


Status found in post-bonding inspection

STATUS VARCHAR(384) TYPE-IN

Packing info PACK VARCHAR(128) TYPE-IN

Release date& time

(by Post-Bonding to Testing or Repair)


Ready-for-Testing status READY_FOR_TEST VARCHAR(64) RADIO BUTTON (default: NO)


“BONDREP” Table


Bonding Repair operator name OPERATOR VARCHAR(128) PULL-DOWN LIST WITH AUTOMATIC DEFAULT


(by Bonding Repair operator)


Repairs done REPAIRS_DONE VARCHAR(1024) TYPE-IN

Release date & time

( by Bonding Repair operator)


Ready-for-Testing status READY_FOR_TEST VARCHAR(64) RADIO BUTTON (default: NO)

Bonding Repair Forms also write back into BONDSTATUS Table (and increment VERSION):

Channels not bonded

(PA to SEN)

PA2SEN_NOT_BONDED VARCHAR(4000) CLICK CHECKBOXES

Channels not bonded

(SEN to SEN)

SEN2SEN_NOT_BONDED VARCHAR(4000) CLICK CHECKBOXES


“PULL” Table


Pull Test operator name OPERATOR VARCHAR(128) PULL-DOWN LIST WITH AUTOMATIC DEFAULT


(by Pull Test operator)


Pull Tester type TYPE VARCHAR(128) TYPE-IN

Pull Tester ID ID INT PULL-DOWN LIST WITH AUTOMATIC DEFAULT

# ND pulls ND_N_PULLS INT TYPE-IN

# ND challenging strength ND_STR_G FLOAT TYPE-IN WITH AUTOMATIC DEFAULT

# ND bonds breaking ND_N_BREAKING INT TYPE-IN

# D pulls D_N_PULLS INT TYPE-IN

D min strength D_STR_MIN _G FLOAT TYPE-IN

D max strength D_STR_MAX _G FLOAT TYPE-IN

D average strength D_STR_AVG _G FLOAT TYPE-IN

D strength sigma D_STR_SIGMA_G FLOAT TYPE-IN

D# bonds breaking by… D_N_FBHB… FLOAT TYPE-IN

Release date& time

(by Pull Test operator)



“BONDPARAM” TableDescription Name Data Type Entry Mode

Name of Machine-specific Parameter file

PARAM_FILENAME VARCHAR(128) Automatically generated

Contents of the (text) file PARAM_SET VARCHAR(1024) Automatically generated

by filling a form whose entries depend on CENTER, since relevant parameters may vary with machine

Example:

LOOP_HEIGHT: 6 umPULL_UP: 50 whateverPULL_DOWN: 99Etc…

Date post:	01-Jan-2016
Category:	Documents
Upload:	martina-marsh
View:	215 times
Download:	1 times

22 Oct 2002Tracker Week - Bonding WGSalvatore Costa - Catania Status of Database Interface for...

Documents