Changes between Version 244 and Version 245 of DatabaseBasedAnalysis/Spectrum


Ignore:
Timestamp:
12/10/19 14:07:43 (5 years ago)
Author:
tbretz
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • DatabaseBasedAnalysis/Spectrum

    v244 v245  
    113113== Get Data File List ==
    114114
    115 A list with file IDs containing the events to be analyed is required a.t.m. The following query retrieves such a list and fills a temporary table (!DataFiles) with the IDs.
     115A list with file IDs containing the events to be analyed is required a.t.m. The following query retrieves such a list and fills a temporary table (`DataFiles`) with the IDs.
    116116
    117117{{{#!Spoiler
     
    148148== Get Observation Time ==
    149149
    150 The following query bins the effective observation time of the runs listed above in zenith angle bins and stores the result in a temporary table (!ObservationTime). Note that the result contains only those bins which have entries.
     150The following query bins the effective observation time of the runs listed above in zenith angle bins and stores the result in a temporary table (`ObservationTime`). Note that the result contains only those bins which have entries.
    151151
    152152{{{#!Spoiler
     
    179179== Get Monte Carlo File List ==
    180180
    181 The next query obtains all Monte Carlo runs which have their !ThetaMin or !ThetaMax within one of the bins obtained in the previous query (so all MC runs that correspond to bins in which data is available). Strictly speaking, this step is not necessary, but it accelerats further processing. In addition (here as an example) only runs with even FileIDs are obtained as test-runs (assuming that odd runs were used for training). The resulting FileIDs are stored in a temporary table (!MonteCarloFiles).
     181The next query obtains all Monte Carlo runs which have their !ThetaMin or !ThetaMax within one of the bins obtained in the previous query (so all MC runs that correspond to bins in which data is available). Strictly speaking, this step is not necessary, but it accelerats further processing. In addition (here as an example) only runs with even FileIDs are obtained as test-runs (assuming that odd runs were used for training). The resulting FileIDs are stored in a temporary table (`MonteCarloFiles`).
    182182
    183183{{{#!Spoiler