[[TOC]]

This is an overview of the most important tables and some important remarks. Links are given to the comments and type of each column.

== !RunType ==

[https://fact-project.org/run_db/db/printinfo.php?db=factdata&fSortBy=ColumnName+&t=RunType factdata/RunType]

== Source ==

[https://fact-project.org/run_db/db/printinfo.php?db=factdata&fSortBy=ColumnName+&t=Source factdata/Source]

== !RunInfo ==

[https://fact-project.org/run_db/db/printinfo.php?db=factdata&fSortBy=ColumnName+&t=RunInfo factdata/RunInfo]

The !RunInfo table is the most important one. It stored run-wise information. In a first step, a lot of data is directly extracted from the header of the ''raw'' run-files. Later, values are calculated from other sources, mainly slow-control file (auxiliary data: ''aux'') and filled into the table as well.

=== Calculating the on-time ===

The best estimate for the on-time of the data acquisition is the difference between the first and last event (`fRunStop-fRunStart`). It should be precise with roughly the data rate, so better than 1s. The on-time calculated by the FTM is only precise with the FTM rate which is a few seconds, but the FTM provides accurate information on the relative on-time w.r.t. to the total time. This information can be used to calculate the on-time in seconds of a run as follows:

{{{#!sql
TIME_TO_SEC(TIMEDIFF(fRunStop,fRunStart))*fEffectiveOn
}}}





== Events ==

--- not yet available ---

== Position ==

--- not yet available ---

== AnalysisResultsRunISDC ==

[https://fact-project.org/run_db/db/printinfo.php?db=factdata&fSortBy=ColumnName+&t=AnalysisResultsRunISDC factdata/AnalysisResultsRunISDC]

The number of background events (`fNumBgEvts`) is already divided by the number of wobble regions (5).

To calculate the signifciance, you can simply do `LiMa(fNumSigEvts, fNumBgEvts). To calculate the statistical error, use `ExcErr(fNumSigEvts, fNumBgEvts)`. Both function assume that the number of background events given is the average number and that the scale factor is 5.