LINSSI DATABASE RELEASE NOTES
2006, 32 tables with 557 fields
The CTBT-laboratory tables have been
modified by introducing
13 new fields.
usage of version number 1.1 in scripts and in the internal documentation of the
developers refers consistently to this version, and
changes in CTBT-tables affects only the Finnish CTBT laboratory,
version number has not been
Version 1.1 (preliminary release)
January 2005, 32 tables with 544 fields.
Under script testing at STUK from 7th
Ready 3rd December 2004 (1.1 beta 4.7).
A new consistent naming convention, defying English, for all
the tables was adopted requiring plural and dropping Data-endings. The
changed names are (old ones in parenthesis): weathers (weather), stations
(station), samplers (sampler), airFilterSOH (samplingSOH), airFilterSamples
(samplingData), samples (sampleData),
sources (source), detectors (detector), attenuators (attenuator), shields
(shield), measurementSetups (measurementSetup),
measurements (measurementData), calibrations (calibrationData), analyses
(analysisData), peaks (peakData), lineAssociations (peakAssociations),
activities (activityData), activityLimits (mda). Below
we will use the new names.
Calibration and calibration point tracking
This is a major new feature facilitating tracking of the
calibration history and the origin for each calibration point.
- A new table for calibration data points named calPoints
was established. Its purpose is to provide detailed information of each
calibration. Table calPoints establishes
many-to-many relation between table calibrations and analyses/peaks. That
provides the ability to base each calibration point to any peak in any
analysis. On the other hand, any analysis and/or peak can now serve as a
source for any calibration point. Adding this table made the fields
calDataPairs and idMeas in table calibrations obsolete and they were
history tracking was also improved by adding field inputIdCal
to table calibrations. The field points to a calibration, if any, that has
been a basis for this calibration. Following the chain backwards all the
members of the chain can be reached. In order to further support this
feature a Boolean field changed was added. This is useful since the full
calibration (idCal) must always be saved even if
only one calibration type (idCal.calTypeId) has
further information on the calibration a field class was added to table
calibrations. This field provides information on the origin of this
calibration, whether it has been obtained with the spectrum, is a
State-Of-Health-update of the calibration, etc.
As a consequence table calDataSOH has been removed.
ease the tracking the field creationTime was forced to NOT NULL.
Calibration usage in analysis
This major new feature provides information on which
calibrations have been used and how they are used in analyses.
- For the purpose a new table calPreferences was
postulated. It provides also a many-to-many relationship between table
analyses and calibrations (primary keys: idCal
and idAnalysis, other fields:usedInAnalysis (Boolean)).
At this time, however, we
are not interested on how the calibrations have been produced but how they
have been used in analyses. Analysis software may have several alternative
calibrations available for a given spectrum but only one can be chosen to
provide the analysis results. For that idCal.idAnalysis
only the field usedInAnalysis is TRUE.
order to be able to make source geometry corrections to calibrations the
analysis software needs to have access to the reference source of the
measurement setup, measurementSetups.sourceId
.as well as to the source measured, measurements.sourceId.
The latter was missing, i.e., now field sourceId
has been added to table measurements.
- Since table calPreferences provides the relation
between tables analyses and calibrations the field idCal
has been removed from table analyses.
Tables for defining calibration samples were defined. These
tables are used if field sampleProductionTable in
table samples is calibrationSamples. These tables
provide the information of the calibration samples (most importantly the
contained nuclides and their certified activities), their certificates and
nuclear data used in connection of the analysis of these samples. The following
new tables have been defined: calibrationSamples, calibrationNuclides, and
Tables for radionuclide laboratories of the Comprehensive
Nuclear-Test-Ban Treaty were added. These tables support the protocol used
within CTBT when sending samples to radionuclide laboratories for measurement
and analysis. These tables are used if field sampleProductionTable
in table samples is ctbtLabSamples. The following
new tables have been defined: ctbtLabSamples, ctbtMessages, ctbtTransports,
ctbtRecipients, and ctbtSampleTrackings.
Control of combined and split samples
Some (daughter) samples may be a
result of splitting, or combining, one or more (parent)samples. If we have the
information of the parent-daughter-relationships, however complicated it may
be, we can store it in a new table sampleSplitCombines.
The primary keys are parentIdSample and daughterIdSample, which provide many-to-many-relationship
between the samples in table samples. Other relevant fields in table
sampleSplitsCombines are activityBranching
Experiences gained in SONNI dictated the following additions
to table mobileCoordinates.
new primary key idPosition was added. The name
of mobileTimeId was changed to positionTime and its
type changed from primary key to
name of the field gpsName was changed to
positionSource and its type changed to primary key.
type of the field idMeas was changed to foreign
key. Foreign key idSample was added.
name of posDilPfPrecision was changed to pDOP.
Fields hDOP and vDOP were added.
x- and y-coordinates of position are not necessarily the longitude and
latitude the names of the fields were changed to xCoordinate
two new fields were added: positionType, fix
facilitate simple time zero calculations based only on the information
obtainable from LINSSI following fields were added to table
nuclideRatios. Half-lives and their uncertainties of
both nuclides, i.e., firstHalflife, uncFirstHalflife, secondHalflife,
uncSecondHalfLife and halflifeUnit.
Branching ratio and its uncertainty, i.e., netBranching
and uncNetBranching. Activity ratio at zero time
and its uncertainty, i.e., zeroRatio, uncZeroRatio.
of ratioFirstToSecond and uncRatio
were changed to refRatio and uncRefRatio,
uncertainty of zeroTime was added, i.e., uncZeroTimeLow,
The changes below are shown for each table. Table ordering
is the same as in the manual. Unrelated changes are shown as separate items.
The changes already described above are not presented here.
tables. The lengths of the varchar fields were
restricted to following values 4, 8, 10, 20, 40, 80, and 255=max. The
existing lengths were rounded upwards to the nearest
samples. Field split was changed to splitSymbol (varchar) to
support the now
depreciated split naming concept of the CTBTO. A Boolean field split was
added to inform that the sample is a result of splitting its parent(s).
samples. A new field sampleReceivedBy was added.
samples. The name of the field samplingTableName
was changed to sampleProductionTable, which more
properly describes its meaning now that we have postulated three types of
sample production methods: airFilterSamples (old
sources. Fields idSample and preparationMethod
have been added.
measurementSetups. New fields blankIdAnalysis and bacgroundIdAnalysis
were added. These fields point to table analyses that
provides the results of the background and blank measurement for
this measurement setup.
analyses. Fields strippedSpectrum (spectrum
minus peak functions) and peakSearchSignificance
(peak significance at each channel of the spectrum given by the peak
search algorithm) have been added.
peaks. The name of the field searchSens was
changed to searchSignificance in order to be
consistent with peakSearchSignificance.
peaks. Field peakOrigin was added. This is a
character string providing a set of flags denoting the peak origin. As a
consequence the fields multiplet and inserted
lineAssociations (ex peakAssociations).
For evaluation of the analysis results the following Boolean fields were
added: primaryLine, ThresholdLine,
found, foundClose and lineSignificance
(double). Boolean fields neutronScatter
and neutronCapture were added to support
additional line types.
lineAssociations (and activities). In order to
support off-line, possibly manual, activity calculations fields
uncLineEnergy, emissionProb, and uncEmisssionProb
were added (and the corresponding fields from table activities removed).A
Boolean field actMan was added. This field informs
if the line has been used in calculation of actRawMan.
activities. See table lineAssociations above.
activities. Fields CCfactor and uncCCfactor were removed since
they were already in
activities. Fields netCountRate, uncNetCountRate, efficiency, and
were removed since they were already in table peaks.
activities. The requirement for actRawLSQ and actRawPriline to be
interference corrected was removed
and Boolean fields interfCorrLSQ and interfCorrPriLine were
added to inform whether the
interference correction has been applied or not.
activities. Fields actRawMan, uncActRawMan, and actRawManMethod(varchar)
were added to support off-line, possibly
manual, activity (actRawMan) calculations.
activities. Boolean field actSelect was added.
The field informs which activity has been deemed the correct one by the
analyst. The possible values are: LSQ, PRI, MAN
corresponding the three activities provided in the table.
activities. All the decay corrected activities were removed since they are
readily available from the raw activities (actRawLSQ,
using the correction factors of the table.
activities. Irradiation correction irrCorr and
its uncertainty uncIrrCorr were added. This
correction can be used to calculate saturation activities.
finalResults. Field idResult
was removed. Boolean field lowQualitySpectrum
was added. Field projectFileName was replaced
with field projectFile (longblob).
February 2004, 26 tables with 499 fields
In operation at the FiNDC
name sourceData changed to source.
key idSample removed from source.
overallAct moved from source to sampleData
sourceReady and preparedBy
moved to measurementData.
idSource (int) changed
to sourceId (varchar)
in source and measurementSetup.
key detectorId removed from measurementData.
isBackground added to activityData.
January 2004, 26 tables with 500 fields
The database schema was frozen today with the last changes
given below. Manual updating and proof reading are still pending.
eff for effective was added to fields halflife, halflifeUnit, uncHalflife,
i.e., they were changed to effHalflife, effHalflifeUnit, uncEffHalflife
in table activityData. This was done a) because
the halflife is effective, b) to accommodate the
calibration certificate and library extension being developed for a later
version of Linssi.
were changed to flowFactor1, flowPower1, flowFactor2, flowPower2 in table
sampler. These parameters describe the flow meters in a two channel
sampler. They have nothing to do with the filters in these channels.
weatherTimeId renamed to weatherTimeStartId
and added weatherTimeEnd in table weather. Now
we have both the staring and ending time of the weather report period in Linssi. Earlier version required continuous availability
of the reports.
field correctedToNTP has been added to samplingData and samplingSOH.
sourceDiam renamed to sourceDiam1 and added
sourceDiam2 to table source. Now we have room for outer and inner source
creationDate renamed to creationTime
in tables calData and calDataSOH
for consistency reasons.
energyPriLine renamed to energy and added uncEnergy to table activityData.
Ordering of the table has been changed; first library info of the nuclide
and line parameters, then info at the peak associated with the primary
line, then activities, then decay corrections.
removed, i.e., defaults are all null.
stationId in table sampler renamed to stationName, which is not a foreign key.
pressDiff and airVolume
in table samplingDataSOH replaced with fields
pressDiff1, airVolume1, pressDiff2 and airVolume2.
foreign key stationId added to table samplingData.
and pressure difference fields in table samplingData
have been replaced with airVolume, airVolume1,
pressDiff1Start, pressDiff1End, airVolume2, pressDiff2Start,
analysisMethod removed from table analysisData.
kAlpha and kBeta
changed to alpha and beta in table analysisData.
and blankType added to table peakData.
of coincSumPeak and randomSumPeak
changed to coincSum and randomSum
in table peakAssociations
idRatio removed from table nuclideRatios.
Fields firstNuclideId and secondNuclideId
moved immediately after idAnalysis. This triplet
forms the primary key.
projectFilename (type blob) added to table finalResults.
pages opened for limited access. Manual uploaded.
useThisCalibration removed from table calData.
idCal added to table measurementSetup.
For older versions below the release notes are available in Finnish.
January 2004. 26 tables, 486 fields
December 2003. 26 tables 477 fields
In operation at the FiNDC from
mid-December 2003 to 2nd February 2004
November 2003. 25 tables, 466 fields
November 2003. 25 tables, 459 fields
October 2003. 24 tables, 444 fields
October 2003. 22 tables, 428 fields
October 2003. 22 tables, 426 fields
June 2003. 22 tables, 365 fields
In operation at the FiNDC from
July 2003 to mid-November 2003
February 2003. 22 tables, 342 fields
September 2002. 7 tables
In operation at the FiND from
October 2002 to June 2003