Changeset 1222 for trunk/documents/UserDoc/DocBookUsersGuides/ForApplicationDeveloper/xml/Detector/electroMagneticField.xml
- Timestamp:
- Dec 16, 2009, 12:14:47 PM (15 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
trunk/documents/UserDoc/DocBookUsersGuides/ForApplicationDeveloper/xml/Detector/electroMagneticField.xml
r904 r1222 13 13 <!-- Corrections, changes by: John APOSTOLAKIS, 7-Jul-2005 --> 14 14 <!-- Converted to DocBook: Katsuya Amako, Aug-2006 --> 15 <!-- Corrections, changes by: John APOSTOLAKIS,15-Dec-2009 --> 15 16 <!-- --> 16 17 <!-- ******************************************************** --> … … 441 442 442 443 <para> 444 A new stepper for propagation in magnetic field is available in 445 release 9.3. Choosing the G4NystromRK4 stepper provides accuracy 446 near that of G4ClassicalRK4 (4th order) with a significantly reduced 447 cost in field evaluation. Using a novel analytical expression for 448 estimating the error of a proposed step and the Nystrom reuse of the 449 mid-point field value, it requires only 2 additional field 450 evaluations per attempted step, in place of 10 field evaluations of 451 ClassicalRK4 (which uses the general midpoint method for estimating 452 the step error.) 453 454 <informalexample> 455 <programlisting> 456 G4Mag_UsualEqRhs* 457 pMagFldEquation = new G4Mag_UsualEqRhs(fMagneticField); 458 fStepper = new G4NystromRK4( pMagFldEquation ); 459 </programlisting> 460 </informalexample> 461 </para> 462 463 <para> 464 It is proposed as an alternative stepper in the case of a pure 465 magnetic field. It is not applicable for the simulation of electric 466 or full electromagnetic or other types of field. For a pure 467 magnetic field, results should be fully compatible with the results 468 of ClassicalRK4 in nearly all cases. ( The only potential exceptions 469 are large steps for tracks with small momenta - which cannot be 470 integrated well by any RK method except the Helical extended methods.) 471 </para> 472 473 <para> 443 474 You can choose an alternative stepper either when the field 444 475 manager is constructed or later. At the construction of the … … 546 577 the position of the track after a number of boundary crossings is 547 578 directly proportional to the number of boundaries. 579 </para> 580 581 </sect3> 582 583 584 <!-- ******************* Section (Level#3) ****************** --> 585 <sect3 id="sect.EMField.Pract.RedNumCall"> 586 <title> 587 Reducing the number of field calls to speed-up simulation 588 </title> 589 590 <para> 591 An additional method to reduce the number of field evaluations is 592 to utilise the new class G4CachedMagneticField class. It is 593 applicable only for pure magnetic fields which do not vary with time. 594 595 596 <informalexample> 597 <programlisting> 598 G4MagneticField * pMagField; // Your field - Defined elsewhere 599 600 G4double distanceConst = 2.5 * millimeter; 601 G4MagneticField * pCachedMagField= new G4CachedMagneticField( pMagField, distanceConst); 602 </programlisting> 603 </informalexample> 548 604 </para> 549 605
Note: See TracChangeset
for help on using the changeset viewer.