Difference: GaussDevelopment (1 vs. 28)

Revision 282012-04-27 - JimmyMcCarthy

Line: 1 to 1
 
META TOPICPARENT name="LHCbSimulation"

Gauss current and future developments

Changed:
<
<
The topics on this page are being migrated to the savannah task list. This page will become a list of supporting documentation for the savannah tasks with the number of the task indicated and that will be cross referenced from there.
>
>
The topics on this page are being migrated to the savannah task list. This page will become a list of supporting documentation for the savannah tasks with the number of the task indicated and that will be cross referenced from there.
 
Line: 10 to 9
 

Work in Progress / Open and long term topics / Closed topics

Gauss configurable

Added:
>
>
 Last update : 02 October 2009
Changed:
<
<
Gloria is working on this. A first version of the Gauss() configurable was made available with v37r3(p1), but not all control parameters yet. In particular the generator of non pp collisions (pgun and mib) have been reactivated with a special control in v37r4, but merging with min bias is still off. There is some issues as where to put the monitoring subphases for Generation and Simulation as part of the top level Gauss sequence (more appropriate when reading) or of the Generation and Simulation sub-sequence (more appropriate when the corresponding sub-sequence are executed). Victor Coco is working on the segmented control of geometry and simulation response of the sub-detectors.
>
>
Gloria is working on this. A first version of the Gauss() configurable was made available with v37r3(p1), but not all control parameters yet. In particular the generator of non pp collisions (pgun and mib) have been reactivated with a special control in v37r4, but merging with min bias is still off. There is some issues as where to put the monitoring subphases for Generation and Simulation as part of the top level Gauss sequence (more appropriate when reading) or of the Generation and Simulation sub-sequence (more appropriate when the corresponding sub-sequence are executed). Victor Coco is working on the segmented control of geometry and simulation response of the sub-detectors.
 
Changed:
<
<
A list of the existing control parameters and some of foreseen new one, their meaning as well as status of the implementation is available in a dedicated page
>
>
A list of the existing control parameters and some of foreseen new one, their meaning as well as status of the implementation is available in a dedicated page
 

QMTests

Added:
>
>
 Last update : 04 January 2010
Changed:
<
<
Silvia has prepared the QMTests running the default for few events. This is in from Gauss v37r0. She has also committed a SAM test for checking the installation on remote sites, for Gauss, as the G4 geometry (hence the access) is done during the first event this means running one event.
>
>
Silvia has prepared the QMTests running the default for few events. This is in from Gauss v37r0. She has also committed a SAM test for checking the installation on remote sites, for Gauss, as the G4 geometry (hence the access) is done during the first event this means running one event.
 
Changed:
<
<
Need to check that problems reported by Stuart of not being able to run the tests because written in 'release area' has been fixed: Marco Cl. should have modified the system to allow to write the output in other temporary directories.
>
>
Need to check that problems reported by Stuart of not being able to run the tests because written in 'release area' has been fixed: Marco Cl. should have modified the system to allow to write the output in other temporary directories.
  A test at generator level for 1000 events has also been introduced.
Changed:
<
<
Need to prepare a list of additional QMTests that may be useful, eg. some at generator level for the various generators and for signal to test EvtGen.
>
>
Need to prepare a list of additional QMTests that may be useful, eg. some at generator level for the various generators and for signal to test EvtGen.
  Test with Gauss-2008.py has been removed (obsolete file), probably a test at different energies/beam settings would also be useful.
Line: 60 to 54
  Patrick has prepared a first version of python stearing for producing spillover, Gloria took this as one of the inputs to prepare the Gauss configurable and it is available in Gauss v37r3(p1).
Changed:
<
<
The whole "Gauss-event" is not written out when any one of the "25nsec slots events" is failing in G4. The containers of empty events of possible spill-over are not written at all. The GenHeader and the MCHeader are written for all possible spill-over slots.
>
>
The whole "Gauss-event" is not written out when any one of the "25nsec slots events" is failing in G4. The containers of empty events of possible spill-over are not written at all. The GenHeader and the MCHeader are written for all possible spill-over slots.
 
Changed:
<
<
It is not possible to generate events with special generators and spill-over as the initialization of Pythia would need to be redone in this case (as the underlying code is fortran and the same, so no instances with different initializations). A mechanism similar to that of the pileup for special events will need to be put in place.
>
>
It is not possible to generate events with special generators and spill-over as the initialization of Pythia would need to be redone in this case (as the underlying code is fortran and the same, so no instances with different initializations). A mechanism similar to that of the pileup for special events will need to be put in place.
 

Gauss read and configurable

Line: 82 to 76
  Patrick will look into this.
Changed:
<
<
MC09 compatible ? The data members in GenHeader will be removed and methods will get them via access to class BeamParameter Proposed list of data members is
>
>
MC09 compatible ? The data members in GenHeader will be removed and methods will get them via access to class BeamParameter Proposed list of data members is
 
Energy (or Pz)
RMS bunch lenght (sigma_s)
Line: 115 to 107
 Investigate putting this data in FSR as it will be the same for all events in the same job.

CP violation in new EvtGen

Deleted:
<
<
Last update : 08 January 2010
 
Changed:
<
<
CPV models had temporarly been switched off to prevent their use before validating them. Mark Whitehead found problems looking into the model provided by EvtGen and found solutions. They have been introduced in Gauss v38r1 and v37r3. A conversation with Anders Rys will take place on this sometime in January and we should also discuss when we want to make the new 'stable' EvtGen available to LCG Generators Service. The VHCP model written by Tristan duPree has been rechecked with the new EvtGen by Greig Cowan, and some adaptation have been introduced.
>
>
Last update : 08 January 2010
 
Added:
>
>
CPV models had temporarly been switched off to prevent their use before validating them. Mark Whitehead found problems looking into the model provided by EvtGen and found solutions. They have been introduced in Gauss v38r1 and v37r3. A conversation with Anders Rys will take place on this sometime in January and we should also discuss when we want to make the new 'stable' EvtGen available to LCG Generators Service. The VHCP model written by Tristan duPree has been rechecked with the new EvtGen by Greig Cowan, and some adaptation have been introduced.
 

EvtGen

Deleted:
<
<
Last update : 04 January 2010
 
Changed:
<
<
New model for leptonic B decays by Nikolai (see Gauss meeting in April). Introduced in EvtGenExtras (Gauss v37r5). Additional new models and modification by NIkolai expected soon. Some changes committed to CVS by Will Reece for models he introduced: investigate as no entries in release notes.
>
>
Last update : 04 January 2010
 
Changed:
<
<
Anders Rys asked to give him the changes we made to EvtGen, Patrick will organize a meeting beginning of January to discuss with him and Mark Whitehead & Paul Harrison, as they did the changes. Also request by LCG Generator Service to make out version available once things have been ironed out. Should foresee a presentation by Mark to LCG monthly meeting when we deem the code can be given to them.
>
>
New model for leptonic B decays by Nikolai (see Gauss meeting in April). Introduced in EvtGenExtras (Gauss v37r5). Additional new models and modification by NIkolai expected soon. Some changes committed to CVS by Will Reece for models he introduced: investigate as no entries in release notes.
 
Added:
>
>
Anders Rys asked to give him the changes we made to EvtGen, Patrick will organize a meeting beginning of January to discuss with him and Mark Whitehead & Paul Harrison, as they did the changes. Also request by LCG Generator Service to make out version available once things have been ironed out. Should foresee a presentation by Mark to LCG monthly meeting when we deem the code can be given to them.
 

New Decfiles

Added:
>
>
 Last update : 08 January 2010
Changed:
<
<
Various new DecFiles added as necessary. The script generating automatic options should be modified to write them in configurable python form. Can the extention be kept as .opts ? This would simplify backward compatibility for production system.
>
>
Various new DecFiles added as necessary. The script generating automatic options should be modified to write them in configurable python form. Can the extention be kept as .opts ? This would simplify backward compatibility for production system.
 

SHERPA interface

Changed:
<
<
Julian and Tobias from Dortmund, private build of new version of sherpa. In CVS but will wait to put in a release for official build of necessary version by LCG. Julian was able to geenerate inclusive b events with Sherpa as production engine. He observes differences in the rapidity distribution for all particles and for B mesons with respect to Pythia.
>
>
Julian and Tobias from Dortmund, private build of new version of sherpa. In CVS but will wait to put in a release for official build of necessary version by LCG. Julian was able to geenerate inclusive b events with Sherpa as production engine. He observes differences in the rapidity distribution for all particles and for B mesons with respect to Pythia.
 

New particle property service

Line: 155 to 141
 Plamen is looking into this.

Validation reports and checks, tuning.

Added:
>
>
 Last update : 08 January 2010
Changed:
<
<
Silvia worked on using the Data Quality and OMALib infrastructure, large effort. She made changes to make it work with latest Gauss v38r* and Boole v20r*. People should be in charge/define both for physics and detectors what plots to check. Silvia will look into some general ones to verify processes like gamma convertions, etc. are as observed in the data. Automatic mails when big differences? Material checks should be part of this at least for what can be done with existing code (see below for rad lenght and overlaps).
>
>
Silvia worked on using the Data Quality and OMALib infrastructure, large effort. She made changes to make it work with latest Gauss v38r* and Boole v20r*. People should be in charge/define both for physics and detectors what plots to check. Silvia will look into some general ones to verify processes like gamma convertions, etc. are as observed in the data. Automatic mails when big differences? Material checks should be part of this at least for what can be done with existing code (see below for rad lenght and overlaps).
 

Monitors of time/steps

Changed:
<
<
Stefania commited code from Olga for muons. It needs some clean up and to be extended to all detectors, an older version for that (what Olga took as guideline) exists made by one of Gloria old summer students
>
>
Stefania commited code from Olga for muons. It needs some clean up and to be extended to all detectors, an older version for that (what Olga took as guideline) exists made by one of Gloria old summer students
 

Material scans in parallel geometry

Changed:
<
<
Silvia will prepare options to be run with current geometry structure. Once the restructuring of the LHCb -->
G4 geometry is done and allow parallel geometry, this will make use of the parallel geometry. In DDDB it will already be prepared in a parallel structure.
>
>
Silvia will prepare options to be run with current geometry structure. Once the restructuring of the LHCb -->G4 geometry is done and allow parallel geometry, this will make use of the parallel geometry. In DDDB it will already be prepared in a parallel structure.
 

New mechanism for geometry 'conversion' from LHCb to G4

Added:
>
>
 Last update : 08 January 2010
Changed:
<
<
Marco P. is looking into this. He has began to move the converters to service methods/tools. He obtains identical material scans with this than with the converters. Next step will be to clean up the code and then to take the DetectorElement misalignment information into account more fully. Checking of overlaps at construction should/could also be introduced as an option. investigated. For the moment material checks should be included in standard tests when geometry is modified.
>
>
Marco P. is looking into this. He has began to move the converters to service methods/tools. He obtains identical material scans with this than with the converters. Next step will be to clean up the code and then to take the DetectorElement misalignment information into account more fully. Checking of overlaps at construction should/could also be introduced as an option. investigated. For the moment material checks should be included in standard tests when geometry is modified.
 

Overlaps in geometry

Changed:
<
<
Velo group has been notified for overal in its detector. Tom (Latham) and Mark (Whitehead) are working on the VELO overlaps and remarked that david only works for simple solids. They have found one overlap upstream of the VELO with the beam pipe. Gloria will dig up the CDD drawings for this area.
>
>
Velo group has been notified for overal in its detector. Tom (Latham) and Mark (Whitehead) are working on the VELO overlaps and remarked that david only works for simple solids. They have found one overlap upstream of the VELO with the beam pipe. Gloria will dig up the CDD drawings for this area.
  Marco (Pappagallo) is also running david when switching on the "BeforeMagnet" region and has found some overlap there.
Line: 193 to 173
 For MC09 will need to keep using the script, in the long term the FSR should be used. Need somebody (more than a summer student) to work on this.

Choice of settings (delta rays, physics lists, etc)

Deleted:
<
<
Last update : 08 January 2010
 
Changed:
<
<
Delta rays have been switched on everywere from Gauss v38r0. Possible issues. Currently we are using LHEP for hadronic physics. Known issues with this. Need to investigate other physics lists. Decide which one are worth investigating. Also known issues in processes for K+/- interations.
>
>
Last update : 08 January 2010
 
Added:
>
>
Delta rays have been switched on everywere from Gauss v38r0. Possible issues. Currently we are using LHEP for hadronic physics. Known issues with this. Need to investigate other physics lists. Decide which one are worth investigating. Also known issues in processes for K+/- interations.
 

Windows and MacOS builds

Changed:
<
<
Work done in the past by Karl Harrison for win32 for default generator (still some problems when running). May become a problem due to availability of fortran compiler on win32. Asked to deploy/build also herwig, etc. No generators libraries on MacOS, will request it formally.
>
>
Work done in the past by Karl Harrison for win32 for default generator (still some problems when running). May become a problem due to availability of fortran compiler on win32. Asked to deploy/build also herwig, etc. No generators libraries on MacOS, will request it formally.
 

Repackaging

Changed:
<
<
Idea is to separate all interfaces and base classes in a separate package for both generators and simulation. Separate LHCb specific parts from generic GiGa parts.
>
>
Idea is to separate all interfaces and base classes in a separate package for both generators and simulation. Separate LHCb specific parts from generic GiGa parts.
 

Revision of Tutorial

Revision of User Guide

Dark matter under RICH1

Changed:
<
<
In DC06 there was the issue of some interactions being produced in the beam pipe vacuum in the RICH1 region. This was reported by Thomas R. that observed them in pp elastic collisions. Sajan think this may be due to an error in geometry where the vacuum is not put it and the gas of RICH1 is left in a small area. Sajan checked this and verified all materials (including vacuum) are correctly put in. Thomas will investigate once more statistics is available if there is still an issue for MC09.
>
>
In DC06 there was the issue of some interactions being produced in the beam pipe vacuum in the RICH1 region. This was reported by Thomas R. that observed them in pp elastic collisions. Sajan think this may be due to an error in geometry where the vacuum is not put it and the gas of RICH1 is left in a small area. Sajan checked this and verified all materials (including vacuum) are correctly put in. Thomas will investigate once more statistics is available if there is still an issue for MC09.
  UPDATE:
Changed:
<
<
Thomas investigated using MC09 (see his slides in: http://indico.cern.ch/conferenceDisplay.py?confId=60170). The Z distribution of these observed proton-vacuum interactions was quite homogeneous between -4m and +1m (despite removing overlaps between DC06 and MC09, at present it seems that these interactions have increased).
>
>
Thomas investigated using MC09 (see his slides in: http://indico.cern.ch/conferenceDisplay.py?confId=60170). The Z distribution of these observed proton-vacuum interactions was quite homogeneous between -4m and +1m (despite removing overlaps between DC06 and MC09, at present it seems that these interactions have increased).
  Checks performed by Gloria and Silvia revealed that:
  • the simulation in Gauss is activated starting from "BeforeMagnetRegion/Velo", i.e. from -4m to ~-1m there is no detector simulation taken into account. The interactions in that region were occurring with the Air inside the Universe.
Line: 257 to 234
 

Selectively switch off geometry/simulation/monitor

Added:
>
>
 Last update : 04 January 2010
Changed:
<
<
Use Gauss().DetGeometry, etc... to selectively switch off/on geometry, simulation and monitoring of generator, detectors&infrastructures. At the moment the controls does not quite works. Partly because of configuration of algorithms, etc. Old style forcing does work as in extra python files provided.
>
>
Use Gauss().DetGeometry, etc... to selectively switch off/on geometry, simulation and monitoring of generator, detectors&infrastructures. At the moment the controls does not quite works. Partly because of configuration of algorithms, etc. Old style forcing does work as in extra python files provided.
 

VELO new geometry

Added:
>
>
 Last update : 14 January 2010
Changed:
<
<
A new geometry has been introduced for the VELO in DDDB (velo ) to get closer to the really installed one by Tom Latham and Mark Whitehead. At the same time they also reviewed the VELO vacuum tank and integrated in the VELO description the interface part to the beam pipe and RICH1 (a.k.a. Velo2Rich1). This had to be picked up by Gauss by changing the configurable when the new tag is used to include new detector elements and remove the old Velo2Rich1. This new description gave too much material as seen by the LHCb detector description and too little in the Geant4 description in Gauss. The problem has been tracked down to overlaps in the interface region and they have been fixed. At the same time Tom and Mark introduced detectors elements for all passive structures so that everything would be correctly simulated for all positions of the VELO. See
>
>
A new geometry has been introduced for the VELO in DDDB (velo ) to get closer to the really installed one by Tom Latham and Mark Whitehead. At the same time they also reviewed the VELO vacuum tank and integrated in the VELO description the interface part to the beam pipe and RICH1 (a.k.a. Velo2Rich1). This had to be picked up by Gauss by changing the configurable when the new tag is used to include new detector elements and remove the old Velo2Rich1. This new description gave too much material as seen by the LHCb detector description and too little in the Geant4 description in Gauss. The problem has been tracked down to overlaps in the interface region and they have been fixed. At the same time Tom and Mark introduced detectors elements for all passive structures so that everything would be correctly simulated for all positions of the VELO. See
 
Changed:
<
<
  • Marco Cheks with G4:
    CheckVelo.png
>
>
  • Marco Cheks with G4:
    CheckVelo.png
 
Changed:
<
<
  • Check by Tom with Transport Service before 835mm:
    hrad_eta0_eta.gif
>
>
  • Check by Tom with Transport Service before 835mm:
    hrad_eta0_eta.gif
 
Changed:
<
<
  • Check by Tom with Transport Service between 835-978mm:
    hrad_eta1_eta.gif
>
>
  • Check by Tom with Transport Service between 835-978mm:
    hrad_eta1_eta.gif
  A new DDDB tag will be released with this geometry and a new version of Gauss that will pick up the complete list of detector elements for this new geometry and support the older one as well.

Cable attachments in beam pipe magnet supports

Deleted:
<
<
Last update : 14 January 2010
 
Changed:
<
<
Daria wrote the xml for this for the upgrade. Gloria is taking out the parts for the upgrade (change of materials of the collars) and making an xml from it. In the process of checking it.
>
>
Last update : 27 April 2012
 
Changed:
<
<

Geometry and mis-alignment for simulation

>
>
FixedPipeSupports.png
 
Changed:
<
<

Conditions for Simulation

>
>
The current geometry for the beam pipe supports has been implemented, and has been released in DDDB under the global tag head-20120413.
 
Changed:
<
<

Migration to HepMC2

>
>
The geometry for the upgrade will look like:
 
Changed:
<
<

Old issues

See:
>
>
upgradePipeSupports.png
 
Added:
>
>
This is made of beryllium and contains less material. Jimmy (Birmingham) is currently writing the xml for this geometry.
 
Added:
>
>

Geometry and mis-alignment for simulation

 
Added:
>
>

Conditions for Simulation

 
Added:
>
>

Migration to HepMC2

 
Changed:
<
<
-- GloriaCorti - 22 Apr 2009
>
>

Old issues

See:

 
Added:
>
>
-- GloriaCorti - 22 Apr 2009
 
META FILEATTACHMENT attachment="Velo_material_new.pdf" attr="h" comment="Silvia checks with Gauss" date="1263497109" name="Velo_material_new.pdf" path="D:\Gauss\NewVeloCheck-20100114\Velo_material_new.pdf" size="842440" stream="D:\Gauss\NewVeloCheck-20100114\Velo_material_new.pdf" tmpFilename="/usr/tmp/CGItemp20107" user="gcorti" version="1"
META FILEATTACHMENT attachment="CheckVelo.png" attr="h" comment="Marco Cheks with G4" date="1263497133" name="CheckVelo.png" path="D:\Gauss\NewVeloCheck-20100114\CheckVelo.png" size="124834" stream="D:\Gauss\NewVeloCheck-20100114\CheckVelo.png" tmpFilename="/usr/tmp/CGItemp20197" user="gcorti" version="1"
META FILEATTACHMENT attachment="hrad_eta0_eta.gif" attr="h" comment="Check by Tom before 838" date="1263497353" name="hrad_eta0_eta.gif" path="D:\Gauss\NewVeloCheck-20100114\hrad_eta0_eta.gif" size="6548" stream="D:\Gauss\NewVeloCheck-20100114\hrad_eta0_eta.gif" tmpFilename="/usr/tmp/CGItemp20094" user="gcorti" version="1"
META FILEATTACHMENT attachment="hrad_eta1_eta.gif" attr="h" comment="Check by Tom after 838" date="1263497397" name="hrad_eta1_eta.gif" path="D:\Gauss\NewVeloCheck-20100114\hrad_eta1_eta.gif" size="6837" stream="D:\Gauss\NewVeloCheck-20100114\hrad_eta1_eta.gif" tmpFilename="/usr/tmp/CGItemp20142" user="gcorti" version="1"
Added:
>
>
META FILEATTACHMENT attachment="FixedPipeSupports.png" attr="" comment="" date="1335534996" name="FixedPipeSupports.png" path="FixedPipeSupports.png" size="11039" stream="FixedPipeSupports.png" tmpFilename="/usr/tmp/CGItemp50617" user="jmccarth" version="2"
META FILEATTACHMENT attachment="upgradePipeSupports.png" attr="h" comment="" date="1335534901" name="upgradePipeSupports.png" path="upgradePipeSupports.png" size="13606" stream="upgradePipeSupports.png" tmpFilename="/usr/tmp/CGItemp50625" user="jmccarth" version="1"

Revision 272011-05-24 - GloriaCorti

Line: 1 to 1
 
META TOPICPARENT name="LHCbSimulation"

Gauss current and future developments

Added:
>
>
The topics on this page are being migrated to the savannah task list. This page will become a list of supporting documentation for the savannah tasks with the number of the task indicated and that will be cross referenced from there.
 
Changed:
<
<

Gauss configurable

>
>

Work in Progress / Open and long term topics / Closed topics

Gauss configurable

 Last update : 02 October 2009

Gloria is working on this. A first version of the Gauss() configurable was made available with v37r3(p1), but not all control parameters yet.

Line: 16 to 21
 A list of the existing control parameters and some of foreseen new one, their meaning as well as status of the implementation is available in a dedicated page
Changed:
<
<

QMTests

>
>

QMTests

 Last update : 04 January 2010

Silvia has prepared the QMTests running the default for few events. This is in from Gauss v37r0.

Line: 41 to 46
 
  • 14143011 (BcVegPy)
  • 60001008 (Hijing)
Changed:
<
<

AppConfig and job specifications

>
>

AppConfig and job specifications

 Last update : 05 October 2009

AppConfing v3rX is used by Gauss v37r3 and higher to set the Simulation Conditions specifying the 'SIMCOND' settings and the beam settings. A list of the avalaible steering options for is provided here.

Line: 50 to 55
  Additional options can be put in upon request for productions.
Changed:
<
<

Spill-over and configurables

>
>

Spill-over and configurables

 Last update : 02 October 2009

Patrick has prepared a first version of python stearing for producing spillover, Gloria took this as one of the inputs to prepare the Gauss configurable and it is available in Gauss v37r3(p1).

Line: 62 to 66
 It is not possible to generate events with special generators and spill-over as the initialization of Pythia would need to be redone in this case (as the underlying code is fortran and the same, so no instances with different initializations). A mechanism similar to that of the pileup for special events will need to be put in place.
Changed:
<
<

Gauss read and configurable

>
>

Gauss read and configurable

  Raluca has provided a GaussRead.py, Gloria has began to look into it to adapt it the the generic case and it will be available as a Gauss() option.
Changed:
<
<

GENSER split and re-commission extra generators

>
>

GENSER split and re-commission extra generators

 Last update : 02 October 2009

No work yet in GENSER split.

Jibo He has re-commissioned BcVegPy and extended it to work in a single release providing pdf data for 3.5+3.5TeV, 5+5TeV and 7+7TeV. The choice of PDF is now possible.

Changed:
<
<

Beam settings in GenHeader and in transient SIMCOND

>
>

Beam settings in GenHeader and in transient SIMCOND

 Last update : 02 October 2009

Patrick will look into this.

Line: 110 to 114
  Investigate putting this data in FSR as it will be the same for all events in the same job.
Changed:
<
<

CP violation in new EvtGen

>
>

CP violation in new EvtGen

 Last update : 08 January 2010

CPV models had temporarly been switched off to prevent their use before validating them.

Line: 120 to 124
 and some adaptation have been introduced.
Changed:
<
<

EvtGen

>
>

EvtGen

 Last update : 04 January 2010

New model for leptonic B decays by Nikolai (see Gauss meeting in April). Introduced in EvtGenExtras (Gauss v37r5).

Line: 130 to 134
 him and Mark Whitehead & Paul Harrison, as they did the changes. Also request by LCG Generator Service to make out version available once things have been ironed out. Should foresee a presentation by Mark to LCG monthly meeting when we deem the code can be given to them.
Changed:
<
<

New Decfiles

>
>

New Decfiles

 Last update : 08 January 2010

Various new DecFiles added as necessary. The script generating automatic options should be modified to write them in configurable python form. Can the extention be kept as .opts ? This would simplify backward compatibility for production system.

Changed:
<
<

SHERPA interface

>
>

SHERPA interface

  Julian and Tobias from Dortmund, private build of new version of sherpa. In CVS but will wait to put in a release for official build of necessary version by LCG. Julian was able to geenerate inclusive b events with Sherpa as production engine. He observes differences in the rapidity distribution for all particles and for B mesons with respect to Pythia.
Changed:
<
<

New particle property service

>
>

New particle property service

  For next version of Gauss based on Gaudi v21r*. Backward compatible for MC09. Old one will disappear from Gaudi v22.
Changed:
<
<

Hijing: 64 bits and random seeds

>
>

Hijing: 64 bits and random seeds

 Last update : 02 October 2009

Plamen is looking into this.

Changed:
<
<

Validation reports and checks, tuning.

>
>

Validation reports and checks, tuning.

 Last update : 08 January 2010

Silvia worked on using the Data Quality and OMALib infrastructure, large effort. She made changes to make it work with latest Gauss v38r* and Boole v20r*. People should be in charge/define both for physics and detectors what plots to check. Silvia will look into some general ones to verify processes like gamma convertions, etc. are as observed in the data. Automatic mails when big differences? Material checks should be part of this at least for what can be done with existing code (see below for rad lenght and overlaps).

Changed:
<
<

Monitors of time/steps

>
>

Monitors of time/steps

  Stefania commited code from Olga for muons. It needs some clean up and to be extended to all detectors, an older version for that (what Olga took as guideline) exists made by one of Gloria old summer students
Changed:
<
<

Material scans in parallel geometry

>
>

Material scans in parallel geometry

 
Silvia will prepare options to be run with current geometry structure. Once the restructuring of the LHCb -->
G4 geometry is done and allow parallel geometry, this will make use of the parallel geometry. In DDDB it will already be prepared in a parallel structure.
Changed:
<
<

New mechanism for geometry 'conversion' from LHCb to G4

>
>

New mechanism for geometry 'conversion' from LHCb to G4

 Last update : 08 January 2010

Marco P. is looking into this. He has began to move the converters to service methods/tools.

Line: 175 to 179
 Checking of overlaps at construction should/could also be introduced as an option. investigated. For the moment material checks should be included in standard tests when geometry is modified.
Changed:
<
<

Overlaps in geometry

>
>

Overlaps in geometry

  Velo group has been notified for overal in its detector. Tom (Latham) and Mark (Whitehead) are working on the VELO overlaps and remarked that david only works for simple solids. They have found one overlap upstream of the VELO with the beam pipe. Gloria will dig up the CDD drawings for this area.
Line: 184 to 188
  For beam pipe cables and T envelope, Gloria will look for somebody that could do it.
Changed:
<
<

Generator statistics, script and FSR

>
>

Generator statistics, script and FSR

  For MC09 will need to keep using the script, in the long term the FSR should be used. Need somebody (more than a summer student) to work on this.
Changed:
<
<

Moving to Geant4 9.2.p01

Hubert modified Geant4 cmt build scripts (copy of source from LCG area) and it is now in the nightly.

Choice of settings (delta rays, physics lists, etc)

>
>

Choice of settings (delta rays, physics lists, etc)

 Last update : 08 January 2010

Delta rays have been switched on everywere from Gauss v38r0. Possible issues. Currently we are using LHEP for hadronic physics. Known issues with this. Need to investigate other physics lists. Decide which one are worth investigating. Also known issues in processes for K+/- interations.

Changed:
<
<

Windows and MacOS builds

>
>

Windows and MacOS builds

  Work done in the past by Karl Harrison for win32 for default generator (still some problems when running). May become a problem due to availability of fortran compiler on win32. Asked to deploy/build also herwig, etc. No generators libraries on MacOS, will request it formally.
Changed:
<
<

Repackaging

>
>

Repackaging

  Idea is to separate all interfaces and base classes in a separate package for both generators and simulation. Separate LHCb specific parts from generic GiGa parts.
Changed:
<
<

Revision of Tutorial

>
>

Revision of Tutorial

 
Changed:
<
<

Revision of User Guide

>
>

Revision of User Guide

 
Changed:
<
<

Dark matter under RICH1

>
>

Dark matter under RICH1

 In DC06 there was the issue of some interactions being produced in the beam pipe vacuum in the RICH1 region. This was reported by Thomas R. that observed them in pp elastic collisions. Sajan think this may be due to an error in geometry where the vacuum is not put it and the gas of RICH1 is left in a small area. Sajan checked this and verified all materials (including vacuum) are correctly put in. Thomas will investigate once more statistics is available if there is still an issue for MC09.
Line: 227 to 227
 
  • the simulation in Gauss is activated starting from "BeforeMagnetRegion/Velo", i.e. from -4m to ~-1m there is no detector simulation taken into account. The interactions in that region were occurring with the Air inside the Universe.
  • moving from DC06 to MC09 the way the Velo geometry is activated in Gauss has changed. The envelope "BeforeMagnetRegion/Velo" (which is filled with "vacuum" and contains all the Velo sub-elements) is no longer activated in order to avoid double counting of the Velo sub-elements (which are instead individually activated due to misalignment requirements). The results is that the mother of the sensors (and the other Velo sub-elements) is no longer "Velo" but the Universe/World (i.e. filled with Air).
Changed:
<
<

Ganga doesn't put development BcVegPydata into the tarball of the job

>
>

Ganga doesn't put development BcVegPydata into the tarball of the job

 Last update : 04 January 2010

Jibo He reported that Ganga doesn't put BcVegPyData into the tarball of the job if one is developing its own copy. Ganga only takes care of the lib files and not of data packages built privately. Such function may also be needed for other data like the Magnetic field map. Make a feature request to the Ganga people?

Changed:
<
<

Activate multiple magnetic fields

>
>

Activate multiple magnetic fields

 Last update : 04 January 2010

Need to integrate in Gauss() the options from Magnus Lieng. Use simcond tags or better leave it as options?

Line: 256 to 256
 ScaleFactor = -1;
Changed:
<
<

Selectively switch off geometry/simulation/monitor

>
>

Selectively switch off geometry/simulation/monitor

 Last update : 04 January 2010

Use Gauss().DetGeometry, etc... to selectively switch off/on geometry, simulation and monitoring of generator, detectors&infrastructures. At the moment the controls does not quite works. Partly because of configuration of algorithms, etc. Old style forcing does work as in extra python files provided.

Changed:
<
<

VELO new geometry

>
>

VELO new geometry

 Last update : 14 January 2010

A new geometry has been introduced for the VELO in DDDB (velo ) to get closer to the really installed one by Tom Latham and Mark Whitehead. At the same time they also reviewed the VELO vacuum tank and integrated in the VELO description the interface part to the beam pipe and RICH1 (a.k.a. Velo2Rich1).

Line: 283 to 283
  A new DDDB tag will be released with this geometry and a new version of Gauss that will pick up the complete list of detector elements for this new geometry and support the older one as well.
Changed:
<
<
--++ Cable attachments in beam pipe magnet supports
>
>

Cable attachments in beam pipe magnet supports

 Last update : 14 January 2010

Daria wrote the xml for this for the upgrade. Gloria is taking out the parts for the upgrade (change of materials of the collars) and making an xml from it. In the process of checking it.

Added:
>
>

Geometry and mis-alignment for simulation

Conditions for Simulation

Migration to HepMC2

 
Added:
>
>

Old issues

See:
 

Revision 262010-09-15 - GloriaCorti

Line: 1 to 1
 
META TOPICPARENT name="LHCbSimulation"

Gauss current and future developments

Line: 88 to 88
 Revolution frequency (fixed at 11.245 kHz) (cannot be settable) Total cross section Effective crossing angle (better that to set external and calculate internal from Pz and mag field)
Changed:
<
<
beta*
>
>
Beta*
 Bunch spacing (for subsequent trains, i.e. 25 nsec, 50 nsec, etc. to give possible spill-over) ?
Added:
>
>
Luminous region mean position (x,y,z)
 
Deleted:
<
<
Thomas suggested to also add the
mean position(x,y,z)
of the primary vertex (pp or p-gas) as it could be offset with respect to the LHCb reference system.
  Methods derived from above quantities:

Revision 252010-01-14 - GloriaCorti

Line: 1 to 1
 
META TOPICPARENT name="LHCbSimulation"

Gauss current and future developments

Line: 271 to 271
 This had to be picked up by Gauss by changing the configurable when the new tag is used to include new detector elements and remove the old Velo2Rich1. This new description gave too much material as seen by the LHCb detector description and too little in the Geant4 description in Gauss. The problem has been tracked down to overlaps in the interface region and they have been fixed. At the same time Tom and Mark introduced detectors elements for all passive structures so that everything would be correctly simulated for all positions of the VELO.
Changed:
<
<
See pdf for summary with what seen by Gauss and this list of plots for what seen by the Transport Service.
>
>
See
  • Silvia checks with Gauss, for summary with what seen by Gauss with material scans with particle guns (Silvia)
  • Marco Cheks with G4:
    CheckVelo.png

  • Check by Tom with Transport Service before 835mm:
    hrad_eta0_eta.gif

  • Check by Tom with Transport Service between 835-978mm:
    hrad_eta1_eta.gif
 A new DDDB tag will be released with this geometry and a new version of Gauss that will pick up the complete list of detector elements for this new geometry and support the older one as well.
Added:
>
>
--++ Cable attachments in beam pipe magnet supports Last update : 14 January 2010

Daria wrote the xml for this for the upgrade. Gloria is taking out the parts for the upgrade (change of materials of the collars) and making an xml from it. In the process of checking it.

 
Line: 281 to 297
 

-- GloriaCorti - 22 Apr 2009 \ No newline at end of file

Added:
>
>

META FILEATTACHMENT attachment="Velo_material_new.pdf" attr="h" comment="Silvia checks with Gauss" date="1263497109" name="Velo_material_new.pdf" path="D:\Gauss\NewVeloCheck-20100114\Velo_material_new.pdf" size="842440" stream="D:\Gauss\NewVeloCheck-20100114\Velo_material_new.pdf" tmpFilename="/usr/tmp/CGItemp20107" user="gcorti" version="1"
META FILEATTACHMENT attachment="CheckVelo.png" attr="h" comment="Marco Cheks with G4" date="1263497133" name="CheckVelo.png" path="D:\Gauss\NewVeloCheck-20100114\CheckVelo.png" size="124834" stream="D:\Gauss\NewVeloCheck-20100114\CheckVelo.png" tmpFilename="/usr/tmp/CGItemp20197" user="gcorti" version="1"
META FILEATTACHMENT attachment="hrad_eta0_eta.gif" attr="h" comment="Check by Tom before 838" date="1263497353" name="hrad_eta0_eta.gif" path="D:\Gauss\NewVeloCheck-20100114\hrad_eta0_eta.gif" size="6548" stream="D:\Gauss\NewVeloCheck-20100114\hrad_eta0_eta.gif" tmpFilename="/usr/tmp/CGItemp20094" user="gcorti" version="1"
META FILEATTACHMENT attachment="hrad_eta1_eta.gif" attr="h" comment="Check by Tom after 838" date="1263497397" name="hrad_eta1_eta.gif" path="D:\Gauss\NewVeloCheck-20100114\hrad_eta1_eta.gif" size="6837" stream="D:\Gauss\NewVeloCheck-20100114\hrad_eta1_eta.gif" tmpFilename="/usr/tmp/CGItemp20142" user="gcorti" version="1"

Revision 242010-01-14 - GloriaCorti

Line: 1 to 1
 
META TOPICPARENT name="LHCbSimulation"

Gauss current and future developments

Line: 264 to 264
 At the moment the controls does not quite works. Partly because of configuration of algorithms, etc. Old style forcing does work as in extra python files provided.
Added:
>
>

VELO new geometry

Last update : 14 January 2010

A new geometry has been introduced for the VELO in DDDB (velo ) to get closer to the really installed one by Tom Latham and Mark Whitehead. At the same time they also reviewed the VELO vacuum tank and integrated in the VELO description the interface part to the beam pipe and RICH1 (a.k.a. Velo2Rich1). This had to be picked up by Gauss by changing the configurable when the new tag is used to include new detector elements and remove the old Velo2Rich1. This new description gave too much material as seen by the LHCb detector description and too little in the Geant4 description in Gauss. The problem has been tracked down to overlaps in the interface region and they have been fixed. At the same time Tom and Mark introduced detectors elements for all passive structures so that everything would be correctly simulated for all positions of the VELO. See pdf for summary with what seen by Gauss and this list of plots for what seen by the Transport Service. A new DDDB tag will be released with this geometry and a new version of Gauss that will pick up the complete list of detector elements for this new geometry and support the older one as well.

 

-- GloriaCorti - 22 Apr 2009

Revision 232010-01-08 - GloriaCorti

Line: 1 to 1
 
META TOPICPARENT name="LHCbSimulation"

Gauss current and future developments

Deleted:
<
<
Last update : 02 October 2009
 

Gauss configurable

Line: 114 to 112
 Investigate putting this data in FSR as it will be the same for all events in the same job.

CP violation in new EvtGen

Added:
>
>
Last update : 08 January 2010
 
Changed:
<
<
CPV models have temporarly been switched off to prevent their use before validating them. Mark Whitehead is looking into the model provided by EvtGen.
>
>
CPV models had temporarly been switched off to prevent their use before validating them. Mark Whitehead found problems looking into the model provided by EvtGen and found solutions. They have been introduced in Gauss v38r1 and v37r3. A conversation with Anders Rys will take place on this sometime in January and we should also discuss when we want to make the new 'stable' EvtGen available to LCG Generators Service.
 The VHCP model written by Tristan duPree has been rechecked with the new EvtGen by Greig Cowan,
Changed:
<
<
some adaptation necessary. Additional tests in progress.
>
>
and some adaptation have been introduced.
 

EvtGen

Changed:
<
<
Last update : 04 October 2010
>
>
Last update : 04 January 2010
  New model for leptonic B decays by Nikolai (see Gauss meeting in April). Introduced in EvtGenExtras (Gauss v37r5). Additional new models and modification by NIkolai expected soon. Some changes committed to CVS by Will Reece for models he introduced: investigate as no entries in release notes.
Line: 132 to 132
 

New Decfiles

Added:
>
>
Last update : 08 January 2010
 
Changed:
<
<
Various new DecFiles added by Patrick. Additional files can be added as necessary.
>
>
Various new DecFiles added as necessary. The script generating automatic options should be modified to write them in configurable python form. Can the extention be kept as .opts ? This would simplify backward compatibility for production system.
 

SHERPA interface

Line: 151 to 152
 Plamen is looking into this.

Validation reports and checks, tuning.

Changed:
<
<
Last update : 02 October 2009
>
>
Last update : 08 January 2010
 
Changed:
<
<
Silvia worked on using the Data Quality and OMALib infrastructure, but large effort, people should be in charge/define both for physics and detectors. Automatic mails when big differences? Material checks should be part of this at least for what can be done with existing code (see below for rad lenght and overlaps)
>
>
Silvia worked on using the Data Quality and OMALib infrastructure, large effort. She made changes to make it work with latest Gauss v38r* and Boole v20r*. People should be in charge/define both for physics and detectors what plots to check. Silvia will look into some general ones to verify processes like gamma convertions, etc. are as observed in the data. Automatic mails when big differences? Material checks should be part of this at least for what can be done with existing code (see below for rad lenght and overlaps).
 

Monitors of time/steps

Line: 166 to 169
 

New mechanism for geometry 'conversion' from LHCb to G4

Added:
>
>
Last update : 08 January 2010
 
Changed:
<
<
Marco P. will look into this wen he is back in september. Checking of overlaps at construction should also be
>
>
Marco P. is looking into this. He has began to move the converters to service methods/tools. He obtains identical material scans with this than with the converters. Next step will be to clean up the code and then to take the DetectorElement misalignment information into account more fully. Checking of overlaps at construction should/could also be introduced as an option.
 investigated. For the moment material checks should be included in standard tests when geometry is modified.

Overlaps in geometry

Line: 188 to 194
 Hubert modified Geant4 cmt build scripts (copy of source from LCG area) and it is now in the nightly.

Choice of settings (delta rays, physics lists, etc)

Added:
>
>
Last update : 08 January 2010
 
Changed:
<
<
Delta rays will be switched on everywere in Gauss v38r0. Expect issues.

slc5 and gcc 4.3

>
>
Delta rays have been switched on everywere from Gauss v38r0. Possible issues. Currently we are using LHEP for hadronic physics. Known issues with this. Need to investigate other physics lists. Decide which one are worth investigating. Also known issues in processes for K+/- interations.
 
Deleted:
<
<
Will need to move to latest version of external libraries
Generators libraries exist/will exist only for latest version, in some cases need to change version 
  • pythia6 4.18 --> 4.20
  • lhpadf 5.3.1 --> 5.7.0
  • photos ? not clear chnages made in 215.5 (using 215.2)
  • pythia8 107.1 -->
210
  • herwig 6.510.2 --> 6.510.3 (-f_no_automatic flag)
  • Of the Geant4 versions only G4 9.2 has been validated.
     

    Windows and MacOS builds

    Revision 222010-01-04 - GloriaCorti

    Line: 1 to 1
     
    META TOPICPARENT name="LHCbSimulation"

    Gauss current and future developments

    Line: 19 to 19
     available in a dedicated page

    QMTests

    Added:
    >
    >
    Last update : 04 January 2010
     
    Changed:
    <
    <
    Silvia has prepared the QMTests running the default for few events. This is in Gauss v37r0. She has also committed a SAM test for checking the installation on remote sites, for Gauss, as
    >
    >
    Silvia has prepared the QMTests running the default for few events. This is in from Gauss v37r0. She has also committed a SAM test for checking the installation on remote sites, for Gauss, as
     the G4 geometry (hence the access) is done during the first event this means running one event.
    Added:
    >
    >
    Need to check that problems reported by Stuart of not being able to run the tests because written in 'release area' has been fixed: Marco Cl. should have modified the system to allow to write the output in other temporary directories.
     A test at generator level for 1000 events has also been introduced.

    Need to prepare a list of additional QMTests that may be useful, eg. some at generator level for

    Line: 118 to 122
     

    EvtGen

    Changed:
    <
    <
    Last update : 02 October 2009
    >
    >
    Last update : 04 October 2010

    New model for leptonic B decays by Nikolai (see Gauss meeting in April). Introduced in EvtGenExtras (Gauss v37r5). Additional new models and modification by NIkolai expected soon. Some changes committed to CVS by Will Reece for models he introduced: investigate as no entries in release notes.

    Anders Rys asked to give him the changes we made to EvtGen, Patrick will organize a meeting beginning of January to discuss with him and Mark Whitehead & Paul Harrison, as they did the changes. Also request by LCG Generator Service to make out version available once things have been ironed out. Should foresee a presentation by Mark to LCG monthly meeting when we deem the code can be given to them.

     
    Deleted:
    <
    <
    New model for leptonic B decays by Nikolai (see Gauss meeting in April). Introduced in EvtGenExtras (Gauss v37r5)
     

    New Decfiles

    Line: 222 to 231
     
    • moving from DC06 to MC09 the way the Velo geometry is activated in Gauss has changed. The envelope "BeforeMagnetRegion/Velo" (which is filled with "vacuum" and contains all the Velo sub-elements) is no longer activated in order to avoid double counting of the Velo sub-elements (which are instead individually activated due to misalignment requirements). The results is that the mother of the sensors (and the other Velo sub-elements) is no longer "Velo" but the Universe/World (i.e. filled with Air).

    Ganga doesn't put development BcVegPydata into the tarball of the job

    Added:
    >
    >
    Last update : 04 January 2010
      Jibo He reported that Ganga doesn't put BcVegPyData into the tarball of the job if one is developing its own copy. Ganga only takes care of the lib files and not of data packages built privately. Such function may also be needed for other data like the Magnetic field map. Make a feature request to the Ganga people?

    Activate multiple magnetic fields

    Added:
    >
    >
    Last update : 04 January 2010
      Need to integrate in Gauss() the options from Magnus Lieng. Use simcond tags or better leave it as options?
    Line: 248 to 259
     ScaleFactor = -1;
    Added:
    >
    >

    Selectively switch off geometry/simulation/monitor

    Last update : 04 January 2010

    Use Gauss().DetGeometry, etc... to selectively switch off/on geometry, simulation and monitoring of generator, detectors&infrastructures. At the moment the controls does not quite works. Partly because of configuration of algorithms, etc. Old style forcing does work as in extra python files provided.

     

    -- GloriaCorti - 22 Apr 2009

    Revision 212010-01-04 - GloriaCorti

    Line: 1 to 1
     
    META TOPICPARENT name="LHCbSimulation"

    Gauss current and future developments

    Line: 221 to 221
     
    • the simulation in Gauss is activated starting from "BeforeMagnetRegion/Velo", i.e. from -4m to ~-1m there is no detector simulation taken into account. The interactions in that region were occurring with the Air inside the Universe.
    • moving from DC06 to MC09 the way the Velo geometry is activated in Gauss has changed. The envelope "BeforeMagnetRegion/Velo" (which is filled with "vacuum" and contains all the Velo sub-elements) is no longer activated in order to avoid double counting of the Velo sub-elements (which are instead individually activated due to misalignment requirements). The results is that the mother of the sensors (and the other Velo sub-elements) is no longer "Velo" but the Universe/World (i.e. filled with Air).
    Added:
    >
    >

    Ganga doesn't put development BcVegPydata into the tarball of the job

    Jibo He reported that Ganga doesn't put BcVegPyData into the tarball of the job if one is developing its own copy. Ganga only takes care of the lib files and not of data packages built privately. Such function may also be needed for other data like the Magnetic field map. Make a feature request to the Ganga people?

    Activate multiple magnetic fields

    Need to integrate in Gauss() the options from Magnus Lieng. Use simcond tags or better leave it as options?

    The options are:

     
    GiGaGeo.FieldMgr.LHCbField.MagneticFieldService = "MultipleMagneticFieldSvc";
    
    MultipleMagneticFieldSvc.MagneticFieldServices = { "MagneticFieldSvc", "MagneticFieldSvc/MBXWHFieldSvc", "MagneticFieldSvc/MBXWS1L8FieldSvc", "MagneticFieldSvc/MBXWS1R8FieldSvc" };
    
    //MagneticFieldSvc.UseConditions = false;
    MBXWHFieldSvc.UseConditions = false;
    MBXWS1R8FieldSvc.UseConditions = false;
    MBXWS1L8FieldSvc.UseConditions = false;
    
    //MagneticFieldSvc.FieldMapFile = "$FIELDMAP";
    MBXWHFieldSvc.FieldMapFile = "$FIELDMAPROOT/cdf/compensator.MBXWH.001.cdf";
    MBXWS1L8FieldSvc.FieldMapFile = "$FIELDMAPROOT/cdf/compensator.MBXWS.1L8.001.cdf";
    MBXWS1R8FieldSvc.FieldMapFile = "$FIELDMAPROOT/cdf/compensator.MBXWS.1R8.001.cdf";
    
    MBXWS1L8FieldSvc.ScaleFactor = -1;
    
     

    -- GloriaCorti - 22 Apr 2009 \ No newline at end of file

    Revision 202009-10-06 - GloriaCorti

    Line: 1 to 1
     
    META TOPICPARENT name="LHCbSimulation"

    Gauss current and future developments

    Line: 42 to 42
     

    AppConfig and job specifications

    Last update : 05 October 2009
    Changed:
    <
    <
    AppConfing v3rX is used by Gauss v37r3 and higher to set the Simulation Conditions specifying the 'SIMCOND' settings and the beam settings. A list of the avalaible steering options for is provided here.
    >
    >
    AppConfing v3rX is used by Gauss v37r3 and higher to set the Simulation Conditions specifying the 'SIMCOND' settings and the beam settings. A list of the avalaible steering options for is provided here.
      For the MC09 detector they need to be used with Conditions/MC09-....py for the Upgrade detector with Conditions/Upgrade-....py

    Revision 192009-10-05 - GloriaCorti

    Line: 1 to 1
     
    META TOPICPARENT name="LHCbSimulation"

    Gauss current and future developments

    Line: 40 to 40
     
    • 60001008 (Hijing)

    AppConfig and job specifications

    Changed:
    <
    <
    Last update : 02 October 2009
    >
    >
    Last update : 05 October 2009
     
    Added:
    >
    >
    AppConfing v3rX is used by Gauss v37r3 and higher to set the Simulation Conditions specifying the 'SIMCOND' settings and the beam settings. A list of the avalaible steering options for is provided here.
     
    Changed:
    <
    <
    AppConfing v3rX is used by Gauss v37r3 and higher For MC09 the following steering options are provided

    Name Beam energy Magnetic Field (crossing angle) Number of collisions/bunch (nu)
    MC09-b5TeV-md100.py 5 TeV Full field downward direction 1
    MC09-b5TeV-md100-nu2.py 5 TeV Full field downward direction 2
    MC09-b5TeV-md100-nu3.py 5 TeV Full field downward direction 3
    MC09-b5TeV-md100-nu4.py 5 TeV Full field downward direction 4
    MC09-b5TeV-moff.py 5 TeV Field off 1
    MC09-b450GeV-moff.py 450 GeV Field off 1
    >
    >
    For the MC09 detector they need to be used with Conditions/MC09-....py for the Upgrade detector with Conditions/Upgrade-....py
     
    Deleted:
    <
    <
    See presentation at Tuesday Meeting 24 April 2009 for details on configuration.
     Additional options can be put in upon request for productions.
    Deleted:
    <
    <
    A request by Franz Muheim has been made to setup simulation configurations for 7 TeV beams at nominal machine for average luminosities/bunch of and . This has been made available in AppConfig v3r0.

    A request by Olivier Schneider has been made to setup simulation configurations for 3.5 TeV beams at startup conditions (head on, nu=1). Gloria will provide this shortly.

     

    Spill-over and configurables

    Last update : 02 October 2009

    Revision 182009-10-04 - GloriaCorti

    Line: 1 to 1
     
    META TOPICPARENT name="LHCbSimulation"

    Gauss current and future developments

    Line: 15 to 15
     as part of the top level Gauss sequence (more appropriate when reading) or of the Generation and Simulation sub-sequence (more appropriate when the corresponding sub-sequence are executed). Victor Coco is working on the segmented control of geometry and simulation response of the sub-detectors.
    Added:
    >
    >
    A list of the existing control parameters and some of foreseen new one, their meaning as well as status of the implementation is available in a dedicated page
     

    QMTests

    Revision 172009-10-02 - GloriaCorti

    Line: 1 to 1
     
    META TOPICPARENT name="LHCbSimulation"

    Gauss current and future developments

    Changed:
    <
    <
    Last update : 03 July 2009
    >
    >
    Last update : 02 October 2009
     

    Gauss configurable

    Added:
    >
    >
    Last update : 02 October 2009
     
    Changed:
    <
    <
    Gloria is working on this. A first version of the Gauss() configurable is available with v37r3(p1), but not all control parameters yet. In particular the generator of non pp collisions (pgun and mib) are temporarly off.
    >
    >
    Gloria is working on this. A first version of the Gauss() configurable was made available with v37r3(p1), but not all control parameters yet. In particular the generator of non pp collisions (pgun and mib) have been reactivated with a special control in v37r4, but merging with min bias is still off.
     There is some issues as where to put the monitoring subphases for Generation and Simulation as part of the top level Gauss sequence (more appropriate when reading) or of the Generation and Simulation sub-sequence (more appropriate when the corresponding sub-sequence are executed).
    Changed:
    <
    <
    A list of some of the control parameters and meaning is given below as well as status of the implementation

    Option Explanation Type Possible values Default value Available in Gauss version
    Histograms Type of histograms string '','None','Default' 'Default' v37r3(p1)
    DatasetName String used to build output file names string any 'Gauss' v37r3(p1)
    SpilloverPaths Spillover paths to fill: [] means no spillover, for 25 ns put ['Next', 'Prev', 'PrevPrev'] list of strings any [] v37r3(p1), in future may be replaced with bunch spacing
    PhysicsList Name of physics list to be passed, will look for options PhysList-xxx.opts string 'LHEP','QGSP' 'LHEP' v37r3(p1), in future may change
    GenStandAlone Flag to indicate that only generator phase is run bool True, False False v37r3(p1)
    BeamMomentum Momentum of the beam real any 5.0*SystemOfUnits.TeV v37r3(p1)
    BeamCrossingAngle Crossing angle of beam 1 in LHCb reference system with respect to z axis real any 0.329*SystemOfUnits.mrad v37r3(p1)
    BeamEmittance Emittance at given energy real any 0.704*(10**(-9))*SystemOfUnits.rad*SystemOfUnits.m v37r3(p1)
    BeamBetaStar Beta* at interaction point real any 2.0*SystemOfUnits.m v37r3(p1)
    InteractionSize Sigma of luminous region in the three coordinates list of 3 real any [ 0.027*SystemOfUnits.mm, 0.027*SystemOfUnits.mm, 3.82*SystemOfUnits.cm ] v37r3(p1)
    BeamSize Sigma of the beam in the transverse coordinates list of 2 real any [ 0.038*SystemOfUnits.mm, 0.038*SystemOfUnits.mm ] v37r3(p1)
    CrossingRate Rate of crossing of filled bunches in LHCb (default is for single crossing per turn) real any 11.245*SystemOfUnits.kilohertz v37r3(p1)
    Luminosity Luminosity per bunch, used with crossing rate and total cross section to calculate nu (collisions/bunch) real any 0.116*(10**30)/(SystemOfUnits.cm2*SystemOfUnits.s) v37r3(p1)
    TotalCrossSection Total cross section at given CM energy, used with crossing rate and luminosity to calculate nu (collisions/bunch) real any 97.2*SystemOfUnits.millibarn v37r3(p1)
    Output Type of data output to write, allow to swith it off string ['', 'NONE', 'SIM'] 'SIM' v37r4, may evolve to have reduced info or have GEN, F(ast)SIM or should we set them automatically with processing?
    Production Type of production to make: physics (with beam), particle guns or machine induced background string ''. 'PHYS', 'PGUN', 'MIB' 'PHYS' v37r4, may be togheter with generator or here put also 'none' that would not make necessary a 'SimOnly'
    Generator Name of generator to use for production (pythia/herwig/bcvegpy) maybe can be a single one with Productio. Note cannot use 'Generator' as name of phase nor 'Generation' as name of algorithm in options of decfiles        
    EventType Event type code to generate, not clear if we want it here or in Generator(), but may want to check consistecy        
    Monitor Type of monitors: GEN, list of detectors. etc... or default, expert, debug... two options?        
    SimOnly/SimStandAlone Execute only the simulation phase, requires an input file        
    SkipG4/FastSim Skip the G4 part but still fill MCParticles/MCVertices from generator info, have a single one with above 'Sim' = none, fast, full? In which case GenStandAlone may be the same as 'Sim=none' and 'Monitor=gen'        
    Geometry List of group of detectors to simulate?        
    Detectors List of detector giving hits (could also give something like reduced info (see RichExtendedInfo)        
    MagneticField Use MagneticFieldSvc or MultipleMagneticFieldSvc that include compensators fileds        

    A SimWriter() configurables also need to be provided where its configuration will depend on which phase of gauss is being executed and has to be usable also by Boole and Brunel for xDST.

    >
    >
    Victor Coco is working on the segmented control of geometry and simulation response of the sub-detectors.
     

    QMTests

    Line: 68 to 38
     
    • 60001008 (Hijing)

    AppConfig and job specifications

    Changed:
    <
    <
    Last update : 9 June 2009
    >
    >
    Last update : 02 October 2009
     
    Changed:
    <
    <
    AppConfing v2rX is used by Gauss v37rX.
    >
    >
    AppConfing v3rX is used by Gauss v37r3 and higher
     For MC09 the following steering options are provided

    Name Beam energy Magnetic Field (crossing angle) Number of collisions/bunch (nu)
    Line: 84 to 55
     See presentation at Tuesday Meeting 24 April 2009 for details on configuration. Additional options can be put in upon request for productions.
    Changed:
    <
    <
    A request by Franz Muheim has been made to setup configuration in MC09 conditions for
    >
    >
    A request by Franz Muheim has been made to setup simulation configurations for
     7 TeV beams at nominal machine for average luminosities/bunch of
    Changed:
    <
    <
    and
    >
    >
    and . This has been made available in AppConfig v3r0.

    A request by Olivier Schneider has been made to setup simulation configurations for 3.5 TeV beams at startup conditions (head on, nu=1). Gloria will provide this shortly.

     

    Spill-over and configurables

    Added:
    >
    >
    Last update : 02 October 2009

    Patrick has prepared a first version of python stearing for producing spillover, Gloria took this as one of the inputs to prepare the Gauss configurable and it is available in Gauss v37r3(p1).

     
    Changed:
    <
    <
    Patrick has prepared a first version of python stearing for producing spillover, Gloria is taking this as one of the inputs to prepare the Gauss configurable.
    >
    >
    The whole "Gauss-event" is not written out when any one of the "25nsec slots events" is failing in G4. The containers of empty events of possible spill-over are not written at all. The GenHeader and the MCHeader are written for all possible spill-over slots.
     
    Changed:
    <
    <
    The whole "Gauss-event" will not written out when any one of the "25nsec slots events" is failing in G4. One thing that needs to be documented is also if the containers of empty events of possible spill-over are written out (empty) or not written at all. The GenHeader and the MCHeader are written for all possible spill-over slots.
    >
    >
    It is not possible to generate events with special generators and spill-over as the initialization of Pythia would need to be redone in this case (as the underlying code is fortran and the same, so no instances with different initializations). A mechanism similar to that of the pileup for special events will need to be put in place.
     

    Gauss read and configurable

    Changed:
    <
    <
    Raluca has provided a GaussRead.py, Gloria has began to look into it to adapt it the the generic case.
    >
    >
    Raluca has provided a GaussRead.py, Gloria has began to look into it to adapt it the the generic case and it will be available as a Gauss() option.
     

    GENSER split and re-commission extra generators

    Added:
    >
    >
    Last update : 02 October 2009

    No work yet in GENSER split.

     
    Changed:
    <
    <
    No work done yet
    >
    >
    Jibo He has re-commissioned BcVegPy and extended it to work in a single release providing pdf data for 3.5+3.5TeV, 5+5TeV and 7+7TeV. The choice of PDF is now possible.
     

    Beam settings in GenHeader and in transient SIMCOND

    Added:
    >
    >
    Last update : 02 October 2009

    Patrick will look into this.

      MC09 compatible ? The data members in GenHeader will be removed and methods will get them via access to class BeamParameter
    Line: 148 to 131
     

    EvtGen

    Added:
    >
    >
    Last update : 02 October 2009
     
    Changed:
    <
    <
    New model for leptonic B decays by Nikolai (see Gauss meeting in April). Will go into EvtGenExtras
    >
    >
    New model for leptonic B decays by Nikolai (see Gauss meeting in April). Introduced in EvtGenExtras (Gauss v37r5)
     

    New Decfiles

    Line: 166 to 150
     For next version of Gauss based on Gaudi v21r*. Backward compatible for MC09. Old one will disappear from Gaudi v22.

    Hijing: 64 bits and random seeds

    Added:
    >
    >
    Last update : 02 October 2009

    Plamen is looking into this.

     

    Validation reports and checks, tuning.

    Added:
    >
    >
    Last update : 02 October 2009
     
    Changed:
    <
    <
    Silvia will work on consolidation of the tools, but large effort, people should be in charge/define both for physics and detectors. Automatic mails when big differences?
    >
    >
    Silvia worked on using the Data Quality and OMALib infrastructure, but large effort, people should be in charge/define both for physics and detectors. Automatic mails when big differences?
     Material checks should be part of this at least for what can be done with existing code (see below for rad lenght and overlaps)

    Monitors of time/steps

    Line: 201 to 189
     

    Moving to Geant4 9.2.p01

    Changed:
    <
    <
    Hubert is modifying Geant4 cmt build scripts (copy of source from LCG area) to be able to put it in the nightly.
    >
    >
    Hubert modified Geant4 cmt build scripts (copy of source from LCG area) and it is now in the nightly.
     

    Choice of settings (delta rays, physics lists, etc)

    Revision 162009-09-19 - GloriaCorti

    Line: 1 to 1
     
    META TOPICPARENT name="LHCbSimulation"

    Gauss current and future developments

    Line: 39 to 39
     
    SkipG4/FastSim Skip the G4 part but still fill MCParticles/MCVertices from generator info, have a single one with above 'Sim' = none, fast, full? In which case GenStandAlone may be the same as 'Sim=none' and 'Monitor=gen'        
    Geometry List of group of detectors to simulate?        
    Detectors List of detector giving hits (could also give something like reduced info (see RichExtendedInfo)        
    Added:
    >
    >
    MagneticField Use MagneticFieldSvc or MultipleMagneticFieldSvc that include compensators fileds        
     

    A SimWriter() configurables also need to be provided where its configuration will depend on which

    Revision 152009-09-16 - GloriaCorti

    Line: 1 to 1
     
    META TOPICPARENT name="LHCbSimulation"

    Gauss current and future developments

    Line: 31 to 31
     
    Luminosity Luminosity per bunch, used with crossing rate and total cross section to calculate nu (collisions/bunch) real any 0.116*(10**30)/(SystemOfUnits.cm2*SystemOfUnits.s) v37r3(p1)
    TotalCrossSection Total cross section at given CM energy, used with crossing rate and luminosity to calculate nu (collisions/bunch) real any 97.2*SystemOfUnits.millibarn v37r3(p1)
    Output Type of data output to write, allow to swith it off string ['', 'NONE', 'SIM'] 'SIM' v37r4, may evolve to have reduced info or have GEN, F(ast)SIM or should we set them automatically with processing?
    Changed:
    <
    <
    Production Type of production to make: physics (with beam), particle guns or machine induced background string ''. 'PHYS', 'PGUN', 'MIB' 'PHYS' v37r4, may be togheter with generator
    Generator Name of generator to use for production (pythia/herwig/bcvegpy) maybe can be a single one with Production        
    >
    >
    Production Type of production to make: physics (with beam), particle guns or machine induced background string ''. 'PHYS', 'PGUN', 'MIB' 'PHYS' v37r4, may be togheter with generator or here put also 'none' that would not make necessary a 'SimOnly'
    Generator Name of generator to use for production (pythia/herwig/bcvegpy) maybe can be a single one with Productio. Note cannot use 'Generator' as name of phase nor 'Generation' as name of algorithm in options of decfiles        
     
    EventType Event type code to generate, not clear if we want it here or in Generator(), but may want to check consistecy        
    Monitor Type of monitors: GEN, list of detectors. etc... or default, expert, debug... two options?        
    SimOnly/SimStandAlone Execute only the simulation phase, requires an input file        
    Changed:
    <
    <
    SkipG4/FastSim Skip the G4 part but still fill MCParticles/MCVertices from generator info, have a single one with above Sim = none, fast, full?        
    >
    >
    SkipG4/FastSim Skip the G4 part but still fill MCParticles/MCVertices from generator info, have a single one with above 'Sim' = none, fast, full? In which case GenStandAlone may be the same as 'Sim=none' and 'Monitor=gen'        
     
    Geometry List of group of detectors to simulate?        
    Detectors List of detector giving hits (could also give something like reduced info (see RichExtendedInfo)        

    Revision 142009-09-15 - GloriaCorti

    Line: 1 to 1
     
    META TOPICPARENT name="LHCbSimulation"

    Gauss current and future developments

    Line: 8 to 8
     

    Gauss configurable

    Changed:
    <
    <
    Gloria is working on this. At the moment a Gauss() configurable is not yet ready, but some stand alone functions have been defined and are being implemented.
    >
    >
    Gloria is working on this. A first version of the Gauss() configurable is available with v37r3(p1), but not all control parameters yet. In particular the generator of non pp collisions (pgun and mib) are temporarly off.
     There is some issues as where to put the monitoring subphases for Generation and Simulation as part of the top level Gauss sequence (more appropriate when reading) or of the Generation and Simulation sub-sequence (more appropriate when the corresponding sub-sequence are executed).
    Changed:
    <
    <
    Not all of the control parameters will be available with the first version. Some of the control parameters will/could be:
    >
    >
    A list of some of the control parameters and meaning is given below as well as status of the implementation
     
    Changed:
    <
    <
    • Generation = true/false
    • Generator = pythia/herwig/bcvegpy/etc.
    • Simulation = none/fake (skipg4 but fill MCP and MCV)/full
    • MagneticField = up/down/off
    • All beam settings necessary ?
    • Spillover = on/off
    • SpilloverPaths = list of possible slots
    • RichExtendedInfo
    • Monitors = default/detailed/none
    >
    >
    Option Explanation Type Possible values Default value Available in Gauss version
    Histograms Type of histograms string '','None','Default' 'Default' v37r3(p1)
    DatasetName String used to build output file names string any 'Gauss' v37r3(p1)
    SpilloverPaths Spillover paths to fill: [] means no spillover, for 25 ns put ['Next', 'Prev', 'PrevPrev'] list of strings any [] v37r3(p1), in future may be replaced with bunch spacing
    PhysicsList Name of physics list to be passed, will look for options PhysList-xxx.opts string 'LHEP','QGSP' 'LHEP' v37r3(p1), in future may change
    GenStandAlone Flag to indicate that only generator phase is run bool True, False False v37r3(p1)
    BeamMomentum Momentum of the beam real any 5.0*SystemOfUnits.TeV v37r3(p1)
    BeamCrossingAngle Crossing angle of beam 1 in LHCb reference system with respect to z axis real any 0.329*SystemOfUnits.mrad v37r3(p1)
    BeamEmittance Emittance at given energy real any 0.704*(10**(-9))*SystemOfUnits.rad*SystemOfUnits.m v37r3(p1)
    BeamBetaStar Beta* at interaction point real any 2.0*SystemOfUnits.m v37r3(p1)
    InteractionSize Sigma of luminous region in the three coordinates list of 3 real any [ 0.027*SystemOfUnits.mm, 0.027*SystemOfUnits.mm, 3.82*SystemOfUnits.cm ] v37r3(p1)
    BeamSize Sigma of the beam in the transverse coordinates list of 2 real any [ 0.038*SystemOfUnits.mm, 0.038*SystemOfUnits.mm ] v37r3(p1)
    CrossingRate Rate of crossing of filled bunches in LHCb (default is for single crossing per turn) real any 11.245*SystemOfUnits.kilohertz v37r3(p1)
    Luminosity Luminosity per bunch, used with crossing rate and total cross section to calculate nu (collisions/bunch) real any 0.116*(10**30)/(SystemOfUnits.cm2*SystemOfUnits.s) v37r3(p1)
    TotalCrossSection Total cross section at given CM energy, used with crossing rate and luminosity to calculate nu (collisions/bunch) real any 97.2*SystemOfUnits.millibarn v37r3(p1)
    Output Type of data output to write, allow to swith it off string ['', 'NONE', 'SIM'] 'SIM' v37r4, may evolve to have reduced info or have GEN, F(ast)SIM or should we set them automatically with processing?
    Production Type of production to make: physics (with beam), particle guns or machine induced background string ''. 'PHYS', 'PGUN', 'MIB' 'PHYS' v37r4, may be togheter with generator
    Generator Name of generator to use for production (pythia/herwig/bcvegpy) maybe can be a single one with Production        
    EventType Event type code to generate, not clear if we want it here or in Generator(), but may want to check consistecy        
    Monitor Type of monitors: GEN, list of detectors. etc... or default, expert, debug... two options?        
    SimOnly/SimStandAlone Execute only the simulation phase, requires an input file        
    SkipG4/FastSim Skip the G4 part but still fill MCParticles/MCVertices from generator info, have a single one with above Sim = none, fast, full?        
    Geometry List of group of detectors to simulate?        
    Detectors List of detector giving hits (could also give something like reduced info (see RichExtendedInfo)        
      A SimWriter() configurables also need to be provided where its configuration will depend on which phase of gauss is being executed and has to be usable also by Boole and Brunel for xDST.

    Revision 132009-07-03 - GloriaCorti

    Line: 1 to 1
     
    META TOPICPARENT name="LHCbSimulation"

    Gauss current and future developments

    Line: 143 to 143
     

    SHERPA interface

    Julian and Tobias from Dortmund, private build of new version of sherpa. In CVS but will wait to

    Changed:
    <
    <
    put in a release for official build of necessary version by LCG
    >
    >
    put in a release for official build of necessary version by LCG. Julian was able to geenerate inclusive b events with Sherpa as production engine. He observes differences in the rapidity distribution for all particles and for B mesons with respect to Pythia.
     

    New particle property service

    Line: 173 to 173
     

    Overlaps in geometry

    Velo group has been notified for overal in its detector.

    Added:
    >
    >
    Tom (Latham) and Mark (Whitehead) are working on the VELO overlaps and remarked that david only works for simple solids. They have found one overlap upstream of the VELO with the beam pipe. Gloria will dig up the CDD drawings for this area.

    Marco (Pappagallo) is also running david when switching on the "BeforeMagnet" region and has found some overlap there.

      For beam pipe cables and T envelope, Gloria will look for somebody that could do it.

    Revision 122009-07-03 - GloriaCorti

    Line: 1 to 1
     
    META TOPICPARENT name="LHCbSimulation"

    Gauss current and future developments

    Changed:
    <
    <
    Last update : 22 Apr 2009
    >
    >
    Last update : 03 July 2009
     

    Gauss configurable

    Gloria is working on this. At the moment a Gauss() configurable is not yet ready, but

    Changed:
    <
    <
    some stand alone functions have been defined.
    >
    >
    some stand alone functions have been defined and are being implemented. There is some issues as where to put the monitoring subphases for Generation and Simulation as part of the top level Gauss sequence (more appropriate when reading) or of the Generation and Simulation sub-sequence (more appropriate when the corresponding sub-sequence are executed).
     Not all of the control parameters will be available with the first version. Some of the control parameters will/could be:
    Line: 51 to 54
     

    AppConfig and job specifications

    Last update : 9 June 2009
    Changed:
    <
    <
    AppConfing v2r* is used by Gauss v37rX.
    >
    >
    AppConfing v2rX is used by Gauss v37rX.
     For MC09 the following steering options are provided

    Name Beam energy Magnetic Field (crossing angle) Number of collisions/bunch (nu)
    Line: 65 to 68
     See presentation at Tuesday Meeting 24 April 2009 for details on configuration. Additional options can be put in upon request for productions.
    Added:
    >
    >
    A request by Franz Muheim has been made to setup configuration in MC09 conditions for 7 TeV beams at nominal machine for average luminosities/bunch of and
     

    Spill-over and configurables

    Patrick has prepared a first version of python stearing for producing spillover, Gloria is taking this as one of the inputs to prepare the Gauss configurable.

    Added:
    >
    >
    The whole "Gauss-event" will not written out when any one of the "25nsec slots events" is failing in G4. One thing that needs to be documented is also if the containers of empty events of possible spill-over are written out (empty) or not written at all. The GenHeader and the MCHeader are written for all possible spill-over slots.
     

    Gauss read and configurable

    Raluca has provided a GaussRead.py, Gloria has began to look into it to adapt it the the generic case.

    Line: 116 to 126
     

    CP violation in new EvtGen

    CPV models have temporarly been switched off to prevent their use before validating them.

    Changed:
    <
    <
    Mark Whitehead will look into the model provided by EvtGen. The VHCP model written by Tristan duPree needs to be rechecked with the new EvtGen, Olivier Leroy is looking for volonteers.
    >
    >
    Mark Whitehead is looking into the model provided by EvtGen. The VHCP model written by Tristan duPree has been rechecked with the new EvtGen by Greig Cowan, some adaptation necessary. Additional tests in progress.
     

    EvtGen

    Line: 125 to 137
     

    New Decfiles

    Changed:
    <
    <
    Neal Gueissaz sent new decfiles for susy, not done yet, requires also addition to GaussPhysics.
    >
    >
    Various new DecFiles added by Patrick. Additional files can be added as necessary.
     
    Deleted:
    <
    <
    Loic Esteve sent new decfile for B+ -> D0 K+, D0 -->
    KS pi pi pi0, to be added.
     

    SHERPA interface

    Revision 112009-06-29 - GloriaCorti

    Line: 1 to 1
     
    META TOPICPARENT name="LHCbSimulation"

    Gauss current and future developments

    Line: 93 to 93
     beta* Bunch spacing (for subsequent trains, i.e. 25 nsec, 50 nsec, etc. to give possible spill-over) ?
    Added:
    >
    >
    Thomas suggested to also add the
    mean position(x,y,z)
    of the primary vertex (pp or p-gas) as it could be offset with respect to the LHCb reference system.
      Methods derived from above quantities:
    Line: 141 to 143
     

    Validation reports and checks, tuning.

    Silvia will work on consolidation of the tools, but large effort, people should be in charge/define both for physics and detectors. Automatic mails when big differences?

    Changed:
    <
    <
    Material checks should be part of this at least for what can be done with existing code (see below)
    >
    >
    Material checks should be part of this at least for what can be done with existing code (see below for rad lenght and overlaps)
     

    Monitors of time/steps

    Line: 149 to 151
     older version for that (what Olga took as guideline) exists made by one of Gloria old summer students

    Material scans in parallel geometry

    Added:
    >
    >
    Silvia will prepare options to be run with current geometry structure. Once the restructuring of the LHCb -->
    G4 geometry is done and allow parallel geometry, this will make use of the parallel geometry. In DDDB it will already be prepared in a parallel structure.
     

    New mechanism for geometry 'conversion' from LHCb to G4

    Marco P. will look into this wen he is back in september. Checking of overlaps at construction should also be

    Changed:
    <
    <
    investigated.
    >
    >
    investigated. For the moment material checks should be included in standard tests when geometry is modified.
     

    Overlaps in geometry

    Changed:
    <
    <
    Velo group has been notified.
    >
    >
    Velo group has been notified for overal in its detector.
      For beam pipe cables and T envelope, Gloria will look for somebody that could do it.

    Revision 102009-06-24 - SilviaMiglioranzi

    Line: 1 to 1
     
    META TOPICPARENT name="LHCbSimulation"

    Gauss current and future developments

    Line: 40 to 40
      Test with Gauss-2008.py has been removed (obsolete file), probably a test at different energies/beam settings would also be useful.
    Added:
    >
    >
    Update: QMTests at generator-only level added in the repository for the following eventypes (running only on 10 evts):
    • 10000000
    • 14103000
    • 22112000
    • 42112002
    • 14143011 (BcVegPy)
    • 60001008 (Hijing)
     

    AppConfig and job specifications

    Last update : 9 June 2009

    Revision 92009-06-23 - SilviaMiglioranzi

    Line: 1 to 1
     
    META TOPICPARENT name="LHCbSimulation"

    Gauss current and future developments

    Line: 195 to 195
     and verified all materials (including vacuum) are correctly put in. Thomas will investigate once more statistics is available if there is still an issue for MC09.
    Added:
    >
    >
    UPDATE:

    Thomas investigated using MC09 (see his slides in: http://indico.cern.ch/conferenceDisplay.py?confId=60170). The Z distribution of these observed proton-vacuum interactions was quite homogeneous between -4m and +1m (despite removing overlaps between DC06 and MC09, at present it seems that these interactions have increased).

    Checks performed by Gloria and Silvia revealed that:

    • the simulation in Gauss is activated starting from "BeforeMagnetRegion/Velo", i.e. from -4m to ~-1m there is no detector simulation taken into account. The interactions in that region were occurring with the Air inside the Universe.
    • moving from DC06 to MC09 the way the Velo geometry is activated in Gauss has changed. The envelope "BeforeMagnetRegion/Velo" (which is filled with "vacuum" and contains all the Velo sub-elements) is no longer activated in order to avoid double counting of the Velo sub-elements (which are instead individually activated due to misalignment requirements). The results is that the mother of the sensors (and the other Velo sub-elements) is no longer "Velo" but the Universe/World (i.e. filled with Air).

      -- GloriaCorti - 22 Apr 2009 \ No newline at end of file

    Revision 82009-06-09 - GloriaCorti

    Line: 1 to 1
     
    META TOPICPARENT name="LHCbSimulation"

    Gauss current and future developments

    Line: 40 to 40
      Test with Gauss-2008.py has been removed (obsolete file), probably a test at different energies/beam settings would also be useful.
    Changed:
    <
    <

    AppConfig and job specifications

    >
    >

    AppConfig and job specifications

    Last update : 9 June 2009
     
    Changed:
    <
    <
    AppConfing v2r* is used by Gauss v37r0. Gloria is preparing the Gauss options to go there for MC09. There is currently one Gauss-MC09, with standard configuration for it MC09-b5TeV-md100.py with nu=1 (see presentation at Tuesday Meeting 24 Apr for full list oif configuration). Different nu will be put in as new MC09-b5TeV-md100-nuN.py
    >
    >
    AppConfing v2r* is used by Gauss v37rX. For MC09 the following steering options are provided

    Name Beam energy Magnetic Field (crossing angle) Number of collisions/bunch (nu)
    MC09-b5TeV-md100.py 5 TeV Full field downward direction 1
    MC09-b5TeV-md100-nu2.py 5 TeV Full field downward direction 2
    MC09-b5TeV-md100-nu3.py 5 TeV Full field downward direction 3
    MC09-b5TeV-md100-nu4.py 5 TeV Full field downward direction 4
    MC09-b5TeV-moff.py 5 TeV Field off 1
    MC09-b450GeV-moff.py 450 GeV Field off 1

    See presentation at Tuesday Meeting 24 April 2009 for details on configuration. Additional options can be put in upon request for productions.

     

    Spill-over and configurables

    Revision 72009-06-05 - GloriaCorti

    Line: 1 to 1
     
    META TOPICPARENT name="LHCbSimulation"

    Gauss current and future developments

    Line: 69 to 69
     Normalized emittance (epsilon_n) Revolution frequency (fixed at 11.245 kHz) (cannot be settable) Total cross section
    Changed:
    <
    <
    Effective crossing angle (or external and calculate internal from Pz and mag field? effective probably better)
    >
    >
    Effective crossing angle (better that to set external and calculate internal from Pz and mag field)
     beta* Bunch spacing (for subsequent trains, i.e. 25 nsec, 50 nsec, etc. to give possible spill-over) ?
    Line: 83 to 83
     RMS bunch size in y RMS luminous size in x for beam-beam collisions RMS luminous size in y
    Changed:
    <
    <
    RMS luminous size in z
    >
    >
    RMS luminous size in z (should handle also beam gas large spread...)
     Luminosity per bunch Average number of interactions per bunch
    Changed:
    <
    <
    >
    >
    Position of interaction in x, y and z
     
    Added:
    >
    >
    Investigate putting this data in FSR as it will be the same for all events in the same job.
     

    CP violation in new EvtGen

    CPV models have temporarly been switched off to prevent their use before validating them.

    Line: 130 to 132
     

    New mechanism for geometry 'conversion' from LHCb to G4

    Added:
    >
    >
    Marco P. will look into this wen he is back in september. Checking of overlaps at construction should also be investigated.

    Overlaps in geometry

    Velo group has been notified.

    For beam pipe cables and T envelope, Gloria will look for somebody that could do it.

     

    Generator statistics, script and FSR

    Added:
    >
    >
    For MC09 will need to keep using the script, in the long term the FSR should be used. Need somebody (more than a summer student) to work on this.
     

    Moving to Geant4 9.2.p01

    Hubert is modifying Geant4 cmt build scripts (copy of source from LCG area) to be able to put it in the nightly.

    Line: 166 to 179
     

    Revision of User Guide

    Dark matter under RICH1

    Changed:
    <
    <
    In DC06 there was the issue of some interactions being produced in the beam pipe vacuum in the RICH1 region. This was reported by Thomas R. that observed them in pp elastic collisions. Sajan think this may be due to an error in geometry where the vacuum is not put it and the gas of RICH1 is left in a small area. This has not been investigated but as this part has not changed it should be looked at again in MC09.
    >
    >
    In DC06 there was the issue of some interactions being produced in the beam pipe vacuum in the RICH1 region. This was reported by Thomas R. that observed them in pp elastic collisions. Sajan think this may be due to an error in geometry where the vacuum is not put it and the gas of RICH1 is left in a small area. Sajan checked this and verified all materials (including vacuum) are correctly put in. Thomas will investigate once more statistics is available if there is still an issue for MC09.
     

    -- GloriaCorti - 22 Apr 2009 \ No newline at end of file

    Revision 62009-06-05 - GloriaCorti

    Line: 1 to 1
     
    META TOPICPARENT name="LHCbSimulation"

    Gauss current and future developments

    Line: 24 to 24
     
    • Monitors = default/detailed/none

    A SimWriter() configurables also need to be provided where its configuration will depend on which

    Changed:
    <
    <
    phase of gauss is being executed.
    >
    >
    phase of gauss is being executed and has to be usable also by Boole and Brunel for xDST.
     

    QMTests

    Line: 33 to 33
     She has also committed a SAM test for checking the installation on remote sites, for Gauss, as the G4 geometry (hence the access) is done during the first event this means running one event.
    Added:
    >
    >
    A test at generator level for 1000 events has also been introduced.
     Need to prepare a list of additional QMTests that may be useful, eg. some at generator level for the various generators and for signal to test EvtGen.
    Added:
    >
    >
    Test with Gauss-2008.py has been removed (obsolete file), probably a test at different energies/beam settings would also be useful.
     

    AppConfig and job specifications

    AppConfing v2r* is used by Gauss v37r0. Gloria is preparing the Gauss options to go there for

    Line: 48 to 52
     

    Gauss read and configurable

    Changed:
    <
    <
    Raluca has provided a GaussRead.py, this will constitute an input for
    >
    >
    Raluca has provided a GaussRead.py, Gloria has began to look into it to adapt it the the generic case.
     

    GENSER split and re-commission extra generators

    Line: 57 to 61
     

    Beam settings in GenHeader and in transient SIMCOND

    MC09 compatible ?

    Changed:
    <
    <

    Mixing in new EvtGen

    Warwick should be looking into this with help from Patrick. Patrick is going to look into it. For the moment mixing is off and decay files with yesIncoherentMixing will not work, nor with the VHCP model that has been temporarly switched off.

    >
    >
    The data members in GenHeader will be removed and methods will get them via access to class BeamParameter Proposed list of data members is
    Energy (or Pz)
    RMS bunch lenght (sigma_s)
    Normalized emittance (epsilon_n)
    Revolution frequency (fixed at 11.245 kHz) (cannot be settable)
    Total cross section
    Effective crossing angle (or external and calculate internal from Pz and mag field? effective probably better)
    beta*
    Bunch spacing (for subsequent trains, i.e. 25 nsec, 50 nsec, etc. to give possible spill-over) ?
    

    Methods derived from above quantities:

    Relativistic gamma
    Relativistic beta (is it really necessary?)
    Emittance (not normalized vs. E)
    RMS bunch size in x 
    RMS bunch size in y
    RMS luminous size in x for beam-beam collisions
    RMS luminous size in y
    RMS luminous size in z
    Luminosity per bunch
    Average number of interactions per bunch
    
    

    CP violation in new EvtGen

    CPV models have temporarly been switched off to prevent their use before validating them. Mark Whitehead will look into the model provided by EvtGen. The VHCP model written by Tristan duPree needs to be rechecked with the new EvtGen, Olivier Leroy is looking for volonteers.

     

    EvtGen

    Line: 69 to 101
     

    New Decfiles

    Changed:
    <
    <
    Neal send new decfiles for susy, not done yet
    >
    >
    Neal Gueissaz sent new decfiles for susy, not done yet, requires also addition to GaussPhysics.
    

    Loic Esteve sent new decfile for B+ -> D0 K+, D0 -->

    KS pi pi pi0, to be added.
     

    SHERPA interface

    Line: 78 to 112
     

    New particle property service

    Added:
    >
    >
    For next version of Gauss based on Gaudi v21r*. Backward compatible for MC09. Old one will disappear from Gaudi v22.
     

    Hijing: 64 bits and random seeds

    Changed:
    <
    <

    Validation reports

    >
    >

    Validation reports and checks, tuning.

    Silvia will work on consolidation of the tools, but large effort, people should be in charge/define both for physics and detectors. Automatic mails when big differences? Material checks should be part of this at least for what can be done with existing code (see below)

     

    Monitors of time/steps

    Added:
    >
    >
    Stefania commited code from Olga for muons. It needs some clean up and to be extended to all detectors, an older version for that (what Olga took as guideline) exists made by one of Gloria old summer students
     

    Material scans in parallel geometry

    New mechanism for geometry 'conversion' from LHCb to G4

    Line: 93 to 134
     

    Moving to Geant4 9.2.p01

    Added:
    >
    >
    Hubert is modifying Geant4 cmt build scripts (copy of source from LCG area) to be able to put it in the nightly.
     

    Choice of settings (delta rays, physics lists, etc)

    Added:
    >
    >
    Delta rays will be switched on everywere in Gauss v38r0. Expect issues.
     

    slc5 and gcc 4.3

    Will need to move to latest version of external libraries

    Revision 52009-05-11 - GloriaCorti

    Line: 1 to 1
     
    META TOPICPARENT name="LHCbSimulation"

    Gauss current and future developments

    Line: 120 to 120
     

    Revision of User Guide

    Added:
    >
    >

    Dark matter under RICH1

    In DC06 there was the issue of some interactions being produced in the beam pipe vacuum in the RICH1 region. This was reported by Thomas R. that observed them in pp elastic collisions. Sajan think this may be due to an error in geometry where the vacuum is not put it and the gas of RICH1 is left in a small area. This has not been investigated but as this part has not changed it should be looked at again in MC09.
     

    -- GloriaCorti - 22 Apr 2009 \ No newline at end of file

    Revision 42009-05-08 - GloriaCorti

    Line: 1 to 1
     
    META TOPICPARENT name="LHCbSimulation"

    Gauss current and future developments

    Line: 39 to 39
     

    AppConfig and job specifications

    AppConfing v2r* is used by Gauss v37r0. Gloria is preparing the Gauss options to go there for

    Changed:
    <
    <
    MC09. There will be two Gauss-MC09, with standard configuration and then Beam5TeV-FieldDown and Beam5TeV-FieldUp.
    >
    >
    MC09. There is currently one Gauss-MC09, with standard configuration for it MC09-b5TeV-md100.py with nu=1 (see presentation at Tuesday Meeting 24 Apr for full list oif configuration). Different nu will be put in as new MC09-b5TeV-md100-nuN.py
     

    Spill-over and configurables

    Line: 60 to 60
     

    Mixing in new EvtGen

    Changed:
    <
    <
    Warwick should be looking into this with help from Patrick
    >
    >
    Warwick should be looking into this with help from Patrick. Patrick is going to look into it. For the moment mixing is off and decay files with yesIncoherentMixing will not work, nor with the VHCP model that has been temporarly switched off.

    EvtGen

    New model for leptonic B decays by Nikolai (see Gauss meeting in April). Will go into EvtGenExtras

     

    New Decfiles

    Revision 32009-05-07 - GloriaCorti

    Line: 1 to 1
     
    META TOPICPARENT name="LHCbSimulation"

    Gauss current and future developments

    Line: 92 to 92
     

    slc5 and gcc 4.3

    Changed:
    <
    <
    Generators libraries exist/will exist only for latest version, in some cases need to change version (pythia 6.4.18 -->
    6.4.20) Only Geant4 9.2 validated.
    >
    >
    Will need to move to latest version of external libraries
    Generators libraries exist/will exist only for latest version, in some cases need to change version 
    • pythia6 4.18 --> 4.20
    • lhpadf 5.3.1 --> 5.7.0
    • photos ? not clear chnages made in 215.5 (using 215.2)
    • pythia8 107.1 -->
    210
  • herwig 6.510.2 --> 6.510.3 (-f_no_automatic flag)
  • Of the Geant4 versions only G4 9.2 has been validated.
     

    Windows and MacOS builds

    Changed:
    <
    <
    Work done in the past by Karl Harrison for win32 for default generator (still some problems when running). Asked to deploy/build also herwig, etc. No generators libraries on MacOS, will request it formally.
    >
    >
    Work done in the past by Karl Harrison for win32 for default generator (still some problems when running). May become a problem due to availability of fortran compiler on win32. Asked to deploy/build also herwig, etc. No generators libraries on MacOS, will request it formally.
     

    Repackaging

    Added:
    >
    >
    Idea is to separate all interfaces and base classes in a separate package for both generators and simulation. Separate LHCb specific parts from generic GiGa parts.
     

    Revision of Tutorial

    Revision of User Guide

    Revision 22009-04-22 - GloriaCorti

    Line: 1 to 1
     
    META TOPICPARENT name="LHCbSimulation"
    Changed:
    <
    <

    Current and future developments

    >
    >

    Gauss current and future developments

    Last update : 22 Apr 2009

     

    Gauss configurable

    Added:
    >
    >
    Gloria is working on this. At the moment a Gauss() configurable is not yet ready, but some stand alone functions have been defined. Not all of the control parameters will be available with the first version. Some of the control parameters will/could be:

    • Generation = true/false
    • Generator = pythia/herwig/bcvegpy/etc.
    • Simulation = none/fake (skipg4 but fill MCP and MCV)/full
    • MagneticField = up/down/off
    • All beam settings necessary ?
    • Spillover = on/off
    • SpilloverPaths = list of possible slots
    • RichExtendedInfo
    • Monitors = default/detailed/none

    A SimWriter() configurables also need to be provided where its configuration will depend on which phase of gauss is being executed.

     

    QMTests

    Added:
    >
    >
    Silvia has prepared the QMTests running the default for few events. This is in Gauss v37r0. She has also committed a SAM test for checking the installation on remote sites, for Gauss, as the G4 geometry (hence the access) is done during the first event this means running one event.

    Need to prepare a list of additional QMTests that may be useful, eg. some at generator level for the various generators and for signal to test EvtGen.

     

    AppConfig and job specifications

    Added:
    >
    >
    AppConfing v2r* is used by Gauss v37r0. Gloria is preparing the Gauss options to go there for MC09. There will be two Gauss-MC09, with standard configuration and then Beam5TeV-FieldDown and Beam5TeV-FieldUp.
     

    Spill-over and configurables

    Added:
    >
    >
    Patrick has prepared a first version of python stearing for producing spillover, Gloria is taking this as one of the inputs to prepare the Gauss configurable.
     

    Gauss read and configurable

    Added:
    >
    >
    Raluca has provided a GaussRead.py, this will constitute an input for
     

    GENSER split and re-commission extra generators

    Added:
    >
    >
    No work done yet
     

    Beam settings in GenHeader and in transient SIMCOND

    Added:
    >
    >
    MC09 compatible ?
     

    Mixing in new EvtGen

    Added:
    >
    >
    Warwick should be looking into this with help from Patrick

     

    New Decfiles

    Added:
    >
    >
    Neal send new decfiles for susy, not done yet
     

    SHERPA interface

    Added:
    >
    >
    Julian and Tobias from Dortmund, private build of new version of sherpa. In CVS but will wait to put in a release for official build of necessary version by LCG
     

    New particle property service

    Added:
    >
    >
     

    Hijing: 64 bits and random seeds

    Validation reports

    Line: 44 to 92
     

    slc5 and gcc 4.3

    Added:
    >
    >
    Generators libraries exist/will exist only for latest version, in some cases need to change version (pythia 6.4.18 -->
    6.4.20) Only Geant4 9.2 validated.
     

    Windows and MacOS builds

    Added:
    >
    >
    Work done in the past by Karl Harrison for win32 for default generator (still some problems when running). Asked to deploy/build also herwig, etc. No generators libraries on MacOS, will request it formally.
     

    Repackaging

    Revision of Tutorial

    Line: 54 to 107
     
    Changed:
    <
    <
    -- Last update GloriaCorti - 22 Apr 2009
    >
    >
    -- GloriaCorti - 22 Apr 2009

    Revision 12009-04-22 - GloriaCorti

    Line: 1 to 1
    Added:
    >
    >
    META TOPICPARENT name="LHCbSimulation"

    Current and future developments

    Gauss configurable

    QMTests

    AppConfig and job specifications

    Spill-over and configurables

    Gauss read and configurable

    GENSER split and re-commission extra generators

    Beam settings in GenHeader and in transient SIMCOND

    Mixing in new EvtGen

    New Decfiles

    SHERPA interface

    New particle property service

    Hijing: 64 bits and random seeds

    Validation reports

    Monitors of time/steps

    Material scans in parallel geometry

    New mechanism for geometry 'conversion' from LHCb to G4

    Generator statistics, script and FSR

    Moving to Geant4 9.2.p01

    Choice of settings (delta rays, physics lists, etc)

    slc5 and gcc 4.3

    Windows and MacOS builds

    Repackaging

    Revision of Tutorial

    Revision of User Guide

    -- Last update GloriaCorti - 22 Apr 2009

     
    This site is powered by the TWiki collaboration platform Powered by PerlCopyright & 2008-2019 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
    Ideas, requests, problems regarding TWiki? Send feedback