Problem 38 - test15: Ion not stopped and killed - sticks making many small steps.
Summary: test15: Ion not stopped and killed - sticks making many small steps.
Status: CLOSED LATER
Alias: None
Product: Tests
Classification: Unclassified
Component: test15 (show other problems)
Version: 1.0
Hardware: Sun Solaris
: P2 major
Assignee: John.Allison
URL:
Depends on:
Blocks:
 
Reported: 1999-12-07 11:30 CET by John.Allison
Modified: 2007-04-08 18:32 CEST (History)
3 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this problem.
Description John.Allison 1999-12-07 11:30:51 CET
Report on test15 for "Large N"
        ==============================

   1000 events for each particle (p, pi+, pi-, kaon+, kaon-, kaon0S,
   kaon0L) at 10 GeV for each material (Pb, Al, Air, U) in a "simple
   box".

SUN:   After 307 minutes it has processed <2000 events, has grown to 136
       MB and seems to be stuck in electromagnetic processes, e.g.,
       G4PhotoElectricEffect, G4ComptonScatteringwith, with very small
       step size, e.g., previousStepSize = 7.9431524222885e-13.

       It looks like the same problem Hans-Peter, Makoto and I
       investigated last week - heavy ion is not killed - except this
       time the process is PiMinusAbsorptionAtRest.  Printing from
       TrackingManager:

(dbx) p *fpTrack->fpDynamicParticle
*fpTrack->fpDynamicParticle = {
    theMomentumDirection        = {
        dx = -0.83679017416538
        dy = 0.25400620126893
        dz = -0.48503922948274
    }
    theParticleDefinition       = 0x118fbe0
    thePolarization             = {
        dx = 0.0
        dy = 0.0
        dz = 0.0
    }
    theKineticEnergy            = 7.1710415383563e-12
    theProperTime               = 0.0
    theDynamicalMass            = 0.0
    theDynamicalCharge          = 81.0
    theElectronOccupancy        = (nil)
    thePreAssignedDecayProducts = (nil)
    verboseLevel                = 1
}
(dbx) p *fpTrack->fpStep
*fpTrack->fpStep = {
    fTotalEnergyDeposit   = 0.0
    fpPreStepPoint        = 0x13f1ef0
    fpPostStepPoint       = 0x13f1f90
    fStepLength           = 9.4883733391396e-12
    fpTrack               = 0x1a77688
    fpSteppingControlFlag = NormalCondition
}
(dbx) p *fpTrack->fpCreatorProcess
*fpTrack->fpCreatorProcess = {
    pParticleChange                  = 0x16fb0e0
    aParticleChange                  = {
        theMomentumDirectionChange = {
            dx = 0.9791428266563
            dy = 0.19101351988672
            dz = 0.069232652903025
        }
        thePolarizationChange      = {
            dx = 0.0
            dy = 0.0
            dz = 0.0
        }
        theEnergyChange            = 0.0
        thePositionChange          = {
            dx = 257.93709493304
            dy = -80.063149025237
            dz = -62.647880159645
        }
        theTimeChange              = 1.4137954535008
        theProperTimeChange        = 0.17428205431323
        theWeightChange            = 1.0
        theMassChange              = 139.57
        theChargeChange            = 0.0
        fUseEBForAll               = 0
    }
    theNumberOfInteractionLengthLeft = -1.0
    currentInteractionLength         = -1.0
    G4VProcess::theProcessName       = {
        G4String::basic_string<char,char_traits_char,allocator<char>>::size_ =
23U
        G4String::basic_string<char,char_traits_char,allocator<char>>::capacity_
= 32U
        G4String::basic_string<char,char_traits_char,allocator<char>>::data_ =
0x146cca8 "PiMinusAbsorptionAtRest"

G4String::basic_string<char,char_traits_char,allocator<char>>::allocator_ = {
            allocator<char>::impl_ = (nil)
        }
    }
    theProcessType                   = fNotDefined
    verboseLevel                     = 0
}
Comment 1 Hans-Peter.Wellisch 1999-12-09 00:54:59 CET
As I said before, this seems to be a problem with transportation, or may be
energy loss.

Subject:
           Re: Bug 38
       Date:
           Wed, 08 Dec 1999 09:20:52 +0100
       From:
           Johannes Peter Wellisch <Hans-Peter.Wellisch@cern.ch>
 Organization:
           CERN. European Lab. for Particle Physics
         To:
           John.Allison@man.ac.uk
        CC:
           Makoto Asai <Makoto.Asai@cern.ch>, Hisaya Kurasige
<kurasige@phys.sci.kobe-u.ac.jp>,
           John Allison <johna@pcitasoc01.cern.ch>, John Apostolakis
<John.Apostolakis@cern.ch>,
           Gabriele Cosmo <Gabriele.Cosmo@cern.ch>, Gunter Folger
<Gunter.Folger@cern.ch>
   References:
           1




+        It looks like the same problem Hans-Peter, Makoto and I
+        investigated last week - heavy ion is not killed - except this
+        time the process is PiMinusAbsorptionAtRest.  Printing from
+        TrackingManager:

Hi folks,

   hmmm. May be I misunderstand.
PiMinusabsorptionAtRest has created the ion and given it to tracking
for propagation. This seems to be the behaviour one would expect.

Many greetings,
              Hans-Peter.
Comment 2 Gabriele Cosmo 1999-12-09 01:14:59 CET
Who should take care of this problem?
Comment 3 John.Allison 2000-02-28 09:01:59 CET
Cannot be reproduced in latest tags, but suspect it's still there.
Comment 4 John.Allison 2000-08-19 17:25:59 CEST
Cannot be reproduced in latest tags.  CLOSE.