7
Database entry of Database entry of irradiation data irradiation data PROBLEMS New form of DB data 1. One set of data may de-qualify whole batch of sensors composite of composite action: NEW 2. Tests are done on teststructures TS is NOT a database object Even worse on diodes and minisensors on TS how to name? WHERE to register? in addition there will be modules to be irradiated.

Database entry of irradiation data

Embed Size (px)

DESCRIPTION

Database entry of irradiation data. PROBLEMS New form of DB data One set of data may de-qualify whole batch of sensors  composite of composite action: NEW Tests are done on teststructures  TS is NOT a database object  Even worse on diodes and minisensors on TS  - PowerPoint PPT Presentation

Citation preview

Page 1: Database entry of irradiation data

Database entry of irradiation dataDatabase entry of irradiation data

PROBLEMS • New form of DB data

1. One set of data may de-qualify whole batch of sensors composite of composite action: NEW

2. Tests are done on teststructures TS is NOT a database object

• Even worse on diodes and minisensors on TS

• how to name? WHERE to register?

• in addition there will be modules to be irradiated.

• FACT: The PQC centers will face the same problem

Page 2: Database entry of irradiation data

Steps to go, and possible solutionSteps to go, and possible solution

• We need a discussion with Didier

1. The composite of composite action has to be introduced in the DB scheme

2. IQC and also PQC tables could be inserted in the QTC existing DB objects• Addition of new tables• Optional, since only a fraction will be irradiated

• M200 and pre-series is approaching fast!

Page 3: Database entry of irradiation data

Irrad tables already exist in Irrad tables already exist in XMLXML

• Tables are done and already underwent one iteration between Karlsruhe and Louvain

• We will have 3 simple tables: – diode minisensor sensor– Tables show the results from the agreed

measurements– Ramps, mean values, difference of values before

and after irradiation

Page 4: Database entry of irradiation data

DB content DB content (for sensor & minissensor)(for sensor & minissensor)

• ENV: Date,Time;Irrad_Date;Comment;Humidity,Temp

Duration; operator; location; status

• GLOBAL: I_TOT, V_dep; C_TOT; alpha (before and after irrad)

• IRRAD-SPECS: fluence(p,n); dose(p,n); energy(p,n)

• STRIP-PARAMETERS: mean[Rpoly;Cint;Ileak;Rint (CAC optional)]@Vstandard

Delta of all strip parameters before and after irrad

Raw Data: IV,CV, ONE RAMP {Rpoly;Cint;Ileak;Rint (CAC optional)} vs. Voltage

Page 5: Database entry of irradiation data

Tables for diodeTables for diode<action> <action_description input_id="??" name="irrad"object_name="DIODE" version="1"/> <result name="Test_center" value="KARLSRUHE-IEKP"/> <result name="Parent_action" value="Validation"/> <result name="input_file" value="Sensor_irrad_v_0"/> <result name="Tdate" value="2001-09-07 09:15:25"/> <result name="Tdate_irradiation" value="2001-09-07 09:15:25"/> <result name="Duration_minutes" value="25.21"/> <result name="tool_id" value="??"/> <result name="Tcomment" value="null"/> <result name="Temp_start" value="-9.80"/> <result name="Humidity_start" value="2.02"/> <result name="Temp_end" value="-10.2.00"/> <result name="Humidity_end" value="1.81"/> <result name="I_tot_V1_nA" value="175.44"/> <result name="I_tot_V1_delta_nA" value="175.44"/> <result name="V_break_V" value="552.00"/> <result name="V_depl_V" value="552.00"/> <result name="V_depl_delta_V" value="100.00"/> <result name="C_TOT_pF" value="100.00"/> <result name="C_TOT_delta_pF" value="100.00"/> <result name="alpha" value=":0:"/> <result name="p_fluence_e14_1Mev_Neq" value=":0:"/> <result name="p_dose_kGray" value=":0:"/> <result name="p_energy_MeV" value=":0:"/> <result name="p_irrad_val" value=":0:"/> <result name="n_fluence_e14_1Mev_Neq" value=":0:"/>

<result name="n_dose_kGray" value=":0:"/> <result name="n_energy_MeV" value=":0:"/> <result name="n_irrad_val" value=":0:"/> <result name="Status" value="reference"/> <result name="Operator" value="Frank_Hartmann"/> <result name="Voltage_V" value="0.00 5.00 10.00 15.00 …………….545.00 550.00"/> <result name="I_tot_nA" value="52.10 95.48 126.58 123.26 ………………………………194.36 194.94"/> <result name="C_tot_pF" value="22530.00 21370.00 7946.00 4882.00 …………………….1855.00 1855.00"/>

</action>

Tables for sensors and minisensors are similar but more extensive.

Page 6: Database entry of irradiation data

Addition for sensor and Addition for sensor and minisensorminisensor

<result name="Rpoly_mean_V1_MOhm" value="175.44"/> <result name="Rpoly_delta_V1_MOhm" value=".10"/> <result name="I_strip_nA" value="552.00"/> <result name="I_strip_delta_nA" value="0"/> <result name="C_ac_mean_V1_pF" value="552.00"/> <result name="C_ac_delta_V1_pF" value="0"/> <result name="C_int_1Mhz_mean_V1_pF" value="552.00"/> <result name="C_int_1MHz_delta_V1_pF" value="552.00"/> <result name="R_int_mean_V1_MOhm" value="552.00"/> <result name="R_int_delta_V1_MOhm" value="552.00"/> <result name="C_tot_pF" value="22530.00 21370.00 ..... 1855.00 1855.00"/> <result name="Rpoly_MOhm" value="52.10 95.48 ...... 194.36 194.94"/> <result name="C_int_1MHz_pF" value="52.10 95.48 .... 194.36 194.94"/> <result name="I_strip_nA" value="0.32 0.33 ...... 0.32 0.29"/> <result name="C_ac_100Hz_pF" value="52.10 95.48 ........194.36 194.94"/> <result name=„R_int_MOhm" value=„0.68 1.38 ........100.00 100.00"/> </action>

Page 7: Database entry of irradiation data

Pending ActionsPending Actions

• Agreement how to label tables for diode, sensor, minisensor!?!

Is the diode, the irrad. Sensor and the minisensor a

component of the sensor (same ID)?Are they seperate objects; where will they be registered?

• @DB people implemtation of the composite of composites

• Implementation of the agreed! Tables into the DB (discussion underway)

• Labview vi for the XML output (I volonteer)