Present interface (simple API, up to the CMSSW_1_6_5)
Now is accomplished for (CMSSW code):
src/GeneratorInterface/ComphepInterface
example: src/GeneratorInterface/ComphepInterface/test/testComphepMCDBInterface.cfg
src/GeneratorInterface/MadGraphInterface
example: src/GeneratorInterface/MadGraphInterface/test/testMCDBInterface.cfg
The important lines are (e.g. for
CompHep file):
untracked bool getInputFromMCDB = true
int32
MCDBArticleID = 116
string
ComphepInputFile = "rfio://castor/cern.ch/sft/mcdb/storage/116/tb_mnbb_lhc.pev"
The same is for
MadGraph, except input file parameter should be named "MadGraphInputFile".
This interface automatically creates local copy of the file and passes it to the standard
MadGraph or
CompHEP CMSSW interfaces.
*
BugFix: need to comment out the following line (for both
MadGraph and
CompHEP):
MCDBInterface.cc:31:
//edmplugin::PluginManager::configure(edmplugin::standard::config());
Near Future interface
The main purpose of new development is to add a possibility to document automatically the event sample inside CMSSW chain.
The description of the sample (and the sample itself) should be provided by the author of the sample in
LCG MCDB with flexible WEB interface.
By means of MCDB API library (C++) CMSSW automatically connects to the MCDB, download the description of the sample in
HepML format, parse the XML output and create the special C++ classes with the sample description, than download the sample (the samples are in the CERN CASTOR and available via GRID) and then passes local copy of the file to the particular CMSSW interface (
MadGraph,
CompHEP, etc.).
From user side, to process with CMSSW a sample from MCDB it's enough to specify in CMSSW configuration file the article number the sample belongs to in MCDB and the name of file (or full file path in MCDB).
untracked bool getInputFromMCDB = true
int32
MCDBArticleID = 116
string
ComphepInputFile = "tb_mnbb_lhc.pev"
There is a plan to move the new version of MCDB-CMSSW API in the section:
CMSSW_1_X_X/src/GeneratorInterface/CommonInterface/
instead of the same code for each of the possible generator (the present interface).
The real example of the sample description in
HepML output can be reached by the following link (as an example this link for the article 116):
http://mcdb.cern.ch/cgi-bin/xmlquery.cgi?article=116
The new MCDB API library is available in the
download section of MCDB web site. The most recent (development) version is available in CERN CVS (simu.cvs.cern.ch:/cvs/simu/GENSER/MCDB/API)
Fully Automatic Interface
For the specific generators, which support
LHEF and
HepML standards we plan to provide the fully automatic interface to document the event samples from the generator level and up to the CMSSW reconstruction.
It will be possible, for the ME generators where the LHEF event format has been realised for the event records. LHEF standard provides the possibility to use one standard interface to read the events at the next level of simulation. The
HepML header of LHEF event sample provides the possibility automatically save the event sample description (e.g. the necessary information like generator cuts, model parameters, etc.) in the flexible XML form. This
HepML header can be saved automatically in ME generator and parsed by the standard library at the next level of simulation. Such a chain provides the automatic documentation and processing of the event sample from the hard process simulation (ME generator) and up to the CMSSW output.
At present, there are only two ME generators where the LHEF format has been implemented (
MadGraph,
CompHEP) and
HepML header has been implemented only in
CompHEP generator. The standard LHEF input interfaces are realised in PYTHIA and HERWIG SH generators, the
HepML input interface is realised in the standard library in MCDB API.