The actions are applied on sensor test structures. The test structures belong to the objects SEN. To differentiate with the actions on SENsors themselves, the action names start with TS (Test Structure).
We have first defined a composite action with a degree of compositness  10, called TSProcessQualification, which includes the following 10 individual actions:
1. TSCONDITIONS
2. TSIV
3 TSCV
4. TSMOS
5. TSGCD
6. TSsheet
7. TSCAC
8. TSCint
9. TSRint
10. TSIVDielectric
then the individual actions

Table for the action TSProcessQualification

sbgat222 51: ./newaction
You are about to create the description of a new action table.
You will be prompted for the description of this new action.
At any time, you can enter h for help, c to cancel.
Use ./newaction -h for a list of options.
If you are borred by this message, use the -q option ;-)
We need a name for your new action.
It is a string, 32 characters max.
For example: fabinfo, or modulexvalidation.
Don't use special character like _ , ; : or space!

action name ? TSProcessQualification

Give a version name for this action.
It is a string, 32 characters max.
For example: 1 or withextendedtest.
Create a new version only if the ouput format of the test change.
If the condition of the test change, use the same version
and change the input parameters.
Don't use special character like _ , ; : or space!
action version ? 1

Give the object name to which this action apply.
This name must be in the object description table.
For example: MOD, SEN.
object ? SEN

Give the object type to which this action apply.
This type must be in the object description table.
If the action apply on all types, just it enter.
For example: 1.1.2.
object type ?

Give the object version to which this action apply.
This version must be in the object description table.
If the action apply on all versions, just it enter.
For example: 1.
object version ?

If this action is already defined,
you could add a new set of input parameters.
only input param(y/n) ? n

Give the description of the input parameters.
It is a string that cound contain any characters (max: 255).
The format is a list of comma separated items.
It is a good idea to put the unit into the string.
For example: threshold in mV, cut in dB.
input description: ?

Give the value(s) of the input parameters.
It is a string that cound contain any characters (max: 255).
The format is a list of comma separated items.
For example: 13.4, 95.
You could also put a reference to another action tables
by adding an @ to the table name, for example:
@APV_1_FESET_
input values ?

Give a comment about this set of input parameters.
It is a string that cound contain any characters (max: 255).
It is a good idea to put a keyword that identifie this set.
input comment ?

If your new action is a composite action,
enter the number of sub-actions.
If it is a non-composite action, enter 0.
(a composite action consist in a list of sub-actions)
composite ? 10

You are describing a composite action.
The level of an elementary action is 0,
the level of a composite of elementaries is 1,
the level of a composite of composites of level 1 is 2, etc...
level of the composite ? 1

Give now the order of this composite action.
If there is no specific order, enter 0
order for this action ? 0

You are describing a composite action.
For each sub-action you need to give:
-the name of the action
-the version of the action
-the object on which the action act
-the type of this object (facultative)
name of sub-action 1 ? TSconditions
You are describing a composite action.
For each sub-action you need to give:
-the name of the action
-the version of the action
-the object on which the action act
-the type of this object (facultative)
version of sub-action 1 ? 1
You are describing a composite action.
For each sub-action you need to give:
-the name of the action
-the version of the action
-the object on which the action act
-the type of this object (facultative)
object for sub-action 1 ? SEN
You are describing a composite action.
For each sub-action you need to give:
-the name of the action
-the version of the action
-the object on which the action act
-the type of this object (facultative)
type of object for sub-action 1 ?

You are describing a composite action.
For each sub-action you need to give:
-the name of the action
-the version of the action
-the object on which the action act
-the type of this object (facultative)
name of sub-action 2 ? TSIV
You are describing a composite action.
For each sub-action you need to give:
-the name of the action
-the version of the action
-the object on which the action act
-the type of this object (facultative)
version of sub-action 2 ? 1
You are describing a composite action.
For each sub-action you need to give:
-the name of the action
-the version of the action
-the object on which the action act
-the type of this object (facultative)
object for sub-action 2 ? SEN
You are describing a composite action.
For each sub-action you need to give:
-the name of the action
-the version of the action
-the object on which the action act
-the type of this object (facultative)
type of object for sub-action 2 ?

You are describing a composite action.
For each sub-action you need to give:
-the name of the action
-the version of the action
-the object on which the action act
-the type of this object (facultative)
name of sub-action 3 ? TSCV
You are describing a composite action.
For each sub-action you need to give:
-the name of the action
-the version of the action
-the object on which the action act
-the type of this object (facultative)
version of sub-action 3 ? 1
You are describing a composite action.
For each sub-action you need to give:
-the name of the action
-the version of the action
-the object on which the action act
-the type of this object (facultative)
object for sub-action 3 ? SEN
You are describing a composite action.
For each sub-action you need to give:
-the name of the action
-the version of the action
-the object on which the action act
-the type of this object (facultative)
type of object for sub-action 3 ?

You are describing a composite action.
For each sub-action you need to give:
-the name of the action
-the version of the action
-the object on which the action act
-the type of this object (facultative)
name of sub-action 4 ? TSMOS
You are describing a composite action.
For each sub-action you need to give:
-the name of the action
-the version of the action
-the object on which the action act
-the type of this object (facultative)
version of sub-action 4 ? 1
You are describing a composite action.
For each sub-action you need to give:
-the name of the action
-the version of the action
-the object on which the action act
-the type of this object (facultative)
object for sub-action 4 ? SEN
You are describing a composite action.
For each sub-action you need to give:
-the name of the action
-the version of the action
-the object on which the action act
-the type of this object (facultative)
type of object for sub-action 4 ?

You are describing a composite action.
For each sub-action you need to give:
-the name of the action
-the version of the action
-the object on which the action act
-the type of this object (facultative)
name of sub-action 5 ? TSGCD
You are describing a composite action.
For each sub-action you need to give:
-the name of the action
-the version of the action
-the object on which the action act
-the type of this object (facultative)
version of sub-action 5 ? 1
You are describing a composite action.
For each sub-action you need to give:
-the name of the action
-the version of the action
-the object on which the action act
-the type of this object (facultative)
object for sub-action 5 ? SEN
You are describing a composite action.
For each sub-action you need to give:
-the name of the action
-the version of the action
-the object on which the action act
-the type of this object (facultative)
type of object for sub-action 5 ?

You are describing a composite action.
For each sub-action you need to give:
-the name of the action
-the version of the action
-the object on which the action act
-the type of this object (facultative)
name of sub-action 6 ? TSsheet
You are describing a composite action.
For each sub-action you need to give:
-the name of the action
-the version of the action
-the object on which the action act
-the type of this object (facultative)
version of sub-action 6 ? 1
You are describing a composite action.
For each sub-action you need to give:
-the name of the action
-the version of the action
-the object on which the action act
-the type of this object (facultative)
object for sub-action 6 ? SEN
You are describing a composite action.
For each sub-action you need to give:
-the name of the action
-the version of the action
-the object on which the action act
-the type of this object (facultative)
type of object for sub-action 6 ?

For each sub-action you need to give:
-the name of the action
-the version of the action
-the object on which the action act
-the type of this object (facultative)
name of sub-action 7 ? TSCAC
You are describing a composite action.
For each sub-action you need to give:
-the name of the action
-the version of the action
-the object on which the action act
-the type of this object (facultative)
version of sub-action 7 ? 1
You are describing a composite action.
For each sub-action you need to give:
-the name of the action
-the version of the action
-the object on which the action act
-the type of this object (facultative)
object for sub-action 7 ? SEN
You are describing a composite action.
For each sub-action you need to give:
-the name of the action
-the version of the action
-the object on which the action act
-the type of this object (facultative)
type of object for sub-action 7 ?

You are describing a composite action.
For each sub-action you need to give:
-the name of the action
-the version of the action
-the object on which the action act
-the type of this object (facultative)
name of sub-action 8 ? TSCint
You are describing a composite action.
For each sub-action you need to give:
-the name of the action
-the version of the action
-the object on which the action act
-the type of this object (facultative)
version of sub-action 8 ? 1
You are describing a composite action.
For each sub-action you need to give:
-the name of the action
-the version of the action
-the object on which the action act
-the type of this object (facultative)
object for sub-action 8 ? SEN
You are describing a composite action.
For each sub-action you need to give:
-the name of the action
-the version of the action
-the object on which the action act
-the type of this object (facultative)
type of object for sub-action 8 ?

You are describing a composite action.
For each sub-action you need to give:
-the name of the action
-the version of the action
-the object on which the action act
-the type of this object (facultative)
name of sub-action 9 ? TSRint
You are describing a composite action.
For each sub-action you need to give:
-the name of the action
-the version of the action
-the object on which the action act
-the type of this object (facultative)
version of sub-action 9 ? 1
You are describing a composite action.
For each sub-action you need to give:
-the name of the action
-the version of the action
-the object on which the action act
-the type of this object (facultative)
object for sub-action 9 ? SEN
You are describing a composite action.
For each sub-action you need to give:
-the name of the action
-the version of the action
-the object on which the action act
-the type of this object (facultative)
type of object for sub-action 9 ?

You are describing a composite action.
For each sub-action you need to give:
-the name of the action
-the version of the action
-the object on which the action act
-the type of this object (facultative)
name of sub-action 10 ? TSIVDielectric
You are describing a composite action.
For each sub-action you need to give:
-the name of the action
-the version of the action
-the object on which the action act
-the type of this object (facultative)
version of sub-action 10 ? 1
You are describing a composite action.
For each sub-action you need to give:
-the name of the action
-the version of the action
-the object on which the action act
-the type of this object (facultative)
object for sub-action 10 ? SEN
You are describing a composite action.
For each sub-action you need to give:
-the name of the action
-the version of the action
-the object on which the action act
-the type of this object (facultative)
type of object for sub-action 10 ?

You can now enter a description for this action.
It can be any text up to 2048 characters.
description ? Qualification of a process after 9 measurements on test structures
You can save all your answers in a file
which you can mail to Didier (contardo@ipnl.in2p3.fr).
file name ? pq
sbgat222 52:

sbgat222 51: ./newaction
You are about to create the description of a new action table.
You will be prompted for the description of this new action.
At any time, you can enter h for help, c to cancel.
Use ./newaction -h for a list of options.
If you are borred by this message, use the -q option ;-)
We need a name for your new action.
It is a string, 32 characters max.
For example: fabinfo, or modulexvalidation.
Don't use special character like _ , ; : or space!
action name ? TSCONDITIONS

Give a version name for this action.
It is a string, 32 characters max.
For example: 1 or withextendedtest.
Create a new version only if the ouput format of the test change.
If the condition of the test change, use the same version
and change the input parameters.
Don't use special character like _ , ; : or space!
action version ? 1

Give the object name to which this action apply.
This name must be in the object description table.
For example: MOD, SEN.
object ? SEN

Give the object type to which this action apply.
This type must be in the object description table.
If the action apply on all types, just it enter.
For example: 1.1.2.
object type ?

Give the object version to which this action apply.
This version must be in the object description table.
If the action apply on all versions, just it enter.
For example: 1.
object version ?

If this action is already defined,
you could add a new set of input parameters.
only input param(y/n) ? n

Give the description of the input parameters.
It is a string that cound contain any characters (max: 255).
The format is a list of comma separated items.
It is a good idea to put the unit into the string.
For example: threshold in mV, cut in dB.
input description: ?
Give the value(s) of the input parameters.
It is a string that cound contain any characters (max: 255).
The format is a list of comma separated items.
For example: 13.4, 95.
You could also put a reference to another action tables
by adding an @ to the table name, for example:
@APV_1_FESET_
input values ?
Give a comment about this set of input parameters.
It is a string that cound contain any characters (max: 255).
It is a good idea to put a keyword that identifie this set.
input comment ?

If your new action is a composite action,
enter the number of sub-actions.
If it is a non-composite action, enter 0.
(a composite action consist in a list of sub-actions)
composite ? 0

We need now the description of the result of the action.
It is the description of the columns of the corresponding table.
It must be a valid SQL description of the table (max 2048 chars).
SQL description is a comma separated list of pairs variable/type.
For example: temp float, hygr float, batchid varchar(32), ivcurve blob.
(a blob is a Binary Large OBject, an opaque container)
It could also contain more complex SQL commands like constraints.
output format ? Duration number, Temp_start number, Humidity_start number, Temp_end number, Humidity_end number

Give now the list of the units of the results.
For example: 'degC , percent, number, mA/mV'.
units ? minutes, degC, percent, degC, percent

You can now enter a description for this action.
It can be any text up to 2048 characters.
description ? Description of the conditions of a measurement
You can save all your answers in a file
which you can mail to Didier (contardo@ipnl.in2p3.fr).
file name ? conditions
sbgat222 52:

sbgat222 51: ./newaction -v
You are about to create the description of a new action table.
You will be prompted for the description of this new action.
At any time, you can enter h for help, c to cancel.
Use ./newaction -h for a list of options.
If you are borred by this message, use the -q option ;-)
We need a name for your new action.
It is a string, 32 characters max.
For example: fabinfo, or modulexvalidation.
Don't use special character like _ , ; : or space!
action name ? TSIV

Give a version name for this action.
It is a string, 32 characters max.
For example: 1 or withextendedtest.
Create a new version only if the ouput format of the test change.
If the condition of the test change, use the same version
and change the input parameters.
Don't use special character like _ , ; : or space!
action version ? 1

Give the object name to which this action apply.
This name must be in the object description table.
For example: MOD, SEN.
object ? SEN

Give the object type to which this action apply.
This type must be in the object description table.
If the action apply on all types, just it enter.
For example: 1.1.2.
object type ?

Give the object version to which this action apply.
This version must be in the object description table.
If the action apply on all versions, just it enter.
For example: 1.
object version ?

If this action is already defined,
you could add a new set of input parameters.
only input param(y/n) ? n

Give the description of the input parameters.
It is a string that cound contain any characters (max: 255).
The format is a list of comma separated items.
It is a good idea to put the unit into the string.
For example: threshold in mV, cut in dB.
input description: ? start in V, stop in V, step_size in V, delay_time in seconds, Voltage_1 in V, I_tot_max_at_V1 in microA, V_break_min in V, delay_time in seconds

Give the value(s) of the input parameters.
It is a string that cound contain any characters (max: 255).
The format is a list of comma separated items.
For example: 13.4, 95.
You could also put a reference to another action tables
by adding an @ to the table name, for example:
@APV_1_FESET_
input values ? 0, 700, 5, 1, 450, 1, 500, 1

Give a comment about this set of input parameters.
It is a string that cound contain any characters (max: 255).
It is a good idea to put a keyword that identifie this set.
input comment ? fixed at Vienna on June 7th, 2002

If your new action is a composite action,
enter the number of sub-actions.
If it is a non-composite action, enter 0.
(a composite action consist in a list of sub-actions)
composite ? 0

We need now the description of the result of the action.
It is the description of the columns of the corresponding table.
It must be a valid SQL description of the table (max 2048 chars).
SQL description is a comma separated list of pairs variable/type.
For example: temp float, hygr float, batchid varchar(32), ivcurve blob.
(a blob is a Binary Large OBject, an opaque container)
It could also contain more complex SQL commands like constraints.
output format ? I_tot_V1 float, V_break number, Voltage varchar(4000), I_tot varchar(4000)

Give now the list of the units of the results.
For example: 'degC , percent, number, mA/mV'.
units ? nA, V, V, nA

You can now enter a description for this action.
It can be any text up to 2048 characters.
description ? IV for test structures
You can save all your answers in a file
which you can mail to Didier (contardo@ipnl.in2p3.fr).
file name ? TSIV
sbgat222 52:

sbgat222 51: ./newaction
You are about to create the description of a new action table.
You will be prompted for the description of this new action.
At any time, you can enter h for help, c to cancel.
Use ./newaction -h for a list of options.
If you are borred by this message, use the -q option ;-)
We need a name for your new action.
It is a string, 32 characters max.
For example: fabinfo, or modulexvalidation.
Don't use special character like _ , ; : or space!
action name ? TSCV

Give a version name for this action.
It is a string, 32 characters max.
For example: 1 or withextendedtest.
Create a new version only if the ouput format of the test change.
If the condition of the test change, use the same version
and change the input parameters.
Don't use special character like _ , ; : or space!
action version ? 1

Give the object name to which this action apply.
This name must be in the object description table.
For example: MOD, SEN.
object ? SEN

Give the object type to which this action apply.
This type must be in the object description table.
If the action apply on all types, just it enter.
For example: 1.1.2.
object type ?

Give the object version to which this action apply.
This version must be in the object description table.
If the action apply on all versions, just it enter.
For example: 1.
object version ?

If this action is already defined,
you could add a new set of input parameters.
only input param(y/n) ? n

Give the description of the input parameters.
It is a string that cound contain any characters (max: 255).
The format is a list of comma separated items.
It is a good idea to put the unit into the string.
For example: threshold in mV, cut in dB.
input description: ? start in V, stop in V, step_size in V, frequency in kHz, signal_amplitude in mV, V_depl_min in V, V_depl_max in V, C_tot _min in pF, C_tot_max in pF, delay_time in seconds

Give the value(s) of the input parameters.
It is a string that cound contain any characters (max: 255).
The format is a list of comma separated items.
For example: 13.4, 95.
You could also put a reference to another action tables
by adding an @ to the table name, for example:
@APV_1_FESET_
input values ? 0, 300, 5, 100, 100, 100, 250, 6, 10, 1

Give a comment about this set of input parameters.
It is a string that cound contain any characters (max: 255).
It is a good idea to put a keyword that identifie this set.
input comment ? fixed at Vienna on June 7th, 2002

If your new action is a composite action,
enter the number of sub-actions.
If it is a non-composite action, enter 0.
(a composite action consist in a list of sub-actions)
composite ? 0

We need now the description of the result of the action.
It is the description of the columns of the corresponding table.
It must be a valid SQL description of the table (max 2048 chars).
SQL description is a comma separated list of pairs variable/type.
For example: temp float, hygr float, batchid varchar(32), ivcurve blob.
(a blob is a Binary Large OBject, an opaque container)
It could also contain more complex SQL commands like constraints.
output format ? V_depl number, C_tot_depl float, Voltage varchar(4000), C_tot varchar(4000)

Give now the list of the units of the results.
For example: 'degC , percent, number, mA/mV'.
units ? V, pF, V, pF

You can now enter a description for this action.
It can be any text up to 2048 characters.
description ? CV for thin/low resistivity test structures
You can save all your answers in a file
which you can mail to Didier (contardo@ipnl.in2p3.fr).
file name ? TSCV_thin
sbgat222 52:
 

sbgat222 51: ./newaction -v
You are about to create the description of a new action table.
You will be prompted for the description of this new action.
At any time, you can enter h for help, c to cancel.
Use ./newaction -h for a list of options.
If you are borred by this message, use the -q option ;-)
We need a name for your new action.
It is a string, 32 characters max.
For example: fabinfo, or modulexvalidation.
Don't use special character like _ , ; : or space!
action name ? TSCV

Give a version name for this action.
It is a string, 32 characters max.
For example: 1 or withextendedtest.
Create a new version only if the ouput format of the test change.
If the condition of the test change, use the same version
and change the input parameters.
Don't use special character like _ , ; : or space!
action version ? 1

Give the object name to which this action apply.
This name must be in the object description table.
For example: MOD, SEN.
object ? SEN

Give the object type to which this action apply.
This type must be in the object description table.
If the action apply on all types, just it enter.
For example: 1.1.2.
object type ? 2

Give the object version to which this action apply.
This version must be in the object description table.
If the action apply on all versions, just it enter.
For example: 1.
object version ?

If this action is already defined,
you could add a new set of input parameters.
only input param(y/n) ? y

Give the description of the input parameters.
It is a string that cound contain any characters (max: 255).
The format is a list of comma separated items.
It is a good idea to put the unit into the string.
For example: threshold in mV, cut in dB.
input description: ? start in V, stop in V, step_size in V, frequency in kHz, signal_amplitude in mV, V_depl_min in V, V_depl_max in V, C_tot _min in pF, C_tot_max in pF, delay_time in seconds

Give the value(s) of the input parameters.
It is a string that cound contain any characters (max: 255).
The format is a list of comma separated items.
For example: 13.4, 95.
You could also put a reference to another action tables
by adding an @ to the table name, for example:
@APV_1_FESET_
input values ? 0, 300, 5, 100, 100, 100, 250, 3, 10, 1

Give a comment about this set of input parameters.
It is a string that cound contain any characters (max: 255).
It is a good idea to put a keyword that identifie this set.
input comment ? fixed at CERN on September 24th, 2002
You can save all your answers in a file
which you can mail to Didier (contardo@ipnl.in2p3.fr).
file name ? TSCV_thick
sbgat222 54:

sbgat222 51: ./newaction
You are about to create the description of a new action table.
You will be prompted for the description of this new action.
At any time, you can enter h for help, c to cancel.
Use ./newaction -h for a list of options.
If you are borred by this message, use the -q option ;-)
We need a name for your new action.
It is a string, 32 characters max.
For example: fabinfo, or modulexvalidation.
Don't use special character like _ , ; : or space!
action name ? TSMOS

Give a version name for this action.
It is a string, 32 characters max.
For example: 1 or withextendedtest.
Create a new version only if the ouput format of the test change.
If the condition of the test change, use the same version
and change the input parameters.
Don't use special character like _ , ; : or space!
action version ? 1

Give the object name to which this action apply.
This name must be in the object description table.
For example: MOD, SEN.
object ? SEN

Give the object type to which this action apply.
This type must be in the object description table.
If the action apply on all types, just it enter.
For example: 1.1.2.
object type ?

Give the object version to which this action apply.
This version must be in the object description table.
If the action apply on all versions, just it enter.
For example: 1.
object version ?

If this action is already defined,
you could add a new set of input parameters.
only input param(y/n) ? n

Give the description of the input parameters.
It is a string that cound contain any characters (max: 255).
The format is a list of comma separated items.
It is a good idea to put the unit into the string.
For example: threshold in mV, cut in dB.
input description: ? start in V, stop in V, step_size in V, frequency in kHz, signal_amplitude in mV, C_tot_min in pF, C_tot_max in pF, flat_band_Vmin in V, flat_band_Vmax in V, delay_time in seconds

Give the value(s) of the input parameters.
It is a string that cound contain any characters (max: 255).
The format is a list of comma separated items.
For example: 13.4, 95.
You could also put a reference to another action tables
by adding an @ to the table name, for example:
@APV_1_FESET_
input values ? -5, 20, 0.2, 75, 100, 200, 1400, 0, 3, 1

Give a comment about this set of input parameters.
It is a string that cound contain any characters (max: 255).
It is a good idea to put a keyword that identifie this set.
input comment ? fixed at Vienna on June 7th, 2002

If your new action is a composite action,
enter the number of sub-actions.
If it is a non-composite action, enter 0.
(a composite action consist in a list of sub-actions)
composite ? 0

We need now the description of the result of the action.
It is the description of the columns of the corresponding table.
It must be a valid SQL description of the table (max 2048 chars).
SQL description is a comma separated list of pairs variable/type.
For example: temp float, hygr float, batchid varchar(32), ivcurve blob.
(a blob is a Binary Large OBject, an opaque container)
It could also contain more complex SQL commands like constraints.
output format ? C_tot float, Flat_band_voltage float, Voltage varchar(4000), C_mos varchar(4000)

Give now the list of the units of the results.
For example: 'degC , percent, number, mA/mV'.
units ? pF, V, V, pF

You can now enter a description for this action.
It can be any text up to 2048 characters.
description ? MOS for thin/low resistivity test structures
You can save all your answers in a file
which you can mail to Didier (contardo@ipnl.in2p3.fr).
file name ? TSMOS_thin
sbgat222 52:
 

sbgat222 51: ./newaction
You are about to create the description of a new action table.
You will be prompted for the description of this new action.
At any time, you can enter h for help, c to cancel.
Use ./newaction -h for a list of options.
If you are borred by this message, use the -q option ;-)
We need a name for your new action.
It is a string, 32 characters max.
For example: fabinfo, or modulexvalidation.
Don't use special character like _ , ; : or space!
action name ? TSMOS

Give a version name for this action.
It is a string, 32 characters max.
For example: 1 or withextendedtest.
Create a new version only if the ouput format of the test change.
If the condition of the test change, use the same version
and change the input parameters.
Don't use special character like _ , ; : or space!
action version ? 1

Give the object name to which this action apply.
This name must be in the object description table.
For example: MOD, SEN.
object ? SEN

Give the object type to which this action apply.
This type must be in the object description table.
If the action apply on all types, just it enter.
For example: 1.1.2.
object type ? 2

Give the object version to which this action apply.
This version must be in the object description table.
If the action apply on all versions, just it enter.
For example: 1.
object version ?

If this action is already defined,
you could add a new set of input parameters.
only input param(y/n) ? y

Give the description of the input parameters.
It is a string that cound contain any characters (max: 255).
The format is a list of comma separated items.
It is a good idea to put the unit into the string.
For example: threshold in mV, cut in dB.
input description: ? start in V, stop in V, step_size in V, frequency in kHz, signal_amplitude in mV, C_tot_min in pF, C_tot_max in pF, flat_band_Vmin in V, flat_band_Vmax in V, delay_time in seconds

Give the value(s) of the input parameters.
It is a string that cound contain any characters (max: 255).
The format is a list of comma separated items.
For example: 13.4, 95.
You could also put a reference to another action tables
by adding an @ to the table name, for example:
@APV_1_FESET_
input values ? -5, 20, 0.2, 75, 100, 300, 600, 0, 10, 1

Give a comment about this set of input parameters.
It is a string that cound contain any characters (max: 255).
It is a good idea to put a keyword that identifie this set.
input comment ? fixed at CERN on September 24th, 2002
You can save all your answers in a file
which you can mail to Didier (contardo@ipnl.in2p3.fr).
file name ? TSMOS_thick
sbgat222 52:

sbgat222 51: ./newaction
You are about to create the description of a new action table.
You will be prompted for the description of this new action.
At any time, you can enter h for help, c to cancel.
Use ./newaction -h for a list of options.
If you are borred by this message, use the -q option ;-)
We need a name for your new action.
It is a string, 32 characters max.
For example: fabinfo, or modulexvalidation.
Don't use special character like _ , ; : or space!
action name ? TSGCD

Give a version name for this action.
It is a string, 32 characters max.
For example: 1 or withextendedtest.
Create a new version only if the ouput format of the test change.
If the condition of the test change, use the same version
and change the input parameters.
Don't use special character like _ , ; : or space!
action version ? 1

Give the object name to which this action apply.
This name must be in the object description table.
For example: MOD, SEN.
object ? SEN

Give the object type to which this action apply.
This type must be in the object description table.
If the action apply on all types, just it enter.
For example: 1.1.2.
object type ?

Give the object version to which this action apply.
This version must be in the object description table.
If the action apply on all versions, just it enter.
For example: 1.
object version ?

If this action is already defined,
you could add a new set of input parameters.
only input param(y/n) ? n

Give the description of the input parameters.
It is a string that cound contain any characters (max: 255).
The format is a list of comma separated items.
It is a good idea to put the unit into the string.
For example: threshold in mV, cut in dB.
input description: ? bias in V, start in V, stop in V, step_size in V, surface_current_min in pA, surface_current_max in pA, delay_time in seconds

Give the value(s) of the input parameters.
It is a string that cound contain any characters (max: 255).
The format is a list of comma separated items.
For example: 13.4, 95.
You could also put a reference to another action tables
by adding an @ to the table name, for example:
@APV_1_FESET_
input values ? 5, 5, -20, -0.5, 5, 100, 1

Give a comment about this set of input parameters.
It is a string that cound contain any characters (max: 255).
It is a good idea to put a keyword that identifie this set.
input comment ? fixed at Vienna on June 7th, 2002

If your new action is a composite action,
enter the number of sub-actions.
If it is a non-composite action, enter 0.
(a composite action consist in a list of sub-actions)
composite ? 0

We need now the description of the result of the action.
It is the description of the columns of the corresponding table.
It must be a valid SQL description of the table (max 2048 chars).
SQL description is a comma separated list of pairs variable/type.
For example: temp float, hygr float, batchid varchar(32), ivcurve blob.
(a blob is a Binary Large OBject, an opaque container)
It could also contain more complex SQL commands like constraints.
output format ? Surface_current float, flat_band_Voltage float, Voltage varchar(4000), I_surf varchar(4000)

Give now the list of the units of the results.
For example: 'degC , percent, number, mA/mV'.
units ? pA, V, V, pA

You can now enter a description for this action.
It can be any text up to 2048 characters.
description ? GCD for test structures
You can save all your answers in a file
which you can mail to Didier (contardo@ipnl.in2p3.fr).
file name ? TSGCD
sbgat222 52:

sbgat222 51: ./newaction
You are about to create the description of a new action table.
You will be prompted for the description of this new action.
At any time, you can enter h for help, c to cancel.
Use ./newaction -h for a list of options.
If you are borred by this message, use the -q option ;-)
We need a name for your new action.
It is a string, 32 characters max.
For example: fabinfo, or modulexvalidation.
Don't use special character like _ , ; : or space!
action name ? TSsheet

Give a version name for this action.
It is a string, 32 characters max.
For example: 1 or withextendedtest.
Create a new version only if the ouput format of the test change.
If the condition of the test change, use the same version
and change the input parameters.
Don't use special character like _ , ; : or space!
action version ? 1

Give the object name to which this action apply.
This name must be in the object description table.
For example: MOD, SEN.
object ? SEN

Give the object type to which this action apply.
This type must be in the object description table.
If the action apply on all types, just it enter.
For example: 1.1.2.
object type ?

Give the object version to which this action apply.
This version must be in the object description table.
If the action apply on all versions, just it enter.
For example: 1.
object version ?

If this action is already defined,
you could add a new set of input parameters.
only input param(y/n) ? n

Give the description of the input parameters.
It is a string that cound contain any characters (max: 255).
The format is a list of comma separated items.
It is a good idea to put the unit into the string.
For example: threshold in mV, cut in dB.
input description: ? Voltage_for_poly in V, R_poly_min in MOhm, R_poly_max in MOhm, delay_time in seconds, Start_Voltage_for_Alu in mV, Stop_Voltage_for_Alu in mV, Step_for_Alu in mV, Alu_min in mOhm/sqr, Alu_max in mOhm/sqr, delay_time in seconds, Voltage_for_pplus in V, pplus_max in Ohm/sqr, delay_time in seconds

Give the value(s) of the input parameters.
It is a string that cound contain any characters (max: 255).
The format is a list of comma separated items.
For example: 13.4, 95.
You could also put a reference to another action tables
by adding an @ to the table name, for example:
@APV_1_FESET_
input values ? 1, 1, 2, 1, 5, 25, 5, 10, 30, 1, 1, 400, 1

Give a comment about this set of input parameters.
It is a string that cound contain any characters (max: 255).
It is a good idea to put a keyword that identifie this set.
input comment ? fixed at Vienna on June 7th, 2002

If your new action is a composite action,
enter the number of sub-actions.
If it is a non-composite action, enter 0.
(a composite action consist in a list of sub-actions)
composite ? 0

We need now the description of the result of the action.
It is the description of the columns of the corresponding table.
It must be a valid SQL description of the table (max 2048 chars).
SQL description is a comma separated list of pairs variable/type.
For example: temp float, hygr float, batchid varchar(32), ivcurve blob.
(a blob is a Binary Large OBject, an opaque container)
It could also contain more complex SQL commands like constraints.
output format ? R_poly varchar(40), R_poly_mean float, R_pplus varchar(40), Rho_pplus float, R_alu varchar(40), Rho_alu float

Give now the list of the units of the results.
For example: 'degC , percent, number, mA/mV'.
units ? MegaOhm, MegaOhm, kiloOhm, kiloOhm/square, Ohm, milliOhm/square

You can now enter a description for this action.
It can be any text up to 2048 characters.
description ? sheet for test structures
You can save all your answers in a file
which you can mail to Didier (contardo@ipnl.in2p3.fr).
file name ? TSsheet
sbgat222 52:

sbgat222 51: ./newaction
You are about to create the description of a new action table.
You will be prompted for the description of this new action.
At any time, you can enter h for help, c to cancel.
Use ./newaction -h for a list of options.
If you are borred by this message, use the -q option ;-)
We need a name for your new action.
It is a string, 32 characters max.
For example: fabinfo, or modulexvalidation.
Don't use special character like _ , ; : or space!
action name ? TSCAC

Give a version name for this action.
It is a string, 32 characters max.
For example: 1 or withextendedtest.
Create a new version only if the ouput format of the test change.
If the condition of the test change, use the same version
and change the input parameters.
Don't use special character like _ , ; : or space!
action version ? 1

Give the object name to which this action apply.
This name must be in the object description table.
For example: MOD, SEN.
object ? SEN

Give the object type to which this action apply.
This type must be in the object description table.
If the action apply on all types, just it enter.
For example: 1.1.2.
object type ?

Give the object version to which this action apply.
This version must be in the object description table.
If the action apply on all versions, just it enter.
For example: 1.
object version ?

If this action is already defined,
you could add a new set of input parameters.
only input param(y/n) ? n

Give the description of the input parameters.
It is a string that cound contain any characters (max: 255).
The format is a list of comma separated items.
It is a good idea to put the unit into the string.
For example: threshold in mV, cut in dB.
input description: ? frequency in kHz, signal_amplitude in mV, C_ac_min in pF, C_ac_max in pF, delay_time in seconds

Give the value(s) of the input parameters.
It is a string that cound contain any characters (max: 255).
The format is a list of comma separated items.
For example: 13.4, 95.
You could also put a reference to another action tables
by adding an @ to the table name, for example:
@APV_1_FESET_
input values ? 75, 100, 18, 25, 1

Give a comment about this set of input parameters.
It is a string that cound contain any characters (max: 255).
It is a good idea to put a keyword that identifie this set.
input comment ? fixed at Vienna on June 7th, 2002

If your new action is a composite action,
enter the number of sub-actions.
If it is a non-composite action, enter 0.
(a composite action consist in a list of sub-actions)
composite ? 0

We need now the description of the result of the action.
It is the description of the columns of the corresponding table.
It must be a valid SQL description of the table (max 2048 chars).
SQL description is a comma separated list of pairs variable/type.
For example: temp float, hygr float, batchid varchar(32), ivcurve blob.
(a blob is a Binary Large OBject, an opaque container)
It could also contain more complex SQL commands like constraints.
output format ? C_ac_mean float, Number_of_bad_strips number, Position_of_bad_strips varchar(20), Strip_number varchar(4000), CAC varchar(4000)

Give now the list of the units of the results.
For example: 'degC , percent, number, mA/mV'.
units ? pF, numbers, numbers, numbers, pF

You can now enter a description for this action.
It can be any text up to 2048 characters.
description ? C_ac for test structures
You can save all your answers in a file
which you can mail to Didier (contardo@ipnl.in2p3.fr).
file name ? TSCAC_thick
sbgat222 52:

sbgat222 54: ./newaction
You are about to create the description of a new action table.
You will be prompted for the description of this new action.
At any time, you can enter h for help, c to cancel.
Use ./newaction -h for a list of options.
If you are borred by this message, use the -q option ;-)
We need a name for your new action.
It is a string, 32 characters max.
For example: fabinfo, or modulexvalidation.
Don't use special character like _ , ; : or space!
action name ? TSCAC
Give the object type to which this action apply.
This type must be in the object description table.
If the action apply on all types, just it enter.
For example: 1.1.2.
object type ? 2

Give the object version to which this action apply.
This version must be in the object description table.
If the action apply on all versions, just it enter.
For example: 1.
object version ?

If this action is already defined,
you could add a new set of input parameters.
only input param(y/n) ? y

Give the description of the input parameters.
It is a string that cound contain any characters (max: 255).
The format is a list of comma separated items.
It is a good idea to put the unit into the string.
For example: threshold in mV, cut in dB.
input description: ? frequency in kHz, signal_amplitude in mV, C_ac_min in pF, C_ac_max in pF, delay_time in seconds

Give the value(s) of the input parameters.
It is a string that cound contain any characters (max: 255).
The format is a list of comma separated items.
For example: 13.4, 95.
You could also put a reference to another action tables
by adding an @ to the table name, for example:
@APV_1_FESET_
input values ? 75, 100, 16, 20, 1

Give a comment about this set of input parameters.
It is a string that cound contain any characters (max: 255).
It is a good idea to put a keyword that identifie this set.
input comment ? C_ac for thin/low resistivity test structures
You can save all your answers in a file
which you can mail to Didier (contardo@ipnl.in2p3.fr).
file name ? TSCV_thick
sbgat222 55:

sbgat222 51: ./newaction
You are about to create the description of a new action table.
You will be prompted for the description of this new action.
At any time, you can enter h for help, c to cancel.
Use ./newaction -h for a list of options.
If you are borred by this message, use the -q option ;-)
We need a name for your new action.
It is a string, 32 characters max.
For example: fabinfo, or modulexvalidation.
Don't use special character like _ , ; : or space!
action name ? TSCint

Give a version name for this action.
It is a string, 32 characters max.
For example: 1 or withextendedtest.
Create a new version only if the ouput format of the test change.
If the condition of the test change, use the same version
and change the input parameters.
Don't use special character like _ , ; : or space!
action version ? 1

Give the object name to which this action apply.
This name must be in the object description table.
For example: MOD, SEN.
object ? SEN

Give the object type to which this action apply.
This type must be in the object description table.
If the action apply on all types, just it enter.
For example: 1.1.2.
object type ?

Give the object version to which this action apply.
This version must be in the object description table.
If the action apply on all versions, just it enter.
For example: 1.
object version ?

If this action is already defined,
you could add a new set of input parameters.
only input param(y/n) ? n

Give the description of the input parameters.
It is a string that cound contain any characters (max: 255).
The format is a list of comma separated items.
It is a good idea to put the unit into the string.
For example: threshold in mV, cut in dB.
input description: ? bias in V, frequency in MHz, signal_amplitude in mV, C_int_min in pF, C_int_max in pF, delay_time in seconds

Give the value(s) of the input parameters.
It is a string that cound contain any characters (max: 255).
The format is a list of comma separated items.
For example: 13.4, 95.
You could also put a reference to another action tables
by adding an @ to the table name, for example:
@APV_1_FESET_
input values ? 20, 0.1, 100, 0.3, 1.3, 5

Give a comment about this set of input parameters.
It is a string that cound contain any characters (max: 255).
It is a good idea to put a keyword that identifie this set.
input comment ? fixed at CERN on September 24th, 2002

If your new action is a composite action,
enter the number of sub-actions.
If it is a non-composite action, enter 0.
(a composite action consist in a list of sub-actions)
composite ? 0

We need now the description of the result of the action.
It is the description of the columns of the corresponding table.
It must be a valid SQL description of the table (max 2048 chars).
SQL description is a comma separated list of pairs variable/type.
For example: temp float, hygr float, batchid varchar(32), ivcurve blob.
(a blob is a Binary Large OBject, an opaque container)
It could also contain more complex SQL commands like constraints.
output format ? C_int float

Give now the list of the units of the results.
For example: 'degC , percent, number, mA/mV'.
units ? pF

You can now enter a description for this action.
It can be any text up to 2048 characters.
description ? C_int for test structures
You can save all your answers in a file
which you can mail to Didier (contardo@ipnl.in2p3.fr).
file name ? TSCint
sbgat222 52:

sbgat222 52: ./newaction
You are about to create the description of a new action table.
You will be prompted for the description of this new action.
At any time, you can enter h for help, c to cancel.
Use ./newaction -h for a list of options.
If you are borred by this message, use the -q option ;-)
We need a name for your new action.
It is a string, 32 characters max.
For example: fabinfo, or modulexvalidation.
Don't use special character like _ , ; : or space!
action name ? TSRint

Give a version name for this action.
It is a string, 32 characters max.
For example: 1 or withextendedtest.
Create a new version only if the ouput format of the test change.
If the condition of the test change, use the same version
and change the input parameters.
Don't use special character like _ , ; : or space!
action version ? 1

Give the object name to which this action apply.
This name must be in the object description table.
For example: MOD, SEN.
object ? SEN

Give the object type to which this action apply.
This type must be in the object description table.
If the action apply on all types, just it enter.
For example: 1.1.2.
object type ?

Give the object version to which this action apply.
This version must be in the object description table.
If the action apply on all versions, just it enter.
For example: 1.
object version ?

If this action is already defined,
you could add a new set of input parameters.
only input param(y/n) ? n

Give the description of the input parameters.
It is a string that cound contain any characters (max: 255).
The format is a list of comma separated items.
It is a good idea to put the unit into the string.
For example: threshold in mV, cut in dB.
input description: ? bias in V, Start_Voltage_acr in V, Stop_Voltage_acr in V, Step in V, R_int_min in MOhm, delay_time in seconds

Give the value(s) of the input parameters.
It is a string that cound contain any characters (max: 255).
The format is a list of comma separated items.
For example: 13.4, 95.
You could also put a reference to another action tables
by adding an @ to the table name, for example:
@APV_1_FESET_
input values ? 20, -2, 2, 0.2, 1000, 1

Give a comment about this set of input parameters.
It is a string that cound contain any characters (max: 255).
It is a good idea to put a keyword that identifie this set.
input comment ? fixed at Vienna on June 7th, 2002

If your new action is a composite action,
enter the number of sub-actions.
If it is a non-composite action, enter 0.
(a composite action consist in a list of sub-actions)
composite ? 0

We need now the description of the result of the action.
It is the description of the columns of the corresponding table.
It must be a valid SQL description of the table (max 2048 chars).
SQL description is a comma separated list of pairs variable/type.
For example: temp float, hygr float, batchid varchar(32), ivcurve blob.
(a blob is a Binary Large OBject, an opaque container)
It could also contain more complex SQL commands like constraints.
output format ? R_int float, Voltage varchar(4000), I_inter varchar(4000)

Give now the list of the units of the results.
For example: 'degC , percent, number, mA/mV'.
units ? MegaOhm, V, pA

You can now enter a description for this action.
It can be any text up to 2048 characters.
description ? R_int for test structures
You can save all your answers in a file
which you can mail to Didier (contardo@ipnl.in2p3.fr).
file name ? TSRint
sbgat222 53:

sbgat222 51: ./newaction -v
You are about to create the description of a new action table.
You will be prompted for the description of this new action.
At any time, you can enter h for help, c to cancel.
Use ./newaction -h for a list of options.
If you are borred by this message, use the -q option ;-)
We need a name for your new action.
It is a string, 32 characters max.
For example: fabinfo, or modulexvalidation.
Don't use special character like _ , ; : or space!
action name ? TSIVdielectric

Give a version name for this action.
It is a string, 32 characters max.
For example: 1 or withextendedtest.
Create a new version only if the ouput format of the test change.
If the condition of the test change, use the same version
and change the input parameters.
Don't use special character like _ , ; : or space!
action version ? 1

Give the object name to which this action apply.
This name must be in the object description table.
For example: MOD, SEN. br>object ? SEN

Give the object type to which this action apply.
This type must be in the object description table.
If the action apply on all types, just it enter.
For example: 1.1.2.
object type ?

Give the object version to which this action apply.
This version must be in the object description table.
If the action apply on all versions, just it enter.
For example: 1.
object version ?

If this action is already defined,
you could add a new set of input parameters.
only input param(y/n) ? n

Give the description of the input parameters.
It is a string that cound contain any characters (max: 255).
The format is a list of comma separated items.
It is a good idea to put the unit into the string.
For example: threshold in mV, cut in dB.
input description: ? bias in V, start in V, stop in V, step_size in V, V_break_min in V, current_max_at_120V in nA, delay_time in seconds

Give the value(s) of the input parameters.
It is a string that cound contain any characters (max: 255).
The format is a list of comma separated items.
For example: 13.4, 95.
You could also put a reference to another action tables
by adding an @ to the table name, for example:
@APV_1_FESET_
input values ? 1, 0, -200, -10, 120, 10, 1

Give a comment about this set of input parameters.
It is a string that cound contain any characters (max: 255).
It is a good idea to put a keyword that identifie this set.
input comment ? fixed at Vienna on June 7th, 2002

If your new action is a composite action,
enter the number of sub-actions.
If it is a non-composite action, enter 0.
(a composite action consist in a list of sub-actions)
composite ? 0

We need now the description of the result of the action.
It is the description of the columns of the corresponding table.
It must be a valid SQL description of the table (max 2048 chars).
SQL description is a comma separated list of pairs variable/type.
For example: temp float, hygr float, batchid varchar(32), ivcurve blob.
(a blob is a Binary Large OBject, an opaque container)
It could also contain more complex SQL commands like constraints.
output format ? I_diel_mean float, V_break_mean float, Number_of_bad_strips number, Position_of_bad_strips varchar(20), voltage varchar(4000), Idiel_strip1 varchar(4000), Idiel_strip2 varchar(4000), Idiel_strip3 varchar(4000), Idiel_strip4 varchar(4000), Idiel_strip5 varchar(4000), Idiel_strip6 varchar(4000)

Give now the list of the units of the results.
For example: 'degC , percent, number, mA/mV'.
units ? nA, V, numbers, numbers, V, nA, nA, nA, nA, nA, nA

You can now enter a description for this action.
It can be any text up to 2048 characters.
description ? IV Dielectric for test structures
You can save all your answers in a file
which you can mail to Didier (contardo@ipnl.in2p3.fr).
file name ? TSIVDielectric
sbgat222 52:

The actions have a conformity flag, for instance the action TSIVDielectric has a  conformity flag named TSIVDielectric_val. The meaning of the flags in the same for all TSactions and is the following:

maintained by Pierre Juillot