|Message: G4SmartVoxelHeader::BuildNodes(...)||Not Logged In (login)|
Click on the Forum title, e.g. on the "Forums by Category" page, to read a sequence of postings to the Forum and its threads all in one page. If you are only interested in one thread or the thread following a specific posting, click the thread or the posting, which takes you to a smaller page, which contains only the part you are interested in and may be easier to navigate.
Messages are "chained" if there are only replies at the first level, i.e. 1/1.html, 1/1/1.html etc. In case of "chained" messages the message number is replaced by the icon and there is no indentation.
Inline: Display the subject line only or also the text of the posting(s); for the choice "All" the "Outline" choices are switched off.
|1||0||1||no text / full text of posting|
|2||1||All||text for level 1 only / text for All postings|
Outline: Choose the depth of the posting thread, successive toggle controls provide increasing detail.
|1||2||1||2 levels / 1 level (original posting)|
|2||3||2||3 levels / 2 levels|
|3||3||All||3 levels / all levels (all postings)|
i have 50M voxels of same size (some times, voxel matrix has two blocks of voxels of same size). i use MGH voxel tracking implementation, which is supposed to be the one of the fastest and most efficient (we patch g4 global:|
from the patched file names, i think, i am using parametrized blah-blahh volumes.
now. for just(!) 50M voxels the program cannot fit in 1.8 GB of RAM--pretty sad result.
in debugger i see that the bottleneck is in
that subroutine allocates two arrays:
with voxel extents (as i understand). voxels are always the same size... if the voxels have diff size, their must be, presumably, assigned as different voxel bodies.
anyways, the arrays are double. because my voxels are mm-size, i made them G4float. it helped, but only for a short time. later in the body of that function, as I understand, for each voxel(!!!! omg!) the list of neighboring or something voxels is created. pretty crazy to me. :) well, the memory consumption is over the top, and the code breaks. (no bad allocation catches, btw!)
should i forget about parametrized volumes for voxels?
i suggest at the end of that function to clean: delete minExtents, maxExtents; since the arrays are not used later and the auto cleaner will take a while.
also suggest to catch bad mem allocation. i though it is a std programming habit. it is pretty hard to guess why the program crashes...