Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migration of unmigrated content due to installation of a new plugin

...

LCDetectors contains detector data for the org.lcsim framework. Each detector has a directory in the detectors directory of LCDetectors with . 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.

...

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 of CVS.

Code Block
cvs login -d :pserver:anonymous@cvs.freehep.org:/cvs/lcd
cvs co LCDetectors

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.

It also assumes that First, start by setting the name of the detector being you are working with is sdjan03. Replace this name with whatever detector you are working on.in the environment (bash).

No Format

export DETECTOR=sdjan03

The DETECTOR variable is used for all make commands that use a single detector.

Tip
titleHandy Hint

If you are performing one action for a number of detectors sequentially you can also define the detector
directly on the command line, e.g.

Code Block

make [target] DETECTOR=sdjan03

Build the zip file locally for the current DETECTOR. The zip Build zip file locally for single detector. The LCDD file will be placed at detectors/$DETECTOR.lcddzip

Code Block
make zip DETECTOR=sdjan03

Build Create LCDD file for single detectorDETECTOR. The LCDD file will be placed at detectors/$DETECTOR/$DETECTOR.lcdd

Code Block
make lcdd DETECTOR=sdjan03

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 single local detectorDETECTOR.

Code Block
make build DETECTOR=sdjan03

Remake the taglist and update to WWW (if on SLAC Linux).

...

Code Block
make zip_all

Update single detector DETECTOR's zip file to lcsim WWW from local copy, if needed.

Code Block
make update DETECTOR=sdjan03

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 using the conditions system. Basically, . 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. It is possible to point Point org.lcsim at to a detector from your local LCDetectors copy with an alias, similar to the following.

...

Refer to the Conditions Database Overview writeup under "Detector Alias File" for additional details about using custom detectors.