Re: Trackr common is full!!, increase the Mxtrck parameter

  Dear Maki,

the problem was coming from the too small value set in WHAT(2) of
MGNFIELD. You have requested as upper limit for the boundary accuracy
1e-10cm during the tracking in the mangetic field. Therefore it was
forcing the code to make small steps to check for the boundary leading
to and overflow in the trackr common. Please increase the WHAT(2) e.g.
1e-4 and you will see that the message will disappear.
FLUKA was displaying only the first ten messages in order not to flood
your output with such messages.

Regards
Vasilis

On 10/18/10 08:31, Chrysostomos Valderanis wrote:
> Hello,
> I am trying to run a simple example and I get this message in the
> first event of the err file. My questions
> 1. Is it an error or a warning. It doesn't seem to influence the
> result, but the fact that is written to the error file is worrying.
> 2. Since only tracking is involved, shouldn't it be also produced in
> the other events? Is it suppressed?
> 3. How to avoid it? I thought that enlarging the maximum step in the
> magnetic field was going to remove it, since the magnetic field region
> was going to be passed in one step, but it isn't the case.
> 4. changing the mxtrck parameter in the Trackr include module. It
> gives an error in the linking.
> Thank you,
> Makis

-- 
-------------------------------------------------------
Vasilis Vlachoudis
Dep. EN-STI-EET
Web: home.cern.ch/bnv
Tel: +41-22-7679851
Fax: +41-22-7669644