1 / 15

Monte-Carlo Event Database: current status

Monte-Carlo Event Database: current status. Sergey Belov, JINR, Dubna. Outline. Introduction CMS MCDB – pros and cons Main features of LCG MCDB Main interfaces Technical implementation Current project status Future plans. Introduction.

hritchey
Download Presentation

Monte-Carlo Event Database: current status

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Monte-Carlo Event Database: current status Sergey Belov, JINR, Dubna

  2. Outline • Introduction • CMS MCDB – pros and cons • Main features of LCG MCDB • Main interfaces • Technical implementation • Current project status • Future plans

  3. Introduction • Correct Monte Carlo simulation of complicated processes requires rather sophisticated expertise • Different physics groups often are in need of the same MC samples • Public availability of the event files speeds up their validation • Central and public location where well-documented event files can be found would be very useful

  4. CMS MCDB Problems • Stores parton level events only • The expected number of physics processes in the database is several hundred (data are stored on AFS so there is a space limitation) • Cannot serve sophisticated queries owing to it isn’t SQL based Advantages • Based on web technologies • Stores detailed documentation for each set of event samples • Storing data on AFS let make its easy of access • Provide rapid communication between users and experts

  5. Main features of LCG MCDB The most important reason to develop LCG MCDB is to expel the restrictions of CMS MCDB • An SQL-based database • Wide search abilities • Possibility to keep the events at particle level as well as at partonic level • Direct programming interface from LCG collaboration software • Inheritance of all the advantages of the predecessor - CMS MCDB

  6. General conceptions and terms • Event file (sample) – the file containing particle or partonic events • Article – a document describing the set of samples • Event data – the events themselves, all the data are stored into event files • Event metadata – information which describes all events in a sample in general (beam description, physics parameters, applied cuts, etc.)

  7. MCDB interfaces • Search form • Article management (creating, changing, removing) • Downloading sample files • User management (registration, editing profiles, removing) • Editing metadata on physical models and parameters • Moderating articles and user comments on them • Application programming interface to allow program-based article creation • Comment the articles

  8. Access ways to LCG MCDB End-User • Read articles, comments, news • Download event files Author • Post articles and upload event files • Post news and answer the comments Moderator • Manage users profiles • Moderate articles and comments Administrator • Control the system • Technical database management Application software • Automatic articles posting and samples upload

  9. The most common operations with MCDB Users in general • Browses articles via the tree view of physics categories • Searches by author, title, keywords, physical processes, parameters values, etc. • Downloads desired sample after agreement on MCDB License Articles’ authors • Uploading event files • Completing article with the information that wasn’t not included in the description of an event file

  10. Software selection MySQL (DB management system) • Supported as a standard software in CERN LCG collaboration • Free and open source software • Very fast database operations • Reliable and stable • Doesn’t have good developed DB consistency support Perl (programming language) • Stable, cross platform programming language • Powerful and easy-to-develop • Open source software • Has wide choice of free modules for many purposes Apache (web server) • Powerful and flexible HTTP server • Highly configurable and extensible with third-part modules

  11. SQL tables in MCDB • Authors • Articles • Categories • Generators and their parameters • Models and parameters names • Model parameters’ values • Processes, initial and final states • Applied cuts • Event files, graph files and a few other tables

  12. SQL tables structure

  13. Current status of LCG MCDB By now was developed as a preliminary: • Design of MCDB web site (available at http://top.sinp.msu.ru/lcg) • SQL tables structure • Articles and authors management system • Users privileges schema

  14. Main Perl modules to create/modify • Raw DB access (connection, queries) • Operating with tables (managing users, articles, models, etc.) • Article authors helper • Security check for man-written texts (articles body, user comments, news) • Logging module

  15. Further plans for next two months • Create or amend all base Perl modules described above • Make the following interfaces: article posting, articles management and users management • Write detailed documentation and database consistency rules for develores • Develop the site mailing system

More Related