Thanks an improved volume estimator would be very useful.
I thought during MC volume estimate the burn zones don't use up much memory, so not a problem to divide it up and run volume estimate - it is only when allocating the storage for nuclide inventory in each zone that the memory use goes up.Jaakko Leppänen wrote:The problem is that the code has no way of knowing which material zones are part of the actual geometry and which are not. The only way of identifying the zones would be to run the Monte Carlo based volume calculation routine, but at that point the division is already made.
So I was thinking was it possible that having already run the MC volume estimate, the neutron and burn calculation reads in the volume file, and uses it to decide whether to allocate memory for the burn zone or not. (zero material volume = not allocated). i.e. the burn zone index number is actually the same, but not all the zones are allocated (you store on a smaller array, and need a second array to relate 'array position for active burn zone ID' to the 'original burn ID'...). In this way you do not consume memory allocating for the zones that do not contain any of the specific material. This was what I was thinking. Maybe it is indeed a big change I don't know.