Re: [fluka-discuss]: How could I limit proton energy the detector receive when I use usrbin recording protons fluence?

From: Vittorio Boccone <dr.vittorio.boccone_at_ieee.org>
Date: Sat, 3 May 2014 10:22:17 +0200

Hi Chen Yuan,
   I'm confused by your input file. The kinetic energy of the primary
protons in your beam card is 44 MeV not 100 MeV.
Just to make sure that I understand your problem: you are sending a flat
beam of the exact dimension dimension of your target/object on it and you
score the fluence with a usrbin which is covering only a part of it.

I don't understand what you mean when you say that you can set the detector
thickness in the usrbin card.
What I see is that you are changing the thickness of the USRBIN scoring
protons, there's no material there only vacuum (by the way back there you
will not have only protons...)

Answering to question 1) I Would suggest you to place there a usrbdx or a
usrtrack rather than a usrbin (depending on what exactly you need). Create
a region for which you have a transition. Both cards have the possibility
of choosing the energy range of the scoring.

For Question n.2. Yes if there would be a detector there. But there's just
vacuum and you are not scoring any energy...
Best.
V.


On Fri, May 2, 2014 at 2:44 PM, <yyc2011_at_mail.ustc.edu.cn> wrote:

> Hi everyone,
>
> In my input file,I set DEFAULTS=PRECISIO, and I have a USRBIN detector
> which is been used to record protons fluence(the primary proton energy is
> 100 MeV).The attachment is my input file.Here are my problems.
> (1)According to my input file,the proton energy I record is from 0.1 MeV
> to 100 MeV.But,I think the minimum energy(0.1 MeV) is too low.How could I
> increase the minimum energy? In a word,I want to get protons fluence which
> proton energy is limited from 10 MeV to 100 MeV.
> (2)By the way,you know,we can set the detector thickness in the usrbin
> card.Is there any link between the detector thickness and the proton energy
> I record?
> Thanks for any suggestion.
>
> Best Regards
> Chen Yuan
Received on Sat May 03 2014 - 11:36:24 CEST

This archive was generated by hypermail 2.3.0 : Sat May 03 2014 - 11:36:26 CEST