Changes between Version 42 and Version 43 of DatabaseBasedAnalysis
- Timestamp:
- 08/05/18 11:05:03 (6 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
DatabaseBasedAnalysis
v42 v43 1 1 [[TOC]] 2 2 3 = Purpose=3 == Purpose == 4 4 5 5 The idea is to write all image parameters for data and Monte Carlo files into a database, so that the access to the data becomes more easy. To some extend (also not necessarily very efficient) the database server can already do the analysis. Everybody is free to use the programming language or tool of their choice to do the analysis. Writing the data to be analysed into a root file has the advantage that no additional software installation other than root itself is required. However, be aware that the files can easily become large. 6 6 7 = Status=7 == Status == 8 8 9 9 Most of the data is in the database. Due to some technical reasons still about 1/5th of the data is missing. Most of it from 2016 (seems 2016 the data was more noisy). No automatic process is currently updating the tables and no process is replicating the existing data from La Palma. 10 10 11 = Basics =11 == Basics == 12 12 13 13 Although this page will give some basic examples how to implement an analysis, this is neither an analysis tutorial nor a reference guide to SQL or the required tools. For this, please refer to their manuals. Here are a few examples: … … 19 19 * MySQL++: https://tangentsoft.com/mysqlpp/home 20 20 21 = Connecting to the Database=21 == Connecting to the Database == 22 22 23 23 DatabaseBasedAnalysis/Connection 24 24 25 = Tools to access the database = 25 == Tools to access the database == 26 27 === mysql === 28 29 The mysql client is the classical way to connect to the database and get data. Data is retrieved from a MySQl database always as pure ascii. {{{mysql}}} can print the ascii table to the console either as a nicely formatted text or as a machine readable ascii table. 26 30 27 31 === rootifysql === … … 37 41 To get a fast glimpse on the accessible databases and tables, you can log-in to !PhpMyAdmin at http://iph-pc45.ethz.ch/phpmyadmin 38 42 39 = The Analyis=40 41 == Data Selection==43 == The Analyis == 44 45 === Data Selection === 42 46 43 47 For data selection only run-wise information should be relevant which are stored in the table '''RunInfo'''. The reason is that if you select data on a more fine grained level (e.g. event-wise zenith angle), right now there is no easy method to determine the corresponding observation time. So whenever data is selected event-wise make sure that you do not cut the data in a variable which cuts out events systematically and not randomly. For example, an event-wise cut in zenith angel usually keeps or discards two consecutive events because their zenith angle is correlated. For a cut in any image parameter (Width, Length, Size, ...), the result on two consecutive events is random because their image parameters are not correlated. … … 236 240 root [3] 237 241 }}} 238 239 240 241 242 243 244 245 246 242 247 243 == Data retrieval ==