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

CVS update

Location:
trunk/documents/UserDoc/DocBookUsersGuides/ForApplicationDeveloper/xml/Fundamentals
Files:
4 edited

Legend:

Unmodified
Added
Removed

  • trunk/documents/UserDoc/DocBookUsersGuides/ForApplicationDeveloper/xml/Fundamentals/biasing.xml

    r921 r1211  
    3333concepts of importance sampling. More detailed documentation may be
    3434found in the documents
    35 <ulink url="http://geant4.web.cern.ch/geant4/collaboration/working_groups/geometry/index.shtml">
    36 'Latest development in importance sampling and scoring'
     35<ulink url="http://geant4.cern.ch/collaboration/working_groups/geometry/biasing/Sampling.html">
     36'Scoring, geometrical importance sampling and weight roulette'
    3737</ulink>.
    3838A detailed description of different use-cases which employ the sampling
    3939and scoring techniques can be found in the document
    40 <ulink url="http://geant4.web.cern.ch/geant4/collaboration/working_groups/geometry/index.shtml">
    41 'Scoring and geometrical importance sampling use cases'
     40<ulink url="http://geant4.cern.ch/collaboration/working_groups/geometry/biasing/BiasScoreUseCases.html">
     41'Use cases of importance sampling and scoring in Geant4'
    4242</ulink>.
    4343</para>
    … …  
    6363<para>
    6464Examples on how to use scoring and importance sampling may be found
    65 in <literal>examples/extended/biasing</literal> and
    66 <literal>examples/advanced/Tiara</literal>.
     65in <literal>examples/extended/biasing</literal>.
    6766</para>
    6867
    … …  
    10451044</para>
    10461045
    1047 <para>
    1048 More details can be found in
    1049 <ulink url="http://www.triumf.ca/geant4-03/talks/03-Wednesday-AM-1/03-J.Wellisch/biasing.hadronics.pdf">
    1050 Hadronic cross section biasing
    1051 </ulink>.
    1052 </para>
    1053 
    10541046</sect4>
    10551047</sect3>

  • trunk/documents/UserDoc/DocBookUsersGuides/ForApplicationDeveloper/xml/Fundamentals/eventGenerator.xml

    r904 r1211  
    4343<emphasis>G4PrimaryVertex</emphasis> class object and, thus, this class object
    4444can have one or more <emphasis>G4PrimaryParticle</emphasis> class objects which
    45 share the same vertex. As shown in Fig.?.?, primary vertexes and
    46 primary particles are associated with the <emphasis>G4Event</emphasis> object by
    47 a form of linked list.
     45share the same vertex. Primary vertexes and primary particles are associated
     46with the <emphasis>G4Event</emphasis> object by a form of linked list.
    4847</para>
    4948

  • trunk/documents/UserDoc/DocBookUsersGuides/ForApplicationDeveloper/xml/Fundamentals/global.xml

    r904 r1211  
    3737the Geant4 coding style conventions, each class part of the Geant4
    3838kernel has its name beginning with the prefix <emphasis>G4</emphasis>, e.g.,
    39 <emphasis>G4VHit, G4GeometryManager, G4ProcessVector,</emphasis> etc. Instead of
     39<emphasis>G4VHit, G4GeometryManager, G4ProcessVector</emphasis>, etc. Instead of
    4040the raw C types, <emphasis>G4</emphasis> types are used within the Geant4 code.
    41 For the basic numeric types (<literal>int, float, double,</literal> etc.),
     41For the basic numeric types (<literal>int, float, double</literal>, etc.),
    4242different compilers and different platforms provide different value
    4343ranges. In order to assure portability, the use of <emphasis>G4int,
    44 G4float, G4double,</emphasis> which are base classes globally defined, is
    45 preferable. <emphasis>G4</emphasis> types implement the right generic type for a
    46 given architecture.
     44G4float, G4double, G4bool</emphasis>, globally defined, is preferable.
     45<emphasis>G4</emphasis> types implement the right generic type
     46for a given architecture.
    4747</para>
    4848
    … …  
    652652    </para>
    653653    <para>
    654     <emphasis role="bold">Note</emphasis>: classes which are handled by
    655     <literal>G4Allocator</literal> should <emphasis>avoid</emphasis> to be used
    656     as base classes for others and therefore define their (eventually empty)
    657     destructors to be virtual (and/or inlined). Such measure is necessary in order
    658     to prevent bad aliasing optimisations by compilers which may potentially
    659     lead to crashes in the attempt to free the allocated chunks of memory.
     654    <emphasis role="bold">Note</emphasis>:
     655    <literal>G4Allocator</literal> assumes that objects being allocated
     656    have all the same size for the type they represent. For this reason,
     657    classes which are handled by <literal>G4Allocator</literal> should
     658    <emphasis>avoid</emphasis> to be used as base-classes for others.
     659    Similarly, base-classes of sub-classes handled through
     660    <literal>G4Allocator</literal> should not define their (eventually
     661    empty) virtual destructors inlined; such measure is necessary in order
     662    also to prevent bad aliasing optimisations by compilers which may
     663    potentially lead to crashes in the attempt to free allocated chunks
     664    of memory when using the base-class pointer or not.
    660665    </para>
    661666    <para>
    … …  
    673678      - hits collections of an event (G4HCofThisEvent): anHCoTHAllocator
    674679      - hits collections (G4HitsCollection): anHCAllocator
     680      - touchable histories (G4TouchableHistory): aTouchableHistoryAllocator
    675681      - trajectories (G4Trajectory): aTrajectoryAllocator
    676682      - trajectory points (G4TrajectoryPoint): aTrajectoryPointAllocator

  • trunk/documents/UserDoc/DocBookUsersGuides/ForApplicationDeveloper/xml/Fundamentals/unitSystem.xml

    r904 r1211  
    2424<para>
    2525Geant4 offers the user the possibility to choose and use the
    26 units he prefers for any quantity. In fact, the Geant4 kernel takes
    27 care of the units. Internally it uses a consistent set on units
    28 based on the <literal>HepSystemOfUnits</literal>:
     26preferred units for any quantity. In fact, Geant4 takes
     27care of the units. Internally a consistent set on units
     28based on the <literal>HepSystemOfUnits</literal> is used:
    2929
    3030<informalexample>
    … …  
    6363<para>
    6464In the file
    65 <literal>source/global/management/include/SystemOfUnits.h</literal> you will
    66 find all of these definitions. That file is part of CLHEP.
    67 </para>
    68 
    69 <para>
    70 Moreover, the user is free to change the system of units to be
    71 used by the kernel.
     65<literal>$CLHEP_BASE_DIR/include/CLHEP/Units/SystemOfUnits.h</literal>
     66from the CLHEP installation, one can find all untis definitions.
     67</para>
     68
     69<para>
     70One can also change the system of units to be used by the kernel.
    7271</para>
    7372
    … …  
    8786
    8887<para>
    89 You <emphasis role="bold">must</emphasis> give the units for the
    90 data you are going to
    91 introduce:
     88The user <emphasis role="bold">must</emphasis> give the units for the
     89data to introduce:
    9290
    9391<informalexample>
    … …  
    9997
    10098<para>
    101 Indeed, the full Geant4 code is written respecting these
    102 specifications, and this makes it independent of the units chosen
    103 by the user.
    104 </para>
    105 
    106 <para>
    107 If the units are not specified, it is understood that the data
    108 is implicitly in the internal G4 system, but this is strongly
     99Geant4 assumes that these specifications for the units are respected,
     100in order to assure indeipendence from the units chosen in the client
     101application.
     102</para>
     103
     104<para>
     105If units are not specified in the client application, data are implicitly
     106treated in internal Geant4 system units; this practice is however strongly
    109107discouraged.
    110108</para>
    … …  
    135133<para>
    136134Some built-in commands from the User Interface (UI) also require
    137 the units to be specified.
     135units to be specified.
    138136</para>
    139137
    … …  
    150148
    151149<para>
    152 If the units are not specified, or are not valid, the command is
    153 refused.
     150If units are not specified, or are not valid, the command is refused.
    154151</para>
    155152
    … …  
    165162
    166163<para>
    167 You can output your data with the units you wish. To do so, it is
     164You can output your data with the wished units. To do so, it is
    168165sufficient to <emphasis role="bold">divide</emphasis> the data by the
    169166corresponding unit:
    … …  
    183180
    184181<para>
    185 There is another way to output your data. Let Geant4 choose the
    186 most appropriate units for the actual numerical value of your data.
    187 It is sufficient to specify to which category your data belong
     182There is another way to output the data. Let Geant4 choose the
     183most appropriate units for the actual numerical value of the data.
     184It is sufficient to specify to which category the data belong to
    188185(Length, Time, Energy, etc.). For example
    189186
    … …  
    210207
    211208<para>
    212 If you wish to introduce new units, there are two methods:
     209If wished to introduce new units, there are two methods:
    213210
    214211<itemizedlist spacing="compact">
    … …  
    228225  </para></listitem>
    229226  <listitem><para>
    230     You can instantiate an object of the class
     227    Instantiate an object of the class
    231228    <emphasis>G4UnitDefinition</emphasis>
    232229
Note: See TracChangeset for help on using the changeset viewer.