Dear Roman,
The area estimated by FLUKA is reported in:
1. .out
******* "USRBDX" option:
Bdrx n. 1 "usrbdx " , generalized particle n. 1, from region n.
2 to region n. 3
detector area: 1.2566E+03 cm**2
2. fort, if ASCII scoring is requested
3. sum.lis, if binary scoring is requested, followed by usxsuw (either by the
user or by FLAIR's 'Process')
Running the input file you provided, A) verbatim; B) with SPECSOUR and GCR-SPE
cards removed:
- both A and B get the correct area reported in .out;
- A, but not B, resulted in the aberration you reported, both in fort and
sum.lis (usxsuw is therefore not the culprit).
The practical option would be to just take the area reported by .out rather than
fort or sum.lis.
If you are a keen detective and really want to get to the bottom of things, the
line of investigation might be to start with the *.f files associated with
SPECSOUR and GCR-SPE. Switching temporarily to the ASCII option would save the
extra step of usxsuw.
:) mary
> On 09 November 2015 at 13:08 Roman Savinov <rsavinov_at_calpoly.edu> wrote:
>
>
> Dear Fluka experts,
>
>
>
> the sum.lis file of USRBDX reports a strangely huge number for an Area:
>
>
>
>
>
> Detector n: 1( 1) usrbdx
> (Area: 1.23528358E+18 cmq,
> distr. scored: 1 ,
> from reg. 2 to 3,
> one way scoring,
> fluence scoring scoring)
>
> I have a spherical vacuum detector of radius 10 cm and the source is
> GCR-IONF that consist of protons only. Source is initiated from the sphere of
> 2 0 cm radius.
>
> Where this 1.23528358E+18 cmq is comming from?
>
> thank you,
>
> Roman
>
>
>
>
>
__________________________________________________________________________
You can manage unsubscription from this mailing list at
https://www.fluka.org/fluka.php?id=acc_info
Received on Tue Nov 10 2015 - 07:00:03 CET