SCT detector manufacturer data sheets
Original version discussed in the last SCT week
and revised the 06-Mar-2000
http://dpnc.unige.ch/atlas/atlaspage/db/doc/mfr_upload/specifications.html
Role of the application:
The upload application that insert information into the DB has 2 major roles:
the initial item registration;
the upload of the manufacturer test data sheet.
During the upload data process the application checks if the initial item registration is already done. If so, then the application will proceed for only step 2.
If no initial registration was done before then the application will proceed automatically first with step 1. and then with step 2.
Rules :
The manufacturers are allowed to enter into the SCT DB the test data sheets for detectors that will be shipped to the institutes.
The data are entered either by using a dedicated java application or by using the Omnis client interface.
The application can be lunched using the command line mode, to allow the automation of the upload process.
The manufacturers are allowed to consult from the SCT DB only their own data by using the Web application or the Omnis client interface.
It will be assigned to each manufacturer a username and password to warranty the confidentiality and ownership of the SCT DB data.
After the detector is shipped by the manufacturer to the destination institute, and when received, the ownership of the detector item will be changed to the destination institute username.
The ownership of all the test data inserted by the manufacturer, are not updated.
Detector's test data file format :
The dedicated java application and the Omnis client interface will read the manufacturer data sheet standard file and upload the data into the SCT database.
The manufacturer data sheet standard file must be compliant with the standard file format described below.
The file text is not case sensitive, but for clarity reasons the mandatory attributes are indicated in upper case characters.
A comment line starts with the # character.
The file is structured into section that starts with the % character
Inside each section are the attributes.
The attribute tag and its associated value(s) are separated by a <TAB> character.
Some mandatories database attributes values like manufacturer, location, person_initials are not provided by the file, but are automaticaly inserted into the DB by the upload application, and derived from the username of the connected manufacturer operator.
Serial number semantic :
The size of the serial number provided by the manufacturer is 14 digits .
It contains the following semantic information :
Example : 20220900720329
1013-1010 Atlas prefix (reference: Nobu's document) 2022
109 reserved: must be 0
108-107 : manufacturer number (reference: Nobu's document) 90
106-105 The Item_type of the inserted item (reference: Nobu's document) 07
104-100 The unique number of a specifique wafer. 20329
The upload application will not interpret the most 7 significants digits (1013-107) provided by the manufacturer to derive the mandatory attributes of the DB, but the application will check those 7 digits to warranty the data integrity of the provided serial number, before inserting the data into the DB.
File format specification example
# General information ITEM section
%ITEM
SERIAL NUMBER <TAB> 20220900720329
Mfr serial number <TAB> SDTX270
%ITEM COMMENT
Here is my item comment number 1...
Here is my item comment number 2...
# Test information Test section
%TEST
TEST DATE (DD/MM/YYYY) <TAB> 19/01/2000
PROBLEM <TAB> NO
PASSED <TAB> YES
Run number <TAB> run01
# Test data Data section
%DATA
TEMPERATURE (C) <TAB> 25
I_LEAK150V (microA) <TAB> 0.82
I_LEAK350V (microA) <TAB> 15.8
Substr Origin <TAB> 000
Substr Orient <TAB> 001
Substr R Upper (kOhm .cm) <TAB> 50.4
Substr R Lower (kOhm.cm) <TAB> 50.1
Thickness (micron) <TAB> 250
Vdep (V) <TAB> 250.5
R Bias Upper (MOhm ) <TAB> 50.2
R Bias Lower (MOhm ) <TAB> 50.6
# Comment section
%COMMENT
Here is my test comment1 …
Here is my test comment2 …
# Defects section
%DEFECT
#DEFECT NAME <TAB> FIRST CHANNEL <TAB> LAST CHANNEL <TAB> url
Open <TAB> 12
Open <TAB> 601 <TAB> 603
Short <TAB> 540 <TAB> 541<TAB> http://www.cern.ch
# Weblink section
%WEBLINK
#DESCRIPTION <TAB> URL
Here is the description <TAB> http://www.unige.ch
Here is the description2 <TAB> http://www.unige.ch
# IV raw data Raw data section
%RAWDATA
Filename <TAB> myDataFile.raw
Data <CR>
Any raw data text format (must be after "Data")
# End of manufacturer data file
Data Format :
Sections :
%ITEM Must be declared once
%TEST Must be declared once
%DATA Must be declared once
%Comment Can be declared once
%Defect Can be declared once
%Web link Can be declared once
%RAWDATA Can be declared once
Attributs :
%ITEM section :
SERIAL NUMBER : Integer unique number [0..20220989999999]
Mfr serial number : Internal manufacturer wafer number [string(35)]
%ITEMCOMMENT section :
COMMENT : String(400)
%TEST section :
TEST DATE : String(10) DD/MM/YYYY
PROBLEM : String in [YES/NO],
PASSED : String in [YES/NO],
Run number : String(80) Manufacturer internal representation
%DATA section :
TEMPERATURE : double in [-30..100]
I LEAK 150 : double in [0..99999999]
I LEAK 350 : double in [0..99999999]
Substr Origin : String [40]
Substr Orient : String [40]
Substr R Upper : double
Substr R Lower : double
Thickness : Integer [200..400]
Vdep : double in [0..400]
R Bias Upper : double in [0..100]
R Bias Lower : double in [0..100]
%Comment section :
COMMENT : String(400)
%DEFECT section
DEFECT NAME : String (20) Must exist in the DB
FIRST CHANNEL, LAST CHANNEL : Integer in [1..1536]
Url : String(200)
%WebLink section
DESCRIPTION : String(100)
URL : String(200)
%RAWDATA section
FILENAME : String(100)
Philippe Demierre
Didier Ferrere
Joe Foster
3-Feb-2000