|Message: Help desperately needed on the tessellated GDML volumes.||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)|
Recently I encountered a serious problem which has bothered me for a month and basically paralyzed my working progress on geometry implementation. The thing is, I used Fastrad and CAD .step files for our new detector to generate about 137 tessellated GDML volumes (files/modules). And I tried to include them into G4. It worked with part of those volumes, but with all of them or most of them the program (just to draw geometry, no particles) crashed by throwing the "bad_alloc" message indicating there is not enough (virtual) memory for my job on our computer cluster. And I used 2 parts of the exported GDML volumes which each has perfectly worked without crash, I read them at the same time into G4 and ran the macro but the crash occurred! So that excludes the possibility of a "bug" in a GDML file which can cause this crash.
So I thought the tessellated geometry is just simply too large (compared to the ones made by G4 C++ codes or manually written with GDML), every volume like a screw contains so many vertices and facets and if I didn't get it wrong, the GDML reader just creates the "in-memory" geometry from the parsed in GDML files. So all those "complex" geometrical info is just stored in the memory? So I just tried our most powerful computing cluster in our local research center which has 6 GB virtual ram for each job and it failed again! I also attached the screenshot of the error message which is always the same.
And I don't think it has anything to do with the stack volume either. 'cuz the stack limit for my account was largely increased but nothing was improved. I tried just one more GDML volume and it still crashed.
So I wonder if other G4 users who have experiences with Fastrad produced GDML volumes or any other software generated tessellated GDML volumes have had such problems with (virtual) memory. I guess our largest computer cluster is already quite competent and I don't know what else I can do to overcome this problem. By the way someone suggested there might be a memory leak. But what and where is that exactly? Is it really the cause or??
|Inline Depth:||Outline Depth:||Add message:|