Linear Collider Forum



Today's Messages (off)  | Unanswered Messages (on)

Forum: slic
 Topic: Slic bug for version v03-01-03
Slic bug for version v03-01-03 [message #2314] Thu, 26 June 2014 05:09
remiete
Messages: 1
Registered: February 2013
Location: Lyon
Hi,

I tried to run some examples provided in the slic package v03-01-03 (hcal.lcdd, ecal.lcdd, SteelBox.lcdd, ...).
I got the same error each time :


slic -g /gridsoft/ipnls/ilc/v01-17-05/slic/v03-01-03/examples/SteelBox.lcdd 
Available UI session types: [ Qt, GAG, tcsh, csh ]

*************************************************************
 Application : Simulation for the Linear Collider
 Version : 3.1.3
*************************************************************
LCDD URI <../examples/cal/hcal.lcdd>
Version <>

***** LCDD Header *****
detectorName <HCAL>
detectorVersion <1.0>
detectorUrl <http://www.example.com>
authorName <Tony Johnson>
authorEmail <tonyj@slac.stanford.edu>
generatorName <DummyGenerator>
generatorVersion <1.0>
generatorFile <DummyCompactFile.xml>
generatorChecksum <0>
comment
ECAL:  NIMA 487 (2002) 291-307
end comment
***********************

1.0*mm
-^
Evaluator : syntax error

1.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

WARNING: IdSpec for <ECAL> does not exist!  Position comparison will be used for hit aggregation instead of id.
0.0*MeV
-^
Evaluator : syntax error


^
 

1.0*mm
-^
Evaluator : syntax error

1.0*MeV
-^
Evaluator : syntax error

Expression evaluator:: Error registering constant ecal_layer_x
Evaluator : syntax error

Expression evaluator:: Error registering constant ecal_layer_y
Evaluator : syntax error

Expression evaluator:: Error registering constant ecal_x
Evaluator : unknown variable

Expression evaluator:: Error registering constant ecal_y
Evaluator : unknown variable

0.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

0.0*mm
-^
Evaluator : syntax error

7.0
-^
Evaluator : syntax error

14.00674*g/mol
--^
Evaluator : syntax error

Abandon (core dumped)



followed by a Geant4 exception thrown saying:


-------- EEEE ------- G4Exception-START -------- EEEE -------
*** G4Exception : mat011
      issued by : G4Element::G4Element()
Fail to create G4Element N Z= 0 < 1 !

*** Fatal Exception *** core dump ***
-------- EEEE -------- G4Exception-END --------- EEEE -------



and


*** G4Exception: Aborting execution ***



I tried with my personnal laptop and on our server (lyoserv) with different version of ilcsoft (17-03 17-04 and 17-05) for different versions of slic dependencies. We also tried with different accounts and terminal environments. No other environment is sourced. This error happends all the time.

Thank you for help.

Cordially

RE
 Topic: Use of multiple CylindricalBarrelCalorimeters
Use of multiple CylindricalBarrelCalorimeters [message #2005] Mon, 31 May 2010 17:45
rcowan
Messages: 13
Registered: July 2007
Location: SLAC
Hi,

I have a detector design that I am modeling using the compact description format and slic. Part of the design is to have four consecutive barrel calorimeter layers with the layers increasing in length as the radius increases. Each calorimeter consists of a single absorber and a single sensitive layer.

I get an error from slic if I use this design and all four barrel calorimeters are producing "HcalBarrHits". To avoid this error, I can change the names--say, HcalBarrHits1, HcalBarrHits2, etc--but I'd like to call them all by the same name for consistency.

Question: Is there a better way to describe four concentric barrel calorimeter layers with differing lengths in the compact description?

While I can make a barrel calorimeter with repeating layers of the same length as a single system (using "layer repeat"), I don't know if there is a way to make four layers repeating with differing lengths.

Thanks. --Ray
 Topic: Using heprep files with wired in jas3 with variant geometries
Using heprep files with wired in jas3 with variant geometries [message #1908] Wed, 27 January 2010 19:26
rcowan
Messages: 13
Registered: July 2007
Location: SLAC
When viewing events from a variant detector geometry in wired, jas3 will ask for the heprep file for the given geometry either as a direct path to the heprep file or as an alias to the heprep file.

If you give a complete filespec to the correct heprep file, jas3 will give an error concerning line 59 of org.lcsim.util.heprep.MCParticleConverter. The line is:

trackingRMax = detector.getConstants().get("tracking_region_radius").getValue();


However, this information (the tracking region radius) is not in the heprep file in any case, it's in the compact.xml file. So it seems this particular method of loading the heprep file alone can never work--is this a bug/feature?

Taking the other option--putting an alias to the detector conditions data in your ~/.lcsim/alias.properties file--will work, but only if the directory does contain the compact.xml file.

Just FYI.

[Updated on: Wed, 27 January 2010 19:29]

 Topic: GeomConverter and "reflect=false" objects
GeomConverter and "reflect=false" objects [message #1902] Mon, 11 January 2010 15:23
rcowan
Messages: 13
Registered: July 2007
Location: SLAC
Hi,

I'm using GeomConverter to prepare a compact.xml file for a simple dark photon detector. I find that when I build some detector types (such as DiskTracker and CylindricalEndcapCalorimeter) with reflect="false" that the detectors that are
built with inner_z < 0 build their components in the +Z direction.

For instance, this code snippet builds the "ForwardCalorimeter" as expected--the slices start at inner_z=+50cm and progressively stack in the +z direction--but builds the "BackwardCalorimeter" starting at inner_z=-50cm and still stacks the layers and slices in the +Z direction (inverting the layer structure from what is desired, as well as shifting it by its total thickness).

       <detector id="1" name="ForwardCalorimeter" reflect="false" type="CylindricalEndcapCalorimeter" readout="HcalEndcapHits">
            <dimensions inner_r="20*cm" inner_z="50*cm" outer_r="60*cm" />
            <layer repeat="2">
                <slice material="Steel235" thickness="6.0*cm" />
                <slice material="Polystyrene" thickness="2.0*cm" sensitive="yes" />
            </layer>
        </detector>

        <detector id="2" name="BackwardCalorimeter" reflect="false" type="CylindricalEndcapCalorimeter" readout="HcalEndcapHits">
            <dimensions inner_r="30*cm" inner_z="-50*cm" outer_r="60*cm" />
            <layer repeat="2">
                <slice material="Steel235" thickness="6.0*cm" />
                <slice material="Polystyrene" thickness="2.0*cm" sensitive="yes" />
            </layer>
        </detector>


See the attached file for a plot showing the situation. Note that in the figure, the blue axis (+Z) points to the left, +Y axis in green points upward.

The detector case I am simulating is not symmetric with respect to reflection in the
x-y plane, so I cannot use "reflect=true".

I can work around this by shifting inner_z by the thickness of the whole calorimeter and also inverting the slice order within a layer, but this means (I think) that the layers will be numbered from outside toward the origin rather than the reverse when I get to the reconstruction stage.

Any suggestions on how to make these detector types build "outward" rather than "inward" when inner_z is < 0?

Thanks,
--Ray

  • Attachment: g4_20_x.png
    (Size: 10.93KB, Downloaded 1046 times)
 Topic: I am coming
I am coming [message #1353] Fri, 18 January 2008 12:45
zhangqm
Messages: 4
Registered: January 2008
wish have more chances to communicate with you!

[Updated on: Fri, 18 January 2008 13:32]

 Topic: energy not conserved
energy not conserved [message #1272] Wed, 07 November 2007 15:50
wenzel
Messages: 25
Registered: February 2007
Location: Fermilab
Hi


I am probably doing something wrong. I was shooting different particles with a kinetic energy of 10 GeV onto a dense hydrogen target configured as one sensitive detector with 4 cells.
When I sum up the raw uncorrected energy in he 4 cells I find that the distribution has tails where more energy is deposited than what we shoot in (even accounting for the rest mass of the incident particle)
While I can think of several reasons where energy can get lost
(e.g. leakage or nuclear break up in case of high A targets) getting more out than what we shoot in seems wrong. The default physics list (lcphys) is used. I have attached a tar file with the plots, java analysis file and the detector description files.
Please advice


hans


The tar file contains the following files:
run_lh_e.mac ! mac file to shoot 10 Gev electrons on hydrogen target
run_lh_k.mac ! mac file to shoot 10 Gev electrons on hydrogen target
run_lh.mac ! mac file to shoot 10 Gev electrons on hydrogen target
lh.lcdd ! lcdd file created by GeomConverter
compact_lh.xml ! compact description
AnalyzeCaloHits.java ! Analysis program to cretae the plots
10GeV_e_on_hydrogen.jpg ! plot energy deposit of 10 Gev electrons
10GeV_k-_on_hydrogen.jpg ! plot energy deposit of 10 Gev kaons
10GeV_Pions_on_hydrogen.jpg ! lot energy deposit of 10 Gev pions

  • Attachment: message.tgz
    (Size: 38.44KB, Downloaded 1401 times)
 Topic: Phi Inversion?
Phi Inversion? [message #1138] Mon, 24 September 2007 10:40
jgill
Messages: 2
Registered: March 2006
Location: University of Colorado
I'm running slic using a macro.

# isometric angular distribution
/gps/ang/type iso

# phi range
/gps/ang/minphi 90 deg
/gps/ang/maxphi 91.5 deg

I get momentum vectors that look like this:

Direction: (0.0136482,-0.999903,-0.00282306)

Which seems to me like -90 degrees, since a macro file with this command:

/gps/direction 0 1 0

Produces this momentum vector:

Direction: (0,1,0)

I realize this is a fairly arbitrary issue about how you define your coordinate system, but I was wondering if perhaps there was some standard coordinate system I didn't know about, or if this was just a bug.

Thanks,
Jack Gill
University of Colorado
 Topic: slic 2.3.0
slic 2.3.0 [message #950] Mon, 02 July 2007 10:38
jeremy
Messages: 46
Registered: March 2004
Location: SLAC
The 2.3.0 version of SLIC has been released. It uses Geant4 version 9.0.

Binaries are available for download from the following URL.

http://www.lcsim.org/dist/slic

Changes since last version:

-removed deprecated physics lists
-added new physics lists
-removed deprecated GAGTree visualization driver

Any questions can be sent to jeremym@slac.stanford.edu or posted to this forum.

[Updated on: Mon, 02 July 2007 10:39]


Jeremy McCormick, SLAC <jeremym@slac.stanford.edu>
 Topic: SimDist update
SimDist update [message #651] Tue, 19 December 2006 15:50
jeremy
Messages: 46
Registered: March 2004
Location: SLAC
The SimDist project, for building slic and all of its dependencies from scratch, has been updated for Geant4 8.2 version compatibility.

Here are the current packages tags being used by SimDist.

bdsim v02
clhep v1r9p3_1
gdml v2r8p1
geant4 v8r2
lcdd v1r12p2
lcio v1r7p2
lcphys v1r1p0
mokka 06-02
slic v2r1p0
xerces v2r7p0

You can get more information about SimDist here.

http://confluence.slac.stanford.edu/display/ilc/Simulation+S oftware+Distribution


Jeremy McCormick, SLAC <jeremym@slac.stanford.edu>
 Topic: lcdd 1.12 released
lcdd 1.12 released [message #650] Tue, 19 December 2006 15:13
jeremy
Messages: 46
Registered: March 2004
Location: SLAC
Hello.

I would like to announce the release of LCDD version 1.12, to coincide with the release of SLIC 2.1 .

You can find release notes at this URL.

http://www.lcsim.org/software/lcdd/lcdd_release_notes_1_12_0 .html


Jeremy McCormick, SLAC <jeremym@slac.stanford.edu>
 Topic: slic 2.1 released
slic 2.1 released [message #649] Tue, 19 December 2006 15:11
jeremy
Messages: 46
Registered: March 2004
Location: SLAC
Hello.

I would like to announce the release of SLIC version 2.1 . The release notes can be found here.

http://www.lcsim.org/software/slic/slic_release_notes_2_1_0. html

You can find binaries for your platform at this URL.

http://www.lcsim.org/dist/slic/

I have currently posted only the Linux binaries. The Windows and OSX versions are in the works.

This release is fully compatible with Geant4 version 8.2, which was released on December 15, 2006.

[Updated on: Tue, 19 December 2006 15:14]


Jeremy McCormick, SLAC <jeremym@slac.stanford.edu>
 Topic: slic 2.0
slic 2.0 [message #636] Mon, 13 November 2006 12:31
jeremy
Messages: 46
Registered: March 2004
Location: SLAC
Hello, SLIC users.

SLIC version 2.0 has been released, in the interests of consolidating a number of minor changes since around May 2006 into a single version.

I am planning to make more regular releases in the future and will be posting updates to the lcd-dev mailing list that point to forum postings.

I have attached the release notes to this posting, in HTML format.

Release notes are also available from the slic website.

http://www.lcsim.org/software/slic/release_notes_v2r0p7.html

Please let me know of any questions or concerns.

[Updated on: Mon, 13 November 2006 13:00]


Jeremy McCormick, SLAC <jeremym@slac.stanford.edu>
 Topic: Range Cuts in SLIC
Range Cuts in SLIC [message #348] Thu, 08 September 2005 07:10
karyotak
Messages: 2
Registered: March 2005
Hi all,

I run SLIC and try to find out the range cuts for gammas
Running dumpRegion I find this:

Region DefaultRegionForTheWorld
Materials : Air Tungsten G10 Silicon Steel235 Iron PyrexGlass RPCGasDefault Polystyrene Beryllium Aluminum
Production cuts : gamma 1 mm e- 1 mm e+ 1 mm

Region TrackingRegion
Materials : Air CarbonFiber Rohacell31 Beryllium PolystyreneFoam Aluminum G10 Copper PEEK Epoxy Silicon Kapton Titanium
Production cuts : gamma 1 cm e- 1 cm e+ 1 cm

Does the first region correspond to the Silicon of the calorimeter ?? In this case isn't it too big ??

I can change it by /run/setCut or setCutForRegion. The attached plot shows the energy deposited by 1 GeV gammas at 90 degrees in the 30 layers of Si using cdcaug05 geometry. I think this behavior is well known.

Yannis

  • Attachment: Eraw.png
    (Size: 29.18KB, Downloaded 2000 times)
 Topic: New SLIC and LCDD Releases
New SLIC and LCDD Releases [message #347] Wed, 07 September 2005 14:00
jeremy
Messages: 46
Registered: March 2004
Location: SLAC
I have release two packages today.

SLIC Release v1r10p0

http://www.lcsim.org/software/slic/release_notes_v1r10p0.htm l

LCDD Release v1r8p0

http://www.lcsim.org/software/lcdd/release_notes_v1r8p0.html


Jeremy McCormick, SLAC <jeremym@slac.stanford.edu>


Current Time: Fri Sep 21 04:27:22 Pacific Daylight Time 2018
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.1.
Copyright ©2001-2010 FUDforum Bulletin Board Software