210 likes | 309 Views
S.Belov, JINR, Dubna on behalf of LCG MCDB group. LCG Monte-Carlo Events Data Base (MCDB) : current status and plans. Overview. Motivations To Provide Configuration, Book-keeping, Documentation, Storage for the Shared Monte-Carlo Event Files
E N D
S.Belov, JINR, Dubna on behalf of LCG MCDB group LCG Monte-Carlo Events Data Base (MCDB) : current status and plans
Overview • Motivations • To Provide Configuration, Book-keeping, Documentation, Storage for the Shared Monte-Carlo Event Files • To keep track of the full generation chain, Exploiting the Competences of Monte Carlo Experts and Monte Carlo Authors • CMS MCDB [hep-ph/0403100]http://cmsdoc.cern.ch/cms/generators/mcdb/ • Only parton level files; AFS storage; No Searchable; No SQL • LCG MCDB[hep-ph/0404241] http://mcdb.cern.ch • Same authors + Additional human resources and technical support • Core software supported by LCG Software Project Infrastructure • MySQL; POOL; CASTOR (RFIO); CGI; Perl; Apache 1
The MCDB Project Structure • Authors management and Authorisation block • Articles Management • Event Files management • Log system • Documentation • Users comments management • Search engine • Application Package Interface • Uniform Event Formats and Event Interfaces 2
Existent MCDB subsystems • Users area: • Web site • Web catalog (physics categories) • Search engine • Downloading event files • Comments on articles • Authors area: • Articles Management • Event files management • Administrative area: • Authors management • Authorisation system • Physical categories/web catalog management • Articles management • Other subsystems: • Logging system 3
Articles Management (95% done) • Provide authors clear interface to document events as easy as possible • It is possible to use pre-entered information to describe generator, model, parameters, etc. • Present articles in a very structured way 9
Articles Management, generator and Process description 11
Event Files Management (90% done) • Uploading to disk (as in CMS MCDB) : for files cashing - accomplished • Interface to CASTOR - in progress ( will be done in two weeks ) • GRID and API interfaces (in the future) 14
Authors Management System (done) • Web interface to add, remove, block and edit author records and policies • Simple registration procedure 15
Authorisation System(95% done) • Based on CERN AFS authorisation system • Direct connection with MySQL authors management system • Grid-ecrtificate based authorization: in the future 16
Logging and statistics system(20% done) • Login operations • Implicit logs in database (e.g. creation or modification date) • Separate log files for different subsystems • Need to combine to uniform structure • Add structure to search engine 18
Porting to Scientific Linux CERN 3 • Installation of all nessesary software and packages • Detailed instructions how to setup MCDB from the very beginning • Ready-to-use MCDB version on pcitapi26.cern.ch under SLC3 19
Conclusion :working prototype is ready • We have a working version of MCDB - Basic functionality is supported - Deployed on http://pcitapi26.cern.ch • But still need to do a few important things in the nearest future: - Adjusting operations with Castor ( in two weeks ) - Porting MCDB to mcdb.cern.ch under SLC3 - Making Web-interface more convinient to end-users - Checking for resistance against any kind of faults - API to collaborations software - Cleanup of MCDB tree in CVS and installation scripts 20