|Message: 2 GDML Questions||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 rather recently began using Geant4.10.01, having previously used 4.9.6. There appear to be a couple of new "features" in the latest 3.1.1 version of GDML that is now incorporated that I don't completely understand. Unfortunately, I can't find release notes on GDML to see where these changes are called out, but was hoping someone might know more.
(1) I use the ENTITY capability of XML quite a bit, since most of my simulations uses the modular capabilities of GDML, In other words, when I have a mother volume including a child, I simply do
<physvol> <file name="FILENAME"> <positionref...> <rotationref...> </physvol>
This enables me to quickly set up a simulation with the mother including the child, or the child by itself, since the child is a completely syntactically correct gdml file. However, I've been using ENTITY to specify an overall "materials" file; that way I can use the same material over and over without having to rewrite it in every file. Since I include this file as an entity, however, it is read once for every single gdml file. So in reading the mother, it reads the file, then again when the child is read. This was never a problem before, but now it appears I get warning messages about repeated definitions of materials (a *lot* of them). While I don't care about warnings, I am a little concerned at how cross sections (using Hadron elastic physics, in particular) are being read. I'm worried, based on the amount of time it takes to set up a simulation, that every time my materials file is being read that these cross section files are being read, which is obviously for wasteful computationally.
Does anyone have any idea about this -- namely, is there any way to somehow tell Geant's GDML interpreter to just ignore xml/gdml files its already read (i.e., my materials file)?
(2) The other issue I appear to have is that I used to simply define all my materials AND elements with the <materials> tag. Now, it appears if I use that element in a molecular formula., i.e. with <composite n=X ref=X>, the interpreter can't find the element. I must explicitly define it as an element. On the other hand, it does still work in material mixtures, i.e. <fraction n=X ref=X>. What this has led me to is if I want to use, say, Carbon, in both a mixture and a molecule, I must make one with the <material> tag and one with the <element> tag (with different names of course).
Sorry for the long post and thanks for any help. These issues are not keeping me from running my simulations, I'd just like to understand them better and address them to save time.
|Inline Depth:||Outline Depth:||Add message:|