Date: Fri, 15 Apr 2016 07:28:59 +0000
Hi Roman,
> I noticed that I do not get an "Abort" error if I choose a low number of event requested in the START card.
The question is what you consider as "low" ;-) I've run the 10.000 particles from your input and it worked for me. However, the files already start to get pretty large (~600 MB) and it might be that there is an issue with files > 2GB & G77. I recall that at least that under the Solaris OS this was troublesome.
> Anyway, right now I can only see tracks of the secondary particles. How can I visualize track of the incident particle like in this video:
From the mgdraw.f function that we ship you will get everything (source particle tracks + secondaries etc.). With the FORTRAN tool to create the data-files for the visualization plugin you can create an energy binning structure which will be interpreted and shown by the plugin as filter options. This allows you to filter in SimpleGeo's visualization plugin not only by particle type but also by energy.
The video you are referring to was created in the following way:
Only one (!) primary particle was used and the time dependent animation mode was used for visualization. As the facility sends repetitive shots onto a target several of these single-primary particle events were calculated and then concatenated in terms of time. In FLUKA all primary particles start at t=0 by definition! In order to have a sequence of primary particles hitting a target repetitively we had to artificially introduce an offset for the time stamp of each shot and then simply concatenate the ASCII files for each primary event. When animating this via SimpleGeo you will get a video like the one you're referring to.
If you look into the ASCII files (*.tracks) containing the particle tracks you lines starting with an "s" followed by 4 numbers. "s" means track segment and the numbers are the coordinates X,Y,Z + a time stamp. In order to differentiate between the different shots we had to add a constant offset to this fourth value.
Just as a general remark I'd suggest to use a rather low number of primaries because otherwise it will be difficult for you to really see something as each primary, following FLUKA's convention, starts at t=0 and you will practically get a superposition of all events if you simulate more than 1 primary particle.
Cheers
Chris
From: Roman Savinov [mailto:rsavinov_at_calpoly.edu]
Sent: 14 April 2016 23:39
To: Chris Theis <Christian.Theis_at_cern.ch>; fluka-discuss_at_fluka.org (fluka-discuss_at_fluka.org) <fluka-discuss_at_fluka.org>
Subject: Re: PipsiCAD error
hi Chris,
thank you for your response.
Actually, my FLUKA has been compiled with 32 bits and my compiler is g77 i386
I noticed that I do not get an "Abort" error if I choose a low number of event requested in the START card.
Anyway, right now I can only see tracks of the secondary particles. How can I visualize track of the incident particle like in this video:
http://theis.web.cern.ch/theis/simplegeo/download/Hadronic_cascade_CERF.swf
Does it depends on the What(3) of the USERDUMP? Mine is 0 (All)
thank you,
Roman
________________________________
From: Chris Theis <Christian.Theis_at_cern.ch<mailto:Christian.Theis_at_cern.ch>>
Sent: Thursday, April 14, 2016 2:02 AM
To: Roman Savinov; fluka-discuss_at_fluka.org<mailto:fluka-discuss_at_fluka.org> (fluka-discuss_at_fluka.org<mailto:fluka-discuss_at_fluka.org>)
Cc: Stefan Roesler; Helmut Vincke
Subject: RE: PipsiCAD error
Hi Roman,
I have tried your input and it worked fine for me to produce pictures like the one below. However, could it be that you're using the 64 bit gfortran version of FLUKA? I assume that the problem could be related to the fact that compatibility of FORTRAN produced binary files is neither guaranteed between different platforms nor compilers. The executable Pipsicad_SimpleGeo.linux which we ship is compiled with G77-32 bits and if your FLUKA has been compiled with 64 bits then the produced binary files will not be compatible with 32-bit tools. In the attachment you can find the source code of the tool developed by my colleague Helmut Vincke. I'd propose that you compile it on your platform with the enclosed script and then the compatibility issues should be resolved.
Cheers
Chris
[cid:image001.jpg_at_01D196F7.C0FB05A0]
From: owner-fluka-discuss_at_mi.infn.it<mailto:owner-fluka-discuss_at_mi.infn.it> [mailto:owner-fluka-discuss_at_mi.infn.it] On Behalf Of Roman Savinov
Sent: 14 April 2016 06:33
To: fluka-discuss_at_fluka.org<mailto:fluka-discuss_at_fluka.org>
Subject: [fluka-discuss]: PipsiCAD error
Dear Fluka experts,
When I am running Pipsicad_SimpleGeo.linux interface to obtain an ASCII file which is used by the PipsiCAD plugin, I am getting the following error :
do_us: off end of record
apparent state: unit 17 named test001_collcad
lately reading sequential unformatted external IO
Aborted (core dumped)
I am using mgdraw.f routine found in the plugin package.
The USERDUMP card is defined as follows:
USERDUMP 100. 21. 0.0 1. collcad
The model is simple proton beam hitting an aluminum sphere
my input file is attached
Why the "Aborted" error?
thank you,
Roman
__________________________________________________________________________
You can manage unsubscription from this mailing list at https://www.fluka.org/fluka.php?id=acc_info
(image/jpeg attachment: image001.jpg)