(no subject)

From: Giuseppe Battistoni (Giuseppe.Battistoni@mi.infn.it)
Date: Wed Jan 07 2004 - 09:29:35 CET

  • Next message: Alberto Fasso': "(no subject)"

    Date: Tue, 06 Jan 2004 17:45:20 -0800 (PST)
    From: "Alberto Fasso'" <fasso@SLAC.Stanford.EDU>
    In-reply-to: <Pine.LNX.4.44.0312302316010.24582-100000@lxmi.mi.infn.it>
    To: fluka-discuss@fluka.org
    Cc: vashek.vylet@duke.edu
    Message-id: <Pine.GSO.4.58.0401061642400.29813@flora04.slac.stanford.edu>
    MIME-version: 1.0
    Content-type: TEXT/PLAIN; charset=ISO-8859-1
    Content-transfer-encoding: 8BIT
    References: <Pine.LNX.4.44.0312302316010.24582-100000@lxmi.mi.infn.it>
    X-Authentication-warning: flora04.slac.stanford.edu: fasso owned process doing
     -bs
    X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on
            troisi.fisica.unimi.it
    X-Spam-Level:
    X-Spam-Status: No, hits=-4.9 required=5.0 tests=BAYES_00 autolearn=ham
            version=2.60

    Hi Vashek,

    yes, there is way to tag particles in the way you want.
    In COMMON TRACKR, which is updated at each particle step,
    there are 11 integer flags (ISPUSR) and 11 double precision
    variables (SPAUSR) available to the user.
    The user can assign any arbitrary value to one or more of
    the above variables after any call of subroutine MGDRAW or to
    one of its ENTRYes:
    MGDRAW (step, with or without energy loss)
    BXDRAW (boundary crossing)
    EEDRAW (end of a history)
    ENDRAW (point energy deposition)
    SODRAW (source particle)
    USDRAW (physical interaction)

    A call to one or more of these entries is done with command
    USERDUMP. See more details on the manual, under USERDUMP and
    in Chapter 19 (user routines).
    The value of the user variables is inherited by the particle's
    progeny, as you desire.

    I guess that for your problem you could do the tagging at
    ENTRY BXDRAW. Unfortunately this entry (and EEDRAW) have been
    introduced only recently, and are not yet documented in the manual
    But the argument list should be clear enough:
          ENTRY BXDRAW ( ICODE, MREG, NEWREG, XSCO, YSCO, ZSCO )
    MREG is the region "before" the boundary, and NEWREG is the
    regione after the boundary. Yo can do the flagging by
    something like
          IF(MREG .EQ. xx) ISPUSR(1) = 1
    or even
          IF(MREG .EQ. xx) ISPUSR(1) = LTRACK (or = JTRACK)
    (that would "remember" the generation, or the type, of the particle
    which has crossed region xx)

    Ciao,

         Alberto

    > Hi,
    >
    > I would like to separate a contribution to fluence or energy deposition
    > from particles having passed through a specific region. I suppose I could
    > estimate that by having two separate runs and introducing "black hole"
    > material in appropriate places. However, this approach may be complicated
    > and error-prone for some geometries. Is there a way to "tag" particles (and
    > their progeny) that passed through a given region and score their
    > contribution separately? Perhaps one would write a collision tape and
    > post-process it with an existing utility? I would appreciate any
    > suggestions.
    > Thanks
    >
    > Vashek Vylet
    > <vashek.vylet@duke.edu>
    >
    >

    -- 
    Alberto FassÚ
    SLAC-RP, P.O. Box 4349, MS 48, Stanford CA 94309
    Phone: (1 650) 926 4762   Fax: (1 650) 926 3569
    fasso@slac.stanford.edu
    

  • Next message: Alberto Fasso': "(no subject)"

    This archive was generated by hypermail 2.1.6 : Wed Jan 07 2004 - 09:30:29 CET