Context Navigation

← Previous Change
Next Change →

Changeset 1208 for trunk/documents

Timestamp:

Nov 30, 2009, 3:52:24 PM (15 years ago)

Author:

garnier

Message:

CVS update

Location:

trunk/documents/UserDoc

Files:

: 1834 added
: 108 deleted
: 142 edited

Legend:

: Unmodified
: Added
: Removed

trunk/documents/UserDoc
- Property svn:ignore set to
  CVS
trunk/documents/UserDoc/DocBookUsersGuides
- Property svn:ignore set to
  CVS
trunk/documents/UserDoc/DocBookUsersGuides/ChangesHistory
- Property svn:ignore set to
  CVS

trunk/documents/UserDoc/DocBookUsersGuides/ChangesHistory/ChangesHistory.html

-                      r921
+                      r1208
 <br /><br /><br /><br />
+<!-- ============================================== Section -->
+<HR ALIGN="Center">
+<font COLOR="#238E23">
+<h2>Version: Geant4 9.2 Revison01 (June 2009) </h2>
+</font>
+<HR ALIGN="Center">
+<br />
+<p>
+<b><u>User's Guide: For Application Developers</u></b>
+</p>
+<ul>
+<b>- Modified Chapters/Sections</b>
+  <ul>
+    <li>8.5.6.  Visualization of hits
+    <li>5.4.7.  Special tracking cuts
+    <li>FAQ.6.  Visualization
+  </ul>
+</ul>
+<p>
+<b><u>User's Guide: For Toolkit Developers</u></b>
+</p>
+<ul>
+<b>- Modified Chapters/Sections</b>
+  <ul>
+    <li><b>All</b> figures in the manual are replaced with
+        higher resolution ones.
+  </ul>
+</ul>
 <!-- ============================================== Section -->

trunk/documents/UserDoc/DocBookUsersGuides/FAQ
- Property svn:ignore set to
  CVS
trunk/documents/UserDoc/DocBookUsersGuides/FAQ/xml
- Property svn:ignore set to
  CVS
trunk/documents/UserDoc/DocBookUsersGuides/FAQ/xml/AllResources
- Property svn:ignore set to
  CVS
trunk/documents/UserDoc/DocBookUsersGuides/FAQ/xml/AllResources/IconsGIF
- Property svn:ignore set to
  CVS

trunk/documents/UserDoc/DocBookUsersGuides/FAQ/xml/BookFAQ.xml

-                      r921
+                      r1208
   </authorgroup>
   <pubdate>19 December, 2008</pubdate>
   <releaseinfo>Version: geant4 9.2</releaseinfo>
+  <pubdate>2 June, 2009</pubdate>
+  <releaseinfo>Version: geant4 9.2 Revision01</releaseinfo>
 </bookinfo>

trunk/documents/UserDoc/DocBookUsersGuides/FAQ/xml/XSLCustomizationLayer
- Property svn:ignore set to
  CVS
trunk/documents/UserDoc/DocBookUsersGuides/ForApplicationDeveloper
- Property svn:ignore set to
  CVS
trunk/documents/UserDoc/DocBookUsersGuides/ForApplicationDeveloper/xml
- Property svn:ignore set to
  CVS
trunk/documents/UserDoc/DocBookUsersGuides/ForApplicationDeveloper/xml/AllResources
- Property svn:ignore set to
  CVS
trunk/documents/UserDoc/DocBookUsersGuides/ForApplicationDeveloper/xml/AllResources/Control
- Property svn:ignore set to
  CVS
trunk/documents/UserDoc/DocBookUsersGuides/ForApplicationDeveloper/xml/AllResources/Control/UIcommands
- Property svn:ignore set to
  CVS
trunk/documents/UserDoc/DocBookUsersGuides/ForApplicationDeveloper/xml/AllResources/Detector
- Property svn:ignore set to
  CVS
trunk/documents/UserDoc/DocBookUsersGuides/ForApplicationDeveloper/xml/AllResources/Detector/electroMagneticField.src
- Property svn:ignore set to
  CVS
trunk/documents/UserDoc/DocBookUsersGuides/ForApplicationDeveloper/xml/AllResources/Detector/geometry.src
- Property svn:ignore set to
  CVS
trunk/documents/UserDoc/DocBookUsersGuides/ForApplicationDeveloper/xml/AllResources/Detector/hit.src
- Property svn:ignore set to
  CVS
trunk/documents/UserDoc/DocBookUsersGuides/ForApplicationDeveloper/xml/AllResources/Detector/persistency.src
- Property svn:ignore set to
  CVS
trunk/documents/UserDoc/DocBookUsersGuides/ForApplicationDeveloper/xml/AllResources/Fundamentals
- Property svn:ignore set to
  CVS
trunk/documents/UserDoc/DocBookUsersGuides/ForApplicationDeveloper/xml/AllResources/IconsGIF
- Property svn:ignore set to
  CVS
trunk/documents/UserDoc/DocBookUsersGuides/ForApplicationDeveloper/xml/AllResources/TrackingAndPhysics
- Property svn:ignore set to
  CVS
trunk/documents/UserDoc/DocBookUsersGuides/ForApplicationDeveloper/xml/AllResources/TrackingAndPhysics/particleList.src
- Property svn:ignore set to
  CVS
trunk/documents/UserDoc/DocBookUsersGuides/ForApplicationDeveloper/xml/AllResources/TrackingAndPhysics/particleList.src/baryons
- Property svn:ignore set to
  CVS
trunk/documents/UserDoc/DocBookUsersGuides/ForApplicationDeveloper/xml/AllResources/TrackingAndPhysics/particleList.src/ions
- Property svn:ignore set to
  CVS
trunk/documents/UserDoc/DocBookUsersGuides/ForApplicationDeveloper/xml/AllResources/TrackingAndPhysics/particleList.src/leptons
- Property svn:ignore set to
  CVS
trunk/documents/UserDoc/DocBookUsersGuides/ForApplicationDeveloper/xml/AllResources/TrackingAndPhysics/particleList.src/mesons
- Property svn:ignore set to
  CVS
trunk/documents/UserDoc/DocBookUsersGuides/ForApplicationDeveloper/xml/AllResources/TrackingAndPhysics/particleList.src/others
- Property svn:ignore set to
  CVS
trunk/documents/UserDoc/DocBookUsersGuides/ForApplicationDeveloper/xml/AllResources/TrackingAndPhysics/particleList.src/quarks
- Property svn:ignore set to
  CVS
trunk/documents/UserDoc/DocBookUsersGuides/ForApplicationDeveloper/xml/AllResources/TrackingAndPhysics/physicsProcessOptical.src
- Property svn:ignore set to
  CVS
trunk/documents/UserDoc/DocBookUsersGuides/ForApplicationDeveloper/xml/AllResources/TrackingAndPhysics/physicsProcessPARAM.src
- Property svn:ignore set to
  CVS
trunk/documents/UserDoc/DocBookUsersGuides/ForApplicationDeveloper/xml/AllResources/Visualization
- Property svn:ignore set to
  CVS
trunk/documents/UserDoc/DocBookUsersGuides/ForApplicationDeveloper/xml/AllResources/Visualization/visualization.src
- Property svn:ignore set to
  CVS
trunk/documents/UserDoc/DocBookUsersGuides/ForApplicationDeveloper/xml/Appendix
- Property svn:ignore set to
  CVS

trunk/documents/UserDoc/DocBookUsersGuides/ForApplicationDeveloper/xml/Appendix/buildFile.xml

r904	r1208
75	75	<listitem><para>
76	76	<ulink url="http://www.lcsim.org/docs/gettingstarted/geant4msvc++/net2005/index.htm">
77		Building a MSVC++ Visual Studio 2005 Geant4 project</ulink>.
	77	Building a MSVC++ Visual Studio 2005 Geant4 project</ulink> (setup no longer supported).
78	78	</para></listitem>
79	79	</itemizedlist>

trunk/documents/UserDoc/DocBookUsersGuides/ForApplicationDeveloper/xml/Appendix/developmentDebugTools.xml

-                      r904
+                      r1208
   </para></listitem>
   <listitem><para>
     <ulink url="http://www.ibm.com/software/rational/">
     Rational Rose
+    <ulink url="http://www.sparxsystems.com.au/products/ea/">
+    Enterprise Architect
     </ulink>
     CASE tool.
+    UML Visual Modeling tool.
   </para></listitem>
   <listitem><para>
     <ulink url="http://www.borland.com/us/products/together/index.html">
     Together ControlCenter
+    Borland Together
     </ulink>
+    development environment.
+  </para></listitem>
+  <listitem><para>
+    <ulink url="http://www.telelogic.com/products/logiscope/index.cfm">
+    Logiscope
+    </ulink>
+    tool for metrics analysis.
+    Visual Modeling for Software Architecture Design tool.
   </para></listitem>
 </itemizedlist>

trunk/documents/UserDoc/DocBookUsersGuides/ForApplicationDeveloper/xml/Appendix/histogramming.xml

-                      r904
+                      r1208
 toolkit has no drivers for histogramming, and no drivers are needed
 in Geant4 to use a histogramming package. The code for generating
+histograms should be compliant with the
+histograms on some of the distributed examples should be compliant
+with the
 <ulink url="http://aida.freehep.org/">
 AIDA

trunk/documents/UserDoc/DocBookUsersGuides/ForApplicationDeveloper/xml/Appendix/makeFile.xml

-                      r904
+                      r1208
 To build a single library (or a set of sub-libraries) or an
 executable, you must explicitly change your current directory to
 the one you're interested in and invoke the "<literal>gmake</literal>"
 command from there ("<literal>gmake global</literal>" for building a
+the one you're interested in and invoke the "<literal>make</literal>"
+command from there ("<literal>make global</literal>" for building a
 compound library). Here is a list of the basic commands or GNUmake
 "targets" one can invoke to build libraries and/or executables:
 …
 <itemizedlist spacing="compact">
   <listitem><para>
     <literal>gmake</literal>
+    <literal>make</literal>
     <para>
     starts the compilation process for building a kernel library or a
 …
   </para></listitem>
   <listitem><para>
     <literal>gmake global</literal>
+    <literal>make global</literal>
     <para>
     starts the compilation process to build a single compound kernel
     library per category. If issued after "gmake", both 'granular' and
+    library per category. If issued after "make", both 'granular' and
     'compound' libraries will be available (NOTE: this will
     consistently increase the disk space required. Compound libraries
 …
   </para></listitem>
   <listitem><para>
     <literal>gmake bin</literal> or <literal>gmake</literal> (only for
+    <literal>make bin</literal> or <literal>make</literal> (only for
     examples/)
     <para>
 …
     </term>
     <listitem>
       Defines the path where the Geant4 toolkit should be installed. It
+      Defines the path where the Geant4 toolkit is located. It
       should be set by the system installer. By default, it sets to
       <literal>$HOME/geant4</literal>, assuming the Geant4 distribution
 …
     </term>
     <listitem>
       Used by the system to specify the place where to store libraries.
+      Used by the system to specify the place where to install libraries.
       By default they're set to <literal>$G4INSTALL/lib</literal> and
       <literal>$G4LIB/$G4SYSTEM</literal> respectively.
 …
   <varlistentry>
     <term>
-      $G4EXEC_BUILD
-    </term>
-    <listitem>
-      Flag specifying if to use a secondary template repository or not
-      for handling template instantiations at the time of building a user
-      application/example. For internal category tests in Geant4, this
-      variable is already in the related GNUmakefile. It's however not
-      needed for examples and tests in <literal>$G4INSTALL/examples</literal>,
-      where class names are already mangled and different each other. It
-      applies only on those compilers which make use of template
-      repositories (see Appendix A.2 of this Guide). The secondary
-      template repository is set to <literal>$G4TREP/exec</literal>.
-    </listitem>
-  </varlistentry>
-  <varlistentry>
-    <term>
       $G4DEBUG
     </term>
 …
   <varlistentry>
     <term>
+      $G4OPTDEBUG
+    </term>
+    <listitem>
+      Only available for the <literal>g++</literal> compiler, specifies to
+      compile the code (libraries or examples) in optimised mode, but
+      including symbolic information in the object code for debugging.
+    </listitem>
+  </varlistentry>
+  <varlistentry>
+    <term>
       $G4NO_OPTIMISE
     </term>
 …
       Specifies to compile the code (libraries or examples) without
       compiler optimisation.
-    </listitem>
-  </varlistentry>
-  <varlistentry>
-    <term>
-      $G4OPTDEBUG
-    </term>
-    <listitem>
-      On <literal>Linux</literal> systems with the <literal>g++</literal>
-      compiler, it allows to build in optimised mode including symbolic
-      information for debugging.
     </listitem>
   </varlistentry>
 …
       the built-in system library for compression is adopted instead. Setting
       this flag will also implicitely set the flag below.
+      On Windows systems, if OpenGL or OpenInventor visualization drivers
+      are built, this module is automatically built.
     </listitem>
   </varlistentry>
 …
     <listitem>
       Path to nuclear shell effects data set for INCL/ABLA hadronic model.
+    </listitem>
+  </varlistentry>
+  <varlistentry>
+    <term>
+      $G4REALSURFACEDATA
+    </term>
+    <listitem>
+      Path to the data set for measured optical surface reflectance for
+      precise optical physics.
     </listitem>
   </varlistentry>

trunk/documents/UserDoc/DocBookUsersGuides/ForApplicationDeveloper/xml/Appendix/tipsCompilation.xml

-                      r904
+                      r1208
 more or less perfomant and more or less optimised, depending on
 several factors also related to the system architecture which it
+applies to. A peculiarity of C++ compilers nowadays is the way
+templated instances are treated during the compilation/linkage
+process. Some C++ compilers need to store temporarily template
+instantiation files (object files or temporary source code files)
+in a "template repository" or directory that can be specified as
+unique or not directly from the compilation command (probably
+historically coming from the old cfront-based implementation of the
+C++ compiler).
+applies to.
 </para>
 …
 always distinguish between the installation directory (identified
 by $G4INSTALL) and the working directory (identified by
+$G4WORKDIR), in order not to alter the installation area for the
+template repository.
+$G4WORKDIR), in order not to alter the installation area.
 </para>
-<para>
-In Geant4, the path to the template repository (for those
-compilers which make use of it) is specified by the environment
-variable $G4TREP, which is fixed and points by default to
-<literal>$G4WORKDIR/tmp/$G4SYSTEM/g4.ptrepository/</literal>, where
-<literal>$G4SYSTEM</literal> identifies the system-architecture/compiler
-currently used and <literal>$G4WORKDIR</literal> is the path to the user
-working directory for Geant4.
-</para>
-<para>
-A secondary template repository <literal>$G4TREP/exec</literal> is
-created by default and can be used when building executables to
-isolate the main repository used for building the libraries in case
-of clashes provoked by conflicting class-names. This secondary
-template repository can be activated by defining in the environment
-(or in the GNUmakefile related to the test/example to be built) the
-flag <literal>G4EXEC_BUILD</literal>; once activated, the secondary
-repository will become the read/write one, while the primary
-repository will be considered read-only.
-</para>
-<para>
-At the current time, only few compilers still make use of a
-template repository. A good recommendation valid in general such
-compilers is to make use of a single template repository (specified
-by the <literal>$G4TREP</literal> environment variable) for building all
-Geant4 libraries; then use a secondary template repository
-(<literal>$G4TREP/exec</literal>, together with the
-<literal>$G4EXEC_BUILD</literal> flag) when building any kind of example or
-application.
-</para>
-<para>
-It's always good practise to clean-up the secondary template
-repository from time to time.
-</para>
 <!-- ******************* Section (Level#2) ****************** -->
 …
 compiler flags), also code is compiled with high verbosity
 diagnostics (<literal>-Wall</literal> flag). The default optimisation level
+is <literal>-O2</literal>.
+is <literal>-O2</literal>. The flag <literal>G4OPTDEBUG</literal>, if set
+in the environment, allows for optimised build of the libraries but
+including debug symbols (<literal>-O -g</literal> compilation option).
 </para>
 …
 <para>
 The setup adopted for the <literal>g++</literal> compiler on MacOS
 resembles in great part the one for Linux systems.
+resembles in most parts the one for Linux systems.
 </para>

trunk/documents/UserDoc/DocBookUsersGuides/ForApplicationDeveloper/xml/Bibliography
- Property svn:ignore set to
  CVS

trunk/documents/UserDoc/DocBookUsersGuides/ForApplicationDeveloper/xml/BookForAppliDev.xml

-                      r921
+                      r1208
   </authorgroup>
   <pubdate>19 December, 2008</pubdate>
   <releaseinfo>Version: geant4 9.2</releaseinfo>
+  <pubdate>2 June, 2009</pubdate>
+  <releaseinfo>Version: geant4 9.2 Revision01</releaseinfo>
 </bookinfo>
 …
 &appendix;
 &bibliography;
 </book>

trunk/documents/UserDoc/DocBookUsersGuides/ForApplicationDeveloper/xml/Control
- Property svn:ignore set to
  CVS
trunk/documents/UserDoc/DocBookUsersGuides/ForApplicationDeveloper/xml/Detector
- Property svn:ignore set to
  CVS
trunk/documents/UserDoc/DocBookUsersGuides/ForApplicationDeveloper/xml/Examples
- Property svn:ignore set to
  CVS
trunk/documents/UserDoc/DocBookUsersGuides/ForApplicationDeveloper/xml/FAQ
- Property svn:ignore set to
  CVS

trunk/documents/UserDoc/DocBookUsersGuides/ForApplicationDeveloper/xml/FAQ/Faq.xml

r904	r1208
28	28	&faqUserSupportPolicy;
29	29
30
31	30	</chapter>
32	31	<!-- /appendix -->

trunk/documents/UserDoc/DocBookUsersGuides/ForApplicationDeveloper/xml/FAQ/geometry.xml

r904	r1208
14	14
15	15	<qandaset defaultlabel="qanda">
	16
16	17
17	18	<!-- ***** QandA Entry ****** -->

trunk/documents/UserDoc/DocBookUsersGuides/ForApplicationDeveloper/xml/FAQ/installation.xml

r904	r1208
14	14
15	15	<qandaset defaultlabel="qanda">
	16
16	17
17	18	<!-- ***** QandA Entry ****** -->

trunk/documents/UserDoc/DocBookUsersGuides/ForApplicationDeveloper/xml/FAQ/physicsAndCuts.xml

r904	r1208
14	14
15	15	<qandaset defaultlabel="qanda">
	16
16	17
17	18	<!-- ***** QandA Entry ****** -->

trunk/documents/UserDoc/DocBookUsersGuides/ForApplicationDeveloper/xml/FAQ/runTimeProblems.xml

r904	r1208
14	14
15	15	<qandaset defaultlabel="qanda">
	16
16	17
17	18	<!-- ***** QandA Entry ****** -->

trunk/documents/UserDoc/DocBookUsersGuides/ForApplicationDeveloper/xml/FAQ/tracksAndSteps.xml

r904	r1208
14	14
15	15	<qandaset defaultlabel="qanda">
	16
16	17
17	18	<!-- ***** QandA Entry ****** -->

trunk/documents/UserDoc/DocBookUsersGuides/ForApplicationDeveloper/xml/FAQ/userSupportPolicy.xml

r904	r1208
14	14
15	15	<qandaset defaultlabel="qanda">
	16
16	17
17	18	<!-- ***** QandA Entry ****** -->

trunk/documents/UserDoc/DocBookUsersGuides/ForApplicationDeveloper/xml/FAQ/visualization.xml

-                      r904
+                      r1208
 <qandaset defaultlabel="qanda">
 <!-- ******* QandA Entry ******** -->
 …
       if set.
     </para></listitem>
+    <listitem><para>
       Verify and eventually set the environment variables of the
       visualization module [name] concerned (setenv or export both
 …
       gmake
       </programlisting></informalexample>
+    </para></listitem>
   </itemizedlist>
 …
+<!-- ******* QandA Entry ******** -->
+<qandaentry  id="qanda.Vis.BooleanProc">
+<question><para>
+  While visualizing my geometry setup I often see the following error
+  message printed out:
+  <informalexample><programlisting>
+  BooleanProcessor: boolean operation failed .
+  </programlisting></informalexample>
+</para></question>
+<answer><para>
+  There is a known limitation for the visualization of Boolean solids
+  in the so-called BooleanProcessor which is used to make polyhedra
+  for visualisation. It does not affect the tracking which is done
+  through such solids. So the error message you see does not affect
+  the simulation in any way. The workaround is to move one of the
+  affected solids by a small distance in order to avoid shared surfaces.
+</para></answer>
+</qandaentry>
 </qandaset>
 </section>

trunk/documents/UserDoc/DocBookUsersGuides/ForApplicationDeveloper/xml/Fundamentals
- Property svn:ignore set to
  CVS
trunk/documents/UserDoc/DocBookUsersGuides/ForApplicationDeveloper/xml/GettingStarted
- Property svn:ignore set to
  CVS

trunk/documents/UserDoc/DocBookUsersGuides/ForApplicationDeveloper/xml/GettingStarted/particleDef.xml

-                      r904
+                      r1208
 <!--    Changed by: Hisaya Kurashige, 18-Jan-2007             -->
 <!--    Changed by: Hisaya Kurashige, 1-Dec-2007              -->
+<!--    modified 2.4.2 by: Hisaya Kurashige, 23-Nov-2009      -->
 <!--                                                          -->
 <!-- ******************************************************** -->
 …
 <para>
 The unique object for each particle class is created when its static
 method to get the pointer is called iat the first time.
+method to get the pointer is called at the first time.
 Because particles are dynamic objects and should be instantiated before
 initialization of physics processes,
 …
 takes care of this sequence in usual applications.
 </para>
+<para>
+This range cut value is converted threshold energies
+for each material and for each particle type (i.e. electron,
+positron and gamma)
+so that the particle with threshold energy stops (or is absorbed)
+after traveling the range cut distance.
+In addition, from the 9.3 release ,this range cut value is applied
+to the proton as production thresholds of nuclei for  hadron
+elastic processes. In this case, the range cut value does not means
+the distance of traveling. Threshold energies are calculated
+by a simple formula from the cut in range.
+</para>
+<para>
+Note that the upper limit of the threshold energy is defined as 10
+GeV. If you want to set higher threshold energy, you can change
+the limit by using "/cuts/setMaxCutEnergy" command before setting
+the range cut.
+</para>
 <para>
 …
 coherent manner. For most applications, users need to determine
 only one cut value in range, and apply this value to gammas,
 electrons and positrons alike.
 </para>
 <para>
 In such a case, the <literal>SetCutsWithDefault()</literal> method may be
+electrons and positrons alike. (and proton too)
+</para>
+<para>
+In such case, the <literal>SetCutsWithDefault()</literal> method may be
 used. It is provided by the <literal>G4VuserPhysicsList</literal> base class,
 which has a <literal>defaultCutValue</literal> member as the default range
 …
 <para>
 The <literal>SetDefaultCutValue()</literal> method in
+<literal>G4VUserPhysicsList</literal> may also be used, and the "/run/setCut"
+command may be used to change the default cut value
+interactively.
+<literal>G4VUserPhysicsList</literal> may also be used,
+and the "/run/setCut" command may be used
+to change the default cut value interactively.
+</para>
+<para>
+You can set different cut values in range for different
+particle types. The "/run/setCutForAGivenParticle"  command
+may be used interactively.
 </para>
 …
   SetCutValue(cutForElectron, "e-");
   SetCutValue(cutForElectron, "e+");
+  SetCutValue(cutForProton,   "proton");
+}
 </programlisting>

trunk/documents/UserDoc/DocBookUsersGuides/ForApplicationDeveloper/xml/Introduction
- Property svn:ignore set to
  CVS
trunk/documents/UserDoc/DocBookUsersGuides/ForApplicationDeveloper/xml/TrackingAndPhysics
- Property svn:ignore set to
  CVS

trunk/documents/UserDoc/DocBookUsersGuides/ForApplicationDeveloper/xml/TrackingAndPhysics/physicsProcess.xml

-                      r921
+                      r1208
 </para>
+<para>
+Branching ratios and life time can be set in tracking time.
+<informalexample>
+<programlisting>
+  // set lifetime
+  G4Neutron::Neutron()->SetPDGLifeTime(885.7*second);
+  // allow neutron decay
+  G4Neutron::Neutron()->SetPDGStable(false);
+</programlisting>
+</informalexample>
+Branching ratios and life time can be modified by using user commands, also.
+  <listitem><para>
+    <emphasis role="bold">Example:
+    Set 100% br for dalitz decay of pi0</emphasis>
+    <para>
+    <literal>Idle&gt;> /particle/select pi0</literal>
+    <literal>Idle&gt;> /particle/property/decay/select 0</literal>
+    <literal>Idle> /particle/property/decay/br 0</literal>
+    <literal>Idle> /particle/property/decay/select 1</literal>
+    <literal>Idle> /particle/property/decay/br 1</literal>
+    <literal>Idle> /particle/property/decay/dump</literal>
+    <literal>G4DecayTable:  pi0</literal>
+    <literal>0:  BR:  0  [Phase Space]   :   gamma gamma</literal>
+    <literal>1:  BR:  1  [Dalitz Decay]   :   gamma e- e+</literal>
+    </para>
+  </para></listitem>
+</para>
 </sect3>

trunk/documents/UserDoc/DocBookUsersGuides/ForApplicationDeveloper/xml/TrackingAndPhysics/thresholdVScut.xml

-                      r904
+                      r1208
     </programlisting>
     </informalexample>
+    and in <literal>PhysicsList</literal>, the process
+    <literal>G4StepLimiter</literal> needs to be attached to each
+    particle's process manager where step limitation in the Tracker region
+    is required:
+    <informalexample>
+    <programlisting>
+       // Step limitation seen as a process
+       G4StepLimiter* stepLimiter = new G4StepLimiter();
+       pmanager-&gt;AddDiscreteProcess(StepLimiter);
+    </programlisting>
+    </informalexample>
     </para>
     <para>

trunk/documents/UserDoc/DocBookUsersGuides/ForApplicationDeveloper/xml/TrackingAndPhysics/tracking.xml

-                      r904
+                      r1208
 <!--    Converted to DocBook: Katsuya Amako, Aug-2006         -->
 <!--    Changed by: Hisaya Kurashige, 01-Dec-2007             -->
+<!--    Changed by: Hisaya Kurashige, 18-Nov-2009             -->
 <!--                                                          -->
 <!-- ******************************************************** -->
 …
 the different categories relevant to transporting a particle (for
 example, geometry and interactions in matter). Its public method
 <literal>Stepping()</literal> steers the stepping of the particle. The
 algorithm to handle one step is given below.
+<literal>Stepping()</literal> steers the stepping of the particle.
+The algorithm to handle one step is given below.
 <orderedlist spacing="compact">
   <listitem><para>
+    The particle's velocity at the beginning of the step is
+    calculated.
+  </para></listitem>
+    If the particle stop (i.e. zero kinetic energy), each active atRest
+    process proposes a step length in time based on the interaction
+    it describes. And the process proposing the smallest step length
+    will be invoked.
+  </para></listitem>
   <listitem><para>
     Each active discrete or continuous process must propose a step
 …
     step lengths is taken.
   </para></listitem>
   <listitem><para>
     The geometry navigator calculates "Safety", the distance to the
 …
     geometrical calculations will be performed.
   </para></listitem>
   <listitem><para>
     If the minimum physical-step-length from the processes is
 …
     re-calculated.
   </para></listitem>
   <listitem><para>
     The smaller of the minimum physical-step-length and the
     geometric step length is taken.
   </para></listitem>
   <listitem><para>
     All active continuous processes are invoked. Note that the
 …
     sum of the contributions from these processes.
   </para></listitem>
+  <listitem><para>
+    The track is checked to see whether or not it has been
+    terminated by a continuous process.
+  </para></listitem>
   <listitem><para>
     The current track properties are updated before discrete
+    processes are invoked. This includes:
+    processes are invoked. In the same time, the secondary
+    particles created by processes are stored in SecondaryList.
+    The updated properties are:
     <itemizedlist spacing="compact">
       <listitem><para>
         updating the kinetic energy of the current track particle (note
+        that 'sumEnergyChange' is the sum of the new kinetic energy after
+        each continuos process was invoked, and NOT the sum of the energy
+        difference before and after the process invocation) and
+        that 'sumEnergyChange' is the sum of the energy difference
+         before and after each process invocation)
       </para></listitem>
       <listitem><para>
+        updating position and time.
+        updating position and time
+      </para></listitem>
+     </itemizedlist>
+   </para></listitem>
+  <listitem><para>
+    The kinetic energy of the particle is checked to see whether
+    or not  it has been terminated by a continuous process.
+    If the kinetic energy goes down to zero, atRest processes
+    will be applied at the next step if applicable.
+  </para></listitem>
+  <listitem><para>
+    The discrete process is invoked. After the invocation,
+    <itemizedlist spacing="compact">
+      <listitem><para>
+        the energy, position and time of the current track particle
+        are updated, and
+      </para></listitem>
+      <listitem><para>
+        the secondaries are stored in SecondaryList.
       </para></listitem>
     </itemizedlist>
   </para></listitem>
+  <listitem><para>
+    The discrete process is invoked. After the invocation,
+    <itemizedlist spacing="compact">
+      <listitem><para>
+        the energy of the current track particle is updated, and
+      </para></listitem>
+      <listitem><para>
+        the secondaries from ParticleChange are stored in
+        SecondaryList. This includes constructing "G4Track" objects, and
+        setting their member data. Note that the stepping manager is
+        responsible for deleting secodaries from ParticleChange.
+      </para></listitem>
+    </itemizedlist>
+  </para></listitem>
   <listitem><para>
     The track is checked to see whether or not it has been
     terminated by the discrete process.
   </para></listitem>
   <listitem><para>
     "Safety" is updated.
   </para></listitem>
   <listitem><para>
     If the step was limited by the volume boundary, push the
     particle into the next volume.
   </para></listitem>
   <listitem><para>
     Invoke the user intervention <emphasis>G4UserSteppingAction</emphasis>.
   </para></listitem>
   <listitem><para>
     Handle hit information.
   </para></listitem>
   <listitem><para>
     Save data to Trajectory.
   </para></listitem>
   <listitem><para>
     Update the mean free paths of the discrete processes.
   </para></listitem>
   <listitem><para>
     If the parent particle is still alive, reset the maximum
     interaction length of the discrete process which has occurred.
   </para></listitem>
   <listitem><para>
     One step completed.
   </para></listitem>
 </orderedlist>
 </para>
+<!-- ******* Bridgehead ******* -->
+<bridgehead renderas='sect4'>
+What is a Process?
+</bridgehead>
+<para>
+Only processes can change information of <emphasis>G4Track</emphasis>
+and add secondary tracks via <literal>ParticleChange</literal>.
+<emphasis>G4VProcess</emphasis> is a base class of all processes and
+it has 3 kinds of  <literal>DoIt</literal> and
+<literal>GetPhysicalInteraction</literal> methods in order to
+describe interactions generically.
+If a user want to modify information of <emphasis>G4Track</emphasis>,
+he (or she) SHOULD create a special process for the purpose and
+register the process to the particle.
+</para>
+<!-- ******* Bridgehead ******* -->
+<bridgehead renderas='sect4'>
+What is a Track?
+</bridgehead>
+<para>
+<emphasis>G4Track</emphasis> keeps 'current' information of the particle.
+(i.e. energy,momentum, position ,time and so on) and has 'static'
+information (i.e. mass, charge, life and so on) also.
+Note that <emphasis>G4Track</emphasis> keeps information at the beginning
+of the step while the <literal>AlongStepDoIt</literal>s are being
+invoked for the step in progress.After finishing all
+<literal>AlongStepDoIt</literal>s, <emphasis>G4Track</emphasis>
+is updated.
+On the other hand, <emphasis>G4Track</emphasis> is
+updated after each invocation of a <literal>PostStepDoIt</literal>.
+</para>
 <!-- ******* Bridgehead ******* -->
 …
 <!-- ******* Bridgehead ******* -->
 <bridgehead renderas='sect4'>
+What is a Track?
+</bridgehead>
+<para>
+<emphasis>G4Track</emphasis> keeps information on the final status of the
+particle after the completion of one step. This means that
+<emphasis>G4Track</emphasis> has information on the previous step while the
+<literal>AlongStepDoIt</literal>s are being invoked for the step in progress.
+Only after finishing all <literal>AlongStepDoIt</literal>s, will
+<emphasis>G4Track</emphasis> have the final information (e.g., the final
+position) for the step in progress. Also, <emphasis>G4Track</emphasis> will be
+updated after each invocation of a <literal>PostStepDoIt</literal>.
+</para>
+What is a ParticleChange?
+</bridgehead>
+<para>
+Processes do NOT change any information of <emphasis>G4Track</emphasis>
+directly in their <literal>DoIt</literal>. Instead, they proposes
+changes as a result of interactions
+by using <literal>ParticleChange</literal>.
+After each <literal>DoIt</literal>, <literal>ParticleChange</literal>
+updates <literal>PostStepPoint</literal> based on proposed changes.
+Then, <emphasis>G4Track</emphasis> is updated
+after finishing all <literal>AlongStepDoIt</literal>s and
+after each <literal>PostStepDoIt</literal>.
+</para>
 </sect2>
 …
 <para>
 Secondary particles are passed as <emphasis>G4Track</emphasis>s from a physics
+process to tracking. <emphasis>G4ParticleChange</emphasis> provides the following
+process to tracking.
+<emphasis>G4ParticleChange</emphasis> provides the following
 four methods for a physics process:
 …
 <para>
 In all but the first, the construction of <emphasis>G4Track</emphasis> is done in
 the methods using informaton given by the arguments.
+the methods using information given by the arguments.
 </para>
 …
 kernel at specific points in the tracking. For details, see the
 <emphasis role="bold">Software Reference Manual</emphasis>.
+</para>
+<para>
+<emphasis role="bold">Note:</emphasis>
+Users SHOULD NOT (and CAN NOT) change <emphasis>G4Track</emphasis>
+in  <literal>UserSteppingAction</literal>.
+Only the exception is the <literal>TrackStatus</literal>.
 </para>

trunk/documents/UserDoc/DocBookUsersGuides/ForApplicationDeveloper/xml/UserActions
- Property svn:ignore set to
  CVS
trunk/documents/UserDoc/DocBookUsersGuides/ForApplicationDeveloper/xml/Visualization
- Property svn:ignore set to
  CVS

trunk/documents/UserDoc/DocBookUsersGuides/ForApplicationDeveloper/xml/Visualization/compiledcontrol.xml

-                      r904
+                      r1208
 <!--    Changed by: Dennis Wright, 27-Nov-2001                -->
 <!--    Converted to DocBook: Katsuya Amako, Aug-2006         -->
+<!--    Corrected Get methods: Joseph Perl, 17-Mar-2009       -->
 <!--                                                          -->
 <!-- ******************************************************** -->
 …
   void MyEventAction::EndOfEventAction()
+  {
     const G4Event* evt = fpEventManager-&gt;get_const_currentEvent();
     G4SDManager * SDman = G4SDManager::get_SDMpointer();
+    const G4Event* evt = fpEventManager-&gt;GetConstCurrentEvent();
+    G4SDManager * SDman = G4SDManager::GetSDMpointer();
     G4String colNam;
     G4int trackerCollID = SDman-&gt;get_collectionID(colNam="TrackerCollection");
     G4int calorimeterCollID = SDman-&gt;get_collectionID(colNam="CalCollection");
     G4TrajectoryContainer * trajectoryContainer = evt-&gt;get_trajectoryContainer();
+    G4int trackerCollID = SDman-&gt;GetCollectionID(colNam="TrackerCollection");
+    G4int calorimeterCollID = SDman-&gt;GetCollectionID(colNam="CalCollection");
+    G4TrajectoryContainer * trajectoryContainer = evt-&gt;GetTrajectoryContainer();
     G4int n_trajectories = 0;
     if(trajectoryContainer)
     { n_trajectories = trajectoryContainer-&gt;entries(); }
     G4HCofThisEvent * HCE = evt-&gt;get_HCofThisEvent();
+    G4HCofThisEvent * HCE = evt-&gt;GetHCofThisEvent();
     G4int n_hitCollection = 0;
     if(HCE)
     { n_hitCollection = HCE-&gt;get_capacity(); }
+    { n_hitCollection = HCE-&gt;GetCapacity(); }
     G4VVisManager* pVVisManager = G4VVisManager::GetConcreteInstance();
 …
       for(G4int i=0; i &lt; n_trajectories; i++)
+      {
           (*(evt-&gt;get_trajectoryContainer()))[i]-&gt;DrawTrajectory();
+          (*(evt-&gt;GetTrajectoryContainer()))[i]-&gt;DrawTrajectory();
+      }
       // Construct 3D data for hits
       MyTrackerHitsCollection* THC
         = (MyTrackerHitsCollection*)(HCE-&gt;get_HC(trackerCollID));
+        = (MyTrackerHitsCollection*)(HCE-&gt;GetHC(trackerCollID));
       if(THC) THC-&gt;DrawAllHits();
       MyCalorimeterHitsCollection* CHC
         = (MyCalorimeterHitsCollection*)(HCE-&gt;get_HC(calorimeterCollID));
+        = (MyCalorimeterHitsCollection*)(HCE-&gt;GetHC(calorimeterCollID));
       if(CHC) CHC-&gt;DrawAllHits();

trunk/documents/UserDoc/DocBookUsersGuides/ForApplicationDeveloper/xml/Visualization/enhanceddrawing.xml

-                      r904
+                      r1208
       </entry>
       <entry>
+pixels or mm*
+      </entry>
+    </row>
+    <row>
+      <entry>
+        Auxiliary point size type
+      </entry>
+      <entry>
+        screen
       </entry>
     </row>
 …
       </entry>
       <entry>
+pixels or mm*
+      </entry>
+    </row>
+    <row>
+      <entry>
+        Step point size type
+      </entry>
+      <entry>
+        screen
       </entry>
     </row>
 …
   </tgroup>
 </informaltable>
+</para>
+<para>
+* Depending on size type.  If size type == screen, pixels are assumed and no unit need be supplied.  If size type == world, a unit must be supplied, e.g., 10 cm.
 </para>
 …
     The context approach is intended to replace the configuration
     through the imode parameter. The use of imode is depreciated and
     will be removed in Geant4 v9.0.
+    will be removed in Geant4 v10.0.
   </para></listitem>
   <listitem><para>
 …
 <para>
+To draw by time, you need to use a trajectory that records the
+track time at the beginning and end of each step. To do this, write
+a tracking action that sets G4RichTrajectory, for example:
+<informalexample>
+<programlisting>
+#include "G4UserTrackingAction.hh"
+class G4Track;
+class MyTrackingAction : public G4UserTrackingAction
+{
+   public:
+   virtual void PreUserTrackingAction(const G4Track* aTrack);
+};
+#include "G4RichTrajectory.hh"
+#include "G4TrackingManager.hh"
+#include "G4IdentityTrajectoryFilter.hh"
+#include "G4TransportationManager.hh"
+#include "G4PropagatorInField.hh"
+void MyTrackingAction::PreUserTrackingAction(const G4Track* aTrack)
+{
+  // Require rich trajectory...
+  fpTrackingManager-&gt;SetTrajectory(new G4RichTrajectory(aTrack));
+  // Activate storing of auxiliary points for smoother trajectory...
+  static G4IdentityTrajectoryFilter curvedFilter;
+  G4TransportationManager::GetTransportationManager()-&gt;
+    GetPropagatorInField()-&gt;SetTrajectoryFilter(&amp;curvedFilter);
+}
+</programlisting>
+</informalexample>
+and register an instance of this with the run manager (this can be
+done once and for all as soon as the run manager is instantiated,
+probably in your main program):
+<informalexample>
+<programlisting>
+#include "MyTrackingAction.hh"
+...
+  runManager -&gt; SetUserAction (new MyTrackingAction);
+To draw by time, you need to use G4RichTrajectory, for example:
+<informalexample>
+<programlisting>
+/vis/scene/add/trajectories rich
+</programlisting>
+</informalexample>
+or
+<informalexample>
+<programlisting>
+/vis/scene/add/trajectories rich smooth
 </programlisting>
 </informalexample>
 …
 /vis/open OGLSX
 /vis/drawVolume
 /vis/scene/add/trajectories
+/vis/scene/add/trajectories rich
 /vis/ogl/set/startTime 0.5 ns
 /vis/ogl/set/endTime 0.8 ns

trunk/documents/UserDoc/DocBookUsersGuides/ForApplicationDeveloper/xml/Visualization/visTutor
- Property svn:ignore set to
  CVS
trunk/documents/UserDoc/DocBookUsersGuides/ForApplicationDeveloper/xml/XSLCustomizationLayer
- Property svn:ignore set to
  CVS
trunk/documents/UserDoc/DocBookUsersGuides/ForToolkitDeveloper
- Property svn:ignore set to
  CVS
trunk/documents/UserDoc/DocBookUsersGuides/ForToolkitDeveloper/xml
- Property svn:ignore set to
  CVS
trunk/documents/UserDoc/DocBookUsersGuides/ForToolkitDeveloper/xml/AllResources
- Property svn:ignore set to
  CVS
trunk/documents/UserDoc/DocBookUsersGuides/ForToolkitDeveloper/xml/AllResources/GuideToExtendFunctionality
- Property svn:ignore set to
  CVS
trunk/documents/UserDoc/DocBookUsersGuides/ForToolkitDeveloper/xml/AllResources/GuideToExtendFunctionality/HadronicPhysics
- Property svn:ignore set to
  CVS
trunk/documents/UserDoc/DocBookUsersGuides/ForToolkitDeveloper/xml/AllResources/GuideToExtendFunctionality/Visualization
- Property svn:ignore set to
  CVS
trunk/documents/UserDoc/DocBookUsersGuides/ForToolkitDeveloper/xml/AllResources/IconsGIF
- Property svn:ignore set to
  CVS
trunk/documents/UserDoc/DocBookUsersGuides/ForToolkitDeveloper/xml/AllResources/OOAnalysisDesign
- Property svn:ignore set to
  CVS
trunk/documents/UserDoc/DocBookUsersGuides/ForToolkitDeveloper/xml/AllResources/OOAnalysisDesign/ElectromagneticField
- Property svn:ignore set to
  CVS
trunk/documents/UserDoc/DocBookUsersGuides/ForToolkitDeveloper/xml/AllResources/OOAnalysisDesign/Event
- Property svn:ignore set to
  CVS
trunk/documents/UserDoc/DocBookUsersGuides/ForToolkitDeveloper/xml/AllResources/OOAnalysisDesign/Geometry
- Property svn:ignore set to
  CVS
trunk/documents/UserDoc/DocBookUsersGuides/ForToolkitDeveloper/xml/AllResources/OOAnalysisDesign/GlobalUsage
- Property svn:ignore set to
  CVS
trunk/documents/UserDoc/DocBookUsersGuides/ForToolkitDeveloper/xml/AllResources/OOAnalysisDesign/Hit
- Property svn:ignore set to
  CVS
trunk/documents/UserDoc/DocBookUsersGuides/ForToolkitDeveloper/xml/AllResources/OOAnalysisDesign/Materials
- Property svn:ignore set to
  CVS
trunk/documents/UserDoc/DocBookUsersGuides/ForToolkitDeveloper/xml/AllResources/OOAnalysisDesign/Particles
- Property svn:ignore set to
  CVS
trunk/documents/UserDoc/DocBookUsersGuides/ForToolkitDeveloper/xml/AllResources/OOAnalysisDesign/PhysicsProcesses
- Property svn:ignore set to
  CVS
trunk/documents/UserDoc/DocBookUsersGuides/ForToolkitDeveloper/xml/AllResources/OOAnalysisDesign/PhysicsProcesses/ElectroMagnetic
- Property svn:ignore set to
  CVS
trunk/documents/UserDoc/DocBookUsersGuides/ForToolkitDeveloper/xml/AllResources/OOAnalysisDesign/PhysicsProcesses/Hadronic
- Property svn:ignore set to
  CVS
trunk/documents/UserDoc/DocBookUsersGuides/ForToolkitDeveloper/xml/AllResources/OOAnalysisDesign/Tracking
- Property svn:ignore set to
  CVS
trunk/documents/UserDoc/DocBookUsersGuides/ForToolkitDeveloper/xml/AllResources/OOAnalysisDesign/UserInterface
- Property svn:ignore set to
  CVS
trunk/documents/UserDoc/DocBookUsersGuides/ForToolkitDeveloper/xml/Bibliography
- Property svn:ignore set to
  CVS

trunk/documents/UserDoc/DocBookUsersGuides/ForToolkitDeveloper/xml/BookForToolDev.xml

-                      r921
+                      r1208
   </authorgroup>
   <pubdate>19 December, 2008</pubdate>
   <releaseinfo>Version: geant4 9.2</releaseinfo>
+  <pubdate>2 June, 2009</pubdate>
+  <releaseinfo>Version: geant4 9.2 Revision01</releaseinfo>
 </bookinfo>

trunk/documents/UserDoc/DocBookUsersGuides/ForToolkitDeveloper/xml/GuideToExtendFunctionality
- Property svn:ignore set to
  CVS
trunk/documents/UserDoc/DocBookUsersGuides/ForToolkitDeveloper/xml/GuideToExtendFunctionality/ElectromagneticField
- Property svn:ignore set to
  CVS
trunk/documents/UserDoc/DocBookUsersGuides/ForToolkitDeveloper/xml/GuideToExtendFunctionality/Geometry
- Property svn:ignore set to
  CVS
trunk/documents/UserDoc/DocBookUsersGuides/ForToolkitDeveloper/xml/GuideToExtendFunctionality/HadronicPhysics
- Property svn:ignore set to
  CVS

trunk/documents/UserDoc/DocBookUsersGuides/ForToolkitDeveloper/xml/GuideToExtendFunctionality/HadronicPhysics/hadronics.xml

-                      r921
+                      r1208
   <imageobject role="fo">
     <imagedata fileref="./AllResources/GuideToExtendFunctionality/HadronicPhysics/Level1.jpg"
                format="JPG" align="center" contentwidth="10.0cm" />
+               format="JPG" contentwidth="10.0cm" align="center"  />
   </imageobject>
   <imageobject role="html">
     <imagedata fileref="./AllResources/GuideToExtendFunctionality/HadronicPhysics/Level1.jpg"
                format="JPG" align="center" />
+               format="JPG" contentwidth="120%" align="center" />
   </imageobject>
 </mediaobject>
 …
   <imageobject role="fo">
     <imagedata fileref="./AllResources/GuideToExtendFunctionality/HadronicPhysics/Level2_1.jpg"
                format="JPG" align="center" contentwidth="10.0cm" />
+               format="JPG" contentwidth="10.0cm" align="center" />
   </imageobject>
   <imageobject role="html">
     <imagedata fileref="./AllResources/GuideToExtendFunctionality/HadronicPhysics/Level2_1.jpg"
                format="JPG" align="center" />
+               format="JPG" contentwidth="120%" align="center" />
   </imageobject>
 </mediaobject>
 …
   <imageobject role="fo">
     <imagedata fileref="./AllResources/GuideToExtendFunctionality/HadronicPhysics/Level2_2.jpg"
                format="JPG" align="center" contentwidth="10.0cm" />
+               format="JPG" contentwidth="10.0cm" align="center" />
   </imageobject>
   <imageobject role="html">
     <imagedata fileref="./AllResources/GuideToExtendFunctionality/HadronicPhysics/Level2_2.jpg"
                format="JPG" align="center" />
+               format="JPG" contentwidth="120%" align="center" />
   </imageobject>
 </mediaobject>
 …
   <imageobject role="fo">
     <imagedata fileref="./AllResources/GuideToExtendFunctionality/HadronicPhysics/Level2_3.jpg"
                format="JPG" align="center" contentwidth="10.0cm" />
+               format="JPG" contentwidth="10.0cm" align="center" />
   </imageobject>
   <imageobject role="html">
     <imagedata fileref="./AllResources/GuideToExtendFunctionality/HadronicPhysics/Level2_3.jpg"
                format="JPG" align="center" />
+               format="JPG" contentwidth="120%" align="center" />
   </imageobject>
 </mediaobject>
 …
   <imageobject role="fo">
     <imagedata fileref="./AllResources/GuideToExtendFunctionality/HadronicPhysics/Level3_1.jpg"
                format="JPG" align="center" contentwidth="10.0cm" />
+               format="JPG" contentwidth="10.0cm" align="center" />
   </imageobject>
   <imageobject role="html">
     <imagedata fileref="./AllResources/GuideToExtendFunctionality/HadronicPhysics/Level3_1.jpg"
                format="JPG" align="center" />
+               format="JPG" contentwidth="120%" align="center" />
   </imageobject>
 </mediaobject>
 …
   <imageobject role="fo">
     <imagedata fileref="./AllResources/GuideToExtendFunctionality/HadronicPhysics/Level4_1.jpg"
                format="JPG" align="center" contentwidth="10.0cm" />
+               format="JPG" contentwidth="10.0cm" align="center" />
   </imageobject>
   <imageobject role="html">
     <imagedata fileref="./AllResources/GuideToExtendFunctionality/HadronicPhysics/Level4_1.jpg"
                format="JPG" align="center" />
+               format="JPG" contentwidth="120%" align="center" />
   </imageobject>
 </mediaobject>
 …
   <imageobject role="fo">
     <imagedata fileref="./AllResources/GuideToExtendFunctionality/HadronicPhysics/Level4_2.jpg"
                format="JPG" align="center" contentwidth="10.0cm" />
+               format="JPG" contentwidth="10.0cm" align="center" />
   </imageobject>
   <imageobject role="html">
     <imagedata fileref="./AllResources/GuideToExtendFunctionality/HadronicPhysics/Level4_2.jpg"
                format="JPG" align="center" />
+               format="JPG" contentwidth="120%" align="center" />
   </imageobject>
 </mediaobject>
 …
   <imageobject role="fo">
     <imagedata fileref="./AllResources/GuideToExtendFunctionality/HadronicPhysics/Level5_1.jpg"
                format="JPG" align="center" contentwidth="10.0cm" />
+               format="JPG" contentwidth="10.0cm" align="center" />
   </imageobject>
   <imageobject role="html">
     <imagedata fileref="./AllResources/GuideToExtendFunctionality/HadronicPhysics/Level5_1.jpg"
                format="JPG" align="center" />
+               format="JPG" contentwidth="120%" align="center" />
   </imageobject>
 </mediaobject>

trunk/documents/UserDoc/DocBookUsersGuides/ForToolkitDeveloper/xml/GuideToExtendFunctionality/Particles
- Property svn:ignore set to
  CVS
trunk/documents/UserDoc/DocBookUsersGuides/ForToolkitDeveloper/xml/GuideToExtendFunctionality/PhysicsProcesses
- Property svn:ignore set to
  CVS
trunk/documents/UserDoc/DocBookUsersGuides/ForToolkitDeveloper/xml/GuideToExtendFunctionality/Visualization
- Property svn:ignore set to
  CVS

trunk/documents/UserDoc/DocBookUsersGuides/ForToolkitDeveloper/xml/GuideToExtendFunctionality/Visualization/visualization.xml

r921	r1208
30	30	<imageobject role="html">
31	31	<imagedata fileref="./AllResources/GuideToExtendFunctionality/Visualization/visClassDiagram.jpg"
32		format="JPG" ~~align="center" scale="110~~" />
	32	format="JPG" contentwidth="120%" align="center" />
33	33	</imageobject>
34	34	</mediaobject>

trunk/documents/UserDoc/DocBookUsersGuides/ForToolkitDeveloper/xml/Introduction
- Property svn:ignore set to
  CVS
trunk/documents/UserDoc/DocBookUsersGuides/ForToolkitDeveloper/xml/OOAnalysisDesign
- Property svn:ignore set to
  CVS
trunk/documents/UserDoc/DocBookUsersGuides/ForToolkitDeveloper/xml/OOAnalysisDesign/ElectromagneticField
- Property svn:ignore set to
  CVS

trunk/documents/UserDoc/DocBookUsersGuides/ForToolkitDeveloper/xml/OOAnalysisDesign/ElectromagneticField/electroMagneticField.xml

r921	r1208
25	25	<imageobject role="html">
26	26	<imagedata fileref="./AllResources/OOAnalysisDesign/ElectromagneticField/field-prop.jpg"
27		format="JPG" align="center" />
	27	format="JPG" contentwidth="120%" align="center" />
28	28	</imageobject>
29	29	</mediaobject>

trunk/documents/UserDoc/DocBookUsersGuides/ForToolkitDeveloper/xml/OOAnalysisDesign/Event
- Property svn:ignore set to
  CVS

trunk/documents/UserDoc/DocBookUsersGuides/ForToolkitDeveloper/xml/OOAnalysisDesign/Event/event.xml

-                      r921
+                      r1208
   <imageobject role="html">
     <imagedata fileref="./AllResources/OOAnalysisDesign/Event/classDgmEventManager.jpg"
                format="JPG" align="center" />
+               format="JPG" contentwidth="120%" align="center" />
   </imageobject>
 </mediaobject>
 …
   <imageobject role="html">
     <imagedata fileref="./AllResources/OOAnalysisDesign/Event/classDgmEventGen.jpg"
                format="JPG" align="center" />
+               format="JPG" contentwidth="120%" align="center" />
   </imageobject>
 </mediaobject>

trunk/documents/UserDoc/DocBookUsersGuides/ForToolkitDeveloper/xml/OOAnalysisDesign/Geometry
- Property svn:ignore set to
  CVS

trunk/documents/UserDoc/DocBookUsersGuides/ForToolkitDeveloper/xml/OOAnalysisDesign/Geometry/geometry.xml

-                      r921
+                      r1208
   </imageobject>
   <imageobject role="html">
     <imagedata fileref="./AllResources/OOAnalysisDesign/Geometry/overall.jpg" format="JPG" align="center" />
+    <imagedata fileref="./AllResources/OOAnalysisDesign/Geometry/overall.jpg" format="JPG" contentwidth="140%" align="center" />
   </imageobject>
 </mediaobject>
 …
   </imageobject>
   <imageobject role="html">
     <imagedata fileref="./AllResources/OOAnalysisDesign/Geometry/smart_voxels.jpg" format="JPG" align="center" />
+    <imagedata fileref="./AllResources/OOAnalysisDesign/Geometry/smart_voxels.jpg" format="JPG" contentwidth="120%" align="center" />
   </imageobject>
 </mediaobject>
 …
   </imageobject>
   <imageobject role="html">
     <imagedata fileref="./AllResources/OOAnalysisDesign/Geometry/navigator.jpg" format="JPG" align="center" />
+    <imagedata fileref="./AllResources/OOAnalysisDesign/Geometry/navigator.jpg" format="JPG" contentwidth="120%" align="center" />
   </imageobject>
 </mediaobject>

trunk/documents/UserDoc/DocBookUsersGuides/ForToolkitDeveloper/xml/OOAnalysisDesign/GlobalUsage
- Property svn:ignore set to
  CVS

trunk/documents/UserDoc/DocBookUsersGuides/ForToolkitDeveloper/xml/OOAnalysisDesign/GlobalUsage/globalUsage.xml

-                      r921
+                      r1208
   <imageobject role="html">
     <imagedata fileref="./AllResources/OOAnalysisDesign/GlobalUsage/classDgmRandom.jpg"
                format="JPG" align="center" />
+               format="JPG" contentwidth="120%" align="center" />
   </imageobject>
 </mediaobject>
 …
   <imageobject role="html">
     <imagedata fileref="./AllResources/OOAnalysisDesign/GlobalUsage/ObjDiagStat.jpg"
                format="JPG" align="center" />
+               format="JPG" contentwidth="120%" align="center" />
   </imageobject>
 </mediaobject>
 …
   <imageobject role="html">
     <imagedata fileref="./AllResources/OOAnalysisDesign/GlobalUsage/ObjDiagDist.jpg"
                format="JPG" align="center" />
+               format="JPG" contentwidth="120%" align="center" />
   </imageobject>
 </mediaobject>
 …
   <imageobject role="html">
     <imagedata fileref="./AllResources/OOAnalysisDesign/GlobalUsage/ObjDiagEng.jpg"
                format="JPG" align="center" />
+               format="JPG" contentwidth="120%" align="center" />
   </imageobject>
 </mediaobject>

trunk/documents/UserDoc/DocBookUsersGuides/ForToolkitDeveloper/xml/OOAnalysisDesign/Hit
- Property svn:ignore set to
  CVS

trunk/documents/UserDoc/DocBookUsersGuides/ForToolkitDeveloper/xml/OOAnalysisDesign/Hit/hit.xml

-                      r921
+                      r1208
   </imageobject>
   <imageobject role="html">
     <imagedata fileref="./AllResources/OOAnalysisDesign/Hit/classDgmHitMain.jpg" format="JPG" align="center" />
+    <imagedata fileref="./AllResources/OOAnalysisDesign/Hit/classDgmHitMain.jpg" format="JPG" contentwidth="120%" align="center" />
   </imageobject>
 </mediaobject>
 …
   </imageobject>
   <imageobject role="html">
     <imagedata fileref="./AllResources/OOAnalysisDesign/Hit/classDgmHitUser.jpg" format="JPG" align="center" />
+    <imagedata fileref="./AllResources/OOAnalysisDesign/Hit/classDgmHitUser.jpg" format="JPG" contentwidth="120%" align="center" />
   </imageobject>
 </mediaobject>
 …
   </imageobject>
   <imageobject role="html">
     <imagedata fileref="./AllResources/OOAnalysisDesign/Hit/classDgmReadoutGeom.jpg" format="JPG" align="center" />
+    <imagedata fileref="./AllResources/OOAnalysisDesign/Hit/classDgmReadoutGeom.jpg" format="JPG" contentwidth="120%" align="center" />
   </imageobject>
 </mediaobject>

trunk/documents/UserDoc/DocBookUsersGuides/ForToolkitDeveloper/xml/OOAnalysisDesign/Introduction
- Property svn:ignore set to
  CVS
trunk/documents/UserDoc/DocBookUsersGuides/ForToolkitDeveloper/xml/OOAnalysisDesign/Materials
- Property svn:ignore set to
  CVS

trunk/documents/UserDoc/DocBookUsersGuides/ForToolkitDeveloper/xml/OOAnalysisDesign/Materials/materials.xml

r921	r1208
63	63	<imageobject role="html">
64	64	<imagedata fileref="./AllResources/OOAnalysisDesign/Materials/classDgmMaterials.jpg"
65		format="JPG" align="center" />
	65	format="JPG" contentwidth="120%" align="center" />
66	66	</imageobject>
67	67	</mediaobject>

trunk/documents/UserDoc/DocBookUsersGuides/ForToolkitDeveloper/xml/OOAnalysisDesign/Particles
- Property svn:ignore set to
  CVS

trunk/documents/UserDoc/DocBookUsersGuides/ForToolkitDeveloper/xml/OOAnalysisDesign/Particles/particles.xml

-                      r921
+                      r1208
   <imageobject role="html">
     <imagedata fileref="./AllResources/OOAnalysisDesign/Particles/classDgmParticlesMain.jpg"
                format="JPG" align="center" />
+               format="JPG" contentwidth="120%" align="center" />
   </imageobject>
 </mediaobject>
 …
   <imageobject role="html">
     <imagedata fileref="./AllResources/OOAnalysisDesign/Particles/classDgmParticleTable.jpg"
                format="JPG" align="center" />
+               format="JPG" contentwidth="120%" align="center" />
   </imageobject>
 </mediaobject>
 …
   <imageobject role="html">
     <imagedata fileref="./AllResources/OOAnalysisDesign/Particles/classDgmParticleDecay.jpg"
                format="JPG" align="center" />
+               format="JPG" contentwidth="120%" align="center" />
   </imageobject>
 </mediaobject>

trunk/documents/UserDoc/DocBookUsersGuides/ForToolkitDeveloper/xml/OOAnalysisDesign/PhysicsProcesses
- Property svn:ignore set to
  CVS

trunk/documents/UserDoc/DocBookUsersGuides/ForToolkitDeveloper/xml/OOAnalysisDesign/PhysicsProcesses/physicsProcesses.xml

-                      r921
+                      r1208
   <imageobject role="html">
     <imagedata fileref="./AllResources/OOAnalysisDesign/PhysicsProcesses/classDgmProcessMain.jpg"
                format="JPG" align="center" />
+               format="JPG" contentwidth="120%" align="center" />
   </imageobject>
 </mediaobject>
 …
   <imageobject role="html">
     <imagedata fileref="./AllResources/OOAnalysisDesign/PhysicsProcesses/classDgmProcessProcesses.jpg"
                format="JPG" align="center" />
+               format="JPG" contentwidth="120%" align="center" />
   </imageobject>
 </mediaobject>

trunk/documents/UserDoc/DocBookUsersGuides/ForToolkitDeveloper/xml/OOAnalysisDesign/Run
- Property svn:ignore set to
  CVS
trunk/documents/UserDoc/DocBookUsersGuides/ForToolkitDeveloper/xml/OOAnalysisDesign/Tracking
- Property svn:ignore set to
  CVS

trunk/documents/UserDoc/DocBookUsersGuides/ForToolkitDeveloper/xml/OOAnalysisDesign/Tracking/tracking.xml

r921	r1208
100	100	<imageobject role="html">
101	101	<imagedata fileref="./AllResources/OOAnalysisDesign/Tracking/classDgmTracking.jpg"
102		format="JPG" align="center" />
	102	format="JPG" contentwidth="120%" align="center" />
103	103	</imageobject>
104	104	</mediaobject>

trunk/documents/UserDoc/DocBookUsersGuides/ForToolkitDeveloper/xml/OOAnalysisDesign/UserInterface
- Property svn:ignore set to
  CVS

trunk/documents/UserDoc/DocBookUsersGuides/ForToolkitDeveloper/xml/OOAnalysisDesign/UserInterface/userInterface.xml

r921	r1208
94	94	<imageobject role="html">
95	95	<imagedata fileref="./AllResources/OOAnalysisDesign/UserInterface/classDgmUserInterface.jpg"
96		format="JPG" align="center" />
	96	format="JPG" contentwidth="120%" align="center" />
97	97	</imageobject>
98	98	</mediaobject>

trunk/documents/UserDoc/DocBookUsersGuides/ForToolkitDeveloper/xml/OOAnalysisDesign/Visualization
- Property svn:ignore set to
  CVS
trunk/documents/UserDoc/DocBookUsersGuides/ForToolkitDeveloper/xml/UserRequirementsDocument
- Property svn:ignore set to
  CVS
trunk/documents/UserDoc/DocBookUsersGuides/ForToolkitDeveloper/xml/XSLCustomizationLayer
- Property svn:ignore set to
  CVS
trunk/documents/UserDoc/DocBookUsersGuides/InstallationGuide
- Property svn:ignore set to
  CVS
trunk/documents/UserDoc/DocBookUsersGuides/InstallationGuide/xml
- Property svn:ignore set to
  CVS
trunk/documents/UserDoc/DocBookUsersGuides/InstallationGuide/xml/AllResources
- Property svn:ignore set to
  CVS
trunk/documents/UserDoc/DocBookUsersGuides/InstallationGuide/xml/AllResources/IconsGIF
- Property svn:ignore set to
  CVS
trunk/documents/UserDoc/DocBookUsersGuides/InstallationGuide/xml/Introduction
- Property svn:ignore set to
  CVS
trunk/documents/UserDoc/DocBookUsersGuides/InstallationGuide/xml/PCMachines
- Property svn:ignore set to
  CVS
trunk/documents/UserDoc/DocBookUsersGuides/InstallationGuide/xml/UnixMachines
- Property svn:ignore set to
  CVS
trunk/documents/UserDoc/DocBookUsersGuides/InstallationGuide/xml/XSLCustomizationLayer
- Property svn:ignore set to
  CVS
trunk/documents/UserDoc/DocBookUsersGuides/IntroductionToGeant4
- Property svn:ignore set to
  CVS
trunk/documents/UserDoc/DocBookUsersGuides/IntroductionToGeant4/xml
- Property svn:ignore set to
  CVS
trunk/documents/UserDoc/DocBookUsersGuides/IntroductionToGeant4/xml/AllResources
- Property svn:ignore set to
  CVS
trunk/documents/UserDoc/DocBookUsersGuides/IntroductionToGeant4/xml/AllResources/.ls
- Property svn:ignore set to
  CVS
trunk/documents/UserDoc/DocBookUsersGuides/IntroductionToGeant4/xml/AllResources/Fundamentals
- Property svn:ignore set to
  CVS
trunk/documents/UserDoc/DocBookUsersGuides/IntroductionToGeant4/xml/AllResources/IconsGIF
- Property svn:ignore set to
  CVS
trunk/documents/UserDoc/DocBookUsersGuides/IntroductionToGeant4/xml/Introduction
- Property svn:ignore set to
  CVS
trunk/documents/UserDoc/DocBookUsersGuides/IntroductionToGeant4/xml/XSLCustomizationLayer
- Property svn:ignore set to
  CVS

Note: See TracChangeset for help on using the changeset viewer.

Context Navigation

Changeset 1208 for trunk/documents

Legend:

Download in other formats: