|Message: Re: Non-uniform fields||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)|
The Geant4 toolkit does not calculate the magnetic field of a solenoid from geometry information about the coils. In fact, the G4 toolkit does not contain routines to calculate fields for any standard type of mangnetic element, with a few random exceptions: G4QuadropoleMagField, G4LineCurrentMagField, G4HarmonicPolMagField, G4DELPHIMagField and even in these cases the field is not calculated from current distributions. The user is expected to provide the method: GetFieldValue.
Furthermore, the user needs to decide whether the material distribution that makes up his/her magnetic element is of consequence to his/her simulation. This consideration concerns how shower particles arising from interactions in the magnets themselves become 'detectable'. If that is not the case, there is no need to define the magnet geometry and the field can be associated to an abstract space. This space can fill the whole of the simulation geometry (the 'world') or it can only permeate a subset of the geometry (a logical volume daughter of the world in 'G4 speak'). An example of the first implementation is /examples/extended/fields/field01; for the 2nd case /field03. The example field04 shows how to have numerous overlapping fields in the same simulation. It also has a generic 'SimpleSolenoid' class which can be an example for your implementation.
Hope these examples help you further, Peter