Difference: VeloPix (1 vs. 26)

Revision 262013-06-18 - HellaSnoek

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

VeloPix in LHCb simulations

Line: 129 to 129
 Now when Gauss will call the Upgrade database at $SQLITEDBPATH/DDDB_upgrade.db/DDDB it will see your private VeloPix-friendly database as default. Don't forget to adapt the DDDBtag to the tag present in your private database, as explained on the next section. Usually the tag to use is "HEAD", unless you explicitly specified another one.

VeloPix in Boole

Changed:
<
<
The package for digitization and clusterization (VeloPix/VeloPixAlgorithms) as well as the package with linkers from clusters and digits to MC hits and MC particles (VeloPix/VeloPixAssociators) you may find in the Boole release v20r1 or higher. The package for preparing Raw Data with pixel Velo as well as decoding VeloPix clusters at the level of Brunel (VeloPix/VeloPixDAQ) you may find in the Lbcom release v8r0 or higher. Since VeloPix/VeloPixDAQ package is located in the Lbcom, the algorithms from this package are automatically taken by Boole or Brunel, if these algorithms are added to the Boole/Brunel VeloPix sequences in Configuration.py (they are already added to the Boole VeloPix sequence).
>
>
Different packages are available in Boole from release v20r1 on:

VP/VPAlgorithms - Digitization and Clustering code
VP/VPAssociators - Associators from clusters and digits to MCHits and MCParticles

In Lbcom from release v8r0 on you will find:
VP/VPDAQ - Preparing raw data for the VP and the decoding of the VP clusters (Brunel level)

The algorithms from this package are automatically taken by Boole or Brunel, if these algorithms are added to the Boole/Brunel VP sequences in Configuration.py (they are already added to the Boole VP sequence).
 

Set Boole Environment

In order to set Boole environment, you have to choose Boole version (v20r1 or higher), e.g.:

Revision 252011-10-12 - MatthewReid

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

VeloPix in LHCb simulations

Line: 153 to 153
 To specify the tag of database to use, one needs the following lines (see also VeloPix in Gauss).
LHCbApp().DataType  = "Upgrade"
Changed:
<
<
LHCbApp().DDDBtag = "velopix-mul-20091116" LHCbApp().CondDBtag = "sim-20091112-vc-md100"
>
>
LHCbApp().DDDBtag = "velopix-mul-20100909" LHCbApp().CondDBtag = "sim-20100510-vc-md100"
 

Then you have to specify that you want to use VeloPix instead of Velo and you have to switch the L0 off:

Revision 242011-07-21 - MatthewReid1

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

VeloPix in LHCb simulations

Line: 32 to 32
 
    SetupProject Panoramix v19r4
Changed:
<
<
Then simply copy $WORKDIR/VeloPixSettings.py file to your work directory. This file is a slightly modified version of $myPanoramix which sets the tags and also points Panoramix to the location of your xml description. Lets look at additions to the code in a bit more detail
>
>
Then simply copy $WORKDIR/myPanoramix-upgrade-dddb.py file to your work directory. This file is a slightly modified version of $myPanoramix which sets the tags and also points Panoramix to the location of your xml description. Lets look at the additions to the code in a bit more detail
  start Panoramix configurable

Revision 232011-07-20 - MatthewReid1

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

VeloPix in LHCb simulations

Line: 16 to 16
 

VeloPix in Panoramix

Changed:
<
<
The following instructions were made using Panoramix v19r4 and CondDB tags: DDDB tag "velopix-mul-20100909" and SIMCOND tag. If you wish to modify the xml description of the VeloPix then you must follow these steps.
>
>
The following instructions were made using Panoramix v19r4 and CondDB tags: DDDB tag "velopix-mul-20100909" and SIMCOND tag "sim-20100510-vc-md100". If you wish to modify the xml description of the VeloPix then you must follow these steps.
 

Get the .db for VeloPix

1) Grab the DDDB_upgrade.db xml code and store it to a local area to work from ("SomeLocalPath" in the example I used $HOME/VELOPIX/dddb-velopix-mul-20100909/).
Line: 33 to 33
  SetupProject Panoramix v19r4 Then simply copy $WORKDIR/VeloPixSettings.py file to your work directory.
Changed:
<
<
This file is a slightly modified version of $myPanoramix which sets the tags and also points Panoramix to the location of you xml description. Lets look at additions to the code in a bit more detail
>
>
This file is a slightly modified version of $myPanoramix which sets the tags and also points Panoramix to the location of your xml description. Lets look at additions to the code in a bit more detail
  start Panoramix configurable

Revision 222011-07-19 - MatthewReid1

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

VeloPix in LHCb simulations

Line: 15 to 15
 
Added:
>
>

VeloPix in Panoramix

The following instructions were made using Panoramix v19r4 and CondDB tags: DDDB tag "velopix-mul-20100909" and SIMCOND tag. If you wish to modify the xml description of the VeloPix then you must follow these steps.

Get the .db for VeloPix

1) Grab the DDDB_upgrade.db xml code and store it to a local area to work from ("SomeLocalPath" in the example I used $HOME/VELOPIX/dddb-velopix-mul-20100909/).
SetupProject LHCb
dump_db_to_files.py -c sqlite_file:$SQLITEDBPATH/DDDB_upgrade.db/DDDB -T "velopix-mul-20100909" -d <SomeLocalPath>
dump_db_to_files.py -c sqlite_file:$SQLITEDBPATH/SIMCOND.db/SIMCOND -T "sim-20100510-vc-md100" -d <SomeLocalPath>
This saves the geometry and conditions database in xml format where it can be modified by the user.

Setup the Panoramix environment

2) We must now specify these tags which we have used so that Panoramix can build the xml and display the correct geometry.
    SetupProject Panoramix v19r4
Then simply copy $WORKDIR/VeloPixSettings.py file to your work directory. This file is a slightly modified version of $myPanoramix which sets the tags and also points Panoramix to the location of you xml description. Lets look at additions to the code in a bit more detail

start Panoramix configurable

    from Gaudi.Configuration import *
    from Configurables import LHCbApp,CondDB 
    DDDBtag = "velopix-mul-20100909"
    CondDBtag = "sim-20100510-vc-md100"
    lhcbApp  = LHCbApp()
for simulation, tag should be the same as used in Gauss
    lhcbApp.DDDBtag = DDDBtag
    lhcbApp.CondDBtag = CondDBtag

Later in the file we specify the location of the xml to be used by Panoramix, we pass the lhcb.xml file containing the entire tree structure for the geometry and conditions

#--Geometry dependent options, use information from SIMCOND for positions

    privatedb_path = "<SomeLocalPath>/"
    from Configurables import DDDBConf 
    DDDBConf(DbRoot = privatedb_path + "lhcb.xml")

Running Panoramix with VeloPix

3) Finally to run Panoramix we must specify the head tag, which in this case, is the "Upgrade" tag. Enter the below into the terminal
    python myPanoramix-upgrade-dddb.py -D Upgrade
 
You will probably see lots of errors but stick with it, eventually Panoramix will pop up and you can begin to check the changes you have made in the xml.
 

VeloPix in Gauss

Line: 183 to 232
 

-- VictorCoco - 21-Apr-2010

Added:
>
>
-- MatthewReid - 19-Jul-2011
 
Added:
>
>
 
META FILEATTACHMENT attachment="VeloPixelDoc.pdf" attr="" comment="Full documentation on VeloPix implementation" date="1255437777" name="VeloPixelDoc.pdf" path="VeloPixelDoc.pdf" size="1121697" stream="VeloPixelDoc.pdf" tmpFilename="/usr/tmp/CGItemp11489" user="coco_40lapp_2ein2p3_2efr" version="2"
META FILEATTACHMENT attachment="VeloPixSettings.py.txt" attr="" comment="" date="1260186232" name="VeloPixSettings.py.txt" path="VeloPixSettings.py" size="280" stream="VeloPixSettings.py" tmpFilename="/usr/tmp/CGItemp52273" user="coco_40lapp_2ein2p3_2efr" version="1"
META FILEATTACHMENT attachment="VeloPixBooleOpts.py.txt" attr="h" comment="Option file to run VeloPix algorithms with Boole" date="1264505360" name="VeloPixBooleOpts.py.txt" path="VeloPixBoole.py.txt" size="906" stream="VeloPixBoole.py.txt" tmpFilename="/usr/tmp/CGItemp44979" user="kuchar" version="2"
META FILEATTACHMENT attachment="VeloPixBoole.py.txt" attr="" comment="Option file to run VeloPix algorithms with Boole" date="1264505464" name="VeloPixBoole.py.txt" path="VeloPixBoole.py.txt" size="906" stream="VeloPixBoole.py.txt" tmpFilename="/usr/tmp/CGItemp40816" user="kuchar" version="1"
Added:
>
>
META FILEATTACHMENT attachment="myPanoramix-upgrade-dddb.py.txt" attr="" comment="python script for running Panoramix usin velopix geometry" date="1311093447" name="myPanoramix-upgrade-dddb.py.txt" path="myPanoramix-upgrade-dddb.py" size="18565" stream="myPanoramix-upgrade-dddb.py" tmpFilename="/usr/tmp/CGItemp26478" user="43eef574ab40e184e35d" version="1"

Revision 212010-09-27 - unknown

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

VeloPix in LHCb simulations

Line: 133 to 133
 

VeloPix in Brunel

Set Brunel Environment

Changed:
<
<
For the time being, there is no released version of Brunel compatible with VeloPix. Nonetheless most of the packages needed to have VeloPix tracking enabled are already commited and can be used from lhcb-head slot of the nightlies.

To set lhcb-head environment (add --build-env the first time)

SetupProject Brunel HEAD --nightly lhcb-head

Temporary hack of the Configurables

The solution for maintaining upgrade configurables without interfering with is not yet implemented some private hack of the Brunel configurable and TrackSys configurable is needed. Getpacking those two package is needed:
>
>
Brunel v is the first Brunel release fully compatible with VeloPix. You can use every version posterior to it but also work with the nightlies:
 
Changed:
<
<
getpack Tf/TrackSys head getpack Rec/Brunel head
>
>
SetupProject Brunel HEAD --nightly lhcb-head (add --build-env to create the environment the first time)
 
Changed:
<
<
in Rec/Brunel/python/Configuration.py, replace
KnownOutputTypes = [ "NONE", "DST", "RDST", "XDST" ]   
by
KnownOutputTypes = [ "NONE", "DST", "RDST", "XDST", "VELOPIXDST" ]
>
>

Brunel option files

In order to run Brunel with VeloPix, one need to specify the "Upgrade" datatype as well as the fact one want to use VeloPix instead of Velo. Option file should contains:
 
Deleted:
<
<
and add in the defineOptions function, in the "if withMC:" test, the following case:
 
Changed:
<
<
if outputType == "VELOPIXDST": outputType = "RDST" These modifications will soon disappear, but they are for the moment needed to avoid problem when writing the dsts. in Tf/TrackSys/python/Configuration.py, replace in the end of the file:
importOptions( "$TRACKSYSROOT/options/RecoTracking.py" )
if self.getProp("WithMC"):
   importOptions("$TRACKSYSROOT/options/PatChecking.py")
by
importOptions( "$RECOUPGRADEROOT/options/RecoTrackingUpgrade.py" )
if self.getProp("WithMC"):
   importOptions("$RECOUPGRADEROOT/options/PatCheckingUpgrade.py")
>
>
RecSysConf().RecoSequence = ["Decoding", "VELOPIX","TT","IT","OT","Tr","Vertex","RICH","CALO","MUON","PROTO"]
 
Added:
>
>
Make sure that the correct tag are used for the database (see....). First tag compatible with Brunel is velopix-20100909
 

Configure and run Brunel with VeloPix

An example of option file to run the VeloPix in Brunel is given in Rec/RecoUpgrade/options/Brunel_UpgradeVeloPix.py.
Line: 201 to 172
  IMPORTANT: since for the time beuing the Configurables are not finalised, some of the nominal settings of the sequence (forward tracking, MUON, etc...) are not yet available. This work is in progress...
Added:
>
>

TODO list for VeloPix in Brunel

Reconstruction

VeloPix Monitoring

Track Monitoring

 -- VictorCoco - 21-Apr-2010

Revision 202010-04-21 - unknown

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

VeloPix in LHCb simulations

Line: 132 to 132
 

VeloPix in Brunel

Added:
>
>

Set Brunel Environment

 For the time being, there is no released version of Brunel compatible with VeloPix. Nonetheless most of the packages needed to have VeloPix tracking enabled are already commited and can be used from lhcb-head slot of the nightlies.

To set lhcb-head environment (add --build-env the first time)

Line: 139 to 140
 SetupProject Brunel HEAD --nightly lhcb-head
Changed:
<
<
then since the solution for maintaining upgrade configurables without interfering with is not yet implemented some private hack of the Brunel configurable and TrackSys configurable is needed. Getpacking those two package is needed:
>
>

Temporary hack of the Configurables

The solution for maintaining upgrade configurables without interfering with is not yet implemented some private hack of the Brunel configurable and TrackSys configurable is needed. Getpacking those two package is needed:
 
getpack Tf/TrackSys head
Line: 161 to 163
  if outputType == "VELOPIXDST": outputType = "RDST"
Deleted:
<
<
 These modifications will soon disappear, but they are for the moment needed to avoid problem when writing the dsts.
Added:
>
>
in Tf/TrackSys/python/Configuration.py, replace in the end of the file:
importOptions( "$TRACKSYSROOT/options/RecoTracking.py" )
if self.getProp("WithMC"):
   importOptions("$TRACKSYSROOT/options/PatChecking.py")
by
importOptions( "$RECOUPGRADEROOT/options/RecoTrackingUpgrade.py" )
if self.getProp("WithMC"):
   importOptions("$RECOUPGRADEROOT/options/PatCheckingUpgrade.py")
 
Changed:
<
<
in Tf/TrackSys/python/Configuration.py, replace
>
>

Configure and run Brunel with VeloPix

An example of option file to run the VeloPix in Brunel is given in Rec/RecoUpgrade/options/Brunel_UpgradeVeloPix.py.
 
Added:
>
>
The key points are to specify that VeloPix have to be used in pattern recognition
TrackSys().TrackPatRecAlgorithms = ["VeloPix"]
and that the reconstruction sequence take the VeloPix into account:
RecSysConf().RecoSequence = ["Decoding", "VELOPIX","TT","IT","OT","Tr","Vertex","RICH","CALO","PROTO"]
Note that MUON have been removed because it's sequence call the nominal Velo. This have to be fixed at one point. Finally the output type and database should be specified:
 
Added:
>
>
Brunel().OutputType = "VELOPIXDST"   
from Configurables import LHCbApp
LHCbApp().DDDBtag   = "velopix-mul-20091116"
LHCbApp().CondDBtag = "sim-20091112-vc-md100"
 
Added:
>
>
IMPORTANT: since for the time beuing the Configurables are not finalised, some of the nominal settings of the sequence (forward tracking, MUON, etc...) are not yet available. This work is in progress...
 
Changed:
<
<
-- VictorCoco - 13-Apr-2010
>
>
-- VictorCoco - 21-Apr-2010
 

META FILEATTACHMENT attachment="VeloPixelDoc.pdf" attr="" comment="Full documentation on VeloPix implementation" date="1255437777" name="VeloPixelDoc.pdf" path="VeloPixelDoc.pdf" size="1121697" stream="VeloPixelDoc.pdf" tmpFilename="/usr/tmp/CGItemp11489" user="coco_40lapp_2ein2p3_2efr" version="2"

Revision 192010-04-20 - unknown

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

VeloPix in LHCb simulations

Line: 132 to 132
 

VeloPix in Brunel

Changed:
<
<

Install Brunel with VeloPix

First set your environment. For development we work with Brunel HEAD in the lhcb-head nigtly:
>
>
For the time being, there is no released version of Brunel compatible with VeloPix. Nonetheless most of the packages needed to have VeloPix tracking enabled are already commited and can be used from lhcb-head slot of the nightlies.

To set lhcb-head environment (add --build-env the first time)

SetupProject Brunel HEAD --nightly lhcb-head

then since the solution for maintaining upgrade configurables without interfering with is not yet implemented some private hack of the Brunel configurable and TrackSys configurable is needed. Getpacking those two package is needed:

getpack Tf/TrackSys head
getpack Rec/Brunel head

in Rec/Brunel/python/Configuration.py, replace

KnownOutputTypes = [ "NONE", "DST", "RDST", "XDST" ]   
by
KnownOutputTypes = [ "NONE", "DST", "RDST", "XDST", "VELOPIXDST" ]

and add in the defineOptions function, in the "if withMC:" test, the following case:

 
Changed:
<
<
SetupProject Brunel HEAD --nightly lhcb-head --build-env
>
>
if outputType == "VELOPIXDST": outputType = "RDST"
 
Deleted:
<
<
Then getpack the necessary package
 
Changed:
<
<
(under developpment)
>
>
These modifications will soon disappear, but they are for the moment needed to avoid problem when writing the dsts.

in Tf/TrackSys/python/Configuration.py, replace

 

Revision 182010-04-13 - unknown

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

VeloPix in LHCb simulations

Line: 132 to 132
 

VeloPix in Brunel

Changed:
<
<
not yet implemented
>
>

Install Brunel with VeloPix

First set your environment. For development we work with Brunel HEAD in the lhcb-head nigtly:
SetupProject Brunel HEAD --nightly lhcb-head --build-env
Then getpack the necessary package

(under developpment)

 
Changed:
<
<
-- MarcinKucharczyk - 26-Jan-2010
>
>
-- VictorCoco - 13-Apr-2010
 

META FILEATTACHMENT attachment="VeloPixelDoc.pdf" attr="" comment="Full documentation on VeloPix implementation" date="1255437777" name="VeloPixelDoc.pdf" path="VeloPixelDoc.pdf" size="1121697" stream="VeloPixelDoc.pdf" tmpFilename="/usr/tmp/CGItemp11489" user="coco_40lapp_2ein2p3_2efr" version="2"

Revision 172010-01-26 - MarcinKucharczyk

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

VeloPix in LHCb simulations

Line: 80 to 80
 Now when Gauss will call the Upgrade database at $SQLITEDBPATH/DDDB_upgrade.db/DDDB it will see your private VeloPix-friendly database as default. Don't forget to adapt the DDDBtag to the tag present in your private database, as explained on the next section. Usually the tag to use is "HEAD", unless you explicitly specified another one.

VeloPix in Boole

Changed:
<
<
The package for digitization and clusterization (VeloPixAlgorithms) as well as package with linkers to MC hits and MC particles (VeloPixAssociators) will be in the forecoming official Boole release. For now you have to use HEAD version of Boole (for example nightlies lhcb3) where you have to getpack head versions of several packages (see detail instructions below).
>
>
The package for digitization and clusterization (VeloPix/VeloPixAlgorithms) as well as the package with linkers from clusters and digits to MC hits and MC particles (VeloPix/VeloPixAssociators) you may find in the Boole release v20r1 or higher. The package for preparing Raw Data with pixel Velo as well as decoding VeloPix clusters at the level of Brunel (VeloPix/VeloPixDAQ) you may find in the Lbcom release v8r0 or higher. Since VeloPix/VeloPixDAQ package is located in the Lbcom, the algorithms from this package are automatically taken by Boole or Brunel, if these algorithms are added to the Boole/Brunel VeloPix sequences in Configuration.py (they are already added to the Boole VeloPix sequence).
 

Set Boole Environment

Changed:
<
<
As has been said the VeloPix algorithms are not yet in the official Boole release, thus you have to first SetupProject as it is described on the LHCb nightless web page. For example you may use:
>
>
In order to set Boole environment, you have to choose Boole version (v20r1 or higher), e.g.:
 
Changed:
<
<
SetupProject Boole HEAD --build-env --nightly lhcb3 getpack Digi/Boole head
>
>
setenvBoole v20r1
 
Changed:
<
<
or if you are working already with the nightlies:
>
>
Then you have to getpack Boole, i.e.:
 
Changed:
<
<
SetupProject Boole HEAD --nightly lhcb3
>
>
getpack Digi/Boole v20r1
 

Configure and run Boole with VeloPix

Changed:
<
<
To run Boole with VeloPix, you need first to getpack the head versions of VeloPixAlgorithms and VeloPixAssociators as well as the head version of GaudiConf (you should compile all of them after getpacking):
>
>
To run Boole with VeloPix, you need to create an option file, let say $YOURPATH/VeloPixBoole.py, where the L0 is switched off and VeloPix algorithms are taken instead of present Velo. Then you may run Boole:
 
Changed:
<
<
getpack VeloPix/VeloPixAlgorithms head getpack VeloPix/VeloPixAssociators head getpack GaudiConf head getpack BooleSys head (if working under Boole v20r0) getpack Kernel/LHCbKernel head (if working under Boole v20r0) Then create an option file, let say $YOURPATH/VeloPixBooleOpts.py. Then you will be able to run Boole:
gaudirun.py $BOOLEROOT/options/Boole-Default.py  $YOURPATH/VeloPixBooleOpts.py
>
>
gaudirun.py $BOOLEROOT/options/Boole-Default.py $YOURPATH/VeloPixBoole.py
 
Changed:
<
<
The contents of VeloPixBooleOpts.py in detail:
>
>
The contents of VeloPixBoole.py in detail:
  To specify the tag of database to use, one needs the following lines (see also VeloPix in Gauss).
Line: 135 to 126
  and specify the input sim file which should be generated using Gauss with VeloPix geometry (see VeloPix in Gauss).
Added:
>
>
To produce the digi output file, you have to specify its type and destination, as it is done in the last line of of VeloPixBoole.py.
 In the case of any problems please contact MarcinKucharczyk
Line: 142 to 135
 not yet implemented
Changed:
<
<
-- MarcinKucharczyk - 16-Dec-2009
>
>
-- MarcinKucharczyk - 26-Jan-2010
 

META FILEATTACHMENT attachment="VeloPixelDoc.pdf" attr="" comment="Full documentation on VeloPix implementation" date="1255437777" name="VeloPixelDoc.pdf" path="VeloPixelDoc.pdf" size="1121697" stream="VeloPixelDoc.pdf" tmpFilename="/usr/tmp/CGItemp11489" user="coco_40lapp_2ein2p3_2efr" version="2"
META FILEATTACHMENT attachment="VeloPixSettings.py.txt" attr="" comment="" date="1260186232" name="VeloPixSettings.py.txt" path="VeloPixSettings.py" size="280" stream="VeloPixSettings.py" tmpFilename="/usr/tmp/CGItemp52273" user="coco_40lapp_2ein2p3_2efr" version="1"
Changed:
<
<
META FILEATTACHMENT attachment="VeloPixBooleOpts.py.txt" attr="" comment="Opts for VeloPix in Boole" date="1260983679" name="VeloPixBooleOpts.py.txt" path="VeloPixBooleOpts.py" size="772" stream="VeloPixBooleOpts.py" tmpFilename="/usr/tmp/CGItemp18551" user="kuchar" version="1"
>
>
META FILEATTACHMENT attachment="VeloPixBooleOpts.py.txt" attr="h" comment="Option file to run VeloPix algorithms with Boole" date="1264505360" name="VeloPixBooleOpts.py.txt" path="VeloPixBoole.py.txt" size="906" stream="VeloPixBoole.py.txt" tmpFilename="/usr/tmp/CGItemp44979" user="kuchar" version="2"
META FILEATTACHMENT attachment="VeloPixBoole.py.txt" attr="" comment="Option file to run VeloPix algorithms with Boole" date="1264505464" name="VeloPixBoole.py.txt" path="VeloPixBoole.py.txt" size="906" stream="VeloPixBoole.py.txt" tmpFilename="/usr/tmp/CGItemp40816" user="kuchar" version="1"

Revision 162009-12-26 - unknown

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

VeloPix in LHCb simulations

Line: 85 to 85
 

Set Boole Environment

As has been said the VeloPix algorithms are not yet in the official Boole release, thus you have to first SetupProject as it is described on the LHCb nightless web page. For example you may use:
Changed:
<
<
SetupProject Boole HEAD --build-env --nightly lhcb3 Mon
>
>
SetupProject Boole HEAD --build-env --nightly lhcb3
 getpack Digi/Boole head or if you are working already with the nightlies:
Changed:
<
<
SetupProject Boole HEAD --nightly lhcb3 Mon
>
>
SetupProject Boole HEAD --nightly lhcb3
 

Configure and run Boole with VeloPix

Line: 99 to 99
 getpack VeloPix/VeloPixAlgorithms head getpack VeloPix/VeloPixAssociators head getpack GaudiConf head
Added:
>
>
getpack BooleSys head (if working under Boole v20r0) getpack Kernel/LHCbKernel head (if working under Boole v20r0)
  Then create an option file, let say $YOURPATH/VeloPixBooleOpts.py. Then you will be able to run Boole:

Revision 152009-12-16 - MarcinKucharczyk

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

VeloPix in LHCb simulations

Line: 7 to 7
 First Gauss implementation was presented by Victor Coco at VELO upgrade meeting on Sept. 15, 2009.
Added:
>
>
First Boole implementation was presented by Marcin Kucharczyk at VELO upgrade meeting on Nov 24, 2009.
 This page aims to be a recipe for using already implemented VeloPix solutions in the LHCb simulations. For those who might want to implement a new type of pixel sensors, modify the positions of modules, improve the already implemented solutions, etc. , a full description of the VeloPix implementation can be found in generic VeloPix description documentation. We will concentrate here on the different steps to follow to get VeloPix set up and used by LHCb simulations.
Line: 77 to 80
 Now when Gauss will call the Upgrade database at $SQLITEDBPATH/DDDB_upgrade.db/DDDB it will see your private VeloPix-friendly database as default. Don't forget to adapt the DDDBtag to the tag present in your private database, as explained on the next section. Usually the tag to use is "HEAD", unless you explicitly specified another one.

VeloPix in Boole

Changed:
<
<
implementation in progress
>
>
The package for digitization and clusterization (VeloPixAlgorithms) as well as package with linkers to MC hits and MC particles (VeloPixAssociators) will be in the forecoming official Boole release. For now you have to use HEAD version of Boole (for example nightlies lhcb3) where you have to getpack head versions of several packages (see detail instructions below).

Set Boole Environment

As has been said the VeloPix algorithms are not yet in the official Boole release, thus you have to first SetupProject as it is described on the LHCb nightless web page. For example you may use:
SetupProject Boole HEAD --build-env --nightly lhcb3 Mon
getpack Digi/Boole head
or if you are working already with the nightlies:
SetupProject Boole HEAD --nightly lhcb3 Mon

Configure and run Boole with VeloPix

To run Boole with VeloPix, you need first to getpack the head versions of VeloPixAlgorithms and VeloPixAssociators as well as the head version of GaudiConf (you should compile all of them after getpacking):
getpack VeloPix/VeloPixAlgorithms head
getpack VeloPix/VeloPixAssociators head
getpack GaudiConf head
Then create an option file, let say $YOURPATH/VeloPixBooleOpts.py. Then you will be able to run Boole:
gaudirun.py $BOOLEROOT/options/Boole-Default.py  $YOURPATH/VeloPixBooleOpts.py

The contents of VeloPixBooleOpts.py in detail:

To specify the tag of database to use, one needs the following lines (see also VeloPix in Gauss).

LHCbApp().DataType  = "Upgrade"
LHCbApp().DDDBtag   = "velopix-mul-20091116"
LHCbApp().CondDBtag = "sim-20091112-vc-md100"

Then you have to specify that you want to use VeloPix instead of Velo and you have to switch the L0 off:

theApp.DetectorDigi["VELO"]=['VeloPix']
theApp.DetectorDigi["L0"]=[]
theApp.DetectorLink["VELO"]=['VeloPix']
theApp.DetectorLink["L0"]=[]
theApp.DetectorLink["TR"]=[]
theApp.DetectorMoni["VELO"]=['VeloPix']
theApp.DetectorMoni["L0"]=[]

Next step is to choose the spillover:

theApp.UseSpillover = True
DigiConf().SpilloverPaths = ["Prev","PrevPrev","Next"]
and specify the input sim file which should be generated using Gauss with VeloPix geometry (see VeloPix in Gauss).

In the case of any problems please contact MarcinKucharczyk

 

VeloPix in Brunel

not yet implemented
Changed:
<
<
-- VictorCoco - 13-Oct-2009
>
>
-- MarcinKucharczyk - 16-Dec-2009
 

META FILEATTACHMENT attachment="VeloPixelDoc.pdf" attr="" comment="Full documentation on VeloPix implementation" date="1255437777" name="VeloPixelDoc.pdf" path="VeloPixelDoc.pdf" size="1121697" stream="VeloPixelDoc.pdf" tmpFilename="/usr/tmp/CGItemp11489" user="coco_40lapp_2ein2p3_2efr" version="2"
META FILEATTACHMENT attachment="VeloPixSettings.py.txt" attr="" comment="" date="1260186232" name="VeloPixSettings.py.txt" path="VeloPixSettings.py" size="280" stream="VeloPixSettings.py" tmpFilename="/usr/tmp/CGItemp52273" user="coco_40lapp_2ein2p3_2efr" version="1"
Added:
>
>
META FILEATTACHMENT attachment="VeloPixBooleOpts.py.txt" attr="" comment="Opts for VeloPix in Boole" date="1260983679" name="VeloPixBooleOpts.py.txt" path="VeloPixBooleOpts.py" size="772" stream="VeloPixBooleOpts.py" tmpFilename="/usr/tmp/CGItemp18551" user="kuchar" version="1"

Revision 142009-12-16 - unknown

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

VeloPix in LHCb simulations

Line: 20 to 20
 

Set Gauss Environment

If you don't have Gauss environment already set, let's choose a version. Here we take v38r0p1but latest is usually the best choice:
Deleted:
<
<
SetupProject Gauss v38r0p1 --build-env
 SetupProject Gauss v38r0p1

Revision 132009-12-07 - unknown

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

VeloPix in LHCb simulations

Line: 13 to 13
 
Deleted:
<
<

Get VeloPix recognize by the LHCb simulations

 
Changed:
<
<
THIS STEP IS NOT NEEDED AS SOON AS YOUR APLICATION RUNS ON LHCb v28r1 OR HIGHER
>
>

VeloPix in Gauss

The following instructions are given for Gauss v38r0p1 or higher. VeloPix is not supported on older version.
 
Changed:
<
<
To get VeloPix recognize by the LHCb simulations one needs to get the corresponding detector element, LHCbID and a detector description database containing a implementation of VeloPix. A new channel ID for VeloPix have been added to Kernel/LHCbKernel. One can getpack its head version:
getpack Kernel/LHCbKernel
cd Kernel/LHCbKernel/cmt
source setup.csh
gmake
Detector element is described in Det/VeloPixDet. One can getpack its head version:
>
>

Set Gauss Environment

If you don't have Gauss environment already set, let's choose a version. Here we take v38r0p1but latest is usually the best choice:
 
Changed:
<
<
getpack Det/VeloPixDet cd Det/VeloPixDet/cmt source setup.csh gmake
>
>
SetupProject Gauss v38r0p1 --build-env SetupProject Gauss v38r0p1
 
Deleted:
<
<
Those two package are common to all LHCb applications. Specific instruction for Gauss, Boole and Brunel follows.
 
Changed:
<
<

VeloPix in Gauss

The following instructions are given for Gauss v38r0 or higher. VeloPix is not supported on older version.
>
>

Configure and run Gauss for VeloPix simulations

In order to specify to Gauss that you want to run on VeloPix, you will need to create an option file, say $YOURPATH/VeloPixSettings.py. Then you will be able to run Gauss:
 
Deleted:
<
<

Get Gauss

If you don't have Gauss already, let's choose a version (latest is usually the best choice):
 
Changed:
<
<
setenv G_VERSION v38r0p1 Then let's go through the usual steps:
SetupProject Gauss $G_VERSION --build-env 
getpack Sim/Gauss $G_VERSION
cd Sim/Gauss/cmt
SetupProject Gauss $G_VERSION
source setup.csh
gmake
>
>
gaudirun.py $GAUSSROOT/options/Gauss-Upgrade.py $YOURPATH/VeloPixSettings.py $GAUSSROOT/options/Gauss-Job.py
 
Changed:
<
<

If you are using Gauss v38r0

The Gauss configurable in v38r0 does not fully support VeloPix. Best is to go to v38r0p1 that contains the correct patch. If for some reason you want to keep v38r0, please do
SetupProject Gauss  v38r0 --build-env 
getpack Sim/Gauss cocov_20091203
cd Sim/Gauss/cmt
SetupProject Gauss  v38r0
source setup.csh
gmake

Configure and run Gauss for VeloPix simulations

In order to specify Gauss that you want to run on VeloPix, you will need to create an option file, say $YOURPATH/VeloPixSettings.py, containing settings of the DDDB to take into account and of the Detector to simulate (by default it is present Velo of course).
>
>
Let's detail the contents of VeloPixSettings.py:
 
Changed:
<
<
To specify the tag of database to use, you need to include the following line.
>
>
To specify the tag of database to use, one needs the following lines.
 
from Configurables import LHCbApp
LHCbApp().DDDBtag   = "velopix-mul-20091116"
Line: 73 to 42
  "velopix-mul-20091116" is for the moment the only available official VeloPix tag. Of course if you are running on a private VeloPix geometry, you need to specify your own tag, see previous section.
Changed:
<
<
The to specify that you want to use VeloPix as vertex locator instead of the traditionnal Velo+!PuVeto, you need to replace the "VELO" field of the list of detector of which geometry is described as well as to the list of detector you want to simulate and monitor. That is done through the Gauss configurable by adding to your $YOURPATH/VeloPixSettings.py the lines:
>
>
To specify that one want to use VeloPix as vertex locator instead of the traditionnal Velo+!PuVeto, one need to replace the "VELO" field of the list of detector of which geometry is described as well as to the list of detectors one want to simulate and monitor. That is done through the Gauss configurable by adding to your $YOURPATH/VeloPixSettings.py the lines:
 
from Gauss.Configuration import *
Line: 82 to 51
 Gauss().DetectorGeo["VELO"]=['VeloPix']
Deleted:
<
<
You can now run Gauss:
gaudirun.py $GAUSSROOT/options/Gauss-Upgrade.py $YOURPATH/VeloPixSettings.py $GAUSSROOT/options/Gauss-Job.py
 For more details on the Gauss configuration for upgrade simulations please refer to this page.

Specify to Gauss a private DDDB with modified VeloPix

Line: 122 to 86
  -- VictorCoco - 13-Oct-2009
Added:
>
>
 
META FILEATTACHMENT attachment="VeloPixelDoc.pdf" attr="" comment="Full documentation on VeloPix implementation" date="1255437777" name="VeloPixelDoc.pdf" path="VeloPixelDoc.pdf" size="1121697" stream="VeloPixelDoc.pdf" tmpFilename="/usr/tmp/CGItemp11489" user="coco_40lapp_2ein2p3_2efr" version="2"
Changed:
<
<
META FILEATTACHMENT attachment="Configuration.py.txt" attr="" comment="" date="1255437019" name="Configuration.py.txt" path="Configuration.py" size="57603" stream="Configuration.py" tmpFilename="/usr/tmp/CGItemp7945" user="coco_40lapp_2ein2p3_2efr" version="1"
>
>
META FILEATTACHMENT attachment="VeloPixSettings.py.txt" attr="" comment="" date="1260186232" name="VeloPixSettings.py.txt" path="VeloPixSettings.py" size="280" stream="VeloPixSettings.py" tmpFilename="/usr/tmp/CGItemp52273" user="coco_40lapp_2ein2p3_2efr" version="1"

Revision 122009-12-07 - unknown

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

VeloPix in LHCb simulations

Line: 8 to 8
 VELO upgrade meeting on Sept. 15, 2009.

This page aims to be a recipe for using already implemented VeloPix solutions in the LHCb simulations. For those who might want to implement a new type of pixel sensors, modify the positions of modules, improve the already implemented solutions, etc. , a full description of the VeloPix implementation can be found in generic VeloPix description documentation.

Changed:
<
<
We will concentrate here on the different steps to follow to get VeloPix set up and used by LHCb simulations. Most of the package are under CVS but the releases that includes them by default are still to be announced (probably Gauss v38r0, LHCb v28r1).
>
>
We will concentrate here on the different steps to follow to get VeloPix set up and used by LHCb simulations.
 
Line: 12 to 12
 
Added:
>
>
 

Get VeloPix recognize by the LHCb simulations

Added:
>
>
THIS STEP IS NOT NEEDED AS SOON AS YOUR APLICATION RUNS ON LHCb v28r1 OR HIGHER
 To get VeloPix recognize by the LHCb simulations one needs to get the corresponding detector element, LHCbID and a detector description database containing a implementation of VeloPix. A new channel ID for VeloPix have been added to Kernel/LHCbKernel. One can getpack its head version:
Line: 31 to 35
 Those two package are common to all LHCb applications. Specific instruction for Gauss, Boole and Brunel follows.

VeloPix in Gauss

Changed:
<
<
Most of the following will be simplified as soon as post-MC09 version of Gauss will be released. It will already contains the VeloPix specific dependencies and configuration files. For the moment, one needs to getpack the good packages, get the DDDB containing a VeloPix description and configure Gauss to use the correct database and simulate VeloPix. Those steps are described in the following.
>
>
The following instructions are given for Gauss v38r0 or higher. VeloPix is not supported on older version.
 
Changed:
<
<

Get Gauss packages for VeloPix

If you don't have Gauss already, set up the environment for the last Gauss version and then getpack Gauss.
>
>

Get Gauss

If you don't have Gauss already, let's choose a version (latest is usually the best choice):
 
Changed:
<
<
SetupProject Gauss --build-env getpack Sim/Gauss
>
>
setenv G_VERSION v38r0p1 Then let's go through the usual steps:
SetupProject Gauss $G_VERSION --build-env 
getpack Sim/Gauss $G_VERSION
 cd Sim/Gauss/cmt
Added:
>
>
SetupProject Gauss $G_VERSION
 source setup.csh gmake
Changed:
<
<
First of all check if your Gauss version already contains VeloPix by default.
cmt show uses | grep VeloPixDet
cmt show uses | grep GaussUMC
should return something otherwise you should get the detector element and channelID as described in previous section. Also getpack Sim/GaussUMC since it is needed by the VeloPix monitoring.
>
>

If you are using Gauss v38r0

The Gauss configurable in v38r0 does not fully support VeloPix. Best is to go to v38r0p1 that contains the correct patch. If for some reason you want to keep v38r0, please do
 
Changed:
<
<
getpack Sim/GaussUMC cd Sim/GaussUMC/cmt cmt config
>
>
SetupProject Gauss v38r0 --build-env getpack Sim/Gauss cocov_20091203 cd Sim/Gauss/cmt SetupProject Gauss v38r0
 source setup.csh gmake
Changed:
<
<
Make sure you add those lines in your Gauss requirement file (Sim/Gauss/cmt/requirements),
>
>

Configure and run Gauss for VeloPix simulations

In order to specify Gauss that you want to run on VeloPix, you will need to create an option file, say $YOURPATH/VeloPixSettings.py, containing settings of the DDDB to take into account and of the Detector to simulate (by default it is present Velo of course).

To specify the tag of database to use, you need to include the following line.

 
Changed:
<
<
use GaussUMC v* Sim use VeloPixDet v* Det
>
>
from Configurables import LHCbApp LHCbApp().DDDBtag = "velopix-mul-20091116" LHCbApp().CondDBtag = "sim-20091112-vc-md100"
 
Changed:
<
<
and rerun in Sim/Gauss/cmt
>
>
"velopix-mul-20091116" is for the moment the only available official VeloPix tag. Of course if you are running on a private VeloPix geometry, you need to specify your own tag, see previous section.

The to specify that you want to use VeloPix as vertex locator instead of the traditionnal Velo+!PuVeto, you need to replace the "VELO" field of the list of detector of which geometry is described as well as to the list of detector you want to simulate and monitor. That is done through the Gauss configurable by adding to your $YOURPATH/VeloPixSettings.py the lines:

 
Changed:
<
<
cmt config source setup.csh
>
>
from Gauss.Configuration import * Gauss().DetectorSim["VELO"]=['VeloPix'] Gauss().DetectorMoni["VELO"]=['VeloPix'] Gauss().DetectorGeo["VELO"]=['VeloPix']
 
Changed:
<
<
Now check again if the package are used.

Specify to Gauss a DDDB version containing VeloPix

The normal way to do will be to specify the tag and the path of the upgrade DDDB containing the VeloPix you want to use. Since for the moment this is not completely supported, we will cheat by changing the default path of the DDDB_upgrade.db to point on our VeloPix-friendly DDDB_upgrade.db (An example containing the Timepix Miniplane implementation can be found in /castor/cern.ch/user/c/cocov/DDDB_upgrade_TimePixMinPlane.db. You can copy it locally under ~/database/DDDB_upgrade.db ).
>
>
You can now run Gauss:
gaudirun.py $GAUSSROOT/options/Gauss-Upgrade.py $YOURPATH/VeloPixSettings.py $GAUSSROOT/options/Gauss-Job.py

For more details on the Gauss configuration for upgrade simulations please refer to this page.

Specify to Gauss a private DDDB with modified VeloPix

The normal way to do will be to specify the tag and the path of the upgrade DDDB containing the VeloPix you want to use. Since for the moment this is not completely supported, we will cheat by changing the default path of the DDDB_upgrade.db to point on your VeloPix-friendly DDDB_upgrade.db, located for example in ~/database/DDDB_upgrade_Private.db.
 First of all save the default DDDB location and then getpack the package Det/SQLDDDB
setenv OLD_SQLITEDBPATH $SQLITEDBPATH
Line: 84 to 108
 Delete the link corresponding to the default DDDB_upgrade.db and reorient it to your local VeloPix-friendly database.
cd $SQLITEDBPATH
Changed:
<
<
ln -s ~/database/DDDB_upgrade.db .
>
>
ln -s ~/database/DDDB_upgrade_Private.db DDDB_upgrade.db
  In the end compile the package.
Changed:
<
<
Now when Gauss will call the Upgrade database at $SQLITEDBPATH/DDDB_upgrade.db/DDDB it will see your private VeloPix-friendly database as default. Don't forget to adapt the DDDBtag to the tag present in your private database (is you copied DDDB_upgrade_TimePixMinPlane.db the tag to use is "HEAD"), see the foolowing.

Configuring Gauss for VeloPix simulations

In order to have VeloPix taken into account in the Gauss configuration, and if your version of Gauss does not allow to choose the sub-detector to be simulated via the dictionnaries DetectorSimDict and DetectorGeoDict you will need this Gauss configuration file in your Sim/Gauss/python/Gauss and recompile. It allows you to choose the detector to be used for geometry and those that will be simulated. For example if you want to use VeloPix as vertex locator and to simulate only the tracking system, but to keep the Rich1 and 2 for materials description, you will put in your python option file $YOURPATH/VeloPixSettings.py the following lines:
from Gauss.Configuration import *
Gauss().DataType = "Upgrade"
Gauss().DetectorSim["VELO"] =['VeloPix']
Gauss().DetectorGeo ["VELO"] =['VeloPix']
Gauss().DetectorMoni["VELO"] =['VeloPix']
If the DDDB that contains your VeloPix is not the default one, you need to specify the DDDB location and tags you want to use. For the moment one cannot change the location so you can use the hack described previously to have your private DDDB replacing the default DDDB_upgrade.db location. But you still need to psecify the DDDB tag (usually "HEAD" if it was not explicitly tagged) by specifying:
from Configurables import LHCbApp
LHCbApp().DDDBtag   = "HEAD"
You can now run Gauss:
gaudirun.py $GAUSSROOT/options/Gauss-Upgrade.py $YOURPATH/VeloPixSettings.py $GAUSSROOT/options/Gauss-Job.py
>
>
Now when Gauss will call the Upgrade database at $SQLITEDBPATH/DDDB_upgrade.db/DDDB it will see your private VeloPix-friendly database as default. Don't forget to adapt the DDDBtag to the tag present in your private database, as explained on the next section. Usually the tag to use is "HEAD", unless you explicitly specified another one.
 
Deleted:
<
<
For more details on the Gauss configuration for upgrade simulations please refer to this page.
 

VeloPix in Boole

implementation in progress

VeloPix in Brunel

Revision 112009-11-16 - unknown

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

VeloPix in LHCb simulations

Line: 95 to 95
 
from Gauss.Configuration import *
Gauss().DataType = "Upgrade"
Changed:
<
<
Gauss().DetectorSimDict ={"VELO":['VeloPix'], "TT":['TT'], "IT":['IT'], "OT":['OT'], "RICH":[], "CALO":[], "MUON":[],"MAGNET": True } Gauss().DetectorGeoDict = {"VELO":['VeloPix'], "TT":['TT'], "IT":['IT'], "OT":['OT'], "RICH":['Rich1','Rich2'], "CALO":[], "MUON":[],"MAGNET": True }
>
>
Gauss().DetectorSim["VELO"] =['VeloPix'] Gauss().DetectorGeo ["VELO"] =['VeloPix'] Gauss().DetectorMoni["VELO"] =['VeloPix']
  If the DDDB that contains your VeloPix is not the default one, you need to specify the DDDB location and tags you want to use. For the moment one cannot change the location so you can use the hack described previously to have your private DDDB replacing the default DDDB_upgrade.db location. But you still need to psecify the DDDB tag (usually "HEAD" if it was not explicitly tagged) by specifying:

Revision 102009-10-13 - unknown

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

VeloPix in LHCb simulations

Line: 7 to 7
 First Gauss implementation was presented by Victor Coco at VELO upgrade meeting on Sept. 15, 2009.
Changed:
<
<
This page aims to be a recipe for using already implemented VeloPix solutions in the LHCb simulations. For those who might want to implement a new type of pixel sensors, modify the positions of modules, improve the already implemented solutions, etc. , a full description of the VeloPix implementation can be found in generic VeloPix description documentation. We will concentrate here on the different steps to follow to get VeloPix set up and used by LHCb simulations. Most of the package are under CVS but the releases that includes them by default are still to be announced (probably Gauss v38r0, LHCb v28r1).
>
>
This page aims to be a recipe for using already implemented VeloPix solutions in the LHCb simulations. For those who might want to implement a new type of pixel sensors, modify the positions of modules, improve the already implemented solutions, etc. , a full description of the VeloPix implementation can be found in generic VeloPix description documentation. We will concentrate here on the different steps to follow to get VeloPix set up and used by LHCb simulations. Most of the package are under CVS but the releases that includes them by default are still to be announced (probably Gauss v38r0, LHCb v28r1).
 

Get VeloPix recognize by the LHCb simulations

Changed:
<
<
To get VeloPix recognize by the LHCb simulations one needs to get the corresponding detector element, LHCbID and a detector description database containing a implementation of VeloPix.
>
>
To get VeloPix recognize by the LHCb simulations one needs to get the corresponding detector element, LHCbID and a detector description database containing a implementation of VeloPix.
 A new channel ID for VeloPix have been added to Kernel/LHCbKernel. One can getpack its head version:
getpack Kernel/LHCbKernel
Line: 21 to 21
 source setup.csh gmake
Changed:
<
<
Detector element is described in Det/VeloPixDet. One can getpack its head version:
>
>
Detector element is described in Det/VeloPixDet. One can getpack its head version:
 
getpack Det/VeloPixDet 
cd Det/VeloPixDet/cmt
Line: 31 to 31
 Those two package are common to all LHCb applications. Specific instruction for Gauss, Boole and Brunel follows.

VeloPix in Gauss

Changed:
<
<
Most of the following will be simplified as soon as post-MC09 version of Gauss will be released. It will already contains the VeloPix specific dependencies and configuration files. For the moment, one needs to getpack the good packages, get the DDDB containing a VeloPix description and configure Gauss to use the correct database and simulate VeloPix. Those steps are described in the following.
>
>
Most of the following will be simplified as soon as post-MC09 version of Gauss will be released. It will already contains the VeloPix specific dependencies and configuration files. For the moment, one needs to getpack the good packages, get the DDDB containing a VeloPix description and configure Gauss to use the correct database and simulate VeloPix. Those steps are described in the following.
 

Get Gauss packages for VeloPix

If you don't have Gauss already, set up the environment for the last Gauss version and then getpack Gauss.
Line: 42 to 42
 source setup.csh gmake
Changed:
<
<
First of all check if your Gauss version already contains VeloPix by default.
>
>
First of all check if your Gauss version already contains VeloPix by default.
 
cmt show uses | grep VeloPixDet
cmt show uses | grep GaussUMC
Changed:
<
<
should return something otherwise you should get the detector element and channelID as described in previous section. Also getpack Sim/GaussUMC since it is needed by the VeloPix monitoring.
>
>
should return something otherwise you should get the detector element and channelID as described in previous section. Also getpack Sim/GaussUMC since it is needed by the VeloPix monitoring.
 
getpack Sim/GaussUMC
cd Sim/GaussUMC/cmt
Line: 66 to 66
 source setup.csh Now check again if the package are used.
Changed:
<
<

Specify to Gauss a DDDB version containing VeloPix

The normal way to do will be to specify the tag and the path of the upgrade DDDB containing the VeloPix you want to use. Since for the moment this is not completely supported, we will cheat by changing the default path of the DDDB_upgrade.db to point on our VeloPix-friendly DDDB_upgrade.db (An example containing the Timepix Miniplane implementation can be found in /castor/cern.ch/user/c/cocov/DDDB_upgrade_TimePixMinPlane.db. You can copy it locally under ~/database/DDDB_upgrade.db ).
>
>

Specify to Gauss a DDDB version containing VeloPix

The normal way to do will be to specify the tag and the path of the upgrade DDDB containing the VeloPix you want to use. Since for the moment this is not completely supported, we will cheat by changing the default path of the DDDB_upgrade.db to point on our VeloPix-friendly DDDB_upgrade.db (An example containing the Timepix Miniplane implementation can be found in /castor/cern.ch/user/c/cocov/DDDB_upgrade_TimePixMinPlane.db. You can copy it locally under ~/database/DDDB_upgrade.db ).
 First of all save the default DDDB location and then getpack the package Det/SQLDDDB
setenv OLD_SQLITEDBPATH $SQLITEDBPATH
Line: 81 to 81
 cd $SQLITEDBPATH ln -s $OLD_SQLITEDBPATH/*.db .
Changed:
<
<
Delete the link corresponding to the default DDDB_upgrade.db and reorient it to your local VeloPix-friendly database.
>
>
Delete the link corresponding to the default DDDB_upgrade.db and reorient it to your local VeloPix-friendly database.
 
cd $SQLITEDBPATH
ln -s ~/database/DDDB_upgrade.db .
In the end compile the package.
Changed:
<
<
Now when Gauss will call the Upgrade database at $SQLITEDBPATH/DDDB_upgrade.db/DDDB it will see your private VeloPix-friendly database as default. Don't forget to adapt the DDDBtag to the tag present in your private database (is you copied DDDB_upgrade_TimePixMinPlane.db the tag to use is "HEAD"), see the foolowing.

Configuring Gauss for VeloPix simulations

In order to have VeloPix taken into account in the Gauss configuration, and if your version of Gauss does not allow to choose the sub-detector to be simulated via the dictionnaries DetectorSimDict and DetectorGeoDict you will need this Gauss configuration file in your Sim/Gauss/python/Gauss and recompile. It allows you to choose the detector to be used for geometry and those that will be simulated. For example if you want to use VeloPix as vertex locator and to simulate only the tracking system, but to keep the Rich1 and 2 for materials description, you will put in your python option file $YOURPATH/VeloPixSettings.py the following lines:
>
>
Now when Gauss will call the Upgrade database at $SQLITEDBPATH/DDDB_upgrade.db/DDDB it will see your private VeloPix-friendly database as default. Don't forget to adapt the DDDBtag to the tag present in your private database (is you copied DDDB_upgrade_TimePixMinPlane.db the tag to use is "HEAD"), see the foolowing.

Configuring Gauss for VeloPix simulations

In order to have VeloPix taken into account in the Gauss configuration, and if your version of Gauss does not allow to choose the sub-detector to be simulated via the dictionnaries DetectorSimDict and DetectorGeoDict you will need this Gauss configuration file in your Sim/Gauss/python/Gauss and recompile. It allows you to choose the detector to be used for geometry and those that will be simulated. For example if you want to use VeloPix as vertex locator and to simulate only the tracking system, but to keep the Rich1 and 2 for materials description, you will put in your python option file $YOURPATH/VeloPixSettings.py the following lines:
 
from Gauss.Configuration import *
Gauss().DataType = "Upgrade"
Gauss().DetectorSimDict ={"VELO":['VeloPix'], "TT":['TT'], "IT":['IT'], "OT":['OT'], "RICH":[], "CALO":[], "MUON":[],"MAGNET": True }
Gauss().DetectorGeoDict = {"VELO":['VeloPix'], "TT":['TT'], "IT":['IT'], "OT":['OT'], "RICH":['Rich1','Rich2'], "CALO":[], "MUON":[],"MAGNET": True }
Changed:
<
<
If the DDDB that contains your VeloPix is not the default one, you need to specify the DDDB location and tags you want to use. For the moment one cannot change the location so you can use the hack described previously to have your private DDDB replacing the default DDDB_upgrade.db location. But you still need to psecify the DDDB tag (usually "HEAD" if it was not explicitly tagged) by specifying:
>
>
If the DDDB that contains your VeloPix is not the default one, you need to specify the DDDB location and tags you want to use. For the moment one cannot change the location so you can use the hack described previously to have your private DDDB replacing the default DDDB_upgrade.db location. But you still need to psecify the DDDB tag (usually "HEAD" if it was not explicitly tagged) by specifying:
 
from Configurables import LHCbApp
LHCbApp().DDDBtag   = "HEAD"

Revision 92009-10-13 - TomaszSkwarnicki

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

VeloPix in LHCb simulations

>
>

VeloPix in LHCb simulations

 
Changed:
<
<
This page aims to be a recipe for using already implemented VeloPix solutions in the LHCb simulations. For those who might want to implement a new type of pixel sensors, modify the positions of modules, improve the already implemented solutions, etc. , a full description of the VeloPix implementation can be found in generic VeloPix description documentation.
>
>
For the outline of this option see Paula Collins presentation at LHCb upgrade meeting on July 15, 2009.

First Gauss implementation was presented by Victor Coco at VELO upgrade meeting on Sept. 15, 2009.

This page aims to be a recipe for using already implemented VeloPix solutions in the LHCb simulations. For those who might want to implement a new type of pixel sensors, modify the positions of modules, improve the already implemented solutions, etc. , a full description of the VeloPix implementation can be found in generic VeloPix description documentation.

 We will concentrate here on the different steps to follow to get VeloPix set up and used by LHCb simulations. Most of the package are under CVS but the releases that includes them by default are still to be announced (probably Gauss v38r0, LHCb v28r1).

Changed:
<
<

Get VeloPix recognize by the LHCb simulations

To get VeloPix recognize by the LHCb simulations one needs to get the corresponding detector element, LHCbID and a detector description database containing a implementation of VeloPix. A new channel ID for VeloPix have been added to Kernel/LHCbKernel. One can getpack its head version:
>
>

Get VeloPix recognize by the LHCb simulations

To get VeloPix recognize by the LHCb simulations one needs to get the corresponding detector element, LHCbID and a detector description database containing a implementation of VeloPix. A new channel ID for VeloPix have been added to Kernel/LHCbKernel. One can getpack its head version:
 
getpack Kernel/LHCbKernel
cd Kernel/LHCbKernel/cmt
Line: 25 to 30
  Those two package are common to all LHCb applications. Specific instruction for Gauss, Boole and Brunel follows.
Changed:
<
<

VeloPix in Gauss

>
>

VeloPix in Gauss

 Most of the following will be simplified as soon as post-MC09 version of Gauss will be released. It will already contains the VeloPix specific dependencies and configuration files. For the moment, one needs to getpack the good packages, get the DDDB containing a VeloPix description and configure Gauss to use the correct database and simulate VeloPix. Those steps are described in the following.
Changed:
<
<

Get Gauss packages for VeloPix

>
>

Get Gauss packages for VeloPix

 If you don't have Gauss already, set up the environment for the last Gauss version and then getpack Gauss.
SetupProject Gauss --build-env 
Line: 104 to 109
 

For more details on the Gauss configuration for upgrade simulations please refer to this page.

Changed:
<
<

VeloPix in Boole

>
>

VeloPix in Boole

 implementation in progress
Changed:
<
<

VeloPix in Brunel

>
>

VeloPix in Brunel

 not yet implemented

Revision 82009-10-13 - unknown

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

VeloPix in LHCb simulations

Changed:
<
<
This page aims to be a recipe for using VeloPix geometries in the LHCb simulations. For those who might want to implement a new type of pixel sensors, modify the positions of modules, improve the already implemented solutions, etc. , a full description of the VeloPix implementation can be found in generic VeloPix description documentation.
>
>
This page aims to be a recipe for using already implemented VeloPix solutions in the LHCb simulations. For those who might want to implement a new type of pixel sensors, modify the positions of modules, improve the already implemented solutions, etc. , a full description of the VeloPix implementation can be found in generic VeloPix description documentation.
 We will concentrate here on the different steps to follow to get VeloPix set up and used by LHCb simulations. Most of the package are under CVS but the releases that includes them by default are still to be announced (probably Gauss v38r0, LHCb v28r1).

Line: 23 to 23
 source setup.csh gmake
Changed:
<
<
>
>
Those two package are common to all LHCb applications. Specific instruction for Gauss, Boole and Brunel follows.
 

VeloPix in Gauss

Most of the following will be simplified as soon as post-MC09 version of Gauss will be released. It will already contains the VeloPix specific dependencies and configuration files. For the moment, one needs to getpack the good packages, get the DDDB containing a VeloPix description and configure Gauss to use the correct database and simulate VeloPix. Those steps are described in the following.
Line: 37 to 37
 source setup.csh gmake
Changed:
<
<
First of all check if your Gauss version already contains VeloPix by default. Both
>
>
First of all check if your Gauss version already contains VeloPix by default.
 
cmt show uses | grep VeloPixDet
Deleted:
<
<
and
 cmt show uses | grep GaussUMC
Changed:
<
<
should return something. If those package are not already included then you should get the detector element and channelID as described in previous section. Also getpack Sim/GaussUMC since it is needed by the VeloPix monitoring.
>
>
should return something otherwise you should get the detector element and channelID as described in previous section. Also getpack Sim/GaussUMC since it is needed by the VeloPix monitoring.
 
getpack Sim/GaussUMC
cd Sim/GaussUMC/cmt
Line: 54 to 50
 source setup.csh gmake
Changed:
<
<
Make sure you add in your Gauss requirement file (Sim/Gauss/cmt/requirements)
>
>
Make sure you add those lines in your Gauss requirement file (Sim/Gauss/cmt/requirements),
 
use GaussUMC          v*    Sim 
use VeloPixDet        v*    Det
Deleted:
<
<
in your Gauss requirement file and rerun
 and rerun in Sim/Gauss/cmt
cmt config
source setup.csh
Changed:
<
<
now check again if the package are used.
>
>
Now check again if the package are used.
 

Specify to Gauss a DDDB version containing VeloPix

Changed:
<
<
The normal way to do will be to specify the tag and the path of the upgrade DDDB containing the VeloPix you want to use. Since for the moment this is not completly supported, we will cheat by changing the default path of the DDDB_upgrade.db to point on our VeloPix-friendly DDDB_upgrade.db (An example containing the Timepix Mniplane implementation can be found in /castor/cern.ch/user/c/cocov/DDDB_upgrade_TimePixMinPlane.db you can copy it locally in ~/database/) Save the default DDDB location and then getpack the package Det/SQLDDDB
>
>
The normal way to do will be to specify the tag and the path of the upgrade DDDB containing the VeloPix you want to use. Since for the moment this is not completely supported, we will cheat by changing the default path of the DDDB_upgrade.db to point on our VeloPix-friendly DDDB_upgrade.db (An example containing the Timepix Miniplane implementation can be found in /castor/cern.ch/user/c/cocov/DDDB_upgrade_TimePixMinPlane.db. You can copy it locally under ~/database/DDDB_upgrade.db ). First of all save the default DDDB location and then getpack the package Det/SQLDDDB
 
setenv OLD_SQLITEDBPATH $SQLITEDBPATH
getpack Det/SQLDDDB
Line: 76 to 71
 source setup.csh gmake
Changed:
<
<
then in Det/SQLDDDB/db create links to the database in default DDDB location
>
>
then in Det/SQLDDDB/db create links to the databases stroed in the default DDDB location (they are not copied to your Det/SQLDDDB/db folder since they are very heavy)
 
cd $SQLITEDBPATH
ln -s $OLD_SQLITEDBPATH/*.db .
Changed:
<
<
Delete the link corresponding to the default DDDB_upgrade.db and reorient it to your VeloPix friendly database
>
>
Delete the link corresponding to the default DDDB_upgrade.db and reorient it to your local VeloPix-friendly database.
 
cd $SQLITEDBPATH
ln -s ~/database/DDDB_upgrade.db .
In the end compile the package.
Changed:
<
<
Now when Gauss will call the Upgrade database at $SQLITEDBPATH/DDDB_upgrade.db/DDDB it will see your private VeoPix-friendly database.
>
>
Now when Gauss will call the Upgrade database at $SQLITEDBPATH/DDDB_upgrade.db/DDDB it will see your private VeloPix-friendly database as default. Don't forget to adapt the DDDBtag to the tag present in your private database (is you copied DDDB_upgrade_TimePixMinPlane.db the tag to use is "HEAD"), see the foolowing.
 

Configuring Gauss for VeloPix simulations

In order to have VeloPix taken into account in the Gauss configuration, and if your version of Gauss does not allow to choose the sub-detector to be simulated via the dictionnaries DetectorSimDict and DetectorGeoDict you will need this Gauss configuration file in your Sim/Gauss/python/Gauss and recompile.

Revision 72009-10-13 - unknown

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

VeloPix in LHCb simulations

Deleted:
<
<
This page is under constructions.
 This page aims to be a recipe for using VeloPix geometries in the LHCb simulations. For those who might want to implement a new type of pixel sensors, modify the positions of modules, improve the already implemented solutions, etc. , a full description of the VeloPix implementation can be found in generic VeloPix description documentation.
Changed:
<
<
We will concentrate here on the different step to follow to get VeloPix set up and used by LHCb simulations. Most of the package are under CVS but the release that includes them by default is still to be announced (probably Gauss v38r0, LHCb v28r1).
>
>
We will concentrate here on the different steps to follow to get VeloPix set up and used by LHCb simulations. Most of the package are under CVS but the releases that includes them by default are still to be announced (probably Gauss v38r0, LHCb v28r1).
 
Line: 29 to 26
 

VeloPix in Gauss

Changed:
<
<

Get Gauss with VeloPix

>
>
Most of the following will be simplified as soon as post-MC09 version of Gauss will be released. It will already contains the VeloPix specific dependencies and configuration files. For the moment, one needs to getpack the good packages, get the DDDB containing a VeloPix description and configure Gauss to use the correct database and simulate VeloPix. Those steps are described in the following.

Get Gauss packages for VeloPix

 If you don't have Gauss already, set up the environment for the last Gauss version and then getpack Gauss.
SetupProject Gauss --build-env 
Line: 70 to 65
 cmt config source setup.csh
Deleted:
<
<
 now check again if the package are used.
Changed:
<
<

Get a DDDB version containing VeloPix

The normal way to do will soon be to specify the tag of the upgrade DDDB containing the VeloPix you want to use. Since for the moment

>
>

Specify to Gauss a DDDB version containing VeloPix

The normal way to do will be to specify the tag and the path of the upgrade DDDB containing the VeloPix you want to use. Since for the moment this is not completly supported, we will cheat by changing the default path of the DDDB_upgrade.db to point on our VeloPix-friendly DDDB_upgrade.db (An example containing the Timepix Mniplane implementation can be found in /castor/cern.ch/user/c/cocov/DDDB_upgrade_TimePixMinPlane.db you can copy it locally in ~/database/) Save the default DDDB location and then getpack the package Det/SQLDDDB
setenv OLD_SQLITEDBPATH $SQLITEDBPATH
getpack Det/SQLDDDB
cd Det/SQLDDDB/cmt
source setup.csh
gmake
then in Det/SQLDDDB/db create links to the database in default DDDB location
cd $SQLITEDBPATH
ln -s $OLD_SQLITEDBPATH/*.db .
Delete the link corresponding to the default DDDB_upgrade.db and reorient it to your VeloPix friendly database
cd $SQLITEDBPATH
ln -s ~/database/DDDB_upgrade.db .
In the end compile the package. Now when Gauss will call the Upgrade database at $SQLITEDBPATH/DDDB_upgrade.db/DDDB it will see your private VeoPix-friendly database.
 

Configuring Gauss for VeloPix simulations

In order to have VeloPix taken into account in the Gauss configuration, and if your version of Gauss does not allow to choose the sub-detector to be simulated via the dictionnaries DetectorSimDict and
Changed:
<
<
DetectorGeoDict you will need this Gauss configuration file in your Sim/Gauss/python/Gauss. It allows you to choose the detector to be used for geometry and those that will be simulated. For example by putting in your python option file the lines:
>
>
DetectorGeoDict you will need this Gauss configuration file in your Sim/Gauss/python/Gauss and recompile. It allows you to choose the detector to be used for geometry and those that will be simulated. For example if you want to use VeloPix as vertex locator and to simulate only the tracking system, but to keep the Rich1 and 2 for materials description, you will put in your python option file $YOURPATH/VeloPixSettings.py the following lines:
 
from Gauss.Configuration import *
Gauss().DataType = "Upgrade"
Gauss().DetectorSimDict ={"VELO":['VeloPix'], "TT":['TT'], "IT":['IT'], "OT":['OT'], "RICH":[], "CALO":[], "MUON":[],"MAGNET": True }
Gauss().DetectorGeoDict = {"VELO":['VeloPix'], "TT":['TT'], "IT":['IT'], "OT":['OT'], "RICH":['Rich1','Rich2'], "CALO":[], "MUON":[],"MAGNET": True }
Added:
>
>
If the DDDB that contains your VeloPix is not the default one, you need to specify the DDDB location and tags you want to use. For the moment one cannot change the location so you can use the hack described previously to have your private DDDB replacing the default DDDB_upgrade.db location. But you still need to psecify the DDDB tag (usually "HEAD" if it was not explicitly tagged) by specifying:
from Configurables import LHCbApp
LHCbApp().DDDBtag   = "HEAD"
You can now run Gauss:
gaudirun.py $GAUSSROOT/options/Gauss-Upgrade.py $YOURPATH/VeloPixSettings.py $GAUSSROOT/options/Gauss-Job.py
 
Changed:
<
<
you will use VeloPix as vertex locator and you will only simulate the tracking system, but you will keep in the geometry description the Rich1 and 2 for having their materials taken into account.

Now, if the DDDBupgrade that containsd your VeloPix is not the default one, you need to specify the DDDBupgrade location and the tag you want by adding:

>
>
For more details on the Gauss configuration for upgrade simulations please refer to this page.
 

VeloPix in Boole

implementation in progress
Deleted:
<
<
 

VeloPix in Brunel

not yet implemented
Line: 102 to 115
 not yet implemented
Changed:
<
<
META FILEATTACHMENT attachment="VeloPixelDoc.pdf" attr="" comment="" date="1255418612" name="VeloPixelDoc.pdf" path="VeloPixelDoc.pdf" size="1121472" stream="VeloPixelDoc.pdf" tmpFilename="/usr/tmp/CGItemp8019" user="coco_40lapp_2ein2p3_2efr" version="1"
>
>

-- VictorCoco - 13-Oct-2009

META FILEATTACHMENT attachment="VeloPixelDoc.pdf" attr="" comment="Full documentation on VeloPix implementation" date="1255437777" name="VeloPixelDoc.pdf" path="VeloPixelDoc.pdf" size="1121697" stream="VeloPixelDoc.pdf" tmpFilename="/usr/tmp/CGItemp11489" user="coco_40lapp_2ein2p3_2efr" version="2"
META FILEATTACHMENT attachment="Configuration.py.txt" attr="" comment="" date="1255437019" name="Configuration.py.txt" path="Configuration.py" size="57603" stream="Configuration.py" tmpFilename="/usr/tmp/CGItemp7945" user="coco_40lapp_2ein2p3_2efr" version="1"

Revision 62009-10-13 - unknown

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

VeloPix implementation recipe

>
>

VeloPix in LHCb simulations

  This page is under constructions.
Changed:
<
<
This page aims to be a recipe for creating new VeloPix geometries in the DDDB. The full description of the VeloPix implementation can be found in generic VeloPix description document, while we will concentrate, as an example, on the specific implementation of Timepix Miniplane solution (see..) As mentionned on Sec.1 of generic VeloPix description, in order to define a VeloPix geometry one needs:
>
>
This page aims to be a recipe for using VeloPix geometries in the LHCb simulations. For those who might want to implement a new type of pixel sensors, modify the positions of modules, improve the already implemented solutions, etc. , a full description of the VeloPix implementation can be found in generic VeloPix description documentation. We will concentrate here on the different step to follow to get VeloPix set up and used by LHCb simulations. Most of the package are under CVS but the release that includes them by default is still to be announced (probably Gauss v38r0, LHCb v28r1).
 
Changed:
<
<

ladders definition

Timepix MiniPlane solution modules contains 5 ladders of two chips. The five ladders are similar except that, since the 3 central ladder form a single silicon piece, the guard ring disposition of these ladders are different. Therefore we define 4 types of ladders: * TIMEPIX_x2 is for the top and bottom ladders with guard ring all around the active part. * TIMEPIX_x2Central is for the central ladder. * TIMEPIX_x2CentralTop is for the ladder above the central one. * TIMEPIX_x2CentralBottom is for the ladder below the central one.

Common ladders parameters

Parameters that are common to all ladders can be found in VeloPix/GeomParam/VeloPixParameters_TIMEPIX_MINIPLANE.xml. The mandatory parameter for ladder creation are:

* for silicon sensor (see Sec.2.2.2 of generic VeloPix description):

>
>

Get VeloPix recognize by the LHCb simulations

To get VeloPix recognize by the LHCb simulations one needs to get the corresponding detector element, LHCbID and a detector description database containing a implementation of VeloPix. A new channel ID for VeloPix have been added to Kernel/LHCbKernel. One can getpack its head version:
 
Changed:
<
<
<!-- Silicon tickness                                       -->
<!-- Sensor active Area width                               -->
<!-- Sensor Guard ring width                                -->
>
>
getpack Kernel/LHCbKernel cd Kernel/LHCbKernel/cmt source setup.csh gmake
 
Changed:
<
<
* for the chips (see Sec.2.2.3 of generic VeloPix description)
>
>
Detector element is described in Det/VeloPixDet. One can getpack its head version:
 
    
Changed:
<
<
<!-- Chip 2 Chip distance                                   -->
<!-- Chip Dimensions                                        -->
>
>
getpack Det/VeloPixDet cd Det/VeloPixDet/cmt source setup.csh gmake
 
Deleted:
<
<
* for the chip support (see Sec.2.2.3 of generic VeloPix description)
 
Added:
>
>

VeloPix in Gauss

Get Gauss with VeloPix

If you don't have Gauss already, set up the environment for the last Gauss version and then getpack Gauss.
 
    
Changed:
<
<
<!-- Ticknesses of the different layers                            -->
<!-- Chips support dimension                                       -->
>
>
SetupProject Gauss --build-env getpack Sim/Gauss cd Sim/Gauss/cmt source setup.csh gmake
 
Changed:
<
<
* and for positionning of chips and chips support with respect to the active area (see Sec.2.2.4 of generic VeloPix description):
>
>
First of all check if your Gauss version already contains VeloPix by default. Both
 
    
Changed:
<
<
<!-- Position of the chips support wrt the active area  -->
LadderHDIExtraDistOut+LadderHDIExtraDistIn)/2-LadderHDIExtraDistIn"/> LadderHDIWidth-SensorSiWidth)/2" />
<!-- Position of the chips wrt the active area -->
LadderChipWidth-SensorSiWidth)/2" />
>
>
cmt show uses | grep VeloPixDet
 
Added:
>
>
and
cmt show uses | grep GaussUMC
should return something.
 
Added:
>
>
If those package are not already included then you should get the detector element and channelID as described in previous section. Also getpack Sim/GaussUMC since it is needed by the VeloPix monitoring.
getpack Sim/GaussUMC
cd Sim/GaussUMC/cmt
cmt config
source setup.csh
gmake
 
Added:
>
>
Make sure you add in your Gauss requirement file (Sim/Gauss/cmt/requirements)
use GaussUMC             v*    Sim 
use VeloPixDet              v*    Det
in your Gauss requirement file and rerun
 
Changed:
<
<

Tag specific ladders parameters

Tag specific parameters for ladders can be found in VeloPix/GeomParam/VeloPixLadders_TIMEPIX_x2.xml. One can find :
>
>
and rerun in Sim/Gauss/cmt
 
    
Changed:
<
<
<!-- Number of Chip  -->
>
>
cmt config source setup.csh
 
Changed:
<
<
<!-- Relative position direction of Chip ladder compare to Sensor (offset is set in the VeloPixParameters.xml) before any rotation -->
<!-- X_... = -1 means that compare to Sensor, ... will be moved in the negative X direction (have in mind that 0 for LadderChips is at ) -->
>
>
now check again if the package are used.
 
Deleted:
<
<
<!-- Relative position direction of HDI ladder compare to Sensor  (offset is set in the VeloPixParameters.xml) before any rotation -->
 
Changed:
<
<

TIMEPIX_x2 ladder tags, and tag specifc parameters:

In the file VeloPix/Geom/Catalogue/TIMEPIX_x2@PixelLadder.xml one can find:
>
>

Get a DDDB version containing VeloPix

 
Changed:
<
<
<!ENTITY Size "">
<!ENTITY Type "TIMEPIX_x2">
<!ENTITY Side "">
<!ENTITY SensDet "VeloPixSDet">
<!ENTITY SensorType SYSTEM "../LogVol/GenericPixelLadder.xml">
>
>
The normal way to do will soon be to specify the tag of the upgrade DDDB containing the VeloPix you want to use. Since for the moment
 
Deleted:
<
<
<!ENTITY GRBottom "Default"> <!ENTITY GRBottomPos "Default"> <!ENTITY GRTop "Default"> <!ENTITY GRTopPos "Default"> <!ENTITY GRLeft "Default"> <!ENTITY GRLeftPos "Default"> <!ENTITY GRRight "Default"> <!ENTITY GRRightPos "Default">
 
Changed:
<
<
<!ENTITY MatLay1 "Vacuum"> <!ENTITY MatLay2 "Aluminium"> <!ENTITY MatLay3 "Vacuum"> <!ENTITY MatLay4 "Vacuum"> <!ENTITY MatLay5 "Vacuum">
>
>

Configuring Gauss for VeloPix simulations

In order to have VeloPix taken into account in the Gauss configuration, and if your version of Gauss does not allow to choose the sub-detector to be simulated via the dictionnaries DetectorSimDict and DetectorGeoDict you will need this Gauss configuration file in your Sim/Gauss/python/Gauss. It allows you to choose the detector to be used for geometry and those that will be simulated. For example by putting in your python option file the lines:
from Gauss.Configuration import *
Gauss().DataType = "Upgrade"
Gauss().DetectorSimDict ={"VELO":['VeloPix'], "TT":['TT'], "IT":['IT'], "OT":['OT'], "RICH":[], "CALO":[], "MUON":[],"MAGNET": True }
Gauss().DetectorGeoDict = {"VELO":['VeloPix'], "TT":['TT'], "IT":['IT'], "OT":['OT'], "RICH":['Rich1','Rich2'], "CALO":[], "MUON":[],"MAGNET": True }
 
Changed:
<
<
The naming tags (Size, Type and Side) are set to "TIMEPIX_x2". Therefore the parmeters relative to The guardring tags aere all set to "Default" since the guardring is all over the sensitive area.
>
>
you will use VeloPix as vertex locator and you will only simulate the tracking system, but you will keep in the geometry description the Rich1 and 2 for having their materials taken into account.
 
Added:
>
>
Now, if the DDDBupgrade that containsd your VeloPix is not the default one, you need to specify the DDDBupgrade location and the tag you want by adding:
 
Deleted:
<
<
The chips support materials are set to

sensors definition

 
Changed:
<
<

supports definition

>
>

VeloPix in Boole

implementation in progress
 
Changed:
<
<

modules definition

>
>

VeloPix in Brunel

not yet implemented
 
Deleted:
<
<

detector definition

 
Deleted:
<
<
-- VictorCoco - 12-Oct-2009
 \ No newline at end of file
Added:
>
>
META FILEATTACHMENT attachment="VeloPixelDoc.pdf" attr="" comment="" date="1255418612" name="VeloPixelDoc.pdf" path="VeloPixelDoc.pdf" size="1121472" stream="VeloPixelDoc.pdf" tmpFilename="/usr/tmp/CGItemp8019" user="coco_40lapp_2ein2p3_2efr" version="1"

Revision 52009-10-12 - unknown

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

VeloPix implementation recipe

Line: 19 to 19
 * TIMEPIX_x2CentralBottom is for the ladder below the central one.

Common ladders parameters

Changed:
<
<
Parameters that are common to all ladders can be found in VeloPix/GeomParam/
>
>
Parameters that are common to all ladders can be found in VeloPix/GeomParam/VeloPixParameters_TIMEPIX_MINIPLANE.xml. The mandatory parameter for ladder creation are:

* for silicon sensor (see Sec.2.2.2 of generic VeloPix description):

  <!-- Silicon tickness                                       --> 
  <parameter name="SensorSiThick"     value="0.15*mm"          />
  <!-- Sensor active Area width                               -->
  <parameter name="SensorSiWidth"           value="14.1*mm"    />     
  <!-- Sensor Guard ring width                                -->
  <parameter name="SensorGuardRingTIMEPIX"    value="0.5*mm"   />     

* for the chips (see Sec.2.2.3 of generic VeloPix description)

    
  <!-- Chip 2 Chip distance                                   -->
  <parameter name="LadderChip2ChipDist"      value="0.1*mm"    />
  <!-- Chip Dimensions                                        -->
  <parameter name="LadderChipThick"          value="0.150*mm"  />
  <parameter name="LadderChipWidth"          value="14.1*mm"   />
  <parameter name="LadderChipLenght"         value="14.9*mm"   />

* for the chip support (see Sec.2.2.3 of generic VeloPix description)

    
  <!-- Ticknesses of the different layers                            -->
  <parameter name="LadderHDILayer1Thick"    value="VeloPixEpsilon"    />
  <parameter name="LadderHDILayer2Thick"    value="0.05*mm"           />
  <parameter name="LadderHDILayer3Thick"    value="VeloPixEpsilon"    />
  <parameter name="LadderHDILayer4Thick"    value="VeloPixEpsilon"    />
  <parameter name="LadderHDILayer5Thick"    value="VeloPixEpsilon"    />
  <!-- Chips support dimension                                       -->
  <parameter name="LadderHDIWidth"              value="14.1*mm"       />
  <parameter name="LadderHDIExtraDistOut"       value="0.0*mm"        />
  <parameter name="LadderHDIExtraDistIn"        value="0.0*mm"        />

* and for positionning of chips and chips support with respect to the active area (see Sec.2.2.4 of generic VeloPix description):

    
  <!-- Position of the chips support wrt the active area  -->
  <parameter name="X_Sensor2HDI"     value="(LadderHDIExtraDistOut+LadderHDIExtraDistIn)/2-LadderHDIExtraDistIn"/>
  <parameter name="Y_Sensor2HDI"     value="(LadderHDIWidth-SensorSiWidth)/2"                               />
  <parameter name="Z_Sensor2HDI"     value="LadderHDIThick+LadderChipThick+SensorSiThick/2+2*VeloPixEpsilon"/>
  <!-- Position of the chips wrt the active area -->
  <parameter name="X_Sensor2Chip"          value="0*mm"                                                     />
  <parameter name="Y_Sensor2Chip"          value="(LadderChipWidth-SensorSiWidth)/2"                        />  
  <parameter name="Z_Sensor2Chip"          value="LadderChipThick/2+SensorSiThick/2+VeloPixEpsilon"         />
 

Tag specific ladders parameters

Changed:
<
<
Tag specific parameters for ladders can be found in VeloPix/GeomParam/
>
>
Tag specific parameters for ladders can be found in VeloPix/GeomParam/VeloPixLadders_TIMEPIX_x2.xml. One can find :

    
  <!-- Number of Chip  -->
  <parameter name="NChip4LadderTIMEPIX_x2"         value="2"                   />

  <!-- Relative position direction of Chip ladder compare to Sensor (offset is set in the VeloPixParameters.xml) before any rotation -->
  <!-- X_... = -1 means that compare to Sensor, ... will be moved in the negative X direction (have in mind that 0 for LadderChips is at ) -->
  <parameter name="X_Sensor2ChipDirTIMEPIX_x2"      value="0"                />  
  <parameter name="Y_Sensor2ChipDirTIMEPIX_x2"      value="0"                />  
  <parameter name="Z_Sensor2ChipDirTIMEPIX_x2"      value="1"                />  

  <!-- Relative position direction of HDI ladder compare to Sensor  (offset is set in the VeloPixParameters.xml) before any rotation -->
  <parameter name="X_Sensor2HDIDirTIMEPIX_x2"      value="0"                 />  
  <parameter name="Y_Sensor2HDIDirTIMEPIX_x2"      value="0"                 />  
  <parameter name="Z_Sensor2HDIDirTIMEPIX_x2"      value="1"                 />  
 

TIMEPIX_x2 ladder tags, and tag specifc parameters:

Changed:
<
<
In the file VeloPix/Geom/Catalogue/TIMEPIX_x2@PixelLadder.xml one can find
>
>
In the file VeloPix/Geom/Catalogue/TIMEPIX_x2@PixelLadder.xml one can find:
 
<!ENTITY Size "">
<!ENTITY Type "TIMEPIX_x2">

Revision 42009-10-12 - unknown

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

Pixel VELO Simulations

>
>

VeloPix implementation recipe

  This page is under constructions.
Deleted:
<
<
To be filled in by Victor.
 
Added:
>
>
This page aims to be a recipe for creating new VeloPix geometries in the DDDB. The full description of the VeloPix implementation can be found in generic VeloPix description document, while we will concentrate, as an example, on the specific implementation of Timepix Miniplane solution (see..) As mentionned on Sec.1 of generic VeloPix description, in order to define a VeloPix geometry one needs:
 
Changed:
<
<

Timepix MiniPlane ladders

>
>
 
Changed:
<
<

Timepix MiniPlane sensor

>
>

ladders definition

Timepix MiniPlane solution modules contains 5 ladders of two chips. The five ladders are similar except that, since the 3 central ladder form a single silicon piece, the guard ring disposition of these ladders are different. Therefore we define 4 types of ladders: * TIMEPIX_x2 is for the top and bottom ladders with guard ring all around the active part. * TIMEPIX_x2Central is for the central ladder. * TIMEPIX_x2CentralTop is for the ladder above the central one. * TIMEPIX_x2CentralBottom is for the ladder below the central one.

Common ladders parameters

Parameters that are common to all ladders can be found in VeloPix/GeomParam/
 
Deleted:
<
<
-- TomaszSkwarnicki - 09-Oct-2009t
 
Changed:
<
<
META FILEATTACHMENT attachment="VeloPixelDoc.tex" attr="" comment="" date="1255331863" name="VeloPixelDoc.tex" path="VeloPixelDoc.tex" size="3613" stream="VeloPixelDoc.tex" tmpFilename="/usr/tmp/CGItemp14007" user="coco_40lapp_2ein2p3_2efr" version="1"
>
>

Tag specific ladders parameters

Tag specific parameters for ladders can be found in VeloPix/GeomParam/

TIMEPIX_x2 ladder tags, and tag specifc parameters:

In the file VeloPix/Geom/Catalogue/TIMEPIX_x2@PixelLadder.xml one can find
<!ENTITY Size "">
<!ENTITY Type "TIMEPIX_x2">
<!ENTITY Side "">
<!ENTITY SensDet "VeloPixSDet">
<!ENTITY SensorType SYSTEM "../LogVol/GenericPixelLadder.xml">

<!ENTITY GRBottom "Default">
<!ENTITY GRBottomPos "Default">
<!ENTITY GRTop "Default">
<!ENTITY GRTopPos "Default">
<!ENTITY GRLeft "Default">
<!ENTITY GRLeftPos "Default">
<!ENTITY GRRight "Default">
<!ENTITY GRRightPos "Default">

<!ENTITY MatLay1 "Vacuum">
<!ENTITY MatLay2 "Aluminium">
<!ENTITY MatLay3 "Vacuum">
<!ENTITY MatLay4 "Vacuum">
<!ENTITY MatLay5 "Vacuum">
The naming tags (Size, Type and Side) are set to "TIMEPIX_x2". Therefore the parmeters relative to The guardring tags aere all set to "Default" since the guardring is all over the sensitive area.

The chips support materials are set to

sensors definition

supports definition

modules definition

detector definition

-- VictorCoco - 12-Oct-2009

Revision 32009-10-12 - unknown

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

Pixel VELO Simulations

Line: 13 to 13
 

-- TomaszSkwarnicki - 09-Oct-2009t

Added:
>
>
META FILEATTACHMENT attachment="VeloPixelDoc.tex" attr="" comment="" date="1255331863" name="VeloPixelDoc.tex" path="VeloPixelDoc.tex" size="3613" stream="VeloPixelDoc.tex" tmpFilename="/usr/tmp/CGItemp14007" user="coco_40lapp_2ein2p3_2efr" version="1"

Revision 22009-10-11 - unknown

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

Pixel VELO Simulations

This page is under constructions. To be filled in by Victor.

Deleted:
<
<
-- TomaszSkwarnicki - 09-Oct-2009
 \ No newline at end of file
Added:
>
>

Timepix MiniPlane ladders

Timepix MiniPlane sensor

-- TomaszSkwarnicki - 09-Oct-2009t

Revision 12009-10-09 - TomaszSkwarnicki

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

Pixel VELO Simulations

This page is under constructions. To be filled in by Victor.

-- TomaszSkwarnicki - 09-Oct-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