Ignore:
Timestamp:
Dec 7, 2009, 12:15:45 PM (15 years ago)
Author:
garnier
Message:

CVS update

Location:
trunk/documents/UserDoc/DocBookUsersGuides/ForApplicationDeveloper/xml/Detector
Files:
25 deleted
12 edited

Legend:

Unmodified
Added
Removed

  • trunk/documents/UserDoc/DocBookUsersGuides/ForApplicationDeveloper/xml/Detector/commandScore.xml

    r904 r1211  
    1313</title>
    1414
    15 <note>
    16 <title>
    17   Notice
    18 </title>
    19 
    20 <para>
    21 As of Geant4 release 9.1, this functionality of command-based scoring
    22 is still in <emphasis>alpha</emphasis> release and functionality offered
    23 is preliminary. We do not guarantee the correctness of the code. Also,
    24 we may change any of the commands / methods in the near future release.
    25 We appreciate your feedback.
    26 </para>
    27 </note>
    28 
    2915<!-- ******************* Section (Level#2) ****************** -->
    3016<sect2 id="sect.CommandScore.Intro">
    31 <title>
    32 Command-based scoring
    33 </title>
    34 
    35 <para>
    36 This new command-based scoring utilizes the parallel world described
    37 in the previous section. With UI interactive commands, the user can define :
     17
     18<para>
     19Command-based scoring in Geant4 utilizes parallel navigation in a parallel
     20world volume as descibed in the previous sections. Through interactive commands,
     21the user can define :
    3822
    3923<itemizedlist spacing="compact">
    … …  
    5337
    5438<para>
    55 For the time being of the alpha release, this command-based scoring
    56 is an optional functionality and the user has to explicity define
    57 its use in his/her <literal>main()</literal>. To do this, the
    58 method <literal>G4ScoringManager::GetScoringManager()</literal>
     39Command-based scoring is an optional functionality and the user has
     40to explicity define its use in the <literal>main()</literal>.
     41To do this, the method <literal>G4ScoringManager::GetScoringManager()</literal>
    5942must be invoked <emphasis role="color_red">right after</emphasis>
    6043the instantiation of <literal>G4RunManager</literal>.
    … …  
    11396
    11497<para>
    115 For a scoring mesh the user can have arbitrary number of quantities to be scored for each cell of the mesh.
    116 For each scoring quantity, the use can set one filter. Please note that <literal>/score/filter</literal>
    117 affects on the preceding scorer. Names of scorers and filters must be unique for the mesh.
    118 The user can define more than one scorers of same kind with different names (and most likely with different
    119 filters).
    120 </para>
    121 
    122 <para>
    123 Defining a scoring mesh and scores in thiat mesh should terminate with <literal>/score/close</literal>
    124 command. The following sample UI commands define a scoring mesh named <literal>boxMesh_1</literal>,
    125 size of which is 2 m * 2 m * 2 m, and sliced into 30 cells along each axes. For each cell energy deposition,
    126 number of steps of gamma, number of steps of electron and number of steps of positron are scored.
     98For a scoring mesh the user can have arbitrary number of quantities to be scored for
     99each cell of the mesh.
     100For each scoring quantity, the use can set one filter.
     101Please note that <literal>/score/filter</literal> affects on the preceding scorer.
     102Names of scorers and filters must be unique for the mesh.
     103It is possible to define more than one scorer of same kind with different names
     104and, likely, with different filters.
     105</para>
     106
     107<para>
     108Defining a scoring mesh and scores in the mesh should terminate with the
     109<literal>/score/close</literal> command. The following sample UI commands
     110define a scoring mesh named <literal>boxMesh_1</literal>, size of which is
     1112 m * 2 m * 2 m, and sliced into 30 cells along each axes.
     112For each cell energy deposition, number of steps of gamma, number of steps
     113of electron and number of steps of positron are scored.
    127114<example>
    128115<title>
    … …  
    164151
    165152<para>
    166 Once scores are filled, the user can visualize the scores. The score is
     153Once scores are filled, it is possible to visualize the scores. The score is
    167154drawn on top of the mass geometry with the current visualization settings.
    168155
    … …  
    189176class, and registered to <literal>G4ScoringManager</literal> with the color map
    190177name <literal>"defaultLinearColorMap"</literal>. The user may alternate color map
    191 by implementing his/her own color map class derived from <literal>G4VScoreColorMap</literal>
    192 and register it to <literal>G4ScoringManager</literal>. Then, for each <literal>draw</literal>
    193 command, the user can specify the color map of his/her own.
     178by implementing a customised color map class derived from
     179<literal>G4VScoreColorMap</literal> and register it to
     180<literal>G4ScoringManager</literal>. Then, for each <literal>draw</literal>
     181command, one can specify the preferred color map.
    194182</para>
    195183
    … …  
    203191
    204192<para>
    205 The user may dump a score in a mesh (<literal>/score/dumpQuantityToFile</literal> command)
    206 or all scores in a mesh (<literal>/score/dumpAllQuantitiesToFile</literal> command) to a file.
    207 The default file format is the simple CSV. To alternate the file format, the user should
    208 overwrite <literal>G4VScoreWriter</literal> class and register it to <literal>G4ScoringManager</literal>.
    209 Please refer to <literal>/examples/extended/runAndEvent/RE03</literal> for the detail.
    210 </para>
    211 
     193It is possible to dump a score in a mesh (<literal>/score/dumpQuantityToFile</literal>
     194command) or all scores in a mesh (<literal>/score/dumpAllQuantitiesToFile</literal>
     195command) to a file.
     196The default file format is the simple CSV. To alternate the file format, one should
     197overwrite <literal>G4VScoreWriter</literal> class and register it to
     198<literal>G4ScoringManager</literal>.
     199Please refer to <literal>/examples/extended/runAndEvent/RE03</literal> for details.
     200</para>
    212201
    213202</sect2>

  • trunk/documents/UserDoc/DocBookUsersGuides/ForApplicationDeveloper/xml/Detector/geomASCII.xml

    r904 r1211  
    2222An example showing how to define a geometry in plain text format and import
    2323it in a Geant4 application is shown in
    24 <literal>examples/extended/persistency/P03</literal>.
     24<literal>examples/extended/persistency/P03</literal>. The example also covers
     25the case of associating a sensitive detector to one of the volumes defined
     26in the text geometry, the case of mixing C++ and text geometry definitions
     27and the case of defining new tags in the text format so that regions and
     28cuts by region can be defined in the text file. It also provides an example
     29of how to write a geometry text file from the in-memory Geant4 geometry.
     30
     31For the details on the format see the dedicated
     32<ulink url="http://geant4.cern.ch/collaboration/working_groups/geometry/docs/textgeom/textgeom.pdf">manual</ulink>.
    2533</para>
    2634
     35
    2736</sect2>

  • trunk/documents/UserDoc/DocBookUsersGuides/ForApplicationDeveloper/xml/Detector/geomAssembly.xml

    r904 r1211  
    224224   G4RotationMatrix Ra;
    225225   G4ThreeVector Ta;
     226   G4Transform3D Tr;
    226227
    227228   // Rotation of the assembly inside the world
    … …  
    230231   // Fill the assembly by the plates
    231232   Ta.setX( caloX/4. ); Ta.setY( caloY/4. ); Ta.setZ( 0. );
    232    assemblyDetector-&gt;AddPlacedVolume( plateLV, G4Transform3D(Ta,Ra) );
     233   Tr = G4Transform3D(Ra,Ta);
     234   assemblyDetector-&gt;AddPlacedVolume( plateLV, Tr );
    233235
    234236   Ta.setX( -1*caloX/4. ); Ta.setY( caloY/4. ); Ta.setZ( 0. );
    235    assemblyDetector-&gt;AddPlacedVolume( plateLV, G4Transform3D(Ta,Ra) );
     237   Tr = G4Transform3D(Ra,Ta);
     238   assemblyDetector-&gt;AddPlacedVolume( plateLV, Tr );
    236239
    237240   Ta.setX( -1*caloX/4. ); Ta.setY( -1*caloY/4. ); Ta.setZ( 0. );
    238    assemblyDetector-&gt;AddPlacedVolume( plateLV, G4Transform3D(Ta,Ra) );
     241   Tr = G4Transform3D(Ra,Ta);
     242   assemblyDetector-&gt;AddPlacedVolume( plateLV, Tr );
    239243
    240244   Ta.setX( caloX/4. ); Ta.setY( -1*caloY/4. ); Ta.setZ( 0. );
    241    assemblyDetector-&gt;AddPlacedVolume( plateLV, G4Transform3D(Ta,Ra) );
     245   Tr = G4Transform3D(Ra,Ta);
     246   assemblyDetector-&gt;AddPlacedVolume( plateLV, Tr );
    242247
    243248   // Now instantiate the layers
    … …  
    246251     // Translation of the assembly inside the world
    247252     G4ThreeVector Tm( 0,0,i*(caloZ + caloCaloOffset) - firstCaloPos );
    248      assemblyDetector-&gt;MakeImprint( worldLV, G4Transform3D(Tm,Rm) );
     253     Tr = G4Transform3D(Rm,Tm);
     254     assemblyDetector-&gt;MakeImprint( worldLV, Tr );
    249255   }
    250256}

  • trunk/documents/UserDoc/DocBookUsersGuides/ForApplicationDeveloper/xml/Detector/geomEditor.xml

    r904 r1211  
    1515
    1616<para>
    17 GGE is the Geant4 Graphical Geometry Editor. It is implemented
    18 in JAVA and is part of the Momo environment. GGE aims to serve
    19 physicists who have a little knowledge of C++ and the Geant4
    20 toolkit to construct his or her own detector geometry in a
    21 graphical manner.
     17GGE is the acronym for Geant4 Graphical Geometry Editor.  GGE aims to assist
     18physicists who have a little knowledge on C++ and the Geant4
     19toolkit to construct his or her own detector geometry. In essence, GGE is made up of
     20a set of tables which can contain all relevant parameters to construct
     21a simple detector geometry. Tables for scratch or compound materials, tables for logical
     22and physical volumes are provided. From the values in the tables, C++ source codes are automatically
     23generated.
    2224</para>
    2325
    … …  
    3335  </para></listitem>
    3436  <listitem><para>
    35     view the detector geometry using existing visualization system like DAWN
    36   </para></listitem>
    37   <listitem><para>
    38     keep the detector object in a persistent way
     37    view the detector geometry using existing visualization system, DAWN
     38  </para></listitem>
     39  <listitem><para>
     40    keep the detector object in a persistent way, either in GDML format (currently only logical volumes are supported) or Java serialized format.
    3941  </para></listitem>
    4042  <listitem><para>
    … …  
    4244  </para></listitem>
    4345  <listitem><para>
    44     make a Geant4 executable under adequate environment
     46    make a Geant4 executable, in collaboration with another component of MOMO, i.e., GPE, or Geant4 Physics Editor.
    4547  </para></listitem>
    4648</orderedlist>
    … …  
    4850
    4951<para>
    50 GGE is implemented with Java, using Java Foundation Class,
    51 Swing and is part of Java MOMO Framework. In essence, GGE is made
    52 a set of tables which contain all relevant parameters to construct
    53 a simple detector geometry.
    54 </para>
    55 
    56 <para>
    57 The software, installation instructions and notes for GGE and other
    58 JAVA-based UI tools part of the MOMO Framework can be found in the
    59 Geant4 distribution under the <literal>geant4/enviroments/MOMO</literal>
    60 directory.
     52GGE can be found in the standard
     53Geant4 distribution under the <literal>$G4INSTALL/environments/MOMO/MOMO.jar</literal>.
     54JRE (Java Run-time Environment) is prerequisite to run MOMO.jar, Java archive file of MOMO.
     55MOMO contains GGE, GPE, GAG and other helper tools. Further information is available from the
     56Web pages below.
     57</para>
     58<para>
     59MOMO = GGE + GPE + GAG:
     60<ulink url="http://www-geant4.kek.jp/~yoshidah">
     61http://www-geant4.kek.jp/~yoshidah
     62</ulink>
    6163</para>
    6264
    … …  
    6870
    6971<para>
    70 GGE provides the database of elements in a form of the periodic
    71 table, which users can use to construct new materials. GGE provides
    72 a pre-constructed database of materials taken from the PDG book.
    73 They can be loaded, used, edited and saved as persistent
    74 objects.
     72GGE provides the database of elements in the form of the periodic
     73table, from which users can select element(s) to construct new materials.
     74They can be loaded, used, edited and saved as Java persistent
     75objects or in a GDML file. In <literal>$G4INSTALL/enviroments/MOMO</literal>,
     76a pre-constructed database of materials taken from the PDG book, <literal>PDG.xml</literal>
     77is present.
    7578</para>
    7679
    … …  
    8184<itemizedlist spacing="compact">
    8285  <listitem><para>
    83     creating a material from scratch:
     86    By selecting an element in the periodic table, default values as shown below are copied to a row in the table.
    8487    <para>
    8588    <informaltable>
    … …  
    104107    </para>
    105108    <para>
    106     Only the elements and materials used in the logical volumes are
     109    <emphasis role="bold">Use</emphasis> marks the used materials.
     110        Only the elements and materials used in the logical volumes are
    107111    kept in the detector object and are used to generate C++
    108     constructors. <emphasis role="bold">Use</emphasis> marks the used materials.
    109     </para>
    110   </para></listitem>
    111   <listitem><para>
    112     Constructor to create a material from a combination of
    113     elements, subsequently added via <literal>AddElement</literal>
     112    constructors.
     113    </para>
     114  </para></listitem>
     115  <listitem><para>
     116    By selecting multiple elements in the periodic table, a material from a combination of
     117    elements is assigned to a row of the compound material table. The minimum actions user
     118    have to do is to give a name to the
     119    material and define its density.
    114120    <para>
    115121    <informaltable>
    … …  
    139145    <itemizedlist spacing="compact">
    140146      <listitem><para>
    141         Add an element, giving fraction by weight
     147        Add an element, giving its fraction by weight
    142148      </para></listitem>
    143149      <listitem><para>
    144         Add an element, giving number of atoms.
     150        Add an element, giving its number of atoms.
    145151      </para></listitem>
    146152    </itemizedlist>
    … …  
    161167The most popular CSG solids (<literal>G4Box</literal>, <literal>G4Tubs</literal>,
    162168<literal>G4Cons</literal>, <literal>G4Trd</literal>) and specific BREPs solids
    163 (Pcons, Pgons) are supported at present. All related parameters of such a
    164 solid can be specified in a parameter widget.
    165 </para>
    166 
    167 <para>
    168 Users will be able to view each solid using DAWN.
     169(Pcons, Pgons) are supported. All relevant parameters of such a
     170solid can be specified in the parameter table, which pops up upon selection.
     171</para>
     172
     173<para>
     174Color, or the visualization attribute of a logical volume can be created,
     175using color chooser panel.
     176Users can view each solid using DAWN.
    169177</para>
    170178
    … …  
    195203
    196204<para>
     205The lists of solid types, names of the materials defined in the material tables, and
     206names of user-defined visualization attributes are shown automatically in respective table cell for user's choices.
     207</para>
     208<para>
    197209The construction and assignment of appropriate entities for
    198210<literal>G4FieldManager</literal> and <literal>G4VSensitiveDetector</literal>
    … …  
    209221
    210222<para>
    211 A single copy of a physical volume can be created. Also repeated
    212 copies can be created in several manners. First, a user can
    213 translate the logical volume linearly.
     223Geant4 enables users to create a physical volume in different ways; the mother volume
     224can be either a logical or a physical one, spatial rotation can be either
     225with respect to the volume or to the frame to which the volume is attached. GGE is prepared for
     226such four combinatorial cases to construct a physical volume.
     227</para>
     228<para>
     229Five simple cases of creating physical volumes are supported by GGE.
     230Primo, a single copy of a physical volume can be created by a translation and rotation. Secondo, repeated copies can be created by repeated linear translations.
     231A logical volume is  translated in a Cartesian direction, starting from the initial position,
     232with a given step size.
     233Mother volume can be either
     234another logical volume or a physical volume.
     235
    214236
    215237<informaltable>
    … …  
    219241  <entry>Name</entry>
    220242  <entry>LogicalVolume</entry>
    221   <entry>MotherVolume</entry>
     243  <entry>Type and name of MotherVolume</entry>
    222244  <entry>Many</entry>
    223245  <entry>X0, Y0, Z0</entry>
    … …  
    233255
    234256<para>
    235 Combined translation and rotation are also possible, placing an
    236 object repeatedly on a ``cylindrical'' pattern. Simple models of
    237 replicas and parametrised volume are also implemented. In the
    238 replicas, a volume is slices to create new sub-volumes. In
    239 parametrised volumes, several patterns of volumes can be
    240 created.
     257Third, repeated copies are created by rotation around an axis, placing an
     258object repeatedly on a ``cylindrical'' pattern.
     259Fourth,  replicas are created by slicing a volume along a Cartesian direction.
     260Fifth, replicas are created by cutting a volume cylindrically.
    241261</para>
    242262
    … …  
    246266<sect3 id="sect.Geom.Edit.GeneCode">
    247267<title>
    248 Generation of C++ code: <literal>MyDetectorConstruction.cc</literal>
    249 </title>
    250 
    251 <para>
    252 By simply pushing a button, source code in the form of an
    253 include file and a source file are created. They are called
    254 <literal>MyDetectorConstruction.cc</literal> and <literal>.hh</literal> files.
    255 They reflect all current user modifications in real-time.
     268Generation of C++ code:
     269</title>
     270
     271<para>
     272User has to type in a class name  to his
     273geometry, for example, <literal>MyDetectorConstruction</literal>. Then, with a mouse button click,
     274source codes in the form of an
     275include file and a source file are created and shown in the editor panel. In this example, they are
     276<literal>MyDetectorConstruction.cc</literal> and <literal>MyDetectorConstruction.hh</literal> files.
     277They reflect all current user modifications in the tables in real-time.
    256278</para>
    257279
    … …  
    265287
    266288<para>
    267 Examples of individual solids can be viewed with the help of
    268 DAWN. The visualization of the whole geometry is be done after the
     289The whole geometry can be visualized after the
    269290compilation of the source code <literal>MyDetectorConstruction.cc</literal>
    270291with appropriate parts of Geant4. (In particular only the geometry
    271292and visualization, together with the small other parts they depend
    272 on, are needed.)
     293on, are needed.) MOMO provides Physics Editor to create standard electromagnetic physics
     294and a minimum main program. See the on-line document in MOMO.
    273295</para>
    274296

  • trunk/documents/UserDoc/DocBookUsersGuides/ForApplicationDeveloper/xml/Detector/geomLogical.xml

    r904 r1211  
    143143
    144144<para>
    145 The concept of detector <emphasis>Region</emphasis> was introduced to address
     145The concept of detector <emphasis>Region</emphasis> is introduced to address
    146146this need. Once the final geometry setup of the detector has been
    147147defined, a region can be specified by constructing it with:
    … …  
    217217</para>
    218218
     219<para>
     220Regions can also become 'envelopes' for fast-simulation; can be assigned
     221user-limits or generic user-information (<literal>G4VUserRegionInformation</literal>);
     222can be associated to specific stepping-actions (<literal>G4UserSteppingAction</literal>)
     223or have assigned a local magnetic-field (local fields specifically associated to
     224logical volumes take precedence anyhow).
     225</para>
    219226
    220227</sect3>

  • trunk/documents/UserDoc/DocBookUsersGuides/ForApplicationDeveloper/xml/Detector/geomNav.xml

    r904 r1211  
    210210  G4Navigator* tracking_navigator =
    211211    G4TransportationManager::GetInstance()-&gt;GetNavigatorForTracking();
     212</programlisting>
     213</informalexample>
     214
     215This also allows to retrieve at any time a pointer to the world volume
     216assigned for tracking:
     217
     218<informalexample>
     219<programlisting>
     220  G4VPhysicalVolume* tracking_world = tracking_navigator-&gt;GetWorldVolume();
    212221</programlisting>
    213222</informalexample>

  • trunk/documents/UserDoc/DocBookUsersGuides/ForApplicationDeveloper/xml/Detector/geomOverlap.xml

    r904 r1211  
    124124<mediaobject>
    125125  <imageobject role="fo">
    126     <imagedata fileref="./AllResources/Detector/geometry.src/geomtest.gif"
    127                format="GIF" contentwidth="10.0cm" align="center" />
     126    <imagedata fileref="./AllResources/Detector/geometry.src/geomtest.jpg"
     127               format="JPG" contentwidth="10.0cm" align="center" />
    128128  </imageobject>
    129129  <imageobject role="html">
    130     <imagedata fileref="./AllResources/Detector/geometry.src/geomtest.gif"
    131                format="GIF" align="center" />
     130    <imagedata fileref="./AllResources/Detector/geometry.src/geomtest.jpg"
     131               format="JPG" align="center" />
    132132  </imageobject>
    133133</mediaobject>
    … …  
    255255</informalexample>
    256256
    257 which will force the check for the specified volume. The check
     257which will force the check for the specified volume, and can be therefore
     258used to verify for overlaps also once the geometry is fully built. The check
    258259verifies if each placed or parameterised instance is overlapping
    259260with other instances or with its mother volume. A default
    … …  
    291292<mediaobject>
    292293  <imageobject role="fo">
    293     <imagedata fileref="./AllResources/Detector/geometry.src/DAVID_SAMPLE.gif"
    294                format="GIF" contentwidth="3.0cm" align="center" />
     294    <imagedata fileref="./AllResources/Detector/geometry.src/DAVID_SAMPLE.jpg"
     295               format="JPG" contentwidth="3.0cm" align="center" />
    295296  </imageobject>
    296297  <imageobject role="html">
    297     <imagedata fileref="./AllResources/Detector/geometry.src/DAVID_SAMPLE.gif"
    298                format="GIF" align="center" />
     298    <imagedata fileref="./AllResources/Detector/geometry.src/DAVID_SAMPLE.jpg"
     299               format="JPG" align="center" />
    299300  </imageobject>
    300301</mediaobject>

  • trunk/documents/UserDoc/DocBookUsersGuides/ForApplicationDeveloper/xml/Detector/geomPhysical.xml

    r904 r1211  
    166166
    167167<para>
    168 Currently boolean operations are not implemented at the level of
     168Currently Boolean operations are not implemented at the level of
    169169physical volume. So <literal>pMany</literal> must be false. However, an
    170 alternative implementation of boolean operations exists. In this
     170alternative implementation of Boolean operations exists. In this
    171171approach a solid can be created from the union, intersection or
    172172subtraction of two solids. See  <xref linkend="sect.Geom.Solids.BoolOp" />
    173  above for an explanation of this.
     173above for an explanation of this.
    174174</para>
    175175
    … …  
    735735contain daughter volumes. When the size or type of solid varies,
    736736adding daughters is not supported.
    737 </para>
    738 
    739 <para>
    740737So the full power of parameterised volumes can be used only for
    741738"leaf" volumes, which contain no other volumes.
     739</para>
     740<para>
     741A hierarchy of volumes included in a parameterised volume cannot
     742vary. Therefore, it is not possible to implement a parameterisation
     743which can modify the hierachy of volumes included inside a specific
     744parameterised copy.
    742745</para>
    743746</note>
    … …  
    10831086  </entry>
    10841087  <entry>
     1088    <literal>kRho</literal>, <literal>kPhi</literal>, <literal>kZAxis</literal>
     1089  </entry>
     1090</row>
     1091<row>
     1092  <entry>
     1093    <literal>G4Polyhedra</literal>
     1094  </entry>
     1095  <entry>
    10851096    <literal>kRho</literal>, <literal>kPhi</literal>, <literal>kZAxis</literal> (*)
    1086   </entry>
    1087 </row>
    1088 <row>
    1089   <entry>
    1090     <literal>G4Polyhedra</literal>
    1091   </entry>
    1092   <entry>
    1093     <literal>kRho</literal>, <literal>kPhi</literal>, <literal>kZAxis</literal> (**)
    10941097  </entry>
    10951098</row>
    … …  
    11011104
    11021105<para>
    1103 (*) - <literal>G4Polycone</literal>:
    1104 
    1105 <itemizedlist spacing="compact">
    1106   <listitem><para>
    1107     <literal>kZAxis</literal> - the number of divisions has to be the same as
    1108     solid sections, (i.e. <literal>numZPlanes-1</literal>), the width will
    1109     <emphasis>not</emphasis> be taken into account.</para></listitem>
    1110 </itemizedlist>
    1111 </para>
    1112 
    1113 <para>
    1114 (**) - <literal>G4Polyhedra</literal>:
     1106(*) - <literal>G4Polyhedra</literal>:
    11151107
    11161108<itemizedlist spacing="compact">
    … …  
    11181110    <literal>kPhi</literal> - the number of divisions has to be the same as
    11191111    solid sides, (i.e. <literal>numSides</literal>), the width will
    1120     <emphasis>not</emphasis> be taken into account.
    1121   </para></listitem>
    1122   <listitem><para>
    1123     <literal>kZAxis</literal> - the number of divisions has to be the same as
    1124     solid sections, (i.e. <literal>numZPlanes-1</literal>), the width will
    11251112    <emphasis>not</emphasis> be taken into account.
    11261113  </para></listitem>

  • trunk/documents/UserDoc/DocBookUsersGuides/ForApplicationDeveloper/xml/Detector/geomSolids.xml

    r904 r1211  
    27252725<note><title></title>
    27262726<para>
     2727The constituent solids of a Boolean operation should possibly
     2728<emphasis>avoid</emphasis> be composed by sharing all or part of
     2729their surfaces. This precaution is necessary in order to avoid the
     2730generation of 'fake' surfaces due to precision loss, or errors in
     2731the final visualization of the Boolean shape. Moreover, the final
     2732Boolean solid should represent a single 'closed' solid, i.e. a Boolean
     2733operation between two solids which are disjoint or far apart each
     2734other, is <emphasis>not</emphasis> a valid Boolean composition.
     2735</para>
     2736</note>
     2737
     2738<note><title></title>
     2739<para>
    27272740The tracking cost for navigating in a Boolean solid in the
    27282741current implementation, is proportional to the number of
    … …  
    28712884
    28722885<para>
    2873 We have defined a few simple Elementary BREPS, that can be
    2874 instantiated simply by a user in a manner similar to the
    2875 construction of Constructed Solids (CSGs). We summarize their
    2876 capabilities in the following section.
     2886A few elementary BREPS are provided in the BREPS module as
     2887examples on how to assemble a BREP shap; these can be
     2888instantiated in the same manner as for the Constructed
     2889Solids (CSGs).
     2890We summarize their capabilities in the following section.
    28772891</para>
    28782892
    … …  
    33103324is required to convert first the CAD shapes into tessellated surfaces. A
    33113325way to do this is to save the shapes in the geometrical model as STEP files
    3312 and convert them using a tool like
    3313 <ulink url="http://www.steptools.com/products/stviewer/">STViewer</ulink> or
    3314 <ulink url="http://www.trad.fr/en/">FASTRAD</ulink> to
    3315 tessellated (faceted surfaces) solids. This strategy allows to import any shape
    3316 with some degree of approximation; the converted CAD models can then be
    3317 imported through <ulink url="http://cern.ch/gdml/">GDML (Geometry Description
     3326and convert them to tessellated (faceted surfaces) solids, using a tool which
     3327allows such conversion. At the time of writing, at least two tools are
     3328available for such purpose:
     3329<ulink url="http://www.steptools.com/products/stviewer/">STViewer</ulink>
     3330(part of the STEP-Tools development suite) or
     3331<ulink url="http://www.trad.fr/en/">FASTRAD</ulink>.
     3332This strategy allows to import any shape with some degree of approximation;
     3333the converted CAD models can then be imported through
     3334<ulink url="http://cern.ch/gdml/">GDML (Geometry Description
    33183335Markup Language)</ulink> into Geant4 and be represented as
    33193336<literal>G4TessellatedSolid</literal> shapes.

  • trunk/documents/UserDoc/DocBookUsersGuides/ForApplicationDeveloper/xml/Detector/geomXML.xml

    r904 r1211  
    2222</para>
    2323<para>
    24 The GDML parser is component of Geant4 which can be built
     24The GDML parser is a component of Geant4 which can be built
    2525and installed as an optional choice. It allows for importing and
    2626exporting GDML files, following the schema specified in the

  • trunk/documents/UserDoc/DocBookUsersGuides/ForApplicationDeveloper/xml/Detector/hit.xml

    r904 r1211  
    340340<mediaobject>
    341341  <imageobject role="fo">
    342     <imagedata fileref="./AllResources/Detector/hit.src/RO.gif"
     342    <imagedata fileref="./AllResources/Detector/hit.src/RO.jpg"
    343343               format="JPG" contentwidth="10.0cm" align="center" />
    344344  </imageobject>
    345345  <imageobject role="html">
    346     <imagedata fileref="./AllResources/Detector/hit.src/RO.gif"
     346    <imagedata fileref="./AllResources/Detector/hit.src/RO.jpg"
    347347               format="JPG" align="center" />
    348348  </imageobject>

  • trunk/documents/UserDoc/DocBookUsersGuides/ForApplicationDeveloper/xml/Detector/persistency.xml

    r904 r1211  
    4141<mediaobject>
    4242  <imageobject role="fo">
    43     <imagedata fileref="./AllResources/Detector/persistency.src/pobject.gif"
     43    <imagedata fileref="./AllResources/Detector/persistency.src/pobject.jpg"
    4444               format="JPG" contentwidth="7.0cm" align="center" />
    4545  </imageobject>
    4646  <imageobject role="html">
    47     <imagedata fileref="./AllResources/Detector/persistency.src/pobject.gif"
     47    <imagedata fileref="./AllResources/Detector/persistency.src/pobject.jpg"
    4848               format="JPG" align="center" />
    4949  </imageobject>
Note: See TracChangeset for help on using the changeset viewer.