Changes to Linssi Manual Part I: DATABASE v.1.1
Date: August 22, 2006
Author: Pertti Aarnio
Here I give a list of significant changes to Linssi manual
part I: DATABASE since the release of draft Linssi database version December 3, 2004.
The final release of Linssi version 1.1 is dated July 7, 2006. See Linssi release notes for details.
1. Database changes
- Section 5.
- Section CTBT-laboratory samples has been rewritten because
the tables themselves have been changed. Because of this we should have changed
the database version from 1.1 to 1.2, since the database definition itself has
changed. However, the only facility that has been using CTBT tables is FINDC.
In addition, scripts and their documentation use extensively the version number
1.1 instead of 1.2.
- To cover this loophole we state that the July 2006 database
manual is the official documentation of Linssi database version 1.1. All
earlier documentation should be considered drafts.
2. Documentation improvements
Lots of typos and wording has been corrected. Below we list
the ones you probably need to pay some attention to.
- All sections
- The representation of tables contains now explicit
description of foreign keys and the primary keys they are referencing. Some new
column flags are also used.
- Section 1.3
- Foreign and combined foreign keys are better marked in Fig.
- Section 1.5
- The new column flags are explained here.
- Section 7.5.1
- In draft versions MathML functions were defined in functionDef
but no index was reserved for MathML in function. Implicitly it
meant that if function = NULL functioDef contains a MatML
description of the function. To be explicit, and thus facilitate simpler
parsing, the function value 0 is now reserved for MathML. Note that function
= 99 is still reserved for undefined functions whose representation in functionDef,
if any, is not in MathML.
- Section 7.5.2 and 7.5.3
- Usage of MathML has been clarified.
- Section 8.2
- The usage of peakOrigin has been clarified.
- Section 8.3
- Added a note to the emissionProb to clarify the fact
that its unit is NOT %. The usage itself has been correct all the time.
- Section 8.5
- A note on activity has been added to clarify a situation
where MDA (and raw activity) must be given in terms of specific activity.