LCDetectors
Overview
LCDetectors contains detector data for the
...
org.lcsim
...
framework.
...
Each
...
detector
...
has
...
a
...
directory
...
in
...
the
...
detectors
...
directory
...
of
...
LCDetectors. This directory contains a compact description, various properties files, an LCDD file, and other detector data. These directories are zipped and placed in canonical locations on the LCSIM website. The org.lcsim conditions system can download the zip files from the WWW based on the tag in the LCIO file. This information is used for detector description in the reconstruction framework.
LCSIM WWW
LCDetectors is periodically replicated to the org.lcsim website.
Detector zip resource files are kept at the base URL http://www.lcsim.org/detectors
...
.
...
For
...
instance,
...
the
...
sdjan03
...
zip
...
file
...
is
...
at
...
http://www.lcsim.org/detectors/sdjan03.zip
...
.
...
There
...
also
...
exist
...
directories
...
for
...
each
...
detector.
...
The
...
sdjan03
...
directory
...
is
...
http://www.lcsim.org/detectors/sdjan03/
...
.
...
The
...
LCDD
...
file
...
for
...
sdjan03
...
is
...
kept
...
at
...
http://www.lcsim.org/detectors/sdjan03/sdjan03.lcdd
...
and
...
the
...
compact
...
file
...
is
...
kept
...
at
...
http://www.lcsim.org/detectors/sdjan03/compact.xml
...
.
...
A
...
list
...
of
...
all
...
the
...
current
...
detector
...
tags
...
can
...
be
...
downloaded
...
from
...
http://www.lcsim.org/detectors/taglist.txt
...
.
Getting LCDetectors from CVS
LCDetectors is kept at the SLAC CVS. Instructions to checkout.
| Code Block |
|---|
cvs login h3. Getting from CVS LCDetectors is kept at the SLAC CVS. Instructions to checkout of CVS. {code} cvs -d :pserver:anonymous@cvs.freehep.org:/cvs/lcd cvs co LCDetectors {code} h3. Build Commands The following instructions assume that the current directory is LCDetectors checkout dir. It also assumes that the detector being working with is *sdjan03*. Replace this name with whatever detector you are working on. Build zip file locally for single detector. The LCDD file will be placed at *detectors/$DETECTOR.lcdd* {code} make zip DETECTOR=sdjan03 {code} Build LCDD file for single detector. The LCDD file will be placed at * |
To update an existing installation as new detectors are added you will need to specify that new directories should be built (-d), old ones should be pruned (-P) and any tags should be reset (-A).
| Code Block |
|---|
cvs update -PdA
|
GeomConverter
You will also need to checkout and build the GeomConverter project. Here are the quick build instructions.
| No Format |
|---|
cvs -d :pserver:anonymous@cvs.freehep.org:/cvs/lcd co GeomConverter
cd GeomConverter
mvn clean install
|
You will also need the the Maven 2 build tool.
Build Commands
The following instructions assume that the current directory is LCDetectors checkout dir.
First, start by setting the name of the detector you are working with in the environment (bash).
| No Format |
|---|
export DETECTOR=sdjan03
|
The DETECTOR variable is used for all make commands that use a single detector.
| Tip | ||
|---|---|---|
| ||
If you are performing one action for a number of detectors sequentially you can also define the detector
|
Build the zip file locally for the current DETECTOR. The zip file will be placed at detectors/$DETECTOR.zip
| Code Block |
|---|
make zip
|
Create LCDD file for DETECTOR. The LCDD file will be placed at detectors/$DETECTOR/$DETECTOR.lcdd
| Code Block |
|---|
* {code} make lcdd DETECTOR=sdjan03 {code} Build |
Create HepRep file for DETECTOR. The LCDD file will be placed at *detectors/$DETECTOR/detector.heprep
| Code Block |
|---|
make heprep
|
Build the LCDD file and zip file for DETECTOR.
| Code Block |
|---|
make build
|
Remake the taglist and update to WWW (if on SLAC Linux).
| Code Block |
|---|
make taglist
|
Rebuild all the detectors in place.
| Code Block |
|---|
the LCDD file and zip file for single local detector. {code} make build DETECTOR=sdjan03 {code} Remake the taglist and update to WWW (if on SLAC Linux). {code} make taglist {code} Rebuild all the detectors in place. {code} make build_all {code} |
Update
...
the
...
WWW
...
with
...
new
...
detectors.
| Code Block |
|---|
} make update_www {code} |
Commit
...
a
...
new
...
taglist
...
to
...
CVS.
| Code Block |
|---|
} make taglist_commit {code} |
Update
...
your
...
LCDetectors
...
module.
| Code Block |
|---|
} make cvs_update {code} |
Update
...
all
...
the
...
detectors
...
on
...
lcsim
...
WWW
...
from
...
your
...
local
...
copies.
| Code Block |
|---|
} make update_all {code} |
Make
...
all
...
the
...
LCDD
...
files
...
locally.
| Code Block |
|---|
{code} make lcdd_all {code} |
Make
...
all
...
the
...
zip
...
files
...
locally.
| Code Block |
|---|
} make zip_all {code} Update single detector to lcsim WWW from local copy. {code} make update DETECTOR=sdjan03 {code} h3. Custom Detectors You can configure org.lcsim to use your custom detector configurations using the conditions system. Basically, org.lcsim needs to know how to translate from the tag in the LCIO file to a zip file or directory containing the detector information. It is possible to point org.lcsim at a detector from your local LCDetectors copy with an alias similar to the following. {copy |
Update DETECTOR's zip file to lcsim WWW from local copy, if needed.
| Code Block |
|---|
make update
|
To make a new detector from the detectors/template files, first set DETECTOR equal to a new detector name.
| Code Block |
|---|
export DETECTOR=mynewdet
|
Then execute this command to create the directory structure and blank compact.xml file.
| Code Block |
|---|
make new
|
Custom Detectors
You can configure org.lcsim to use your own custom detector configurations. The org.lcsim conditions system needs to know how to translate from the tag in the LCIO file to a zip file or directory containing the detector information. Point org.lcsim to a detector from your local LCDetectors copy with an alias, similar to the following.
| Code Block |
|---|
} sdjan03: file:/my/LCDetectors/detectors/sdjan03/ {copy} |
Refer
...
to
...
the
...
...
...
...
writeup
...
under
...
"Detector
...
Alias
...
File"
...
for
...
additional
...
details about using custom detectors.