|Message: storing & retrieving physics tables||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)|
Hi, storing & retrieving of physics tables and region/cuts-settings requires to have the same detector setup for storing and reading. From the user point of view, I think that I describe the same detector irrespective of the ordering of the creation of Materials, LogicalVolumes, Regions, ... . But, as it seems, G4 requires to have EXACTLY the same call sequence in creating G4-objects in order to store & retrieve physics tables correctly. This is somewhat odd, as the sequence in which objects are created sometimes can't be predicted. Depending on the implementation of the G4VUserDetectorConstruction the sequence in which G4-object are created could vary allthough the same detector is being described. Example: It should not matter, if I build the Tracker before the ElectromagneticCalorimeter or vice versa. Are there any plans to change the current G4-behavior? Thanks & cheers, Martin
|Inline Depth:||Outline Depth:||Add message:|