Home

Manual - LINSSI

1. calibrationLibraries Field Type Length Flags idCalibrationLibrary int 4 PN nuclideld varchar 10 PIN idCalLine int 4 PN calLineEnergy double 8 uncCalLineEnergy double 8 emissionProb double 8 uncEmissionProb double 8 halflife double 8 halflifeUnit varchar 8 uncHalflife double 8 calibrationLibraryld varchar 20 comments text 0 end of table This table contains gamma line data for calibration samples Even though these data are fundamental constants and thus one library should suffice the table includes a possibility for multiple libraries This may be advantageous for different calibration purposes where the useful gamma lines may differ Due to limited number of calibration sources available in a laboratory this table should not become too big This is further emphasized by the fact that unlike identification libraries a calibration library usually contains data of the prominent gamma lines only idCalibrationLibrary Identification number of the library nuclideld idCalLine calLineEnergy uncCalLineEnergy emissionProb uncEmissionProb halflife halflifeUnit Name of the calibration nuclide The adopted syntax for nuclideld is Ba 137m where m n o denote metastable states of in creasing energy If metastable state energies are not known a b c may be used Note that analysis software may use differ ent naming conventions It is up to the
2. activityLimits Field Type Length Flags nuclideld varchar 10 PN idAnalysis int 4 PIFN idMeas int 4 IFN idSample int 4 IFN energyPriLine double 8 area double 8 uncArea double 8 baselineArea double 8 uncBaselineArea double 8 decisionLimit double 8 detectionLimit double 8 mda double 8 mdc double 8 significance double 8 significanceFlag char 1 comments text 0 idAnalysis analyses idAnalysis idMeas measurements idMeas idSample samples idSample end of table There are many methods to calculate minimum detectable activities MDA and the manual of the software performing the analysis should always be consulted for exact meaning of the fields below It should be noted that the peak area may be based on the peak actually found in peak analysis or its calculation may have been forced by the MDA algorithm itself It is also possible that background peaks or interfering nuclides have been taken into account in the process of defining the peak and baseline areas nuclideld idAnalysis idMeas idSample Name of the nuclide for which this MDA is calculated Note this nuclide does not need to be a nuclide identified in the spectrum For identified nuclides more data can be found in table 8 5 activities For syntax see table 4 3 calibrationLibraries Identification number of the analysis See table 8 1 analyses Identification number of the measurement See table 6 8 measurement
3. 7 1 sampleSplitsCombines 7 samples parentldSample a idSample daughterldSample 12 measurementSetups 8 sources idSample sourceld 10 attenuators attenuatorld 11 shields 9 detectors detectorld firstNuclideld secondNuclideld blankldAnalysis backgroundldAnalysis inputldAnalysis 22 finalResults idAnalysis idMeas idSample 14 1 calPreferences idAnalysis measSetupld inputldCal 15 calPoints 14 calibrations Figure 1 3 Table lay out of the Linssi restaurant Minimum detectable activities and other activity limits are stored in table 20 and activity ratios for relevant nuclides in table 21 Finally the reviewed final results are stored in table 22 This table contains analysts comments and pointers to the best analysis results It should be emphasized that a sample can be measured multiple times and that the resulting spectra can be also analyzed any number of times The results of all measurements and analyses can be stored in the database 1 4 Tables In the following chapters each database table is described in detail This is done in the form of a table followed by explanation of the independent fields In the table header we show first the name of the database table The column Field gives the name of the database column The column Type defines the data type of the field i e whether it is character integer float etc The column Length gives the maximum siz
4. Barcode on the sample Sample package seal number Description of sample condition on arrival to measuring facility Description of sample package condition on arrival to measuring facility Description of sample package seal condition on arrival to measuring facility Sample condition flag on arrival to measuring facility The values of this flag are facility dependent Date and time of sample arrival to measuring facility Name of the person who received the sample Timestamp of entering this record to the database Comments in English en 39 6 2 Splitting and Combining Samples Table 6 2 Splitting and combining samples sampleSplitsCombines Field Type Length Flags parentIdSample int 4 PIFN daughterIdSample int 4 PIFN activityBranching double 8 method varchar 20 comments text 0 parentIdSample gt samples idSample daughterldSample samples idSample end of table A sample may be formed by splitting and combining other samples In many cases it is enough to know simple sample properties i e its history is irrelevant However if we want to know how the sample has been formed from other samples it can be tracked with table sampleSplitsCombines This table is used together with table 6 1 samples where Boolean fields split and combine tell how the sample is formed Note that those fields are useful but not absolutely necessary for tracking parents and d
5. This table aims to describe the attenuator to the extent sufficient for Monte Carlo simulation of the measuring process when used together with the rest of the measurement setup attenuatorId A unique name of the attenuator comments Comments in English en 44 6 6 Shields Table 6 6 Shields shields Field Type Length Flags shieldId varchar 20 PN comments text 0 end of table This table describes shieldings used in measurements This table aims to describe the shielding to the extent sufficient for Monte Carlo simulation of the measuring process when used together with the rest of the measurement setup shieldId A unique name of the shield comments Comments in English en 45 6 7 Measurement Setups Table 6 7 Measurement setups identify the components used in the setups and their positions measurementSetups Field Type Length Flags measSetupld varchar 40 PN detectorld varchar 40 F sourceld varchar 40 F attenuatorld varchar 40 F shieldId varchar 40 F idCal int 4 F blankIdAnalysis int 4 F backgroundIdAnalysis int 4 F sampleDistX double 8 sampleDistY double 8 sampleDistZ double 8 attenDistX double 8 attenDistY double 8 attenDistZ double 8 shieldDistX double 8 shieldDistY double 8 shieldDistZ double 8 comments text 0 detectorld detectors detectorld sourceld
6. idSample samples idSample end of table Identified nuclides and their raw activities are stored in this table The table contains activities calculated using only the primary lines and the activities where all found peaks of the nuclides are used in the least squares LSQ sense The interfering nuclides may have been resolved during the process There is also a field for off line calculated raw activity If the contributions from blank and background are known see table 8 2 peaks their contribution 73 has been subtracted i e peaked background subtraction PBS has been applied to all activities The decay correction factors for evaluation of the nuclide activity at specific dates and times from the raw activities can also be stored If the decay chain is in equilibrium these factors have been calculated using the effective half lives of the nuclides In the case of a decay chain not in equilibrium the effective half lives cannot be used Even in this case the given correction factors can be used to obtain the decay corrected activities The user should however consult the analysis software manual to find out whether the assumption of equilibrium has been applied or not Since the correction factors are cumulative it would be tempting to calculate the total uncertainty from the uncertainties of the individual factors using the normal error propagation law of Gauss However since the decay corrections are strongly correlate
7. idcEventCs137Present idcEventTimesCs137InMonth test comments List of activation products quantified by the IDC including their half lives concentrations Bq m and absolute one sigma of uncertainties of concentrations For the exact format see RLR g_IDCActivitySummary List of fission products quantified by the IDC including their half lives concentrations Bq m and absolute one sigma of uncertainties of concentrations For the exact format see RLR g_IDCActivitySummary Activation products present in the sample Y N See RLR g_IDCEventScreeningF lags Number of days since last activation product seen See RLR g_IDCEventScreeningF lags Only one fission product in the sample Y N See RLR g_IDCEventScreeningF lags Number of days since last fission product seen See RLR g_IDCEventScreeningF lags Two or more fission products in the sample Y N See RLR g_IDCEventScreeningF lags Number of days since two or more fission products seen See RLR g_IDCEventScreeningF lags Cs 137 present in the sample Y N See RLR g_IDCEventScreeningF lags Number of times Cs 137 was seen in the last 30 days See RLR g_IDCEventScreeningF lags Type of test performed See RLR Test Comments in English en 30 5 2 CTBT Transports Table 5 2 CTBT transports ctbt Transports Field Type Length Flags idSample int 4 PFN transportOutId Boolean 1 PN idRecipient int 4 F couri
8. In no event will the authors be liable for any damages including any lost profits lost savings or other incidental or consequential damages arising out of the use or inability to use the program even if authors representative has been advised of the possibility of such damages or for any claim by any other party MySQL is a trademark of MySQL AB SHAMAN is a trademark of Baryon Oy SAMPO MICROSAMPO and SAMPO 90 are trademarks of Logion Oy Other trademarks are the property of their respective owners Any data may be defined in one place only If data are defined in more places they will diverge it will not stay the same if it ever was If data are changed while not in one place only you never know whether you changed every instance However you need a method document control that assures that all places where the changed data is referenced from are informed of any change Relational databases use this principle The same applies to software every function should be defined only once it would have made the millennium problem a piece of cake Niels R Malotaux Contents Introduction el Me nee nase bunten hen 1 2 The Database System oo c za sa 2 san an ER 2 4 1 3 A Stroll between the Tables o oc cocca CE m mn Lal Tall A A A SY A OY A OARS AS A Le Units and Default Vall co 64 4 4 SH KPA da a Shan ehe Stations 21 Eee 2 2 Mobile Coordinates ooo aaa a a a a 23 Wea ooa aene e ee a Oo PR ie ee Air Filt
9. SOURCE to obtain the final results Note that only the last calibration is used to calculate the final results i e usedInAnalysis will be TRUE for that calibration only However after the analysis at the latest all the three above mentioned calibrations are stored in Linssi For information about the class field see table 7 1 calibrations idCal Identification number of the full calibration The full calibration consists of multiple calibrations identified by idCal calTypeld pairs See table 7 1 calibrations idAnalysis Identification number of the analysis which has used or has con sidered to use this calibration See table 8 1 analyses usedInAnalysis TRUE if this is the calibration on which the analysis results are based on comments Comments in English en 59 7 4 Calibration Types Each complete calibration idCal in Linssi consists of calibrations of more than one param eter of the measurement setup Calibrations of these individual parameters are identified by the calibration type identifiers calTypeld in tables 7 1 calibrations The exact mean ing and support of each calibration type depends on the analysis software The currently reserved calibration types are described below 7 4 1 Peak Shape Calibrations The current version of Linssi reserves the following calTypeld s for Gaussian peak shape with extended exponential tails and a baseline step width lowTail highTail lowTailExp highTailExp and step These
10. a sample when it arrives for measurement This is also the first entry point of the sample to the database i e this record must always be the first record created for the sample In many cases the only information at the time of creation may be the sampleld idSample sampleld phdSampleName extSampleName splitSymbol split combined sampleType A unique auto incrementing identification number of the sample A unique sample identifier This character string follows the naming convention applied by the facility running the database A sample reference identifier SRID string following the naming convention of the CTBTO PTS 6 Even though not required by the database this string is likely to be globally unique A sample identifier string following the naming convention of a cus tomer for the analysis Even though not required by the database this string is meant to be unique A two part Pp split symbol of the sample The symbol is used to identify the descendants of the original sample when it is split for multiple counting and analysis purposes The first half P gives the split number the second half p gives the total number of splits The split identifier is thus 11 for all radionuclide samples before any splitting is performed If for example a sample is split into three parts the parts are assigned the following split identifiers 13 for the first piece 23 for the second piece and 33 for the third piece If all
11. database administrator to ascertain that consistent syntax is used Linssi does not include a comprehensive nuclide reference library Index of the gamma line of the calibration nuclide Sorted in an ascending order of the line energy starting from 1 Energy of the gamma line of the calibration nuclide in kiloelectron volts keV One sigma absolute uncertainty of calLineEnergy in kiloelectron volts keV Absolute emission probability of the gamma line i e number of gammas emitted per decay Absolute one sigma uncertainty of emissionProb Half life of the nuclide in units halflifeUnit Half life unit The supported units are year y or a day d hour h minute m or min and second s 24 uncHalflife Absolute one sigma uncertainty of halflife in units halflifeU nit calibrationLibraryId Name of the calibration library comments Comments in English en 25 26 Chapter 5 CTBT Laboratory Samples 2 stations 7 samples idSample 26 ctbtLabSamples idSample stationSiteCodeld 27 ctbtTransports idSample transportOutld idRecipient sampleProductionTable ctbtLabSamples 28 cibtRecipients 30 ctbtSampleTrackings idSample dateTimelnld 29 ctbtMessages idMessage idSample idAnalysis 16 analyses idAnalysis Figure 5 1 Tables of the CTBT sample production group 26 27 28 29 and 30 and their connection to other Linssi tables 7 and 16 These ta
12. function of time This information is continuous in nature i e not specific to a sample even though idSample is provided in the table in order to facilitate on line following of its sampling In generic terms these three tables are used to describe the sample manufacturing process i e the process whose result is a radioactive sample As such they can be applied also to other type of samples These may include irradiated samples wipe samples soil samples xenon gas samples etc The specific activity production process which here is air filter sampling is denoted by the field sampleProductionTable in table 6 1 samples For the time being the following sampleProductionTable s are supported calibrationSamples airFilterSamples and ctbtLabSamples If the specific tables for your application are not available it is recommended to use the tables for air filter samples If that is out of the question one should start from the entry point 2 i e from table 6 1 samples The terminology used also in other than these three tables reflects somewhat the first application of this database We have however tried to minimize air sampling specific terminology and where it is used its interpretation in the context of other sample types should be obvious Calibration samples are discussed in Ch 4 and CTBT laboratory samples in Ch 5 15 3 1 Samplers Samplers consist of two air channels 1 and 2 where total flow is obtained as a sum of these
13. in table mobileCoordinates The third table of the group weathers gives the weather at the station 2 1 Stations Table 2 1 Stations stations Field Type Length Flags stationld varchar 40 PN stationType varchar 20 isMobile Boolean 1 address varchar 40 telephone varchar 40 location varchar 40 longitude double 8 latitude double 8 altitude double 8 comments text 0 end of table stationld Name of the station stationType Type of the station This is very application dependent May be for example P for particulate station weather for weather station etc isMobile address telephone location longitude latitude altitude comments TRUE if the station is mobile In that case the coordinates of the station can be found in table 2 2 mobileCoordinates Address of the station International telephone number of the station Location of the station Longitude of the stationary station Latitude of the stationary station Altitude of the stationary station Comments in English en 10 2 2 Mobile Coordinates Table 2 2 Mobile coordinates of stations mobileCoordinates Field Type Length Flags idPosition int 4 PN positionSource varchar 20 PN stationld varchar 40 PN idSample int 4 F idMeas int 4 F positionType varchar 10 positionTime datetime 8 m
14. multiple analysis results identified by idAnalysis for any measurement without overwriting the earlier ones This facilitates either a fully auto matic pipeline in an once through fashion or an iterative approach where the earlier results are used as a starting point for further interactive or automatic processing The best results are then identified in table 8 8 finalResults 8 1 Analyses Table 8 1 General data on peak analysis analyses Field Type Length Flags idAnalysis int 4 PA idMeas int 4 IFN idSample int 4 IFN blankIdAnalysis int 4 FS backgroundIdAnalysis int 4 FS inputIdAnalysis int 4 FS spectrumArrival datetime 8 analysisBegin datetime 8 analysisEnd datetime 8 inputParam text 0 interactiveLog text 0 continued on next page 61 continued from previous page Field Type Length Flags type varchar 20 software varchar 20 swVersion varchar 80 analyst varchar 20 baseline longblob 0 strippedSpectrum longblob 0 peakSearchSignificance longblob 0 refTimel datetime 8 decayTimel double 8 refTime2 datetime 8 decayTime2 double 8 refConstants text 0 baselineMethod text 0 peaksMethod text 0 nuclideMethod text 0 uncCalcMethod text 0 1cMethod text 0 alpha double 8 beta double 8 searchStartChannel mediumint 3 searchEndChannel mediumint 3 searchThreshold d
15. no measurement setup referring to this calibration any more SOH A State Of Health calibration update generated by the spec trum analysis software FIT A new fit to the calibration points by the spectrum analysis software 52 description creationTime callnfo calCertificate function functionDef startOfRange end0fRange pari par2 par3 part par5 par6 par pars par9 par10 uncPari uncPar2 uncPar3 uncPar4 uncParb uncPar6 uncPar7 uncPar8 uncPar9 uncPar10 comments SOURCE A corrected calibration due to source geometry That is the spectrum analysis software has made a correction to the cal ibration based on the differences in the measuring geometry be tween the source defined in the measurement setup and that actu ally measured The correction may include source self attenuation correction source volume correction source distance correction etc For the corrections actually performed the software documentation must be consulted An identifier given by the analyst to the calibration possibly unique not required Date and time of creation of the calibration Note A valid date and time must be given If old calibrations are searched for this field is needed as an identifier Free form description of the calibration by the analyst Calibration certificate block as described in Ref 6 This is an alternative certificate of the calibration The preferred method is described in Ch 4 If both methods
16. of multiple calibrations identified by idCal calTypeld pairs See table 7 1 calibrations Name of the type of calibration See Ch 7 4 for discussion of the reserved calTypeld s Identification number of the analysis used for this calibration point See table 8 1 analyses Identification number of spectrum peak for this calibration point See table 8 2 peaks Channel or energy keV for efficiency calibration of the calibration point Value of the calibrated parameter at xValue The one sigma absolute uncertainty of the yValue Comments in English en 54 7 3 Calibration Preferences Table 7 3 Calibration preferences calPreferences Field Type Length Flags idCal int 4 PIFN idAnalysis int 4 PIFN usedInAnalysis Boolean 1 N idCal calibrations idCal idAnalysis analyses idAnalysis end of table This table provides many to many relationships between analysis results and calibrations A single full calibration idCal may of course be used in many analyses idAnalysis It is also possible that a single analysis takes advantage of many calibrations For illustration the analysis software may receive a calibration with the spectrum class PHD but the analyst selects to use the default calibration for the measurement setup in question class SETUP Finally the software finetunes the calibration for source geometry differences and uses the adjusted calibration class
17. of the sampler used See table 3 1 samplers stationld This is the identifier of the station where the sampling has been performed See table 2 1 stations collStart Date and time of the start of collection collEnd Date and time of the end of collection collTime Collection time in seconds s samplerOnTime Time the sampler was on during collection in seconds s airVolumeTotal Total air volume sampled through the filter s in cubic meters m airVolumel Air volume sampled through channel 1 in cubic meters m presDiffiStart Air pressure difference in pascals Pa over the flow rate meter in channel 1 at collStart presDiffiEnd Air pressure difference in pascals Pa over the flow rate meter in channel 1 at collEnd airVolume2 Air volume sampled through channel 2 in cubic meters m 18 presDiff2Start presDiff2End sampleSent correctedToNTP comments Air pressure difference in pascals Pa over the flow rate meter in channel 2 at collStart Air pressure difference in pascals Pa over the flow rate meter in channel 2 at collEnd Date and time the sample was sent for measurement If TRUE air volumes are corrected to Normal Temperature and Pressure NTP i e corrected to 20 C and 101 325 0 Pa Comments in English en 19 20 Chapter 4 Calibration Samples 23 calibrationSamples 24 calibrationNuclides idSample nuclideld idCalibrationLibrary 7 samples idSample sampleProduction
18. parameters are given as a function of channel in Linssi For exact meaning of the parameters see UNISAMPO SHAMAN and Aatami manuals 1 2 7 7 4 2 Energy Calibration For energy calibration of photopeak centroids calTypeId energy is reserved Here energy is given in kiloelectronvolts keV as a function of channel 7 4 3 Efficiency Calibration For detector efficiency calibration two calTypeld s are reserved efficiency for the photo peak efficiency and totalEfficiency for the total efficiency of the detector Both efficiencies are defined as a function of energy in kiloelectronvolts keV The efficiencies are absolute and describe the full measurement setup 7 5 Calibration Functions In Linssi the measurement setup calibration functions are used in tables 7 1 calibrations The functions are fitted to points given in table 7 2 calPoints In the functions the depen dent variable y is defined as a function of one independent variable x with varying number of fitted parameters a x is given either in kiloelectronvolts keV for efficiency calibra tion or in channels for all other calibration functions The fitted parameters are stored in par1 par10 and their uncertainties in uncPar1 uncPar10 There are two ways of defining the calibration functions In the first method a set of pre defined functions is used That is indicated by a non zero value of the field function The second method involves storing the function definition in Mat
19. sample Manufacturer serial number of the calibration sample Name of the manufacturer Receipt date and time of the calibration sample Overall activity of the calibration sample at receiptTime This value is NOT certified Comments in English en 22 4 2 Calibration Nuclides Table 4 2 Calibration nuclides calibrationNuclides Field Type Length Flags idSample int 4 PIFN nuclideld varchar 10 PIFIN idCalibrationLibrary int 4 F1 activity double 8 uncActivity double 8 assayTime datetime 8 comments text 0 idSample samples idSample nuclideld idCalibrationLibrary calibrationLibraries nuclideld idCalibrationLibrary end of table This table contains information of the activity content of each nuclide of the calibration sample idSample Identification number of the calibration sample See table 6 1 sam ples nuclideld Name of the calibration nuclide See table 4 3 calibrationLi braries idCalibrationLibrary Identification number of the library of nuclear data for calibration nuclides See table 4 3 calibrationLibraries activity Certified activity of the nuclide in Becquerels Bq uncActivity One sigma absolute uncertainty of activity in Becquerels Bq assayTime The assay date and time of the nuclide i e the date and time of the activity comments Comments in English en 23 4 3 Calibration Libraries Table 4 3 Calibration libraries
20. sampleCondFlagArrival There are special conventions applicable to keys only Other fields are not allowed to use the syntax of keys The rules are 1 The keys of type integer have the prefix id e g idSample 2 The keys of non integer type end with Id e g sampleld 3 The name of the foreign keys must be identical to the corresponding primary keys There are some exceptions where this is not feasible e Self reference A record may contain a key pointing to another record of the same table In this case the key name is formed from the primary key by adding a prefix E g the key blankIdMeas is this way formed from the primary key idMeas e Multiple foreign keys A record may have multiple foreign keys pointing to the same primary key The prefixing is again used e g two nuclides pointing to the primary key nuclideld are firstNuclideld and secondNuclideld 4 The name of a unique non integer field with one to one correspondence with the pri mary integer key of the table is formed by moving the prefix to the end of the name e g from the primary idSample we get the name sampleld for the unique field If the primary key and the unique field are both integers or non integers the name of the unique field must be formed by prefixing We see no reason for them being of the same type however Note that in MySQL the names of the tables are case sensitive whereas the names of the fields are not In Linssi the field names are unique re
21. sampled in standard cubic meters m3 See RLR Collection Purpose of the analysis See RLR Objective Free text describing the tests authorized See RLR Objective Free text describing any special instructions See RLR 0bjective Activity category of the sample according to international shipping regulations See RLR StationSample Sample diameter or length in millimeters mm See RLR StationSample Sample thickness in millimeters mm See RLR StationSample Sample width in millimeters mm See RLR StationSample Sample mass g See RLR StationSample Sample container density g cm See RLR StationSample Sample container thickness in millimeters mm See RLR StationSample Sample container material See RLR StationSample Sample geometry description See RLR StationSample Mass of the split that gets to the lab See RLR Split Air volume of the split that gets to the lab See RLR Split Split method of the split that gets to the lab See RLR Split List of nuclides identified but not quantified by the IDC See RLR g_IDCActivitySummary List of natural nuclides quantified by the IDC including their half lives concentrations Bq m and absolute one sigma of uncertainties of concentrations For the exact format see RLR g_IDCActivitySummary 29 idcActProd idcFissProd idcEventActProdPresent idcEventDaysSinceLastAct idcEventOnlyOneFP idcEventDaysSinceLastFP idcEventMultFP idcEventDaysSinceLastMult
22. sources sourceld attenuatorld attenuators attenuatorld shieldId shields shieldId idCal calibrations idCal blankIdAnalysis analyses idAnalysis backgroundIdAnalysis analyses id Analysis end of table The Cartesian right hand coordinate system used here has its origin at the center of the detector s active front face window on its outer surface The positive z axis points outwards of the detector Ifthe z axis is horizontal the y axis is vertical and points upwards Otherwise the y axis is parallel to the plane of maximum possible symmetry and points outwards of the center of the detector system Sample attenuator and shield coordinate axes are parallel to the coordinate axes defined here but their origins are offset as described below The description of the measurement setup is meant to be accurate enough for Monte Carlo simulation of the measurements measSetupld Unique name of the measurement setup detectorld See table 6 4 detectors sourceld See table 6 3 sources 46 attenuatorld shieldld idCal blankIdAnalysis backgroundIdAnalysis sampleDistX sampleDistY sampleDistZ attenDistX attenDistY attenDistZ shieldDistX shieldDistY shieldDistZ comments See table 6 5 attenuators See table 6 6 shields Identifies the correct calibration to be used with this setup Note each setup may have multiple calibrations but there is only one that is the best See table 7 1 c
23. text 0 idMeas measurements idMeas idSample samples idSample idAnalysis idPeak analyses idAnalysis idPeak end of table Line association results are stored in this table For each gamma line of each identified nuclide in a single analysis there may be at maximum one spectrum peak associated with it At maximum since small library lines may not be visible in the spectrum Put it the other 70 way round for each spectrum peak there may be any number of library lines associated with it It is not necessary for each gamma line to be associated with a spectrum peak These lines have been used by the analysis software to support in nuclide identification For unidentified spectrum peaks idLine is 0 and nuclideIdisNO_ID1 NO_ID2 NO_ID3 idAnalysis nuclideld idLine idPeak idMeas idSample lineEnergy uncLineEnergy emissionProb uncEmissionProb CCfactor uncCCfactor lineSignificance explLevel lorentzGamma xray background annihilation singleEscape doubleEscape xrayEscape Identification number of the analysis See table 8 1 analyses Name of a nuclide If identified the LSQ activity of this nu clide is based on the line s in this table for which the idPeak is not null See table 8 5 activities For syntax see table 4 3 calibrationLibraries If not identified see idLine below Index of the nuclide line starting from 1 This is a unique internal number for nuclide line given by the
24. 5 2 MathML presentation of the functions 7 5 3 MathML support in SHAMAN 8 Analysis 8 1 Analyses III A il ne do oe o ee ee ee ee ee oe a e 3 3 Line Associations coso 3 eaa a 39 ION LUIS ee a AS Bea SO Wien Bi a a mann dan dw ee ew Bit Final Analysis Results o o 4 A A need 8 4 Nuclides and Their Activities Bibliography A Naming Conventions iv 51 ol 54 59 56 56 56 56 56 56 58 58 61 61 65 70 73 78 80 82 83 85 Chapter 1 Introduction 1 1 History Development of a database system to support the analyses of gamma ray spectra from the International Monitoring System IMS for the verification of the Comprehensive Nuclear Test Ban Treaty CTBT was started at the Finnish National Data Centre FINDC situated at the Finnish Nuclear and Radiation and Safety Authority STUK together with the Ra diation Physics Group of Helsinki University of Technology HUT in summer 2002 Before that there had been an analysis pipeline for CTBT spectra in continuous operation for three years already That pipeline based on UNISAMPO 1 and SHAMAN 2 software is still operational and has analyzed hundreds of thousands spectra The storage and retrieval of spectra and results have been based on a hierarchical file structure and have been successful However the file structure is able to support only simple queries and it was clear from the beginning that once a reasonably priced relational datab
25. 5 3 CTBT Recipients Table 5 3 CTBT recipients ctbtRecipients Field Type Length Flags idRecipient int 4 PA pocName varchar 80 pocPhone varchar 40 pocOrg varchar 80 pocAddr varchar 80 pocEmail varchar 80 pocLocal Boolean 1 comments text 0 end of table For a more precise definition of the fields the user is asked to consult the report IDC3 4 1Rev6 6 to which the descriptions below are referencing The reference LABSDN Recipient refers to the Recipient data block of the LABSDN message giving a notification that a sample has been sent to a laboratory Same data blocks are also used in the TECSDN message giving a notification that a sample has been sent from the laboratory LABSDN and TECSDN mes sages together with their data blocks are described in Chapter Other Laboratory Messages of the report IDC3 4 1Rev6 6 idRecipient Identification number of the recipient pocName Point of contact See LABSDN Recipient pocPhone Point of contact phone number See LABSDN Recipient pocOrg Point of contact organization See LABSDN Recipient pocAddr Point of contact address See LABSDN Recipient pocEmail Point of contact address See LABSDN Recipient pocLocal True if the point of contact is local comments Comments in English en 32 5 4 CTBT Messages Table 5 4 CTBT messages ctbtMes
26. 8 2 Peak analysis results peaks Field Type Length Flags idPeak int 4 PN idAnalysis int 4 PIFN idMeas int 4 IFN idSample int 4 IFN centroidChannel double 8 uncCentroidChannel double 8 energy double 8 uncEnergy double 8 area double 8 uncArea double 8 height double 8 width double 8 fwhm double 8 fwtm double 8 lowTail double 8 highTail double 8 lowTailExp double 8 highTailExp double 8 step double 8 netCountRate double 8 uncNetCountRate double 8 efficiency double 8 uncEfficiency double 8 searchSignificance double 8 significance double 8 significanceFlag char 1 decisionLimit double 8 detectionLimit double 8 outOfRange Boolean 1 peakOrigin varchar 20 ROIstart int 4 ROTend int 4 ROlarea double 8 ROlindex mediumint 3 baselineArea double 8 baselinePerChannel double 8 uncBaselinePerChannel double 8 baselineStart mediumint 3 baselineEnd mediumint 3 baselineParami double 8 continued on next page 65 continued from previous page Field Type Length Flags baselineParam2 double 8 baselineParam3 double 8 baselineParam4 double 8 emissionRate double 8 uncEmissionRate double 8 backgroundCps double 8 uncBackgroundCps double 8 backgroundType varchar 20 blankCps double 8 uncBlankCps double 8 blankType varchar 20 commen
27. Aatami 7 has been adopted for the peak origin flags The available flags are shown in Tab 8 3 The syntax requires that two flags from each of the four groups are given and the order shown in the table is followed However the second flag of the first group is always blank Thus a peak found using Mariscotti peak search fitted using Full fit keeping the centroid fixed area also calculated with Full fit but of course keeping its value free and taking the FWHM from peak shape calibration and thus keeping its value fixed in last fitting would read M FOF1CO 68 1 Peak finding source flags one flag and a blank Flag Explanation Artificial peak Background peak External Mariscotti peak search Residual peak search stripped spectrum Manually inserted in certain channel Manually inserted in library position Library inserted multiplet fitting Inserted by natural radionuclide model Inserted by summation peak model yi a z o HS gt Centroid source flags 2 flags a amp ge Explanation Quick fit Full fit User defined External software Multiplet fitting Mariscotti center of gravity Converted library energy Tight fitting Fixed in last fitting Free in last fitting wl o 4 zoll Cc So Net area source flags 2 flags ea amp ge Explanation Quick fit Full fit Us
28. English en 50 Chapter 7 Calibration Data and Functions 7 1 Calibrations Table 7 1 Calibrations calibrations Field Type Length Flags idCal int 4 PIN calTypeld varchar 20 PIN measSetupld varchar 40 F inputIdCal int 4 FS changed Boolean 1 class varchar 20 description varchar 40 creationTime datetime 8 N callnfo text 0 calCertificate text 0 function smallint 2 functionDef text 0 startOfRange double 8 endOfRange double 8 pari double 8 par2 double 8 par3 double 8 par4 double 8 par5 double 8 par6 double 8 par7 double 8 par8 double 8 par9 double 8 par10 double 8 uncPari double 8 uncPar2 double 8 uncPar3 double 8 continued on next page 51 This table gives the calibration description and the fitted calibration function Calibration data points can be found in table 7 2 calPoints Note that in a single analysis multiple different calibrations energy efficiency width tail etc are needed All these calibrations are given in this table and separated from each other by calTypeld Calibrations with a continued from previous page Field Type Length Flags uncPar4 double 8 uncPar5 double 8 uncPar6 double 8 uncPar7 double 8 uncPar8 double 8 uncPar9 double 8 uncPar10 double 8 comments text 0 measSetupld measurementSetups measSetupl
29. Helsinki University of Technology Publications in Engineering Physics A Teknillisen korkeakoulun teknillisen fysiikan julkaisuja A Espoo 2006 TKK F A841 LINSSI SQL DATABASE FOR GAMMA RAY SPECTROMETRY PART I DATABASE Version 1 1 Pertti Aarnio idAnalysis idPeak idMeas ineEnerg 237 563 26 237 569 29 237 Cs134 6 25 121 12 604 66 237 661 62 237 795 76 X TEKNILLINEN KORKEAKOULU HELSINKI UNIVERSITY OF TECHNOLOGY Helsinki University of Technology Publications in Engineering Physics A Teknillisen korkeakoulun teknillisen fysiikan julkaisuja A Espoo 2006 TKK F A841 LINSSI SQL DATABASE FOR GAMMA RAY SPECTROMETRY PART I DATABASE Version 1 1 Pertti Aarnio Helsinki University of Technology Department of Engineering Physics and Mathematics Laboratory of Advanced Energy Systems Teknillinen korkeakoulu Teknillisen fysiikan ja matematiikan osasto Energiateknologiat Database and Software 2005 2006 Pertti Aarnio Jarmo Ala Heikkil Arto Isolankila Antero Kuusi Mikael Moring Mika Nikkinen Teemu Siiskonen Harri Toivonen Kurt Ungar Weihua Zhang Helsinki University of Technology Radiation Physics Group Finnish Radiation and Nuclear Safety Authority 3Health Canada Radiation Protection Bureau Manual 2004 2006 2007 Pertti Aarnio Distribution Helsinki University of Technology Laboratory of Advanced Energy Systems P O Box 4100 FI 02015 TKK ISBN 951 22 8148 8 IS
30. MAN Expert System for Radionuclide Identification version 1 13 User s Guide version 1 8 Baryon Oy Ltd Espoo Finland May 28 2004 http www mysql com Linssi SQL Database for Gamma Ray Spectrometry Part II SCRIPTS AND INTER FACES Helsinki University of Technology Espoo Finland draft available upon request Le Systeme international d unit s SI 7e edition 1998 Organisation intergouvernemen tale de la Convention du M tre Stedi Paris ISBN 92 822 2154 7 Formats and Protocols for Messages IDC 3 4 1 Revision 6 IDC Documentation User Manual of Radionuclide Analysis and Evalution Software Aatami version 3 04 Comprehensive Nuclear Test Ban Treaty Organization Office of the Executive Secretary Evaluation Section Vienna 2003 Mathematical Markup Language MathML Version 2 0 Second Edition W3C Recom mendation 21 October 2003 http www w3 org TR 2003 REC MathML2 20031021 Extensible Markup Language XML 1 0 Second Edition W3C Recommendation 6 October 2000 http www w3 org TR 2000 REC xm1 20001006 10 XML Input for Expert System Shaman User s Guide version 1 0 Baryon Oy Ltd Espoo Finland 2003 83 84 Appendix A Naming Conventions The table and field column names are written in lower case e g stations If a name is composed of multiple words the words are separated by capitalizing their first letters e g sampleType To avoid excessive length the names may be abbreviated e g
31. N idSample int 4 IFN firstIsDaughter Boolean 1 secondIsDaughter Boolean 1 firstHalflife double 8 uncFirstHalflife double 8 secondHalflife double 8 uncSecondHalflife double 8 halflifeUnit varchar 8 netBranching double 8 uncNetBranching double 8 refRatio double 8 uncRefRatio double 8 zeroRatio double 8 uncZeroRatio double 8 refTime datetime 8 zeroTime datetime 8 uncZeroTimeLow double 8 uncZeroTimeHigh double 8 comments text 0 idMeas measurements idMeas idSample samples idSample idAnalysis firstNuclideld activities idAnalysis nuclideld idAnalysis secondNuclideld activities idAnalysis nuclideld end of table This table contains the information of activity ratios of nuclide pairs that facilitates calcu lation of the birth time of activity zeroTime The nuclides may belong to the same decay chain or decay independently If they decay independently it is of course necessary to have priori information on their relative yields zeroRatio at time zero idAnalysis firstNuclideld secondNuclideld idMeas idSample firstIsDaughter Identification number of the analysis See table 8 1 analyses Name of the first nuclide See table 8 5 activities Name of the second nuclide See table 8 5 activities Identification number of the measurement See table 6 8 measurements Identification number of the sample measured See table 6 1 samples The first nuclide follows the sec
32. SN 1456 3320 For the latest version of this manual see http linssi hut fi radphys linssi Information in this document is subject to change without notice and does not represent any commitment on the part of the authors The software described in this document is furnished under a license agreement The user may not copy the software on magnetic or optical tape disk or any other medium for any other purpose than the license holder s personal use Copyright This database and accompanying software and written materials are products of copyright c owners and thereby protected by international copyright laws and treaties You must keep the software package in strict confidence and treat it like any other copyrighted material You may not copy the software or the written materials accompanying the software package except as explicitly allowed by the license The use of the software package must be in strict adherence with the license License License conditions are defined in a separate document that must be consulted Disclaimer of Responsibility for the Software The program is provided as is without warranty of any kind either expressed or implied including but not limited to the implied warranties of merchantability and fitness for a particular purpose The authors do not warrant that the functions contained in the software will meet any requirements or that the operation of the software will be uninterrupted or error free
33. Table calibrationSamples 25 calibrationLibraries idCalibrationLibrary nuclideld idCalLine Figure 4 1 Tables of the calibration sample production group 23 24 and 25 and their connection to other Linssi tables 7 Calibration samples are identified with sampleProductionTable equal to calibrationSam ples in table 6 1 samples Calibration samples are samples with known activity and they are preferably certified The certification is given in the table calibrationSamples the information of the actual nuclides in the sample is given in the table calibrationNuclides and the specific nuclear data in the table calibrationLibraries 4 1 Calibration Samples Table 4 1 Calibration samples calibrationSamples Field Type Length Flags idSample int 4 PFN certificateNumber varchar 20 productCode varchar 20 sourceNumber varchar 20 manufacturer varchar 40 continued on next page 21 idSample certificateNumber productCode sourceNumber manufacturer receiptTime overallAct comments continued from previous page Field Type Length Flags receiptTime datetime 8 overallAct double 8 comments text 0 idSample samples idSample end of table Identification number of the calibration sample See table 6 1 sam ples Certificate number of the calibration sample manufacturer Manufacturer product code of the calibration
34. a laboratory performing gamma ray spectrum analysis can be quite large and very heterogenous It contains everything from the measured spectra to obscure notes on analysts log books Our intention has not been to time gt Entry point 0 Entry point 1 Entry point 2 Entry point 3 Production groups Station group Measurement group Analysis group Figure 1 2 Linssi entry points and major table groups store everything in the Linssi database However the idea has been to include all the relevant information starting from the collection of radioactivity to a sample all the way to the final analysis results and conclusions made by the laboratory experts Clear emphasis has been on the spectrum analysis results and on the information directly affecting the quality of these results The information is meant to be complete enough to allow laboratory certification and thus also to facilitate outside review on the quality of the results based on the information available in the Linssi database In case information not directly available in the database is needed there should be enough pointers in Linssi to identify where the information might be available In most cases that means information on the facility responsible for sample manufacturing and possibly responsible for its measurement The number of fields in the analysis related tables is more than 200 That is quite a lot and we do not expect that they are all needed in eve
35. ak significance The valid values are software dependent in UNISAMPO 0 and 1 Comments in English en Note on specific activity The activities in table 8 5 activities are raw sample activities in Bq There are however cases where sample activities cannot be defined For example an in situ measurement of the surface activity of soil from the distance of 1m above the ground does not give the total surface activity of the globe in Bq In cases like this efficiency calibration must be performed to give directly the specific activity in this case activity per area at the measuring position the unit being Bq m Accordingly the MDA values in the above table refer to the corresponding specific activity In this case distinction between MDA and MDC cannot generally be made and they are thus equal What is the denominator in the unit of the specific activity depends on the specific sample production model and is given in the sample production groups of tables Fig 1 3 In the case where the MDA is real activity in Bq i e not the specific activity these tables also contain the numerical value used to divide the MDA to get the MDC 79 8 6 Nuclide Ratios Table 8 7 Activity ratios of relevant nuclide pairs nuclideRatios Field Type Length Flags idAnalysis int 4 PIF12N firstNuclideld varchar 10 PFIN secondNuclideld varchar 10 PF2N idMeas int 4 IF
36. alculate a new or adjust an existing calibration by comparing the geometry given here with the geometry of the standard setup defined by the source associated with the standard geometry mea surementSetup sourceld See table 6 7 measurementSetups A name of the blank measurement relevant for this sample mea surement This is a unique identifier of the type idMeas pointing to a record in this measurements table A name of the background measurement relevant for this sample measurement This is a unique identifier of the type idMeas point ing to a record in this measurements table A unique measurement name i e this has one to one correspon dence with the primary key idMeas above This name is normally a result of the naming rules applied in the measurement facility A name following the naming rules of the measurement identifica tion MID of the CTBTO 6 Even though not required by the database this name is globally unique across different FULL spec tra However the MID for eventual PREL spectra is identical to that of the FULL spectrum A name of the measurement given or required by the customer This name is normally a result of the naming rules used by the customer This name is most probably unique but it is not required by the database Name of the person who prepared the source Date and time the source was ready for first measurement Detector temperature in degrees centigrade C One sigma absolute uncertainty of the det
37. alibrations Identification number of the analysis of the blank The analysis results of the blank have been used to set up the calibration for this measurement setup Identification number of the analysis of the background The analy sis results of the background have been used to set up the calibration for this measurement setup x component of the offset of the sample origin in millimeters mm y component of the offset of the sample origin in millimeters mm z component of the offset of the sample origin in millimeters mm x component of the offset of the attenuator origin in millimeters mm y component of the offset of the attenuator origin in millimeters mm z component of the offset of the attenuator origin in millimeters mm x component of the offset of the shield origin in millimeters mm y component of the offset of the shield origin in millimeters mm z component of the offset of the shield origin in millimeters mm Comments in English en 47 6 8 Measurements idMeas idSample sourceld Table 6 8 Measurement parameters and results measurements Field Type Length Flags idMeas int 4 PA idSample int 4 IFN sourceld varchar 40 F measSetupld varchar 40 F blankIdMeas int 4 FS backgroundIdMeas int 4 FS measId varchar 80 IUN phdMeasName varchar 80 extMeasName varchar 80 sourcePreparedBy va
38. analysis software It is recom mended that this is the number of the line in the nuclide reference library However for SHAMAN this is an internal index since the properties of coincidence and escape lines are internally calculated in SHAMAN If this index is 0 idPeak has not been identified i e there are no lines associated with it In that case the nuclideld is NO_ID1 NO_ID2 NO_ID3 Identification number of the peak if there is a peak associated with this gamma line Otherwise idPeak is null See table 8 2 peaks This peak has been used in calculation of actRawLSQ Depending on values of actMan and primaryLine this peak has been used also in calculation of actRawMan and actRawPriLine See below Identification number of the measurement See table 6 8 measurements Identification number of the sample measured samples Energy of the gamma line in kiloelectronvolts keV Note this is not the energy of the gamma peak in the spectrum Absolute one sigma uncertainty of lineEnergy Emission probability of the gamma line fraction NOT in One sigma absolute uncertainty of the emission probability True coincidence correction factor of the gamma line One sigma absolute uncertainty of the true coincidence correction factor of the gamma line The significance of the gamma line in units of the detection level La This is the calculated line significance based on the activity of the identified nuclide It gives a measure whether this
39. are used for the same calibra tion they must be consistent Function identifier See Ch 7 5 Function definition See Ch 7 5 Start of the validity range of the calibration function in channels ch or in kiloelectronvolts keV for efficiency calibrations End of the validity range of the calibration function in channels ch or in kiloelectronvolts keV for efficiency calibrations Value of the 1 parameter of the calibration function Value of the 2 parameter of the calibration function Value of the 3 parameter of the calibration function Value of the 4 parameter of the calibration function Value of the 5 parameter of the calibration function Value of the 6 parameter of the calibration function Value of the 7 parameter of the calibration function Value of the 8 parameter of the calibration function Value of the 9 parameter of the calibration function Value of the 10 parameter of the calibration function ncertainty of the 1 parameter of the calibration function ncertainty of the 2 parameter of the calibration function ncertainty of the 3 parameter of the calibration function ncertainty of the 4 parameter of the calibration function ncertainty of the 5 parameter of the calibration function ncertainty of the 6 parameter of the calibration function ncertainty of the 7 parameter of the calibration function ncertainty of the 8 parameter of the calibration function nce
40. ase system becomes available it would be the correct way to handle the increasing amount of information In the summer of 2002 the FINDC made the decision to use MySQL 3 open source relational database As a first step the analysis results from UNISAMPO were stored in the database This was accomplished in the fall of 2002 The database consisted of only seven tables Header Collection Acquisition Peaks Nuclides MDA and Hypothesis This version was running at the FINDC from October 2002 to June 2003 During its testing period it was decided to develop a more comprehensive database that would fulfil also the needs of a more general community performing gamma ray spectrum analysis work In January 2003 the Laboratory of Airborne Radioactivity ASL of STUK joined in the collaboration and took the initiative to develop the database further At the same time STUK and the Radiation Protection Bureau Health Canada started a close cooperation on issues related to the CTBT and environmental monitoring This cooperation was established at the level of directors of the institutes taking the form of Memorandum of Understanding The extended collaboration produced the first draft specifications in February 2003 These specifications later named version 0 8 comprised of 22 tables with 342 fields In June 2003 STUK arranged a meeting on database specifications with Health Canada and HUT The work culminated to a common view on the structure of the databas
41. aughters For that purpose a search through this table is the only thing needed parentIdSample Identification number of the parent sample See table 6 1 samples daughterIdSample Identification number of the daughter sample See table 6 1 sam ples activityBranching Denotes the fraction of activity inherited from the parent to the daughter If we sum activityBranching over all daughterIdSam ple s while keeping parentIdSample fixed the result must be 1 0 Note activityBranching should not be needed for the activity of the daughters The metrics of each sample should be available in its production table method Method of splitting or combining used to form the daughter from the parent s comments Comments in English en 40 6 3 Sources Table 6 3 Source geometry and material description sources Field Type Length Flags sourceld varchar 40 PN idSample int 4 IF sourceGeometry varchar 20 sourceThickness double 8 sourceHeightMar double 8 sourceWidth double 8 sourceLength double 8 sourceDiami double 8 sourceDiam2 double 8 sourceLayers smallint 2 sourceDensity double 8 sourceMass double 8 sourceMaterial varchar 20 contDens double 8 contThick double 8 contMaterial varchar 40 preparationMethod text 0 comments text 0 idSample samples idSample end of table This table describes the source geometry a
42. bles store information about CTBT laboratory samples sent to radionuclide labora tories within the framework of the Comprehensive Nuclear Test Ban Treaty The tables are very specific and for the full details Ref 6 should be consulted 27 5 1 CTBT Laboratory Samples Table 5 1 CTBT laboratory samples ctbtLabSamples Field Type Length Flags idSample int 4 PFN siteCodeld varchar 16 stationSiteCodeld varchar 16 F priority varchar 10 sampleCategory char 1 collStart datetime 8 collEnd datetime 8 airVolumeTotal double 8 analysisPurpose text 0 testsAuthorized text 0 speciallnstructions text 0 stationActCat varchar 40 stationSamDiam double 8 stationSamThick double 8 stationSamWidth double 8 stationSamMass double 8 stationContDens double 8 stationContThick double 8 stationContMat varchar 80 stationSamGeomDescr varchar 80 stationSplitMass double 8 stationSplitAirVolume double 8 stationSplitMethod text 0 idcNuclNotQuant text 0 idcNaturalNucl text 0 idcActProd text 0 idcFissProd text 0 idcEventActProdPresent char 1 idcEventDaysSinceLastAct varchar 10 idcEventOnlyOneFP char 1 idcEventDaysSinceLastFP varchar 10 idcEventMultFP char 1 idcEventDaysSinceLastMultFP varchar 10 idcEventCs137Present char 1 idcEventTimesCs137InMonth varchar 10 test varchar 40 comments text 0 idSample sampl
43. channels In both channels there is a flow meter The flow meters are described by Table 3 1 Samplers samplers Field Type Length Flags samplerld varchar 40 PN stationName varchar 40 samplerType varchar 20 flowFactori double 8 flowPoweri double 8 flowFactor2 double 8 flowPower2 double 8 lastMaintenance datetime 8 nextMaintenance datetime 8 documentDir varchar 255 comments text 0 end of table two parameters flow factor F and flow power c These parameters can be used for orifice plates flow nozzles or multi orifice probes or with any device for which two parameters are sufficient only the method of flow rate calculation will differ In our application the flow rate f is calculated from f F x p where F is the flow factor in cubic meters per hour m h c is the flow power and p is the pressure difference over the measuring device in pascals Pa For p See also table 3 3 airFilterSamples samplerld stationName samplerType flowFactori flowPoweri flowFactor2 flowPower2 lastMaintenance nextMaintenance documentDir comments Name of the sampler This is the name of the station where the sampler is currently sit uated This name should be identical to the stationId of the station if known see table 2 1 stations Note according to the naming conventions of App A this should be a foreign key with the name stationld i e not stationNa
44. ctivity of the daughter is zero at zeroTime One sigma absolute uncertainty of zeroRatio Reference date and time at which the refRatio is calculated Note If the half lives are short when compared to the acquisition time the decay corrections of activities to refTime should take the non equilibrium of the decay chain into account See Fig 8 1 Date and time when the initial activity was created Uncertainty towards past of the zeroTime in hours fh Uncertainty towards future of the zeroTime in hours h Note Since the uncertainty of zeroTime is not necessar ily symmetric there are two uncertainties defined The time together with the corresponding uncertainties is given as zeroTime uncZeroTimeLow uncZeroTimeHigh e g 2004 09 08 22 34 28 34 1h 44 3h The uncertainties correspond to one sigma absolute Gaussian uncertainties i e 34 of the probability mass is between zeroTime uncZeroTimeLow and zeroTime as well as between zeroTime and zeroTime uncZeroTimeHigh Comments in English en 81 8 7 Final Analysis Results Table 8 8 Final analysis results finalResults Field Type Length Flags idAnalysis int 4 PFN idMeas int 4 IFN idSample int 4 IFN completionTime timestamp 4 category smallint 2 categoryReason text 0 analyst varchar 20 analysisStatus varchar 20 purpose text 0 testType text 0 comparison text 0 conclusions text 0 projectFile
45. d inputIdCal calibrations idCal end of table same idCal in this table form a complete calibration used in analyses idCal calTypeld measSetupld inputIdCal changed class Identification number of the full calibration The full calibration consists of multiple calibrations identified by idCal calTypeld Name of the type of calibration See Sec 7 4 for discussion of the reserved calTypeld s Identifier of the measurement setup for which this calibration has been performed Even though there may be several calibrations for one measurement setup only one can be the best Pointer to the calibration that is the basis for this calibration Using this pointer the calibration chain can be tracked to the original calibration This key is a self referencing foreign key i e it points to another record in this table This field is true if the calibration idCal calTypeld has been changed when compared with the calibration inputId Cal calTypeld Additional information on the calibration chain The following val ues have been defined PHD External calibration information received together with the spectrum EXTERNAL External calibration information of unspecified origin SETUP This is or was the default calibration for measurement setup measSetupId class must have the value SETUP if a mea surementSetups idCal refers to this calibration Note old default calibrations may retain this value even if there is
46. d due to identical half lives it must also be taken into account The corrections and the associated times are illustrated in Fig 8 1 below Decay correction factors are multiplicative nuclideld Name of the identified nuclide For syntax see table 4 3 calibrationLibraries idAnalysis Identification number of the analysis See table 8 1 analyses idMeas Identification number of the measurement See table 6 8 measurements idSample Identification number of the sample measured See table 6 1 samples confidence A figure of credit p describing the confidence on the presence of this nuclide in the sample i e there is a probability of 1 p that this nuclide is not present Note identification is a binary decision where valid calculations of the statistics are extremely difficult See the manual of the software producing this number effHalflife Effective half life of the nuclide in units effHalflifeUnit effHalflifeUnit Half life unit The supported units are year y or a day d hour h minute m or min and second s uncEffHalflife Absolute one sigma uncertainty of effHalflife in units effHalflifeUnit isBackground True if background efficiency is used to calculate the activity This is the activity due to surrounding walls etc i e not the activity in the sample Normally its absolute value is not known and only the shape of the background efficiency curve has been used to facilitate more reliable nuclide identificat
47. e This table describes germanium detectors used This table aims to describe the detector to the extent sufficient for Monte Carlo simulation of the measuring process when used together with the rest of the measurement setup detectorld location detectorModel detectorType relEfficiency volume diameter thickness coreDiameter coreLength endcapToCrystal windowMaterial windowThickness deadLayerThickness biasVoltage polarity comments A unique name of the detector Facility and location of the detector Detector manufacturer s model name and number for the detector Type of the detector e g p type Relative efficiency of the detector in percent Volume of the detector in cubic millimeters em Detector diameter in millimeters mm Detector thickness in millimeters mm Diameter of the detector core in millimeters mm Length of the detector core in millimeters mm Distance from the endcap to the crystal surface in millimeters mm Name of the detector window material Detector window thickness in millimeters mm Detector dead layer thickness in millimeters mm Bias voltage in volts V Polarity of the voltage positive or negative Comments in English en 43 6 5 Attenuators Table 6 5 Attenuators attenuators Field Type Length Flags attenuatorld varchar 20 PN comments text 0 end of table This table describes attenuators used in measurements
48. e the activity assuming infinite irradiation time with the average activity production rate irrCorr depends on the time profile of the collection rate If it is not known a common assumption is a constant rate See your software documentation for the actual method used One sigma absolute uncertainty of irrCorr This correction takes into account the activity produc tion collection rate and decay during collection When applied to the activity at the end of collection it gives the total activity collected collCorr depends on the time profile of the collection rate If it is not known a common assumption is a constant rate See your software documentation for the actual method used One sigma absolute uncertainty of collCorr becquerels Bq of 75 decayCorr2 Decay correction multiplier 2 See decayTime2 in table 8 1 analyses uncDecayCorr2 One sigma absolute uncertainty of decayCorr2 comments Comments in English en 76 Decay correction Produces refTime2 activity refTime2 decayTime2 decayCorr2 saturation activity total activity collected collTime samplerOnTime activity collEnd measurements waitTime measurements activity acqStart measurements acqRealTime measurements acqLiveTime measurements decayTime1 decayCorr1 y activity refTime1 Figure 8 1 Decay corrections in Linssi The time intervals used to calculate the various corrections are shown in the left hand part of the figure to
49. e and on the principle of open availability of the scripts for creating and managing the database In this meeting the database was given a name Linssi which may be considered as an acronym for a Linux system for spectral information The first version carrying this name was the version 0 9 of June 2003 containing 22 tables and 365 fields From this version onwards the full 1 Linssi User GRAPHICAL USER INTERFACE GUI Analysis Software Temporary Files Update Scripts Query Scripts Admin Scripts Linssi Database Figure 1 1 How Linssi interfaces with the user and analysis software UNISAMPO SHAMAN pipeline was producing results to the database at the FiNDC The version 0 9 operated from July to mid November in 2003 Linssi v 1 096 was operational from mid December to end of January 2004 The version 1 01 started operation at the FiNDC on February 9 2004 Linssi v 1 01 contained 26 tables with 499 fields Already at the time of the release of the version 1 01 it was known that further extensions of Linssi were needed The most important were the support of the CTBT laboratory samples and the bookkeeping of calibrations Calibration tracking was achieved with a relatively minor but significant extension of the calibration tables For calibration certificates a set of tables defining calibration samples was also added An enhanced support of sample splitting and combining was also found necessary Some streamlining and polishing was a
50. e mobile station Altitude of the mobile station Precision class of dilution of precision of horizontal coordinates Precision class of dilution of precision of vertical coordinate Precision class of dilution of precision of position Age of the information in seconds s The method of fixing the position 0 invalid 1 GPS 2 DGPS 3 PPS 4 RTK 5 float RTK 6 estimated 7 manual 8 simulation Comments in English en 12 2 3 Weather Table 2 3 Weather at the station weathers Field Type Length Flags stationld varchar 40 PFN weatherStartId datetime 8 PIN weatherEnd datetime 8 windDir double 8 windSpeed double 8 avgTemperature double 8 lowTemperature double 8 highTemperature double 8 snowfall double 8 rainfall double 8 humidity double 8 pressure double 8 stabilityClass char 1 comments text 0 stationld stations stationId end of table Table weathers contains the information about the weather conditions at the station The most important weather parameters can be continuously monitored The table is preferably filled on line even though that is not required The average values are the averages over the report period stationld weatherStartld weatherEnd windDir windSpeed avgTemperature lowTemperature highTemperature snowfall rainfall humidity pressure stabilityClass comments See table 2 1 s
51. e of the field in bytes For variable size fields a zero is printed The column Flags gives information of the relational status of the field The available flags are Primary key or a component of the primary key The field is automatically incremented every time a new entry is made Foreign key or a component of the foreign key Self referencing key that points to a record in the same table The field content must be unique within this table P A F Number 1 2 Foreign keys with the same number form a combined foreign key S U I The field is indexed for faster reference N The field must contain a value i e it must not be NULL Note that the primary key may be composed of multiple fields In that case all included fields are marked as primary A set forming the complete primary key must be unique Primary keys are always indexed Their components may also be indexed Since there may be many foreign keys in a table flag F is not enough to define a combined foreign key For that purpose each combined foreign key is numbered flag 1 5 Units and Default Values We use only SI units and units outside the SI that are accepted for use with the SI and thus consistent with the recommendations of the International Committee for Weights and Measures CIPM Comit International des Poids et Mesures 5 It is strongly recommended that users of Linssi follow the unit conventions of this manual If different units are needed
52. ector temperature in de grees centigrade C Ambient temperature in degrees centigrade C Ambient relative humidity in percent Time between end of sampling or end of irradiation or equivalent and start of acquisition in seconds s Date and time of the start of acquisition Date and time of the end of acquisition Real time of acquisition in seconds s Measurement system effective live time of acquisition in seconds s Type of the spectrum Currently two types have been reserved FULL denoting the normal full time spectrum and PREL denoting a time slice of the full spectrum 6 The channel number of the first number of counts in the spectrum The channel number of the first valid number of counts in the spec trum This could be the first channel above the lower level discrim inator for example 49 lastValidChannel lastChannel spectrum spectrumSent comments The channel number of the last valid number of counts in the spec trum This could be the last channel below the upper level discrim inator for example The channel number of the last number of counts in the spectrun The measured spectrum Only the counts y values are stored i e no channel numbers x values The format is one channel per line Date and time when the spectrum was sent to analysis Ifthe anal ysis is carried out in the measuring facility this is most probably the time the spectrum was stored to the database Comments in
53. er Samples Dos VO a e sel o a ee a o ee eee a I 8 32 Sampling State of Health Data lt lt 46 6 sa 5 Hanau 3 3 Air Filter Samples scan ana ran a an aaa e EO Calibration Samples Al Calibration amp av 2 0 2 Ku Ba an na na Rea tii 42 Calibration Nucldes ociosa 43 alba LiDraries aseo A ee ee eR CTBT Laboratory Samples a1 CTBT Laboralory Bsp san che ke oP eRe EPR ee ER a ee eS Go CTBT ee so oo a eces a AA eR A da CTET erie tor ee ed oe eR ee A OES gd CTBI Messages gt eterra Beebe Paka ba Ka Pa Ka Pas Oo CIDT ape Fee os a oe ee has heras Baer Measurement A cc oe dg bk ne ORS Se Be we bP ee OP we OE G 6 2 Splitting and Combining Samples occ coc a ee En aa Ow a Oo SOUE ne we oe od Peed Pa Pe eee Pe wee Pas OA Dee orod pired piped phita eased 2 REE OS REE OS Oe SCRE io oe we ee ee ee KE Ee S Du eee do oe me ee ee Me 6 7 Measurement Setups 2 22 0 6 8 Measurements e i al BEE we ER Ee BEE ae nz ill D DRNRIPA 15 16 17 18 21 21 23 24 27 28 31 32 33 35 7 Calibration Data and Functions TL Calibrations lt 2200 00 cu u eu en e nr nn 7 2 Calibration Points cs cc cs ass a 7 3 Calibration Preferences o u u u ca serca ee TA Callao Ten o carr as a a a 7 4 1 Peak Shape Calibrations AR Energy Calibration cw ae hea ee hee ee hee ee hee eee 7 4 3 Efficiency Calibration 15 Calibration Functions o lt lt a se m 28 ee a ee ee h 75 1 Predefined Functions 7
54. er defined External software Multiplet fitting Calculated from reference line Summation Quick summation Fixed in last fitting FF A Q a HC ID Free in last fitting 4 Full width at half maximum source flags 2 flags Explanation Quick fit Full fit User defined External software Calibration Fixed in last fitting Free in last fitting Table 8 3 Peak origin flags See note on p 68 69 8 3 Line Associations Table 8 4 Line associations lineAssociations Field Type Length Flags idAnalysis int 4 PFIN nuclideld varchar 10 PN idLine smallint 2 PN idPeak int 4 IF1 idMeas int 4 IFN idSample int 4 IFN lineEnergy double 8 uncLineEnergy double 8 emissionProb double 8 uncEmissionProb double 8 CCfactor double 8 uncCCfactor double 8 lineSignificance double 8 explLevel double 8 lorentzGamma double 8 xray Boolean 1 background Boolean 1 annihilation Boolean 1 singleEscape Boolean 1 doubleEscape Boolean 1 xrayEscape Boolean 1 backscatter Boolean 1 coincSum Boolean 1 randomSum Boolean 1 neutronScatter Boolean 1 neutronCapture Boolean 1 userGiven Boolean 1 found Boolean 1 foundClose Boolean 1 thresholdLine Boolean 1 primaryLine Boolean 1 actMan Boolean 1 comments
55. erCompany varchar 40 dateTimeOfHandover datetime 8 eta datetime 8 airwayBill varchar 40 sealNumber varchar 20 comments text 0 idSample samples idSample idRecipient ctbtRecipients idRecipient end of table For a more precise definition of all the fields except idSample the user is asked to consult the report IDC3 4 1Rev6 6 to which the descriptions below are referencing The reference LABSDN Transport refers to the Transport data block of the LABSDN message giving a notification that a sample has been sent to a laboratory Same data blocks are also used in the TECSDN message giving a notification that a sample has been sent from the laboratory LABSDN and TECSDN messages together with their data blocks are described in Chapter Other Laboratory Messages of the report IDC3 4 1Rev6 6 idSample Identification number of the sample measured See table 6 1 sam ples transportOutId True if this is a transport out of the laboratory i e message TECSDN See LABSDN Transport idRecipient Identification number of the recipient See table 5 3 ctbtRecipi ents courierCompany Name of the courier company See LABSDN Transport dateTimeOfHandover Date and time of handover See LABSDN Transport eta Estimated date and time of arrival See LABSDN Transport airwayBill Airway bill number See LABSDN Transport sealNumber Seal number See LABSDN Transport comments Comments in English en 31
56. es idSample stationSiteCodeld stations stationld end of table 28 For a more precise definition of all the fields except idSample the user is asked to consult the report IDC3 4 1Rev6 6 to which the descriptions below are referencing The reference RLR xxx refers to the data block xxx of the radionuclide laboratory report RLR RLR and the related data blocks are described in Chapter Radionuclide Laboratory Reports of the report IDC3 4 1Rev6 6 idSample siteCodeld stationSiteCodeld priority sampleCategory collStart collEnd airVolumeTotal analysisPurpose testsAuthorized speciallnstructions stationActCat stationSamDiam stationSamThick stationSamWidth stationSamMass stationContDens stationContThick stationContMat stationSamGeomDescr stationSplitMass stationSplitAirVolume stationSplitMethod idcNuclNotQuant idcNaturalNucl Identification number of the sample measured See table 6 1 sam ples Site code of the laboratory selected for analysis See RLR Header Site code of the sampling station Priority level Urgent or Routine See RLR Header Sample category A network quality control sample B sample from IMS network categorized by IDC as level 5 C proficiency test sample D station backup sample measured by a lab or E other See RLR Header Collection start date and time See RLR Collection Collection end date and time See RLR Collection Total air volume
57. eter in channel 1 Total volume of air sampled in channel 1 since collStart in cubic meters m at this moment Air pressure difference in pascals Pa over the flow rate meter in channel 2 Total volume of air sampled in channel 2 since collStart in cubic meters m at this moment Air flow rate in m h at this moment If TRUE air volumes and flow rate are corrected to Normal Temperature and Pressure NTP i e corrected to 20 C and 101 325 hPa Comments in English en 17 3 3 Air Filter Samples Table 3 3 Air filter samples airFilterSamples Field Type Length Flags idSample int 4 PFN samplerld varchar 40 F stationld varchar 40 F collStart datetime 8 collEnd datetime 8 collTime double 8 samplerOnTime double 8 airVolumeTotal double 8 airVolumel double 8 presDiffiStart double 8 presDiff1End double 8 airVolume2 double 8 presDiff2Start double 8 presDiff2End double 8 sampleSent datetime 8 correctedToNTP Boolean 1 comments text 0 idSample samples idSample samplerld samplers samplerld stationld stations stationld end of table In this table fields have been reserved for two channels in a sampler This gives a possibility to use two types of filters simultaneously typically active carbon and fiber See also table 3 1 samplers idSample See table 6 1 samples samplerld This is the identifier
58. ference due to other identified nuclides has been accounted for in actRawPriLine One sigma absolute uncertainty in actRawPriLine Offline possibly manually calculated raw activity in becqurels Bq See also note on specific activity on p 79 One sigma absolute uncertainty in becquerels Bq of actRawMan Method used to calculate actRawMan Identifies the activity used to calculate the final results The pos sible values are LSQ actRawLSQ has been used in table 8 8 finalResults PRI actRawPriLine has been used in table 8 8 finalResults MAN actRawMan has been used in table 8 8 finalResults The decision which activity is to be used must be made by the analyst That is the analysis software must set this field to null Which gamma lines have been used in the activity calculation can be found in table 8 4 lineAssociations Acquisition correction multiplier corrects for decay during spectrum measurement See acqRealTime in table 8 1 analyses One sigma absolute uncertainty of acqCorr Decay correction multiplier 1 See decayTimei in table 8 1 analyses One sigma absolute uncertainty of decayCorr1 Decay correction multiplier for wait time See waitTime in table 6 8 measurements One sigma absolute uncertainty of waitCorr This correction takes into account the activity production rate and decay during irradiation collection When applied to the activity at the end of collection it gives the saturation activity of the sample i
59. g Note that a key can simultaneously be both primary and foreign The naming conventions of the keys and other fields are described in App A As can be seen almost half of the tables tables 14 to 22 concentrate on gamma ray spectrum analysis The number of fields is also greatest in these tables Spectrum measurement is covered by tables 7 to 13 and the sample production facility by tables 1 2 and 4 The different sample production processes are covered in the tables of air filter samples group Ch 3 calibration samples group Ch 4 and CTBT lab samples group Ch 5 Starting from table 1 we find the weather reigning outside the station which itself is defined in table 2 The station is assumed to be the place where the radioactivity is collected to the sample or where the sample manufacturing takes place Thus by definition all in situ measurements also take place at the station However nothing prevents defining for example a weather station that has nothing to do with sample production or measurement If the station is mobile its positions are stored in table 4 Obviously a sample can be produced in many different methods Currently we have defined tables for calibration samples air filter samples and CTBT laboratory samples These groups will be described in the subsequent chapters After sampling the sample arrives to a measurement facility which may or may not be situated at the sampling station Table 7 characterizes the
60. gamma line should be visible in the spectrum as a gamma peak or not The fraction of peak area explained by this gamma line Value of the Lorentz gamma width of this X ray line in kiloelec tronvolts keV TRUE if this line is an X ray line TRUE if this line is a background line TRUE if this line is an annihilation line TRUE if this line is a single escape line TRUE if this line is a double escape line TRUE if this line is an X ray escape line See table 6 1 71 backscatter coincSum randomSum neutronScatter neutronCapture userGiven found foundClose thresholdLine primaryLine actMan comments TRUE if this line is a backscatter line TRUE if this line is a true coincidence sum line TRUE if this line is a random coincidence sum line TRUE if this line is due to neutron scatter in the detector TRUE if this line is due to neutron capture in the detector TRUE if this line is a user defined line TRUE if this line is found i e associated with a peak in the spec trum The LSQ calculation of nuclide activity is based on all nuclide lines for which found is TRUE See table 8 5 activities TRUE if this line is found close to a spectrum peak but not associ ated with it TRUE if this line is the threshold line The threshold line is the most significant line of a nuclide that has NOT been associated with a peak in the spectrum TRUE if this line is the primary line i e the most significant line of t
61. gardless of case sensitivity However in order to be safe all the field and table names used must be typed following the conventions of this manual In that way readability of the names is also enhanced 85 86 ISBN 951 22 8148 8 ISSN 1456 3320
62. gether with the times and dates from which they are calculated It also includes the names of the table where the corre sponding fields can be found The right hand part of the figure shows the decay correction factors in table activities and how they are used to obtain the decay corrected activities at given dates and times The activity at the point of an arrow is obtained by multiplying the activity at the tail of the arrow with the correction factor shown Note 1 Raw activity saturation activity and total activity collected are not activities at any specific date and time Note 2 collCorr and irrCorr depend on the shape of the collection rate profile and gen erally cannot be calculated from collTime and samplerOnTime alone Note 3 Even though the collection refers to table airFilterSamples the same correction is also applicable to other sample production methods Note 4 decayTime1 and decayTime2 may be positive or negative The other times by definition are positive Note 5 If the decay chains are in equilibrium the decay corrections can be easily obtained from the effective half lives of the identified nuclides In non equilibrium chains the effective half lives do not exist Depending on the analysis software the correction factors may still be correct Consult your software manual TT 8 5 Activity Limits Table 8 6 Activity limits and minimum detectable ac tivities
63. gnificant etc The levels are decided by the soft ware Decision limit Le in counts for this peak in this spectrum Detection limit L in counts for peak at this position assuming the baseline of this spectrum TRUE if the centroid of this peak is outside of the valid channel range A set of peak flags giving the origin of the peak For the reserved values see Tab 8 3 Starting channel of the Region Of Interest ROI in which this peak belongs to Ending channel of the corresponding ROI Total number of counts in ROI Index identifying the ROI sorted in an ascending order according to ROIstart and starting from 1 Area of the baseline under the peak in counts i e integral of the baseline function over the interval around peak deemed appropriate by the software Baseline area in counts divided by the number of channels included in its calculation One sigma absolute uncertainty of the baselinePerChannel in counts Validity of the baseline function starts at this channel Validity of the baseline function ends at this channel The first of the four parameters reserved to define the baseline func tion The second of the four parameters reserved to define the baseline function The third of the four parameters reserved to define the baseline function algo See 67 baselineParam4 emissionRate uncEmissionRate backgroundCps uncBackgroundCps backgroundType blankCps uncBlankCps blankType comment
64. gt ar 7 6 i 0 function 8 Polynomial in lny against 1 x n 1 a i Iny gt a In 7 7 i 0 a function 9 Inverse exponential y z 7 8 ay a function 99 Other This function is not defined nor is it available in MathML notation Text in functionDef may help in interpreting the type of the function if any in question 57 7 5 2 MathML presentation of the functions Mathematical Markup Language MathML 8 is a markup language defined using Exten sible Markup Language XML 9 If function 0 a MathML presentation of the function definition is stored into functionDef The first parameters of par1 par10 until the first null value shall be used to evaluate the function value The function itself shall be encapsu lated as lt mathml xmlns z http www w3 org 1998 Math MathML gt lt mathml gt where the http reference is to the applicable schema of MathML itself and z is the namespace prefix adopted in Linssi These are the only requirements set by Linssi database specifica tions 7 5 3 MathML support in Shaman Even though Linssi sets minimal requirements for MathML functions it should be pointed out that analysis software may set more stringent limits on the MathML features it is able to take advantage of As far as we know currently the only analysis program able to use use MathML input is SHAMAN 2 It uses a MathML subset briefly discussed here In SHAMAN lambda calculus is used to evaluate the functi
65. h at tenth maximum of the peak in channels ch Distance of the starting point of the low tail from peak centroid in channels ch See table 6 1 66 highTail lowTailExp highTailExp step netCountRate uncNetCountRate efficiency uncEfficiency searchSignificance significance significanceFlag decisionLimit detectionLimit outOfRange peakOrigin ROIstart ROlend ROlarea ROlindex baselineArea baselinePerChannel uncBaselinePerChannel baselineStart baselineEnd baselineParami baselineParam2 baselineParam3 Distance of the starting point of the high tail from peak centroid in channels ch Value of the exponent used for the low tail definition Value of the exponent used for the high tail definition Relative height of the step under the peak i e step height to peak area ratio Net count rate at the peak i e peak area to live time ratio in counts per second 1 sl The contribution from blank and back ground have been subtracted One sigma absolute uncertainty of the net count rate in counts per second 1 s Absolute efficiency of the measuring system at the peak energy One sigma absolute uncertainty of the absolute efficiency Peak significance L as defined by peak search rithm L has a local maximum at centroidChannel analyses peakSearchSignificance Peak significance in multiples of the decision limit Le Peak significance flags They may correspond for example to high medium low insi
66. he nuclide given the spectral baseline The primary line activity actRawPriLine is based on the peak associated with this gamma line See table 8 5 activities TRUE if this line has been used in the off line possibly manual calculation of the nuclide activity actRawMan In that case the line must have been associated with a peak i e idPeak must not be null See table 8 5 activities Comments in English en 12 8 4 Nuclides and Their Activities Table 8 5 Identified nuclides and their activities activities Field Type Length Flags nuclideld varchar 10 PIN idAnalysis int 4 PIFN idMeas int 4 IFN idSample int 4 IFN confidence double 8 effHalflife double 8 effHalflifeUnit varchar 8 uncEffHalflife double 8 isBackground Boolean 1 actRawLSQ double 8 uncActRawLSQ double 8 interfCorrLSQ Boolean 1 actRawPriLine double 8 uncActRawPriLine double 8 interfCorrPriLine Boolean 1 actRawMan double 8 uncActRawMan double 8 actRawManMethod text 0 actSelect varchar 10 acqCorr double 8 uncAcqCorr double 8 decayCorri double 8 uncDecayCorri double 8 waitCorr double 8 uncWaitCorr double 8 irrCorr double 8 uncIrrCorr double 8 collCorr double 8 uncCollCorr double 8 decayCorr2 double 8 uncDecayCorr2 double 8 comments text 0 idAnalysis analyses idAnalysis idMeas measurements idMeas
67. hematical Markup Language MathML into functionDef This is informed by setting function to zero 7 5 1 Predefined Functions Predefined functions are selected by the field function of table table 7 1 calibrations List of currently supported functions is shown below In principle any function can be applied for any calibration type In practice however the functions 5 9 are used only for efficiency calibration The user is advised to consult his analysis software manuals for 56 physical interpretation and support for these functions If new functions are needed their definitions should be sent to Linssi administrative body who will reserve function values for them function 0 MathML function The function definition is stored in Mathematical Markup Language MathML into func tionDef See Sec 7 5 2 below function 1 Interpolation No functional fitting is available Interpolation between the calibration points is used De pending on the software and the type of calibration different types of interpolation may be used i e linear quadratic logarithmic etc function 2 Polynomial ye das 7 1 i 0 function 3 Square root polynomial y aa 7 2 i 0 function 4 Square root of polynomial y ae 7 3 i 0 function 5 Exponential rollover ER a3 es 04 Y do exp 1 exp 7 4 x x function 6 Polynomial in In y against ln x Iny gt a lin x 7 5 i 0 function 7 Polynomial in Iny against x hy
68. ion This background should not be confused with the peaked background subtraction PBS due to background measurement As a matter of fact they are incompat ible and should not be used together actRawLSQ Raw activity in becquerels Bq based on all the peaks of this nu clide Weighted least squares fitting LSQ has been used to obtain the effective peak area Raw activity is the net peak area multi plied by CCfactor see table 8 4 lineAssociations and divided by efficiency live measuring time and emission probability of the gamma line The contribution from blank and background has been subtracted See also note on specific activity on p 79 interfCorrLSQ TRUE if the interference due to other identified nuclides has been accounted for in actRawLSQ uncActRawLSQ One sigma absolute uncertainty in becquerels Bq of actRawLSQ 74 actRawPriLine interfCorrPriLine uncActRawPriLine actRawMan uncActRawMan actRawManMethod actSelect acqCorr uncAcqCorr decayCorri uncDecayCorri waitCorr uncWaitCorr irrCorr uncIrrCorr collCorr uncCollCorr Raw activity in becquerels Bq based on the primary line of this nuclide Raw activity is the net peak area multiplied by CCfactor see table 8 4 lineAssociations and divided by efficiency live measuring time and emission probability of the gamma line The contribution from blank and background has been subtracted See also note on specific activity on p 79 TRUE if the inter
69. ission varchar 40 coordSystem varchar 20 speed double 8 heading double 8 numSatellites int 4 xCoordinate double 8 yCoordinate double 8 altitude double 8 hDOP double 8 vDOP double 8 pDOP double 8 age double 8 fix int 4 comments text 0 idSample samples idSample idMeas measurements idMeas end of table This table tracks the coordinates of mobile stations stationId To facilitate the use of the primary key idPosition as a marker for identical positions from multiple positional devices the third primary key positionSource has been provided And to facilitate easy retrieving of the positions of sample collection and measurements the foreign keys idSample and idMeas have been included In practice the station coordinates are continuously stored from GPS receiver s Asyn chronously with the storing sampling and measuring scripts retrieve data from the table process them and store the relevant positions back to the table While processing they set their respective fields idMeas or idSample to correct values A route processing script is additionally used to replicate the coordinates it deems relevant and identify them by setting positionType to route After the mission the coordinates for which idMeas idSample positionType null can be deleted 11 idPosition positionSource stationld idSample idMeas positionType positionTime mission coordSystem speed heading numSatellites xCoordinate
70. les are just calibration samples On the other hand we believe that the air filter samples can be applied to other sample collection modes too If that is not acceptable new production table groups can be defined This is illustrated with the yet non existent irradiation group of tables in the Fig 1 2 above If we receive a sample to be measured we start from entry point 2 i e from preparing the source and measuring it Ch 6 Finally if we receive a gamma ray spectrum for analysis we start from entry point 3 i e send the spectrum directly to the analysis pipeline Ch 8 If our laboratory controls the whole chain of events from entry point O to entry point 3 the database is updated as we go along On the other hand if the later entry points are applied the necessary data must be provided from outside and stored to the previous tables of the chain Scripts are provided for each of these entry points The entry points also define the most important keys in the Linssi database idSample in table 6 1 samples idMeas in table 6 8 measurements and idAnalysis in table 8 1 identifying the sample its measurements and its analyses respectively 1 3 A Stroll between the Tables Let s take an introductory stroll between the tables in Linssi The table lay out is shown in Fig 1 3 In the figure only the table names and key persons sitting in the table are shown The arrows are drawn from the foreign keys to the primary keys they are referencin
71. locally the conversion should be performed in the interfacing scripts All dates and times datetime timestamp are in Universal Time Coordinated UTC The uncertainties in Linssi are given as one sigma absolute uncertainties If for exam ple uncertainty per cent is needed it should be calculated from the value and its absolute uncertainty when reading the database Linssi implementation does not include default values to fields The action to be taken due to unknown field values should always be left to the user i e to the software or analyst inputting or outputting data to or from Linssi To facilitate this practice unknown values 6 should always be set null That is automatically true for fields that are not filled i e have been left empty Note however that there are some exceptions They are marked with flag N Chapter 2 Stations The station group of tables of Linssi establishes the entry point O of the database Sam ple production takes place at the station where the sample manufacturing equipments are situated Nothing however prevents from also defining other types of stations They may include a moving laboratory with samplers and measuring facilities or even a simple weather station for example Since the group aims to support any kind of station it is quite generic Basically a station has only a name stationId purpose stationType and location location It may be mobile and then its position is given
72. longblob 0 lowQualitySpectrum Boolean 1 comments text 0 idAnalysis analyses idAnalysis idMeas measurements idMeas idSample samples idSample end of table idAnalysis Identification number of the analysis See table 8 1 analyses idMeas Identification number of the measurement See table 6 8 measurements idSample Identification number of the sample measured See table 6 1 samples completionTime Date and time when these results were stored in the database category Facility specific categoryReason Motivations for category analyst Name of the analyst who evaluated these results analysisStatus Status of the analysis Valid values are Preliminary or Final purpose Facility specific testType Facility specific comparison Facility specific conclusions Facility specific projectFile File containing the full project information The contents are soft ware specific Typically this would be a script able to reconstruct all the final analysis results for the given sample and measurement Alternatively this may be the name of the project file or URI where project information is to be found lowQualitySpectrum Set TRUE if the analyst has deemed the spectrum as being of low quality comments Comments in English en 82 Bibliography 8 9 UniSAMPO Advanced Gamma Spectrum Analysis Software User s Guide Version 2 14 Doletum Oy Ltd Espoo Finland August 10 2004 SHA
73. lso carried out Linssi version 1 1 was released on January 11 2005 It contained 32 tables and 544 fields After that CTBT tables were augmented Because of some script compatibility issues and since the CTBT tables had been used only be the developers the version number was not changed A new release of Linssi version 1 1 was published in July 7 2006 It contains 32 tables and 557 fields 1 2 The Database System The Linssi database system consists of the database and the necessary scripts needed to do the updates and administer the database An increasing number of query scripts will also be provided The database is described in detail in this manual The scripts provided with the database are mostly self documenting but are briefly described in the script manual 4 The overall user environment as it is implemented at STUK is shown in Fig 1 1 where the database and script layers form the Linssi distribution and the upper layers are commercial or in house software User interfaces with the system via a graphical user interface GUI The GUI to scripts is web based and the analysis software has its own GUI Most of the reports can be directly created using SQL queries but the analysis software has also a report generating possibility independent from Linssi The analysis software in our case UNISAMPO and SHAMAN is interfaced to the update and query scripts using temporary files documented in the script manual The amount of data processed in
74. lysis is an analysis of a similar sample and thus a good starting point for this analysis Date and time when the spectrum arrived for analysis Date and time when the spectrum analysis started Date and time when the spectrum analysis ended The most essential input parameters used for the analysis Log storing the interactive commands for the analysis given by the analyst Type of the analysis This could be interactive batch pipeline for example Name of the software used in analysis Version of the software used in analysis Name of the analyst Channel by channel spectrum baseline used or gener ated in the analysis The channel range is identical to measurements spectrum but the values are floating point values Channel by channel stripped spectrum used or generated in the analysis i e the spectrum minus the peak functions The channel range and format are identical to measurements spectrum but the values are floating point values Channel by channel peak search significance i e significance values given by the peak search algorithm very often a digital filter The peak search significance Ls usually aims to be directly proportional to the decision limit Le i e Ls C x Le but the constant C is dependent on the method and not always constant either For the exact definition the software manual should be consulted Note usually the maxima of L do not fall on integer channels The channel range and format are ide
75. me However since the sampler may have been moved to a station not having an entry in the table stations the naming convention cannot be enforced Name of the sampler type Flow factor in cubic meters per hour m h for flow meter in chan nel 1 Flow power of flow meter in channel 1 Flow factor in cubic meters per hour m h for flow meter in chan nel 2 Flow power of flow meter in channel 2 Date and time of the last maintenance of this sampler Scheduled date and time of the next maintenance of this sampler The directory or URI Universal Resource Identifier where the documentation of the sampler can be found Comments in English en 16 3 2 Sampling State of Health Data Table 3 2 State of health data SOH for air filter sam pling process airFilterSOH Field Type Length Flags idSample int 4 PIFN samplingHealthTimeld datetime 8 PN samplerld varchar 40 F pressDiff1 double 8 airVolumel double 8 pressDiff2 double 8 airVolume2 double 8 flowRate double 8 correctedToNTP Boolean 1 comments text 0 idSample samples idSample samplerld samplers samplerld idSample samplingHealthTimeld samplerld pressDiff1 airVolumel pressDiff2 airVolume2 flowRate correctedToNTP comments end of table See table 6 1 samples Date and time of SOH data See table 3 1 samplers Air pressure difference in pascals Pa over the flow rate m
76. nt To Email address of the additional recipient Cc True if the message was authenticated True if the authentication passed the checking Comments in English en Summary of the IDC findings RLR Conclusions IDCSummary FIN and PREL See for this sample See 34 5 5 CTBT Sample Tracking This table is used to track the movements of the CTBT laboratory samples The table itself is not specific to CTBT samples The usage for other samples is pending on the overall Table 5 5 CTBT sample tracking ctbtSampleTrackings Field Type Length Flags idSample int 4 PFN dateTimelnld datetime 8 PN dateTimeOut datetime 8 location varchar 40 handledBy varchar 20 comments text 0 idSample samples idSample design of the tracking system idSample dateTimeInId dateTimeOut location handledBy comments Identification number of the sample measured See table 6 1 sam ples Date and time of the sample arrival to the location Date and time of the sample departure from the location Name of the location Name of the person who transferred the sample to the location or end of table is responsible for the sample at the location Comments in English en 35 36 Chapter 6 Measurement The core table of Linssi is samples which describes the radioactive sample when it arrives to the measuring facility This is entry point 2 to Linssi Ever
77. ntical to measurements spectrum but the values are floating point values First reference date and time which the activities may be corrected to Decay time in seconds s from start of spectrum acquisition to refTimel Second reference date and time which the activities may be cor rected to Decay time in seconds s from end of activity collection to refTime 2 References to the physical constants used e g ENSDF version year etc Spectrum baseline calculation method Spectrum peak analysis method Nuclide identification and activity calculation method Method of calculating uncertainties Method of calculating the decision level L 63 alpha beta searchStartChannel searchEndChannel searchThreshold numberOfPeaks totalCounts comments alpha defines the confidence 1 a on the a posteriori decision for accepting a gamma peak Value of a is used to reject against error of the first kind beta defines the confidence 1 8 on the a priori detection of a gamma line Value of 3 is used to reject against error of the second kind Peak search starts from this channel of the spectrum Peak search ends to this channel of the spectrum Value of the search threshold used given in the units of L See peakSearchSignificance above The value is dependent on the search method used Number of peaks in the spectrum Total number of counts in the spectrum Comments in English en 64 8 2 Peaks Table
78. on values The parameters of par1 par10 until the first null value are associated with bvar s of the lambda construct The association is by order i e the first parameter par1 refers to the first bvar The last bvar is the independent variable A function definition starts with a list of bvar s followed by a container tag apply ci cn or piecewise which must evaluate to a single value The following MathML tags are supported in SHAMAN Qualifier bvar Arithmetic and functions plus minus times divide power root degree tag not supported hence only square root available exp In sin cos tan Binary forms of logical operators eq gt lt geq leq Logical operators neq not and or Containers lambda ci cn apply piecewise piece otherwise Type attributes of ci and cn are not supported hence always treated as real The application producing the calibration function in MathML lambda notation is responsi ble for the correctness and numerical robustness of the function While Shaman does perform some rudimentary error checking on the function before use the conversion of the MathML function may involve some reordering of the function terms which while mathematically equivalent may cause numerically unstable functions to break An example of a linear function a bx is presented in the lambda calculus of MathML on the following page 58 Assuming for example that par1 and par2 have values of 2 1 and 1 2 res
79. ond in the decay chain 80 secondIsDaughter firstHalflife uncFirstHalflife secondHalflife uncSecondHalflife halflifeUnit netBranching uncNetBranching refRatio uncRefRatio zeroRatio uncZeroRatio refTime zeroTime uncZeroTimeLow uncZeroTimeHigh comments The second nuclide follows the first in the decay chain Note 1 Both firstIsDaughter and secondIsDaughter may be false but both cannot be true Note 2 If one is true the other one is a parent not necessarily a direct parent Half life of the first nuclide in units halflifeUnit Absolute one sigma uncertainty of firstHalflife in units halflifeUnit Half life of the second nuclide in units halflifeUnit Absolute one sigma uncertainty of secondHalflife in units halflifeUnit Half life unit The supported units are year y or a day d hour h minute m or min and second s Net decay branching from parent to daughter through the decay chain i e the product of branching fractions leading from parent to daughter One sigma absolute uncertainty of netBranching Activity of the first nuclide divided by the activity of the second nuclide at refTime One sigma absolute uncertainty of refRatio A priori assumed initial activity ratio between the first and the second nuclide at zeroTime If not given the nuclides must be long to the same decay chain i e either firstIsDaughter or secondIsDaughter must be true In that case it is assumed that the a
80. ouble 8 numberOfPeaks mediumint 3 totalCounts int 4 comments text 0 idMeas measurements idMeas idSample samples idSample blankIdAnalysis analyses idAnalysis backgroundIdAnalysis analyses idAnalysis inputIdAnalysis analyses id Analysis end of table This table contains general data about the analysis its input and how it has been performed Some general analysis results are also provided idAnalysis Identification number of the analysis idMeas Identification number of the measurement i e spectrum analyzed See table 6 8 measurements idSample Identification number of the sample measured See table 6 1 samples blankIdAnalysis Identification number of the analysis of the blank The analysis results of the blank are used in this analysis for blank subtraction backgroundIdAnalysis Identification number of the analysis of the background The analy sis results of the background are used in this analysis for background subtraction 62 inputIdAnalysis spectrumArrival analysisBegin analysisEnd inputParam interactiveLog type software swVersion analyst baseline strippedSpectrum peakSearchSignificance refTimel decayTimel refTime2 decayTime2 refConstants baselineMethod peaksMethod nuclideMethod uncCalcMethod 1cMethod Identification number of the analysis used as input for this analysis This analysis may be a continuation of the inputIdAnalysis or inputIdAna
81. pectively the function below evaluates to 2 1 1 2x lt mathml xmlns z http www w3 org 1998 Math MathML gt lt z lambda gt lt z bvar gt lt z ci gt a lt z ci gt lt z bvar gt lt z bvar gt lt z ci gt b lt z ci gt lt z bvar gt lt z bvar gt lt z ci gt x lt z ci gt lt z bvar gt lt z apply gt lt z plus gt lt z ci gt a lt z ci gt lt z apply gt lt z times gt lt z ci gt b lt z ci gt lt z ci gt x lt z ci gt lt z apply gt lt z apply gt lt z lambda gt lt mathm1 gt See SHAMAN input parser manual for more details on how to write these lambda con structs 10 59 60 Chapter 8 Analysis The analysis group of tables is in the core of the Linssi database Linssi is designed to be useful in a facility doing gamma ray spectrum analysis The sample collection and measure ment can very well be performed elsewhere and only the analysis results produced in house This is the entry point 3 to the database All the tables in this group are filled with gamma ray peak analysis and identification soft ware The amount of information may vary depending on the software used The number of fields in these tables is large and many programs are not able to provide enough in formation to fill them all Linssi developers have been using UNISAMPO SHAMAN and Aatami SHAMAN chains of software to provide all the information in these tables Our philosophy has been to be able to store
82. rchar 20 sourceReady datetime 8 detectorTemperature double 8 uncDetectorTemperature double 8 ambientTemperature double 8 ambientHumidity double 8 waitTime double 8 acgStart datetime 8 acqEnd datetime 8 acqRealTime double 8 acqLiveTime double 8 spectrumType varchar 8 firstChannel int 4 firstValidChannel int 4 lastValidChannel int 4 lastChannel int 4 spectrum longblob 0 spectrumSent datetime 8 comments text 0 idSample samples idSample sourceld sources sourceld measSetupld measurementSetups measSetupld blankIdMeas measurements idMeas backgroundldMeas measurements idMeas end of table A unique measurement identifier See table 6 1 samples The identifier of the measured source See table 6 3 sources We can identify two cases 48 measSetupld blankIdMeas backgroundIdMeas measId phdMeasName extMeasName sourcePreparedBy sourceReady detectorTemperature uncDetectorTemperature ambientTemperature ambientHumidity waitTime acqstart acqEnd acqRealTime acqLiveTime spectrumType firstChannel firstValidChannel Case 1 If we are using a standard measurement setup without changes in the source geometry then sourceld here should be set to null In this case the relevant geometry information is found using measSetupId below Case 2 If the source is not describing a standard geometry the geometry is defined by sourceld The analysis software is able to c
83. rtainty of the 9 parameter of the calibration function ncertainty of the 10 parameter of the calibration function omments in English en Che ere Cda EE Q 93 7 2 Calibration Points This table contains calibration point values and their uncertainties given as triplets xValue Table 7 2 Calibration points calPoints Field Type Length Flags idCalPoint int 4 PN idCal int 4 PIFIN calTypeld varchar 20 PIFIN idAnalysis int 4 F2 idPeak int 4 IF2 xValue double 8 yValue double 8 uncYValue double 8 comments text 0 idCal calTypeld calibrations idCal calTypeld idAnalysis idPeak peaks idAnalysis idPeak end of table yValue uncYValue sorted in an ascending order with respect to xValue It is not mandatory to have all the calibrations associated with spectrum analysis results For those calibrations idAnalysis null This might be the situation in the case of off line calibrations It is however recommended that the user assigns an entry in the analyses table even for these cases The entry and the corresponding peaks table provide ample space for justifying the calibration idCalPoint idCal calTypeld idAnalysis idPeak xValue yValue uncYValue comments Index of the calibration point For each idcal calTypeld the num bering starts from 1 Identification number of the full calibration The full calibration consists
84. ry application However these are the generic fields readily available from our analysis software and with modern computers the overhead due to unused database fields is negligible We have made every effort to provide a database with information that is generic i e not depending on the specific software used An example of this type of information is nuclide activity It does not depend on the analysis software used even though the results vary On the other hand there exist tens of different peak shape models for example We have provided a relatively flexible model but there certainly exist software for which our definitions do not apply without user modifications The Linssi design assumes three main entry points to the system Fig 1 2 They are sample production entry point 1 sample measurement entry point 2 and spectrum analysis entry point 3 In addition there is the entry point O denoting the station group of tables Ch 2 which can be updated relatively independently from the other table groups In the time line of the analysis we assume that the stations have existed forever In entry point 1 we start from the production or collection of activity to form the sample That can be done in a multitude of ways Currently version 1 1 we have defined three different sample types air filter samples Ch 3 calibration samples Ch 4 and CTBT laboratory samples Ch 5 The CTBT samples are quite specific and the calibration samp
85. s Identification number of the sample measured See table 6 1 samples 78 energyPriLine area uncArea baselineArea uncBaselineArea decisionLimit detectionLimit mda mdc significance significanceFlag comments Energy of the primary line of this nuclide in kiloelectronvolts keV Note the primary line is not necessary the one with the highest emission probability The primary line is defined by the analysis software on the basis of maximum visibility in this analysis The MDA is calculated on the basis of this line Area of the peak at energy energyPriLine in counts Absolute one sigma uncertainty of area in counts Area of the baseline at energy energyPriLine in counts used to calculate activity limits Note this is NOT the baselineArea of table 8 2 peaks Absolute one sigma uncertainty of baselineArea in counts Decision limit in counts This corresponds the value of a in 8 1 analyses Detection limit in counts This corresponds the value of 3 in 8 1 analyses Minimum detectable activity in becquerels Bq decay corrected to start of counting See also the note on specific activity below Minimum detectable concentration The unit may be Bq m Bq g etc depending on the application It is based on the raw activity as defined in Fig 8 1 and table 8 5 activities See also the note on specific activity below Peak area in the units of decision limit i e area divided by decisionLimit Flags indicating pe
86. s The fourth of the four parameters reserved to define the baseline function Emission rate of the source in gammas per second 1 s at peak energy i e peak area divided by the live measuring time and ef ficiency The contribution from blank and background have been subtracted One sigma absolute uncertainty of the emission rate Contribution of the background to peak count rate in counts per second 1 s as derived from backgroundIdAnalysis See table 8 1 analyses Note these are peak counts not baseline counts One sigma absolute uncertainty of background count rate in counts per second 1 s Type of the background detector detector blank etc where detector means background only and detector blank gives the contribution from both the background and blank If detector blank is given blankCps below must be zero Contribution of the blank to peak count rate in counts per second 1 s as derived from blankIdAnalysis See table 8 1 analyses Note these are peak counts not baseline counts One sigma absolute uncertainty of blank count rate in counts per second 1 s Type of the blank blank blank detector etc where blank means blank only i e the background contribution to blank has been subtracted or negligible and blank detector gives the con tribution from both the background and blank If blank detector is given backgroundCps above must be zero Comments in English en Note on peak origin flags The syntax of
87. s it is when placed in the measuring position Ifthe source is processed from a sample see Case 2 below it should contain all the radioactivity of the sample except for decay and possible unavoidable losses in the preparation If the sample has been deliberately split or combined a new sample must be first formed and that sample should be the subject of source preparation This table aims to describe the geometry and material of the source which includes the container to the extent sufficient for Monte Carlo simulation of the measuring process when used together with the rest of the measurement setup sourceld idSample A unique name of the source Identifies the sample See table 6 1 samples We can identify two Cases Case 1 If the source is used to describe a standard measurement setup i e its sourceld appears in table 6 7 measurementSetups then idSample here should be set to null In this case all the relevant samples are found from the calibration tables associated with the measurement setup in question 41 sourceGeometry sourceThickness sourceHeightMar sourceWidth sourceLength sourceDiami sourceDiam2 sourceLayers sourceDensity sourceMass sourceMaterial contDens contThick contMaterial preparationMethod comments Case 2 If the source is not describing a standard geometry idSam ple must be given In this case the analysis software is using the geometry information of the source to calculate a new or
88. sages Field Type Length Flags idMessage int 4 PA messageld varchar 20 N senderSiteCode varchar 16 N idSample int 4 F idAnalysis int 4 F reportNumber int 4 messageType varchar 40 messageDataType varchar 40 reportType varchar 3 messageldRef varchar 20 siteCodeMessageRef varchar 16 transmission datetime 8 receipt datetime 8 messageBody longblob 0 labDataVersion varchar 20 labDataVersionText text 0 receivedFrom varchar 80 sentTo text 0 ccTo text 0 authentication Boolean 1 authenticationPass Boolean 1 comments text 0 idcActSummary text 0 idSample samples idSample idAnalysis analyses idAnalysis end of table For a more precise definition of the fields the user is asked to consult the report IDC3 4 1Rev6 6 to which the descriptions below are referencing The reference RLR xxx refers to the data block xxx of the radionuclide laboratory report RLR RLR and the related data blocks are described in Chapter Radionuclide Laboratory Reports of the report IDC3 4 1Rev6 6 idMessage messageld senderSiteCode idSample idAnalysis Linssi identification number of the message Identification code of the message as represented in the message itself See id_string of MSG_ID in Chapter Message Structure of IDC3 4 1Rev6 6 Site code of facility where the message is originated See source in MSG_ID in Chapter Message Structure of IDC3 4 1Rev6 6 Iden
89. sample at this point The sample is further processed into the actual source geometry table 8 to be put on the spectrometer From the sample it is possible to produce different sources for example by using different containers As long as the radionuclide content is not changed we are dealing with the same sample It has just been transformed to a new source Now the source is measured in a measurement setup described in table 12 The setup uses a detector attenuator and shield described in tables 9 10 and 11 respectively Important information of the measurements themselves and most importantly the measurement results i e gamma ray spectra are stored in table 13 The measurements are followed by analyses General information on analyses is stored in table 16 Analysis itself relies on calibrations of tables 14 and 15 The traditional gamma ray spectrum peak analysis results are stored in table 17 They are followed by the identification and activity calculation results tables 18 and 19 respectively 2 stations 3 sample production tables Bold primary key stationdd xxx samples group Italic primary and foreign key CTBT lab samples Normal foreign key 1 weathers Calibration samples group Underline self pointing foreign key stationld Air filter samples group weatherTimeld connection no connection 4 mobileCoordinates 4 combined foreign key ref idPosition positionSource 17 peaks stationld i
90. tations The starting date and time of the weather report period The ending date and time of the weather report period Average wind direction in degrees 0 360 0 North Average wind speed in meters per second m s Average temperature in degrees centigrade C Lowest temperature in degrees centigrade C during the report period Highest temperature in degrees centigrade C during the report period Amount of snowfall in millimeters mm in the report period Amount of rainfall in millimeters mm in the report period Average relative humidity of air in percent Average air pressure in hectopascals hPa Weather stability class Comments in English en 13 14 Chapter 3 Air Filter Samples 6 airFilterSamples 7 samples idSample sampleProductionTable airFilterSamples 2 stations 5 airFilterSOH samplingHealthTimeld samplerld 3 samplers Figure 3 1 Tables of the air filter sample production group 3 5 and 6 and their connection to other Linssi tables 2 and 7 Air filter sampling is covered by the tables of the air filter samples group Fig 3 1 The three tables 3 5 and 6 define the entry point 1 The table samplers defines the static properties of the sampler The table airFilterSamples gives the information of the sam pling specific to a given sample Finally the table airFilterSOH contains information of the State Of Health of the sampler as a
91. the sample splits are combined together the split number P is set equal to p 1 Therefore if the three sample splits from the previous example are combined together the split identifier reported is 43 This definition is a generalization of the one described in Ref 6 The split symbol is useful for tagging simple splits For more complex cases of splitting and combining samples table 6 2 sam pleSplitsCombines should be used If both the table sample SplitsCombines and splitSymbol are used it is up to the user to make sure that they are consistent TRUE if the sample is formed by splitting other samples For fur ther information see table 6 2 sampleSplitsCombines TRUE if the sample is formed by combining other samples For further information see table 6 2 sampleSplitsCombines Type of the sample The following types are reserved air filter calibration environmental qcspectrum blank background gassample gasbackground 38 sampleProductionTable overallAct barcode sealNumberArrival sampleConditionArrival packConditionArrival sealConditionArrival sampleCondFlagArrival sampleArrivalTime sampleReceivedBy dbEntryTime comments Name of the table describing the creation of this sample Currently tables airFilterSamples calibrationSamples and ctbtLab Samples have been defined Approximate overall activity in becquerels Bq Knowledge is use ful when deciding the measurement setup and for radioprotection purposes
92. tification number of the sample measured See table 6 1 sam ples Identification number of the analysis See table 8 1 analyses 33 reportNumber messageType messageDataType reportType messageldRef siteCodeMessageRef transmission receipt messageBody labDataVersion labDataVersionText receivedFrom sentTo ccTo authentication authenticationPass comments idcActSummary Number of the report See RLR Header Message type i e request subscription data labdata command_request or command_response See MSG_TYPE in Chapter Message Structure of IDC3 4 1Rev6 6 Message data type See DATA_TYPE in Chapter Message Struc ture and the specific radionuclide data types in Chapter Radionu clide Messages in IDC3 4 1Rev6 6 Message report type Valid values are RLR Header A reference to the message for which this message is a response to i e the ref str of the REF_ID See MSG_TYPE and REF_ID in Chapter Message Structure of IDC3 4 1Rev6 6 A reference to the message for which this message is a response to i e refsrc in REF_ID in Chapter Message Structure of IDC3 4 1Rev6 6 Date and time of the transmission of the message Date and time of the receipt of the message The full text of the message Version of message format used See RLR LabDataVersion Notes regarding the message format See RLR LabDataVersion Email address of the sender From Email address of the recipie
93. to adjust an existing calibration See field sourceld in table 6 8 measure ments Name of the source geometry This name identifies the meaning of the source measures below Thickness of the source in millimeters mm Height of the Marinelli beaker source in millimeters mm Width of the source in millimeters mm Length of the source in millimeters mm Outer diameter of the source in millimeters mm Inner diameter of the source in millimeters mm Number of layers in the source Density of the source in grams per cubic centimeter g cm Mass of the source in grams g Name of the source material Density of the source container in grams per cubic centimeter g cm Thickness of the source container in millimeters mm Name of the source container material Describes how the source has been made from the sample Comments in English en 42 6 4 Detectors Table 6 4 Detectors detectors Field Type Length Flags detectorld varchar 40 PN location varchar 40 detectorModel varchar 40 detectorType varchar 20 relEfficiency double 8 volume double 8 diameter double 8 thickness double 8 coreDiameter double 8 coreLength double 8 endcapToCrystal double 8 windowMaterial varchar 20 windowThickness double 8 deadLayerThickness double 8 biasVoltage double 8 polarity varchar 10 comments text 0 end of tabl
94. ts text 0 idAnalysis analyses idAnalysis idMeas measurements idMeas idSample samples idSample end of table This table contains analysis results of spectral peaks One record is used for each peak analyzed In addition to the normal software dependence of all the results it should be noted that many peak parameters may either be taken directly from the calibrations or calculated from spectral data idPeak idAnalysis idMeas idSample centroidChannel uncCentroidChannel energy uncEnergy area uncArea height width fwhm fwtm lowTail Peak index i e the number of the peak in the analysis idAnalysis The list is sorted in an ascending order according to peak channel and starting from 1 Identification number of the analysis See table 8 1 analyses Identification number of the measurement See table 6 8 measurements Identification number of the sample measured samples Channel of the peak centroid ch One sigma absolute uncertainty of the centroid channel in channels ch Peak energy in kiloelectronvolts keV One sigma absolute uncertainty of peak energy in kiloelectronvolts keV Peak area in counts Note baseline area has been subtracted but the contributions from the blank and background not One sigma absolute uncertainty of area in counts Peak height in counts One sigma peak width in channels ch Full width at half maximum of the peak in channels ch Full widt
95. y time an entry is created in Linssi tables it must have a corresponding entry in samples or the entry must be simul taneously created The only exception is the station group of tables which do not require a sample See Ch 2 The radioactivity contained in the sample is converted to the actual source sources which is measured using a setup comprising measurementSetups detectors attenuators and shields Fig 1 3 The data on the measurement and the resulting spectrum are stored in table measurements If the sample is split or combined its history can be reconstructed using the information in table sampleSplitsCombines 6 1 Samples Table 6 1 Sample description at arrival samples Field Type Length Flags idSample int 4 PA sampleld varchar 80 UN phdSampleName varchar 80 extSampleName varchar 80 splitSymbol varchar split Boolean 1 combined Boolean 1 sampleType varchar 20 sampleProductionTable varchar 20 overallAct double 8 barcode text 0 sealNumberArrival varchar 20 sampleConditionArrival text 0 packConditionArrival text 0 sealConditionArrival text 0 sampleCondFlagArrival char 1 continued on next page 37 continued from previous page Field Type Length Flags sampleArrivalTime datetime 8 sampleReceivedBy varchar 20 dbEntryTime timestamp 4 comments text 0 end of table This table describes
96. yCoordinate altitude hDOP vDOP pDOP age fix comments Position identifier Note 1 Since idPosition is only a part of the combined primary key it does not need to be unique This can be use ful when postprocessing of records in mobileCoordinates is needed The postprocessor may store a modified record back to mobileCo ordinates table with identical idPosition and stationId but with differing positionSource Note 2 We recommend the use of Unix timestamp as the position identifier Name of the source providing the coordinates The station may have multiple GPS navigators for example or the source may be the post processor mentioned above See table 2 1 stations See table 6 1 samples See table 6 8 measurements The following position types are defined null If both idMeas and idSample are null this is a raw unprocessed position If not this is a measurement or sampling position route A processed and validated point on station s route gap Before this position there is a gap in position information GPS may have been off or lost its connection with satellites for example Date and time of the coordinate information Name of the mission Name of the coordinate system in use Station speed in meters per second m s Direction the station is heading in degrees 0 360 0 North Number of satellites the GPS navigator sees x coordinate or longitude of the mobile station y coordinate or latitude of th

Manual - LINSSI

Contents

Download Pdf Manuals

Related Search

Related Contents