Gabriele Cosmo
140 lines
5.5 KiB
C++
140 lines
5.5 KiB
C++
//
|
|
// ********************************************************************
|
|
// * DISCLAIMER *
|
|
// * *
|
|
// * The following disclaimer summarizes all the specific disclaimers *
|
|
// * of contributors to this software. The specific disclaimers,which *
|
|
// * govern, are listed with their locations in: *
|
|
// * http://cern.ch/geant4/license *
|
|
// * *
|
|
// * Neither the authors of this software system, nor their employing *
|
|
// * institutes,nor the agencies providing financial support for this *
|
|
// * work make any representation or warranty, express or implied, *
|
|
// * regarding this software system or assume any liability for its *
|
|
// * use. *
|
|
// * *
|
|
// * This code implementation is the intellectual property of the *
|
|
// * GEANT4 collaboration. *
|
|
// * By copying, distributing or modifying the Program (or any work *
|
|
// * based on the Program) you indicate your acceptance of this *
|
|
// * statement, and all its terms. *
|
|
// ********************************************************************
|
|
//
|
|
//
|
|
// $Id: G4FieldManager.hh,v 1.8 2002/07/24 10:43:31 gcosmo Exp $
|
|
// GEANT4 tag $Name: geant4-05-00 $
|
|
//
|
|
//
|
|
// class G4FieldManager
|
|
//
|
|
// Class description:
|
|
//
|
|
// A class to manage (Store) a pointer to the Field subclass that
|
|
// describes the field of a detector (magnetic, electric or other).
|
|
// Also stores a reference to the chord finder.
|
|
//
|
|
// The G4FieldManager class exists to allow the user program to specify
|
|
// the electric, magnetic and/or other field(s) of the detector.
|
|
// (OR, in the future, of a part of it - planned to be a logical volume).
|
|
// It also stores a pointer to the ChordFinder object that can do the
|
|
// propagation in this field. All geometrical track "advancement"
|
|
// in the field is handled by this ChordFinder object.
|
|
//
|
|
// G4FieldManager allows the other classes/object (of the MagneticField
|
|
// & other class categories) to find out whether a detector field object
|
|
// exists and what that object is.
|
|
//
|
|
// The Chord Finder must be created either by calling CreateChordFinder
|
|
// for a Magnetic Field or by the user creating a a Chord Finder object
|
|
// "manually" and setting this pointer.
|
|
//
|
|
// A default FieldManager is created by the singleton class
|
|
// G4NavigatorForTracking and exists before main is called.
|
|
// However a new one can be created and given to G4NavigatorForTracking.
|
|
//
|
|
// Our current design envisions that one Field manager is
|
|
// valid for each region detector.
|
|
|
|
// History:
|
|
// - 10.03.97 John Apostolakis, design and implementation.
|
|
|
|
#ifndef G4FIELDMANAGER_HH
|
|
#define G4FIELDMANAGER_HH 1
|
|
|
|
#include "G4Field.hh"
|
|
#include "G4MagneticField.hh"
|
|
#include "G4ChordFinder.hh"
|
|
|
|
class G4FieldManager
|
|
{
|
|
public: // with description
|
|
|
|
G4FieldManager();
|
|
G4FieldManager(G4MagneticField *detectorField);
|
|
~G4FieldManager();
|
|
|
|
inline G4bool SetDetectorField(G4Field *detectorField);
|
|
inline const G4Field* GetDetectorField() const;
|
|
inline G4bool DoesFieldExist() const;
|
|
|
|
void CreateChordFinder(G4MagneticField *detectorMagField);
|
|
inline void SetChordFinder(G4ChordFinder *aChordFinder);
|
|
inline G4ChordFinder* GetChordFinder();
|
|
|
|
public: // without description
|
|
|
|
inline G4double GetDeltaIntersection() const;
|
|
// Accuracy for boundary intersection.
|
|
|
|
inline G4double GetDeltaOneStep() const;
|
|
// Accuracy for one tracking/physics step.
|
|
|
|
inline void SetAccuraciesWithDeltaOneStep(G4double valDeltaOneStep);
|
|
// Sets both accuracies, maintaining a fixed ratio for accuracties
|
|
// of volume Intersection and Integration (in One Step)
|
|
|
|
inline void SetDeltaOneStep(G4double valueD1step);
|
|
inline void SetDeltaIntersection(G4double valueDintersection);
|
|
|
|
inline G4bool DoesFieldChangeEnergy();
|
|
inline void SetFieldChangesEnergy(G4bool value);
|
|
// For electric field this should be true
|
|
// For magnetic field this should be false
|
|
private:
|
|
|
|
G4FieldManager(const G4FieldManager&);
|
|
G4FieldManager& operator=(const G4FieldManager&);
|
|
// Private copy constructor and assignment operator.
|
|
|
|
private:
|
|
|
|
G4Field* fDetectorField;
|
|
G4ChordFinder* fChordFinder;
|
|
|
|
G4bool fAllocatedChordFinder; // Did we used "new" to
|
|
// create fChordFinder ?
|
|
G4bool fFieldChangesEnergy;
|
|
|
|
// Values for the required accuracies
|
|
//
|
|
G4double fDelta_One_Step_Value; // for one tracking/physics step
|
|
G4double fDelta_Intersection_Val; // for boundary intersection
|
|
|
|
G4double fDefault_Delta_One_Step_Value; // = 0.25 * mm;
|
|
G4double fDefault_Delta_Intersection_Val; // = 0.1 * mm;
|
|
};
|
|
|
|
// Our current design envisions that one Field manager is valid for a region of the detector.
|
|
// (eg a detector with electric E and magnetic B field will now treat
|
|
// them as one field - and could treat any other field of importance
|
|
// as additional components of a single field.)
|
|
// Does it make sense to have several instead ?
|
|
// Is the lack of elegance of the design (of G4Field) made up
|
|
// for by the simplification it allows ?
|
|
|
|
// Implementation of inline functions
|
|
|
|
#include "G4FieldManager.icc"
|
|
|
|
#endif /* G4FIELDMANAGER_HH */
|