Re: [fluka-discuss]: Max Voxel Number

From: Yuri Simeonov <yuri.simeonov_at_gmail.com>
Date: Fri, 26 Aug 2016 17:23:01 +0200

Dear Paola,

thank you for your answer. Dynamic memory allocation is of course very good
news! So the nummber of voxels I can import will be limited only by the
amount of RAM I have, am I right?

I had some interesting ideas, which I wanted to try, but nothing urgent, I
will wait for the next FLUKA release.

Regards
Yuri

2016-08-26 16:51 GMT+02:00 Paola Sala <paola.sala_at_mi.infn.it>:

> Dear Yuri,
> the amount of memory that you ask for may cause problems with memory
> addressing in the distributed fluka version. Take into account that you
> will need memory also for internal data, and probably a lot of memeory for
> scoring.
> The next release will overcome this problem and will allow for dinamic
> allocation of the memory.
> ... can you wait? Let's say beginning of next year.
> Regards
> Paola
> > Dear FLUKA experts,
> >
> > I voxelized a complex triangular-polygon mesh and imported it in FLUKA
> > using the Voxel card. The maximum number of Voxels, which I have in my
> > case
> > is about 45 Million, which is not sufficient for a precise geomterical
> > description.
> > I found a prevoius discussion about this topic :
> >
> > http://www.fluka.org/web_archive/earchive/new-fluka-discuss/0913.html
> >
> > Can I get a recompiled version of the code, with let's say, 1E9
> > Voxel*2bytes=2 GB RAM?
> >
> > I know that the number 1E9 Voxels will eventually decrease, depending on
> > my
> > geometry, bin scoring, etc., but 2 GB is the maximum RAM per core in our
> > cluster.
> >
> > Regards
> > Yuri
> >
>
>
> Paola Sala
> INFN Milano
> tel. Milano +39-0250317374
> tel. CERN +41-227679148
>
>


__________________________________________________________________________
You can manage unsubscription from this mailing list at https://www.fluka.org/fluka.php?id=acc_info
Received on Fri Aug 26 2016 - 18:55:00 CEST

This archive was generated by hypermail 2.3.0 : Fri Aug 26 2016 - 18:55:01 CEST