- Timestamp:
- Feb 16, 2009, 10:14:30 AM (15 years ago)
- Location:
- trunk/documents/UserDoc/DocBookUsersGuides/ForApplicationDeveloper/xml
- Files:
-
- 16 edited
Legend:
- Unmodified
- Added
- Removed
-
trunk/documents/UserDoc/DocBookUsersGuides/ForApplicationDeveloper/xml/Appendix/Appendix.xml
r904 r921 25 25 &appbuildFile; 26 26 &appdevelopmentDebugTools; 27 &apppythonInterface; 27 28 &appmaterialNames; 28 29 -
trunk/documents/UserDoc/DocBookUsersGuides/ForApplicationDeveloper/xml/Appendix/AppendixEntityDef.dtd
r904 r921 19 19 <!ENTITY appmakeFile SYSTEM "./makeFile.xml"> 20 20 <!ENTITY appbuildFile SYSTEM "./buildFile.xml"> 21 <!ENTITY apppythonInterface SYSTEM "./pythonInterface.xml"> 21 22 <!ENTITY appdevelopmentDebugTools SYSTEM "./developmentDebugTools.xml"> 22 23 -
trunk/documents/UserDoc/DocBookUsersGuides/ForApplicationDeveloper/xml/BookForAppliDev.xml
r904 r921 4 4 <!ENTITY % bookForAppliDevEntityDef SYSTEM "./BookForAppliDevEntityDef.dtd"> 5 5 %bookForAppliDevEntityDef; 6 6 7 ]> 7 8 … … 30 31 </authorgroup> 31 32 32 <pubdate>1 4 December, 2007</pubdate>33 <releaseinfo>Version: geant4 9. 1</releaseinfo>33 <pubdate>19 December, 2008</pubdate> 34 <releaseinfo>Version: geant4 9.2</releaseinfo> 34 35 35 36 </bookinfo> -
trunk/documents/UserDoc/DocBookUsersGuides/ForApplicationDeveloper/xml/Fundamentals/biasing.xml
r904 r921 610 610 <mediaobject> 611 611 <imageobject role="fo"> 612 <imagedata fileref="./AllResources/Fundamentals/wwconcept. gif"613 format=" GIF" contentwidth="9.0cm" align="center" />612 <imagedata fileref="./AllResources/Fundamentals/wwconcept.jpg" 613 format="JPG" contentwidth="9.0cm" align="center" /> 614 614 </imageobject> 615 615 <imageobject role="html"> 616 <imagedata fileref="./AllResources/Fundamentals/wwconcept. gif"617 format=" GIF" align="center" />616 <imagedata fileref="./AllResources/Fundamentals/wwconcept.jpg" 617 format="JPG" align="center" /> 618 618 </imageobject> 619 619 <textobject> -
trunk/documents/UserDoc/DocBookUsersGuides/ForApplicationDeveloper/xml/Fundamentals/classCategory.xml
r905 r921 58 58 <mediaobject> 59 59 <imageobject role="fo"> 60 <imagedata fileref="./AllResources/Fundamentals/classCategory. gif"61 format=" GIF" contentwidth="7.0cm" align="center" />60 <imagedata fileref="./AllResources/Fundamentals/classCategory.jpg" 61 format="JPG" contentwidth="7.0cm" align="center" /> 62 62 </imageobject> 63 63 <imageobject role="html"> 64 <imagedata fileref="./AllResources/Fundamentals/classCategory. gif"65 format=" GIF" align="center" />64 <imagedata fileref="./AllResources/Fundamentals/classCategory.jpg" 65 format="JPG" align="center" /> 66 66 </imageobject> 67 67 </mediaobject> -
trunk/documents/UserDoc/DocBookUsersGuides/ForApplicationDeveloper/xml/GettingStarted/graphicalUserInterface.xml
r904 r921 29 29 The "intercoms" category 30 30 provides an expandable command interpreter. It is the key mechanism 31 of Geant4 to realize user interactions of all categories without31 of Geant4 to realize secure user interactions of all categories without 32 32 being annoyed by the dependencies among categories. The direct use 33 33 of Geant4 classes in a C++ program offers a first ground level of … … 36 36 hard-coded in the program. 37 37 </para> 38 39 38 40 39 41 </sect3> … … 52 54 the interfaces category. This interfacing strategy opens an 53 55 important door towards various user interface tools and allows 54 Geant4 to utilize the state-of-the-art GUI tools such as Motif and55 Java,etc..The richness of the collaboration has permitted for56 d ifferent groups to offer various user interfaces to the Geant456 Geant4 to utilize the state-of-the-art GUI tools such as Motif, Qt, 57 and Java etc..The richness of the collaboration has permitted for 58 developers to offer various user interfaces to the Geant4 57 59 command system. Currently available are the following; 58 60 … … 67 69 </para></listitem> 68 70 <listitem><para> 69 GAG, a fully Graphical User Interface and its extension71 GAG, a fully Graphical User Interface and its network extension 70 72 GainServer of the client/server type. 71 73 </para></listitem> … … 76 78 Full implementation of the character 77 79 terminals (1 and 2) is included in the standard Geant4 distribution 78 in the <literal>source/interfaces/basic</literal> directory. As for GAG 79 with rich GUI functionalities, its front-end classes are included 80 in the Geant4 distribution in the source/interfaces/GAG directory. 81 The corresponding GUI package is available either from the author's 82 Web pages (see URL below) or in the distributed package under the 83 <literal>environments/MOMO</literal> directory. 80 in the <literal>source/interfaces/basic</literal> directory. As for GAG, 81 the front-end class is included 82 in the Geant4 distribution in the source/interfaces/GAG directory, 83 while its partner GUI package MOMO.jar is available in the standard Geant4 distribution 84 under the 85 <literal>environments/MOMO</literal> directory. MOMO.jar, Java archive file, contains 86 not only GAG, but also GGE and other helper packages. 87 Supplementary information is available 88 from the author's Webpage(see URL below). 84 89 </para> 85 90 86 91 <para> 87 92 GAG, GainServer's client GUI Gain: 88 <ulink url="http:// erpc1.naruto-u.ac.jp/~geant4">89 http:// erpc1.naruto-u.ac.jp/~geant493 <ulink url="http://www-geant4.kek.jp/~yoshidah"> 94 http://www-geant4.kek.jp/~yoshidah 90 95 </ulink> 91 96 </para> … … 238 243 A command box is at disposal for entering or recalling Geant4 commands. 239 244 Command completion by typing &ldquo;TAB&rdquo; key is 240 available on the command line. The shell commands "exit, cont,245 available on the command line. The shell commands "exit, cont, 241 246 help, ls, cd..." are also supported. A menu bar could be customized 242 247 through the <emphasis>AddMenu</emphasis> and … … 287 292 288 293 <para> 289 They are the front-end classes of Geant4 which interfacewith their290 respective graphical user interfaces, GAG (Geant4 Adaptive GUI) and Gain291 (Geant4 adaptive interface for network) . While GAG must run on the same294 They are the front-end classes of Geant4 which make connection with their 295 respective graphical user interfaces, GAG (Geant4 Adaptive GUI) via pipe, and Gain 296 (Geant4 adaptive interface for network) via sockets. While GAG must run on the same 292 297 system (Windows or Unixen) as a Geant4 application, Gain can run on a 293 remote system (Windows, Linux, etc.) to which JVM (Java Virtual294 Machine) is installed. A Geant4 application is invoked on a Unix298 remote system (Windows, Linux, etc.) in which JRE (Java Runtime 299 Environment) is installed. A Geant4 application is invoked on a Unix 295 300 (Linux) system and behaves as a network server. It opens a port, 296 301 waiting the connection from the Gain. Gain is capable to connect to … … 300 305 301 306 <para> 302 Client GUI, GAG and Gain have almost similar look-and-feel. So, 303 GAG's functionalities are briefly introduced here. Please refer to 304 the above URL for details and to download the client GUIs. 305 </para> 306 307 <para> 308 GAG is a Graphical User Interface tool with which user 309 can set parameters and execute commands. It is adaptive, since GAG 310 reflects the internal states of Geant4 that is a state machine. GAG 311 is based on the server-client model; GAG is the server, while 312 Geant4 executables are clients. Hence, GAG does nothing by itself 313 and it must invoke an executable simulation program. Geant4's 307 Client GUIs, GAG and Gain have almost similar look-and-feel. So, 308 GAG's functionalities are briefly explained here. Please refer to 309 the above URL for details. 310 </para> 311 312 <para> 313 Using GAG, user 314 can select a command, set its parameters and execute it. It is adaptive, in the sense that it 315 reflects the internal states of Geant4 that is a state machine. So, GAG always provides users with 316 the Geant4 commands which may be added, deleted, enabled or disabled during a session. GAG does nothing by itself but to play an intermediate between user and 317 an executable simulation program via pipes. Geant4's 314 318 front-end class <emphasis>G4UIGAG</emphasis> must be instantiated to 315 communicate with GAG. This runs on Linux and Windows 2000. 316 GAG is written in Java and 317 its Jar (Java Archive) file is available from the above URL. See 318 the same pages to know how to install and run Java programs. 319 </para> 319 communicate with GAG. GAG runs on Linux and Windows. If MOMO.jar is in your 320 CLASSPATH, it can be run by a command; 321 </para> 322 323 <informalexample> 324 <programlisting> 325 %java -jar MOMO.jar 326 </programlisting> 327 </informalexample> 320 328 321 329 <para> … … 329 337 a GEANT4 process and to exit GAG. Upon the normal exit or an 330 338 unexpected death of the Geant4 process, GAG window are 331 automatically reset to acceptanother GEANT4 executable.339 automatically reset to run another GEANT4 executable. 332 340 </listitem> 333 341 </varlistentry> … … 335 343 <term>GEANT4 Command tree:</term> 336 344 <listitem> 337 Upon the establishment of the pipe with the GEANT4 process, GAG displays338 the command menu tree whose look and feel is quitesimilar to339 Windows' file browser. Disabled commands are shown opaque. GAG345 Upon the establishment of the pipe connection with the GEANT4 process, GAG displays 346 the command menu, using expandable tree browser whose look and feel is similar to 347 a file browser. Disabled commands are shown in opaque. GAG 340 348 doesn &rsquo;t display commands that are just below the root of 341 349 the command hierarchy. Direct type-in field is available for such … … 364 372 Log can be redirected to the terminal (xterm or cygwin 365 373 window) from which GAG is invoked. It can be interrupted as will, 366 in the middle of long session of execution. Log can be saved to a374 in the middle of a long session of execution. Log can be saved to a 367 375 file independent of the above redirection . GAG displays warning or 368 376 error messages from GEANT4 in a pop-up warning widget. … … 383 391 384 392 <para> 385 The libraries that don't depend on external packages are made by default. 393 The libraries that don't depend on external packages are created by default, using 394 Geant4 configure scripts. 386 395 They include <emphasis>G4UIterminal</emphasis>, <emphasis>G4UItcsh</emphasis> 387 396 and <emphasis>G4UIGAG</emphasis> in libraries <emphasis>libG4UIbasic.a/so</emphasis> and … … 396 405 <emphasis role="bold">G4UI_BUILD_XAW_SESSION</emphasis> or 397 406 <emphasis role="bold">G4UI_BUILD_WIN32_SESSION</emphasis> must be set 398 explicitly .407 explicitly before creating libraries. 399 408 </para> 400 409 … … 405 414 406 415 <para> 407 Build scheme ofthe user interface libraries is416 The scheme of building the user interface libraries is 408 417 specified in "$G4INSTALL/config/G4UI_BUILD.gmk" makefile and the 409 418 dependencies on the external packages are specified in … … 416 425 <sect2 id="sect.HowToSetUpInter.HowToUseInter"> 417 426 <title> 418 How to Use the Interface 427 How to Use the Interface in Your Application 419 428 </title> 420 429 … … 422 431 To use a given interface 423 432 (<literal>G4UIxxx</literal> where <literal>xxx = terminal,Xm, Xaw, Win32, 424 GAG, GainServer</literal>) in a user's program, he has thefollowing425 lines in hismain program;433 GAG, GainServer</literal>) in your program, you have following 434 lines in your main program; 426 435 427 436 <informalexample> 428 437 <programlisting> 429 // to include the class definition in hismain program:438 // to include the class definition in the main program: 430 439 #include "G4Uixxx.hh" 431 // to instantiate a session of hischoice and start the session440 // to instantiate a session of your choice and start the session 432 441 G4UIsession* session = new G4UIxxx; 433 442 session->SessionStart(); 434 // the line next to the "SessionStart" is usually to finish the session443 // the line next to the "SessionStart" is necessary to finish the session 435 444 delete session; 436 445 </programlisting> … … 466 475 467 476 <para> 468 Again, environment variable selectsa given interface. But for your469 convenience, some of them are set defaults.477 Again, environment variable must be preset to select a given interface. But for your 478 convenience, some of them are set by defaults. 470 479 471 480 <itemizedlist spacing="compact"> … … 473 482 <emphasis>G4UIterminal</emphasis>, <emphasis>G4UItcsh</emphasis>, 474 483 <emphasis>G4UIGAG</emphasis> and <emphasis>G4UIGainServer</emphasis> 475 can be used without any environment484 can be used without setting any environment 476 485 variables. Sessions not needing external packages or libraries are 477 486 always built (see "G4UI_BUILD.gmk") and linked, so the user can … … 497 506 <listitem><para> 498 507 If the environment variable <emphasis role="bold">G4UI_NONE</emphasis> is 499 set, no externa 508 set, no external libraries are selected. Also, for your convenience, if any 500 509 <emphasis role="bold">G4UI_USE_XXX</emphasis> environment variable is set, 501 510 then the corresponding C-pre-processor flag is also set. However, if the -
trunk/documents/UserDoc/DocBookUsersGuides/ForApplicationDeveloper/xml/GettingStarted/visualization.xml
r905 r921 2 2 <!-- --> 3 3 <!-- [History] --> 4 <!-- Update HepRApp reference: Joseph Perl, Dec-2008 --> 4 5 <!-- Converted to DocBook: Katsuya Amako, Aug-2006 --> 5 6 <!-- Changed by: Katsuya Amako, 30-Nov-1998 --> … … 72 73 graphics systems use a graphics library compiled with Geant4, such 73 74 as OpenGL, Qt or OpenInventor, while others involve a separate application, such as 74 WIREDor DAWN.75 HepRApp or DAWN. 75 76 </para> 76 77 -
trunk/documents/UserDoc/DocBookUsersGuides/ForApplicationDeveloper/xml/TrackingAndPhysics/physicsProcess.xml
r904 r921 360 360 361 361 <para> 362 This section summarizes the electromagnetic physics processes which 363 are installed in Geant4. For details on the implementation of these 362 This section summarizes the electromagnetic (EM) physics processes which 363 are provided with Geant4. Extended information are avalable at EM web 364 <ulink url="http://geant4.web.cern.ch/geant4/collaboration/EMindex.shtml"> 365 <emphasis role="bold">pages</emphasis></ulink>. 366 For details on the implementation of these 364 367 processes please refer to the 365 368 <ulink url="http://geant4.web.cern.ch/geant4/UserDocumentation/UsersGuides/PhysicsReferenceManual/html/PhysicsReferenceManual.html"> … … 407 410 </para></listitem> 408 411 <listitem><para> 412 Multiple scattering (class name <emphasis>G4eMultipleScattering</emphasis>) 413 </para></listitem> 414 <listitem><para> 409 415 Positron annihilation into two gammas (class name 410 416 <emphasis>G4eplusAnnihilation</emphasis>) … … 424 430 <itemizedlist spacing="compact"> 425 431 <listitem><para> 432 Bremsstrahlung (class name <emphasis>G4MuBremsstrahlung</emphasis>) 433 </para></listitem> 434 <listitem><para> 426 435 Ionisation and delta ray production (class name 427 436 <emphasis>G4MuIonisation</emphasis>) 428 437 </para></listitem> 429 438 <listitem><para> 430 Bremsstrahlung (class name <emphasis>G4MuBremsstrahlung</emphasis>)439 Multiple scattering (class name <emphasis>G4MuMultipleScattering</emphasis>) 431 440 </para></listitem> 432 441 <listitem><para> … … 440 449 <itemizedlist spacing="compact"> 441 450 <listitem><para> 451 Bremsstrahlung (class name <emphasis>G4hBremsstrahlung</emphasis>) 452 </para></listitem> 453 <listitem><para> 442 454 Ionisation (class name <emphasis>G4hIonisation</emphasis>) 443 455 </para></listitem> 444 456 <listitem><para> 457 e+e- pair production (class name <emphasis>G4hPairProduction</emphasis>) 458 </para></listitem> 459 <listitem><para> 445 460 Ionisation for ions (class name <emphasis>G4ionIonisation</emphasis>) 446 461 </para></listitem> 447 462 <listitem><para> 448 Ionisation for ions in low-density media (class name <emphasis>G4ionGasIonisation</emphasis>)463 Multiple scattering (class name <emphasis>G4hMultipleScattering</emphasis>) 449 464 </para></listitem> 450 465 <listitem><para> … … 465 480 is used to simulate the multiple scattering of the all charged 466 481 particles (class name <emphasis>G4MultipleScattering</emphasis>) 467 </para></listitem>468 <listitem><para>469 Specialised process for more fast simulation the multiple scattering470 of muons and hadrons (class name <emphasis>G4hMultipleScattering</emphasis>)471 </para></listitem>472 <listitem><para>473 Alternative process (beta-version) for the multiple scattering474 of muons (class name <emphasis>G4MuMultipleScattering</emphasis>)475 482 </para></listitem> 476 483 <listitem><para> … … 549 556 550 557 <para> 551 An example of the registration of these processes in a physics list 552 is given in <xref linkend="programlist_PhysProc_1" />, 553 similar method is used in EM-builders of reference physics 554 lists ($G4INSTALL/source/physics_lists/builders) and in 555 EM examples ($G4INSTALL/examples/extended/electromagnetic). 556 557 <example id="programlist_PhysProc_1"> 558 <title> 559 <literal>Registration of standard electromagnetic processes</literal> 560 </title> 561 562 <programlisting> 563 void PhysicsList::ConstructEM() 564 565 { 566 567 theParticleIterator->reset(); 568 569 while( (*theParticleIterator)() ){ 570 571 G4ParticleDefinition* particle = theParticleIterator->value(); 572 G4ProcessManager* pmanager = particle->GetProcessManager(); 573 G4String particleName = particle->GetParticleName(); 574 575 if (particleName == "gamma") { 576 577 pmanager->AddDiscreteProcess(new G4PhotoElectricEffect); 578 pmanager->AddDiscreteProcess(new G4ComptonScattering); 579 pmanager->AddDiscreteProcess(new G4GammaConversion); 580 581 } else if (particleName == "e-") { 582 583 pmanager->AddProcess(new G4MultipleScattering, -1, 1, 1); 584 pmanager->AddProcess(new G4eIonisation, -1, 2, 2); 585 pmanager->AddProcess(new G4eBremsstrahlung, -1, 3, 3); 586 587 } else if (particleName == "e+") { 588 589 pmanager->AddProcess(new G4MultipleScattering, -1, 1, 1); 590 pmanager->AddProcess(new G4eIonisation, -1, 2, 2); 591 pmanager->AddProcess(new G4eBremsstrahlung, -1, 3, 3); 592 pmanager->AddProcess(new G4eplusAnnihilation, 0,-1, 4); 593 594 } else if( particleName == "mu+" || 595 particleName == "mu-" ) { 596 597 pmanager->AddProcess(new G4hMultipleScattering,-1, 1, 1); 598 pmanager->AddProcess(new G4MuIonisation, -1, 2, 2); 599 pmanager->AddProcess(new G4MuBremsstrahlung, -1, 3, 3); 600 pmanager->AddProcess(new G4MuPairProduction, -1, 4, 4); 601 602 } else if (particleName == "alpha" || 603 particleName == "He3" || 604 particleName == "GenericIon") { 605 // ions with charge >= +2 606 pmanager->AddProcess(new G4hMultipleScattering,-1, 1, 1); 607 pmanager->AddProcess(new G4ionIonisation, -1, 2, 2); 608 609 } else if ((!particle->IsShortLived()) && 610 (particle->GetPDGCharge() != 0.0) && 611 (particle->GetParticleName() != "chargedgeantino")) { 612 //all others charged particles except geantino and short-lived 613 pmanager->AddProcess(new G4hMultipleScattering,-1, 1, 1); 614 pmanager->AddProcess(new G4hIonisation, -1, 2, 2); 615 616 } 617 } 618 } 619 </programlisting> 620 </example> 621 </para> 622 623 <para> 558 It is recommended to use physics constructor classes provided 559 with rederence physics lists ($G4INSTALL/source/physics_lists/builders): 560 <itemizedlist spacing="compact"> 561 <listitem><para> 562 default EM physics (class name <emphasis>G4EmStandardPhysics</emphasis>) 563 </para></listitem> 564 <listitem><para> 565 optional EM physics providing similar performance as g4 7.1p01 566 (class name <emphasis>G4EmStandardPhysics_option1</emphasis>) 567 </para></listitem> 568 <listitem><para> 569 Experimental EM physics with enabled "ApplyCuts" option 570 (class name <emphasis>G4EmStandardPhysics_option2</emphasis>) 571 </para></listitem> 572 <listitem><para> 573 EM physics for simulation with high accuracy 574 (class name <emphasis>G4EmStandardPhysics_option3</emphasis>) 575 </para></listitem> 576 </itemizedlist> 577 Examples of the registration of these physics constructor and 578 construction of alternative combinations of options are shown 579 in novice and extended examples ($G4INSTALL/examples/extended/electromagnetic). 624 580 Novice and extended electromagnetic examples illustrating the use 625 581 of electromagnetic processes are available as part of the Geant4 … … 676 632 <listitem><para> 677 633 SetApplyCuts(G4bool) 634 </para></listitem> 635 <listitem><para> 636 SetSpline(G4bool) 678 637 </para></listitem> 679 638 <listitem><para> … … 836 795 The following is a summary of the Low Energy Electromagnetic 837 796 processes available in Geant4. Further information is available in 838 the 839 <ulink url="http://www.ge.infn.it/geant4/lowE/index.html"> 840 homepage 797 the web 798 <ulink url="http://geant4.web.cern.ch/geant4/collaboration/working_groups/LEelectromagnetic/index.shtml">pages 841 799 </ulink> 842 800 of the Geant4 Low Energy Electromagnetic Physics Working Group. … … 845 803 Physics Reference Manual 846 804 </ulink> 847 and in other848 <ulink url="http://www.ge.infn.it/geant4/lowE/papers.html">849 papers</ulink>.850 805 </para> 851 806 … … 899 854 900 855 <para> 901 An example of the registration of these processes in a physics list 902 is given in <xref linkend="programlist_PhysProc_2" />. 903 904 <example id="programlist_PhysProc_2"> 905 <title> 906 Registration of electromagnetic low energy electron/photon processes. 907 </title> 908 909 <programlisting> 910 void LowEnPhysicsList::ConstructEM() 911 { 912 theParticleIterator->reset(); 913 914 while( (*theParticleIterator)() ){ 915 916 G4ParticleDefinition* particle = theParticleIterator->value(); 917 G4ProcessManager* pmanager = particle->GetProcessManager(); 918 G4String particleName = particle->GetParticleName(); 919 920 if (particleName == "gamma") { 921 922 theLEPhotoElectric = new G4LowEnergyPhotoElectric(); 923 theLECompton = new G4LowEnergyCompton(); 924 theLEGammaConversion = new G4LowEnergyGammaConversion(); 925 theLERayleigh = new G4LowEnergyRayleigh(); 926 927 pmanager->AddDiscreteProcess(theLEPhotoElectric); 928 pmanager->AddDiscreteProcess(theLECompton); 929 pmanager->AddDiscreteProcess(theLERayleigh); 930 pmanager->AddDiscreteProcess(theLEGammaConversion); 931 932 } 933 else if (particleName == "e-") { 934 935 theLEIonisation = new G4LowEnergyIonisation(); 936 theLEBremsstrahlung = new G4LowEnergyBremsstrahlung(); 937 theeminusMultipleScattering = new G4MultipleScattering(); 938 939 pmanager->AddProcess(theeminusMultipleScattering,-1,1,1); 940 pmanager->AddProcess(theLEIonisation,-1,2,2); 941 pmanager->AddProcess(theLEBremsstrahlung,-1,-1,3); 942 943 } 944 else if (particleName == "e+") { 945 946 theeplusMultipleScattering = new G4MultipleScattering(); 947 theeplusIonisation = new G4eIonisation(); 948 theeplusBremsstrahlung = new G4eBremsstrahlung(); 949 theeplusAnnihilation = new G4eplusAnnihilation(); 950 951 pmanager->AddProcess(theeplusMultipleScattering,-1,1,1); 952 pmanager->AddProcess(theeplusIonisation,-1,2,2); 953 pmanager->AddProcess(theeplusBremsstrahlung,-1,-1,3); 954 pmanager->AddProcess(theeplusAnnihilation,0,-1,4); 955 } 956 } 957 } 958 </programlisting> 959 </example> 960 </para> 961 962 <para> 963 Advanced <emphasis role="bold">examples</emphasis> illustrating the use of Low Energy 964 Electromagnetic processes are available as part of the Geant4 856 Examples of the registration of physics constructor with low-energy 857 electromagnetic processes are shown 858 in Geant4 extended examples ($G4INSTALL/examples/extended/electromagnetic). 859 <emphasis role="bold">Advanced examples</emphasis> illustrating alternative instantiation 860 of these processes. Both are available as part of the Geant4 965 861 <ulink url="http://geant4.web.cern.ch/geant4/support/download.shtml"> 966 release 967 </ulink> 968 and are further documented 969 <ulink url="http://www.ge.infn.it/geant4/lowE/examples/index.html"> 970 here</ulink>. 862 release</ulink>. 971 863 </para> 972 864 … … 979 871 </emphasis> 980 872 need to be copied by the user to his/her code 981 repository. These files are distributed together with Geant4 982 <ulink url="http://geant4.web.cern.ch/geant4/support/download.shtml"> 983 release</ulink>. 984 </para> 985 986 <para> 873 repository. These files are distributed together with Geant4. 987 874 The user should set the environment variable 988 875 <emphasis role="bold">G4LEDATA</emphasis> to the … … 1039 926 </para></listitem> 1040 927 </itemizedlist> 1041 </para>1042 1043 <para>1044 The available models for ElectronicStoppingPower and1045 NuclearStoppingPower are documented in the1046 <ulink url="http://www.ge.infn.it/geant4/lowE/swprocess/design/">1047 class diagrams</ulink>.1048 928 </para> 1049 929 … … 1090 970 <ulink url="http://geant4.web.cern.ch/geant4/UserDocumentation/UsersGuides/PhysicsReferenceManual/html/PhysicsReferenceManual.html"> 1091 971 Physics Reference Manual 1092 </ulink> 1093 and in the Geant4 Low Energy Electromagnetic Physics Working Group 1094 <ulink url="http://www.ge.infn.it/geant4/lowE/index.html"> 1095 homepage</ulink>. 972 </ulink>. 1096 973 </para> 1097 974 … … 1139 1016 G4PhotoElectricAngularGeneratorSauterGavrilla and 1140 1017 G4PhotoElectricAngularGeneratorPolarized can be set using the 1141 strings "standard" and "polarized". Information regarding 1142 conditions of use, performance and energy limits of different 1143 models are available in the 1144 <ulink url="http://geant4.web.cern.ch/geant4/UserDocumentation/UsersGuides/PhysicsReferenceManual/html/PhysicsReferenceManual.html"> 1145 Physics Reference Manual 1146 </ulink> 1147 and in the Geant4 Low Energy Electromagnetic Physics Working Group 1148 <ulink url="http://www.ge.infn.it/geant4/lowE/index.html"> 1149 homepage</ulink>. 1018 strings "standard" and "polarized". 1150 1019 </para> 1151 1020 … … 1155 1024 <sect3 id="sect.PhysProc.EleMag.VeryLowE"> 1156 1025 <title> 1157 Very Low energy Electromagnetic Processes (Geant4 1026 Very Low energy Electromagnetic Processes (Geant4-DNA extension) 1158 1027 </title> 1159 1028 … … 1162 1031 to energies of a few electronVolts suitable for the simulation of radiation 1163 1032 effects in liquid water for applications at the cellular and sub-cellular 1164 level. These developments take place in the framework of the Geant4 DNA 1165 project 1166 [ 1167 <ulink url="http://www.ge.infn.it/geant4/dna"> 1168 http://www.ge.infn.it/geant4/dna 1169 </ulink> 1170 ] and are fully described in the paper 1033 level. These developments take place in the framework of the Geant4-DNA 1034 project and are described in the paper 1171 1035 <citation> 1172 1036 <xref linkend="biblio.chauvie2007" endterm="biblio.chauvie2007.abbrev" /> … … 1196 1060 <itemizedlist spacing="compact"> 1197 1061 <listitem><para> 1198 Elastic scattering (two complementary models available depending on energy range )1062 Elastic scattering (two complementary models available depending on energy range, and one alternative model) 1199 1063 <itemizedlist spacing="compact"> 1200 1064 <listitem><para> 1201 Cross section policy class name, common to both models : 1202 G4CrossSectionElasticScreenedRutherford 1203 </para></listitem> 1204 <listitem><para> 1205 Final state policy class names : G4FinalStateElasticScreenedRutherford 1206 or G4FinalStateElasticBrennerZaider 1065 - 1) either : cross section policy class names : G4CrossSectionElasticScreenedRutherfordLE (below 200 eV) 1066 and G4CrossSectionElasticScreenedRutherfordHE (above 200 eV). Both should be used together. 1067 - 2) or : cross section policy class name : G4CrossSectionElasticChampion. 1068 </para></listitem> 1069 <listitem><para> 1070 - 1) either : final state policy class names : G4FinalStateElasticBrennerZaider (corresponding to G4CrossSectionElasticScreenedRutherfordLE) 1071 and G4CrossSectionElasticScreenedRutherfordLE (corresponding to G4CrossSectionElasticScreenedRutherfordHE). 1072 - 2) or final state policy class name : G4FinalStateElasticChampion (corresponding to G4CrossSectionElasticChampion). 1207 1073 </para></listitem> 1208 1074 </itemizedlist> … … 1471 1337 #include "G4FinalStateExcitationEmfietzoglou.hh" 1472 1338 1473 #include "G4CrossSectionElasticScreenedRutherford.hh" 1339 #include "G4CrossSectionElasticScreenedRutherfordLE.hh" 1340 #include "G4FinalStateElasticBrennerZaider.hh" 1341 1342 #include "G4CrossSectionElasticScreenedRutherfordHE.hh" 1474 1343 #include "G4FinalStateElasticScreenedRutherford.hh" 1475 #include "G4FinalStateElasticBrennerZaider.hh" 1344 1345 #include "G4CrossSectionElasticChampion.hh" 1346 #include "G4FinalStateElasticChampion.hh" 1476 1347 1477 1348 #include "G4CrossSectionExcitationBorn.hh" … … 1495 1366 // Processes definition 1496 1367 1497 typedef G4DNAProcess<G4CrossSectionElasticScreenedRutherford,G4FinalStateElasticScreenedRutherford> 1498 ElasticScreenedRutherford; 1499 typedef G4DNAProcess<G4CrossSectionElasticScreenedRutherford,G4FinalStateElasticBrennerZaider> 1500 ElasticBrennerZaider; 1368 typedef G4DNAProcess<G4CrossSectionElasticScreenedRutherfordLE,G4FinalStateElasticBrennerZaider> 1369 ElasticScreenedRutherfordLE; 1370 typedef G4DNAProcess<G4CrossSectionElasticScreenedRutherfordHE,G4FinalStateElasticScreenedRutherford> 1371 ElasticScreenedRutherfordHE; 1372 typedef G4DNAProcess<G4CrossSectionElasticChampion,G4FinalStateElasticChampion> 1373 ElasticChampion; 1501 1374 typedef G4DNAProcess<G4CrossSectionExcitationEmfietzoglou,G4FinalStateExcitationEmfietzoglou> 1502 1375 ExcitationEmfietzoglou; … … 1527 1400 1528 1401 if (particleName == "e-") { 1529 processManager->AddDiscreteProcess(new ExcitationEmfietzoglou); 1530 processManager->AddDiscreteProcess(new ElasticScreenedRutherford); 1531 processManager->AddDiscreteProcess(new ElasticBrennerZaider); 1532 processManager->AddDiscreteProcess(new IonisationBorn); 1402 processManager->AddDiscreteProcess(new ExcitationEmfietzoglou("ExcitationEmfietzoglou")); 1403 1404 // The two following elastic scattering models should be registered together 1405 processManager->AddDiscreteProcess(new ElasticScreenedRutherfordLE("ElasticScreenedRutherfordLE")); 1406 processManager->AddDiscreteProcess(new ElasticScreenedRutherfordHE("ElasticScreenedRutherfordHE")); 1407 1408 // The following process is commented here because it is ALTERNATIVE to ElasticScreenedRutherfordLE and ElasticScreenedRutherfordHE 1409 // It should NOT be registered simultaneously with ElasticScreenedRutherfordLE and ElasticScreenedRutherfordHE 1410 // processManager->AddDiscreteProcess(new ElasticChampion("ElasticChampion")); 1411 1412 processManager->AddDiscreteProcess(new IonisationBorn("IonisationBorn")); 1533 1413 1534 1414 } else if ( particleName == "proton" ) { 1535 processManager->AddDiscreteProcess(new ExcitationMillerGreen );1536 processManager->AddDiscreteProcess(new ExcitationBorn );1537 processManager->AddDiscreteProcess(new IonisationRudd );1538 processManager->AddDiscreteProcess(new IonisationBorn );1539 processManager->AddDiscreteProcess(new ChargeDecrease );1415 processManager->AddDiscreteProcess(new ExcitationMillerGreen("ExcitationMillerGreen")); 1416 processManager->AddDiscreteProcess(new ExcitationBorn("ExcitationBorn")); 1417 processManager->AddDiscreteProcess(new IonisationRudd("IonisationRudd")); 1418 processManager->AddDiscreteProcess(new IonisationBorn("IonisationBorn")); 1419 processManager->AddDiscreteProcess(new ChargeDecrease("ChargeDecrease")); 1540 1420 1541 1421 } else if ( particleName == "hydrogen" ) { 1542 processManager->AddDiscreteProcess(new IonisationRudd );1543 processManager->AddDiscreteProcess(new ChargeIncrease );1422 processManager->AddDiscreteProcess(new IonisationRudd("IonisationRudd")); 1423 processManager->AddDiscreteProcess(new ChargeIncrease("ChargeIncrease")); 1544 1424 1545 1425 } else if ( particleName == "alpha" ) { 1546 processManager->AddDiscreteProcess(new ExcitationMillerGreen );1547 processManager->AddDiscreteProcess(new IonisationRudd );1548 processManager->AddDiscreteProcess(new ChargeDecrease );1426 processManager->AddDiscreteProcess(new ExcitationMillerGreen("ExcitationMillerGreen")); 1427 processManager->AddDiscreteProcess(new IonisationRudd("IonisationRudd")); 1428 processManager->AddDiscreteProcess(new ChargeDecrease("ChargeDecrease")); 1549 1429 1550 1430 } else if ( particleName == "alpha+" ) { 1551 processManager->AddDiscreteProcess(new ExcitationMillerGreen );1552 processManager->AddDiscreteProcess(new IonisationRudd );1553 processManager->AddDiscreteProcess(new ChargeDecrease );1554 processManager->AddDiscreteProcess(new ChargeIncrease );1431 processManager->AddDiscreteProcess(new ExcitationMillerGreen("ExcitationMillerGreen")); 1432 processManager->AddDiscreteProcess(new IonisationRudd("IonisationRudd")); 1433 processManager->AddDiscreteProcess(new ChargeDecrease("ChargeDecrease")); 1434 processManager->AddDiscreteProcess(new ChargeIncrease("ChargeIncrease")); 1555 1435 1556 1436 } else if ( particleName == "helium" ) { 1557 processManager->AddDiscreteProcess(new ExcitationMillerGreen );1558 processManager->AddDiscreteProcess(new IonisationRudd );1559 processManager->AddDiscreteProcess(new ChargeIncrease );1437 processManager->AddDiscreteProcess(new ExcitationMillerGreen("ExcitationMillerGreen")); 1438 processManager->AddDiscreteProcess(new IonisationRudd("IonisationRudd")); 1439 processManager->AddDiscreteProcess(new ChargeIncrease("ChargeIncrease")); 1560 1440 } 1561 1441 … … 3467 3347 <mediaobject> 3468 3348 <imageobject role="fo"> 3469 <imagedata fileref="./AllResources/TrackingAndPhysics/physicsProcessPARAM.src/ComponentsWithRegion. gif"3349 <imagedata fileref="./AllResources/TrackingAndPhysics/physicsProcessPARAM.src/ComponentsWithRegion.jpg" 3470 3350 format="JPG" contentwidth="7.0cm" align="center" /> 3471 3351 </imageobject> 3472 3352 <imageobject role="html"> 3473 <imagedata fileref="./AllResources/TrackingAndPhysics/physicsProcessPARAM.src/ComponentsWithRegion. gif"3353 <imagedata fileref="./AllResources/TrackingAndPhysics/physicsProcessPARAM.src/ComponentsWithRegion.jpg" 3474 3354 format="JPG" align="center" /> 3475 3355 </imageobject> -
trunk/documents/UserDoc/DocBookUsersGuides/ForApplicationDeveloper/xml/TrackingAndPhysics/physicsTable.xml
r904 r921 25 25 event loop, the <literal>BuildPhysicsTable()</literal> method of 26 26 <emphasis>G4VProcess</emphasis> is invoked for all processes and 27 cross section tables are prepared. "Standard" electromagnetic28 processes calculate cross section and/or energy loss values for27 as a part of initialisation procedure cross section tables are prepared. 28 Energy loss processes calculate cross section and/or energy loss values for 29 29 each material and for each production cut value assigned to each 30 30 material. A change in production cut values therefore require these 31 31 cross sections to be re-calculated. Cross sections for hadronic 32 processes do not depend on the production cut.32 processes and gamma processes do not depend on the production cut. 33 33 </para> 34 34 … … 38 38 <emphasis>G4PhysicsVector</emphasis> (and derived classes), each of which has 39 39 cross section values for a particle within a given energy range 40 traveling in a material. 40 traveling in a material. By default the linear interpolation is used, alternatively 41 spline may be used if the flag 42 of spline is activated by <emphasis>SetSpline</emphasis> method of the 43 <emphasis>G4PhysicsVector</emphasis> 41 44 </para> 42 45 … … 81 84 82 85 <para> 83 Calculated physics tables for "Standard"electromagnetic processes86 Calculated physics tables for electromagnetic processes 84 87 can be stored in files. The user may thus eliminate the time 85 88 required for the calculation of physics tables by retrieving them -
trunk/documents/UserDoc/DocBookUsersGuides/ForApplicationDeveloper/xml/Visualization/commandcontrol.xml
r905 r921 3 3 <!-- [History] --> 4 4 <!-- Converted to DocBook: Katsuya Amako, Aug-2006 --> 5 <!-- Added Qt Info: Laurent Garnier, Dec-2008 --> 5 6 <!-- --> 6 7 <!-- ******************************************************** --> … … 373 374 </para> 374 375 </para></listitem> 376 <listitem><para> 377 <emphasis role="bold">Additional note 2</emphasis> 378 <para> 379 Events may be kept and reviewed at end of run with 380 <programlisting> 381 Idle> /vis/reviewKeptEvents 382 </programlisting> 383 Keep all events with 384 <programlisting> 385 Idle> /vis/scene/endOfEventAction accumulate [maxNumber] 386 </programlisting> 387 (see 388 <xref linkend="sect.VisCntCmmd.EndEvtRun" />) 389 </para><para> 390 or keep some chosen subset with 391 <programlisting> 392 G4EventManager::GetEventManager()->KeepTheCurrentEvent(); 393 </programlisting> 394 as described in 395 <xref linkend="programlist_OptUAct_1" />. 396 </para><para> 397 To suppress drawing during a run 398 <programlisting> 399 Idle> /vis/disable 400 Idle> /run/beamOn 10000 401 </programlisting> 402 then at end of run 403 <programlisting> 404 Idle> /vis/enable 405 Idle> /vis/reviewKeptEvents 406 </programlisting> 407 </para> 408 </para></listitem> 375 409 </itemizedlist> 376 410 … … 650 684 End of Event Action and End of Run Action: 651 685 <literal>/vis/viewer/endOfEventAction</literal> and 652 <literal>/vis/viewer/endOf EventAction</literal> commands686 <literal>/vis/viewer/endOfRunAction</literal> commands 653 687 </title> 654 688 … … 845 879 846 880 <para> 847 The WIRED3HepRep Browser and WIRED4 JAS Plug-In can generate a881 The HepRApp HepRep Browser and WIRED4 JAS Plug-In can generate a 848 882 wide variety of bitmap and vector output formats including 849 883 PostScript and PDF. … … 1225 1259 </para> 1226 1260 </para></listitem> 1227 <listitem><para> 1228 <ulink url="./Visualization/visTutor/exN03Vis15_mac.html"> 1229 exN03Vis15.mac:</ulink> 1230 <para> 1231 A basic macro for visualization of detector geometry and events 1232 using Qt. 1233 </para> 1234 </para></listitem> 1235 <listitem><para> 1261 <listitem><para> 1236 1262 <ulink url="./Visualization/visTutor/exN03Tree0_mac.html"> 1237 1263 exN03Tree0.mac:</ulink> -
trunk/documents/UserDoc/DocBookUsersGuides/ForApplicationDeveloper/xml/Visualization/introduction.xml
r905 r921 6 6 <!-- Proof read by: Joe Chuma, 5-Jul-1999 --> 7 7 <!-- Converted to DocBook: Katsuya Amako, Aug-2006 --> 8 <!-- Added Qt Info: Laurent Garnier, Dec-2008 --> 9 <!-- Updates for Qt and HepRApp: Joseph Perl, Dec-2008 --> 8 10 <!-- --> 9 11 <!-- ******************************************************** --> … … 47 49 graphics systems use a graphics library compiled with Geant4, such 48 50 as OpenGL, Qt, while others involve a separate application, such as 49 WIREDor DAWN.51 HepRApp or DAWN. 50 52 </para> 51 53 … … 123 125 </para></listitem> 124 126 <listitem><para> 125 Uses GL libraries that are already included on most Linux 126 systems (plus some Windows availability) 127 Requires addition of GL libraries that are freely avialable for all operating systems (and pre-installed on many) 127 128 </para></listitem> 128 129 <listitem><para> … … 137 138 </para></listitem> 138 139 <listitem><para> 139 Limited printing ability (pixel graphics, not vectorgraphics)140 Print to EPS (vector and pixel graphics) 140 141 </para></listitem> 141 142 </itemizedlist> … … 148 149 </para></listitem> 149 150 <listitem><para> 150 Uses Qt and GL libraries that are already included on most Linux151 systems (plus some Windows availability)151 Requies addition of Qt and GL libraries that are freely available on most operating 152 systems 152 153 </para></listitem> 153 154 <listitem><para> … … 168 169 </para></listitem> 169 170 <listitem><para> 170 Make movies interactively171 Easy interface to make movies 171 172 </para></listitem> 172 173 </itemizedlist> … … 205 206 </para></listitem> 206 207 <listitem><para> 207 HepRep/WIRED 208 <itemizedlist spacing="compact"> 209 <listitem><para> 210 Create a file to view in the WIRED3 HepRep Browser or the 211 WIRED4 JAS Plugin 212 </para></listitem> 213 <listitem><para> 214 Requires WIRED browser (a Java application easily to install on 215 all operating systems) 208 HepRep 209 <itemizedlist spacing="compact"> 210 <listitem><para> 211 Create a file to view in a HepRep browser such as HepRApp, 212 FRED or WIRED4 213 </para></listitem> 214 <listitem><para> 215 Requires a HepRep browser (above options work on any operating system) 216 216 </para></listitem> 217 217 <listitem><para> … … 348 348 <listitem><para> 349 349 If you want very responsive photorealistic graphics plus more 350 interactivity (and have the OpenInventor libraries installed)351 <itemizedlist spacing="compact"> 352 <listitem><para> 353 OpenInventor is a good solution350 interactivity (and have the OpenInventor or Qt libraries installed) 351 <itemizedlist spacing="compact"> 352 <listitem><para> 353 OpenInventor or Qt are good solutions 354 354 </para></listitem> 355 355 </itemizedlist> … … 370 370 <itemizedlist spacing="compact"> 371 371 <listitem><para> 372 HepRep /WIREDwill meet your needs372 HepRep will meet your needs 373 373 </para></listitem> 374 374 </itemizedlist> … … 473 473 <itemizedlist spacing="compact"> 474 474 <listitem><para> 475 HepRep /WIRED475 HepRep 476 476 </para></listitem> 477 477 <listitem><para> … … 527 527 <xref linkend="sect.VisPlylMrkTxt" /> 528 528 Polylines, Markers and Text 529 </para></listitem> 530 <listitem><para> 531 <xref linkend="sect.MkMovie" /> 532 Making a Movie 529 533 </para></listitem> 530 534 </itemizedlist> -
trunk/documents/UserDoc/DocBookUsersGuides/ForApplicationDeveloper/xml/Visualization/makingamovie.xml
r904 r921 3 3 <!-- [History] --> 4 4 <!-- Converted to DocBook: Katsuya Amako, Aug-2006 --> 5 <!-- Updates for Qt: Laurent Garnier, Dec-2008 --> 5 6 <!-- --> 6 7 <!-- ******************************************************** --> … … 29 30 drivers currently capable of producing picture files are: 30 31 32 <ulink url="http://bmrc.berkeley.edu/frame/research/mpeg/mpeg_encode.html">More informations about MPEG encoder</ulink> 33 31 34 <informaltable> 32 35 <tgroup cols="2"> … … 70 73 <entry> 71 74 eps 75 </entry> 76 </row> 77 <row> 78 <entry> 79 Qt 80 </entry> 81 <entry> 82 jpeg, eps, ppm, ... 72 83 </entry> 73 84 </row> … … 205 216 </sect2> 206 217 218 <!-- ******************* Section (Level#2) ****************** --> 219 <sect2 id="sect.MkMovie.Qt"> 220 <title> 221 Qt 222 </title> 223 224 <para> 225 The Qt driver provides one of the easiest ways to make a movie. 226 Of course, you first need to add the Qt libraries and link with Qt, 227 but once you have that, Qt provides a ready-made function to store all updates of the OpenGL 228 frame into the movie format. 229 You then use loops (as defined in OGLX section above) or even move/rotate/zoom you scene 230 by mouse actions to form your movie. 231 </para> 232 <para> 233 The Qt driver automatically handles all of the movie-making steps described in the OGLX section of this document - storing the files, converting them and assembling the finished movie. 234 You just have to take care of installing an mpeg_encoder. 235 </para> 236 <para> 237 To make a movie : 238 <itemizedlist spacing="compact"> 239 <listitem><para> 240 Right click to display a context menu, "Action"->"Movie parameters". 241 </para></listitem> 242 <listitem><para> 243 Select MPEG encoder path if it was not found. 244 </para></listitem> 245 <listitem><para> 246 Select the name of the output movie. 247 </para></listitem> 248 <listitem><para> 249 Let go! Hit SPACE to Start/Pause recording, RETURN to STOP 250 </para></listitem> 251 </itemizedlist> 252 </para> 253 <para> 254 Then, open your movie (on Mac, for example): 255 256 <informalexample> 257 <programlisting> 258 open G4OpenGL.mpg 259 </programlisting> 260 </informalexample> 261 262 opens a QuickTime player. 263 </para> 264 265 </sect2> 266 207 267 208 268 <!-- ******************* Section (Level#2) ****************** --> -
trunk/documents/UserDoc/DocBookUsersGuides/ForApplicationDeveloper/xml/Visualization/visdrivers.xml
r905 r921 4 4 <!-- Changed by: Dennis Wright, 27-Nov-2001 --> 5 5 <!-- Converted to DocBook: Katsuya Amako, Aug-2006 --> 6 <!-- Updates for Qt and HepRApp: Joseph Perl, Dec-2008 --> 6 7 <!-- --> 7 8 <!-- ******************************************************** --> … … 114 115 </entry> 115 116 <entry> 116 Linux, U nix, Mac with Xlib117 Linux, UNIX, Mac with Xlib 117 118 </entry> 118 119 </row> … … 147 148 </entry> 148 149 <entry> 149 Linux, U nix, Mac, Windows150 Linux, UNIX, Mac, Windows 150 151 </entry> 151 152 </row> … … 177 178 </entry> 178 179 <entry> 179 WIRED or FREDHepRep Browser180 HepRApp, FRED or WIRED4 HepRep Browser 180 181 </entry> 181 182 <entry> … … 191 192 </entry> 192 193 <entry> 193 Linux, U nix, Mac, Windows194 Linux, UNIX, Mac, Windows 194 195 </entry> 195 196 </row> … … 304 305 305 306 <para> 306 If you don't have Motif, all control is done from Geant4 307 Output can be exported to EPS (both vector and pixel graphics) 308 using vis/ogl/printEPS. 309 </para> 310 311 <para> 312 If you don't have Motif or Qt, all control is done from Geant4 307 313 commands: 308 314 … … 327 333 </programlisting> 328 334 </informalexample> 335 </para> 336 337 <para> 338 If you have Qt, see the Qt section below. 329 339 </para> 330 340 … … 367 377 368 378 <para> 369 This driver have been developed by Laurent Garnier (IN2P3, LAL Orsay). 370 It is an interface to the powerful toolkit Qt, now free on lot of 371 platforms. This driver needs OpenGL library to be install. It is well suited for 372 real-time fast visualization and demonstration. Fast visualization 373 is realized with hardware acceleration, reuse of shapes stored in a 379 This driver has been developed by Laurent Garnier (IN2P3, LAL Orsay). 380 It is an interface to the powerful application framework, Qt, now free on most 381 platforms. This driver also requires the OpenGL library. 382 </para><para> 383 The Qt driver is well suited for real-time fast visualization and demonstration. 384 Fast visualization is realized with hardware acceleration, reuse of shapes stored in a 374 385 display list, etc. NURBS visualization is also supported. All OpenGL 375 features are implement s in Qt driver . In addition, mouse events control376 are used to rotation/move/zoom volume, you can save your scene in lots 377 of formats (vector or not), make movies... 386 features are implemented in the Qt driver, but one also gets mouse 387 control of rotation/translation/zoom, the ability to save your scene in many formats 388 (both vector and pixel graphics) and an easy interface for making movies. 378 389 </para><para> 379 There is only one session of Qt driver for all available platform.380 390 Two display modes are available: immediate mode and stored mode. 381 391 The former has no limitation on data size, and the latter is fast … … 386 396 <para> 387 397 To see the visualization window : 388 </para> 398 389 399 <?soft-pagebreak ?> 390 400 <informalexample> 391 401 <programlisting> 392 /vis/open OGLSQt 402 /vis/open OGLSQt (for Stored mode) 403 or 404 /vis/open OGLIQt (for Immediate mode) 393 405 </programlisting> 394 406 </informalexample> … … 404 416 </para></listitem> 405 417 <listitem><para> 406 <ulink url="http:// geant4.slac.stanford.edu/Presentations/vis/G4OpenGLTutorial/G4OpenGLTutorial.html">418 <ulink url="http://users.lal.in2p3.fr/garnier/G4QtTutorial.html"> 407 419 Geant4 Visualization Tutorial 408 420 </ulink> … … 410 422 </para></listitem> 411 423 </itemizedlist> 424 </para> 412 425 </sect2> 413 426 … … 523 536 The HepRepFile driver creates a HepRep XML file in the HepRep1 524 537 format suitable for viewing with the 525 <ulink url="http://www.slac.stanford.edu/ BFROOT/www/Computing/Graphics/Wired/">526 WIRED3</ulink> HepRep Browser.538 <ulink url="http://www.slac.stanford.edu/~perl/HepRApp/"> 539 HepRApp</ulink> HepRep Browser. 527 540 </para> 528 541 … … 565 578 566 579 <para> 567 View the file using the WIRED3HepRep Browser, available from:568 </para> 569 <para> 570 <ulink url="http://www.slac.stanford.edu/ BFROOT/www/Computing/Graphics/Wired/">571 http://www.slac.stanford.edu/ BFROOT/www/Computing/Graphics/Wired/580 View the file using the HepRApp HepRep Browser, available from: 581 </para> 582 <para> 583 <ulink url="http://www.slac.stanford.edu/~perl/HepRApp/"> 584 http://www.slac.stanford.edu/~perl/HepRApp/ 572 585 </ulink> 573 586 . … … 575 588 576 589 <para> 577 WIRED3allows you to pick on volumes, trajectories and hits to590 HepRApp allows you to pick on volumes, trajectories and hits to 578 591 find out their associated HepRep Attributes, such as volume name, 579 592 particle ID, momentum, etc. These same attributes can be displayed … … 584 597 585 598 <para> 586 WIRED3can read heprep files in zipped format as well as599 HepRApp can read heprep files in zipped format as well as 587 600 unzipped, so you can save space by applying gzip to the heprep 588 601 file. This will reduce the file to about five percent of its … … 661 674 <itemizedlist spacing="compact"> 662 675 <listitem><para> 663 WIRED3Users Home Page:676 HepRApp Users Home Page: 664 677 <para> 665 <ulink url="http://www.slac.stanford.edu/ BFROOT/www/Computing/Graphics/Wired/">666 http://www.slac.stanford.edu/ BFROOT/www/Computing/Graphics/Wired/678 <ulink url="http://www.slac.stanford.edu/~perl/HepRApp/"> 679 http://www.slac.stanford.edu/~perl/HepRApp/ 667 680 </ulink> 668 681 . … … 678 691 </para></listitem> 679 692 <listitem><para> 680 Geant4 Visualization Tutorial using the WIRED3HepRep Browser693 Geant4 Visualization Tutorial using the HepRApp HepRep Browser 681 694 <para> 682 <ulink url="http://geant4.slac.stanford.edu/Presentations/vis/G4 WIREDTutorial/G4WIREDTutorial.html">683 http://geant4.slac.stanford.edu/Presentations/vis/G4 WIREDTutorial/G4WIREDTutorial.html695 <ulink url="http://geant4.slac.stanford.edu/Presentations/vis/G4HepRAppTutorial/G4HepRAppTutorial.html"> 696 http://geant4.slac.stanford.edu/Presentations/vis/G4HepRAppTutorial/G4HepRAppTutorial.html 684 697 </ulink> 685 698 </para> … … 1623 1636 <mediaobject> 1624 1637 <imageobject role="fo"> 1625 <imagedata fileref="./AllResources/Visualization/visualization.src/xmlnp. gif"1638 <imagedata fileref="./AllResources/Visualization/visualization.src/xmlnp.jpg" 1626 1639 format="JPG" contentwidth="12.0cm" align="center" /> 1627 1640 </imageobject> 1628 1641 <imageobject role="html"> 1629 <imagedata fileref="./AllResources/Visualization/visualization.src/xmlnp. gif"1642 <imagedata fileref="./AllResources/Visualization/visualization.src/xmlnp.jpg" 1630 1643 format="JPG" align="center" /> 1631 1644 </imageobject> … … 1643 1656 <mediaobject> 1644 1657 <imageobject role="fo"> 1645 <imagedata fileref="./AllResources/Visualization/visualization.src/xmlnpfind. gif"1658 <imagedata fileref="./AllResources/Visualization/visualization.src/xmlnpfind.jpg" 1646 1659 format="JPG" contentwidth="12.0cm" align="center" /> 1647 1660 </imageobject> 1648 1661 <imageobject role="html"> 1649 <imagedata fileref="./AllResources/Visualization/visualization.src/xmlnpfind. gif"1662 <imagedata fileref="./AllResources/Visualization/visualization.src/xmlnpfind.jpg" 1650 1663 format="JPG" align="center" /> 1651 1664 </imageobject> -
trunk/documents/UserDoc/DocBookUsersGuides/ForApplicationDeveloper/xml/Visualization/visexecutable.xml
r905 r921 3 3 <!-- [History] --> 4 4 <!-- Converted to DocBook: Katsuya Amako, Aug-2006 --> 5 <!-- Updates for Qt: Laurent Garnier, Dec-2008 --> 5 6 <!-- --> 6 7 <!-- ******************************************************** --> -
trunk/documents/UserDoc/DocBookUsersGuides/ForApplicationDeveloper/xml/XSLCustomizationLayer/G4XSLCustomFO.xsl
r904 r921 10 10 <!-- Import the FO stylesheet --> 11 11 <!-- ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ --> 12 <xsl:import href="/usr/share/xml/docbook/stylesheet/nwalsh/ current/fo/docbook.xsl"/>12 <xsl:import href="/usr/share/xml/docbook/stylesheet/nwalsh/fo/docbook.xsl" /> 13 13 14 14 <!-- ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ --> -
trunk/documents/UserDoc/DocBookUsersGuides/ForApplicationDeveloper/xml/XSLCustomizationLayer/G4XSLCustomHTML.xsl
r904 r921 9 9 <!-- Import the stylesheet to chunk the html output --> 10 10 <!-- ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ --> 11 <xsl:import href="/usr/share/xml/docbook/stylesheet/nwalsh/ current/html/chunk.xsl" />11 <xsl:import href="/usr/share/xml/docbook/stylesheet/nwalsh/html/chunk.xsl" /> 12 12 13 13 <!-- ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ -->
Note: See TracChangeset
for help on using the changeset viewer.