G4MaterialPropertiesTable Class Reference

#include <G4MaterialPropertiesTable.hh>

Inheritance diagram for G4MaterialPropertiesTable:

Public Member Functions
	G4MaterialPropertiesTable ()
virtual	~G4MaterialPropertiesTable ()
void	AddConstProperty (const char *key, G4double PropertyValue)
G4MaterialPropertyVector *	AddProperty (const char *key, G4double *PhotonEnergies, G4double *PropertyValues, G4int NumEntries)
void	AddProperty (const char *key, G4MaterialPropertyVector *opv)
void	RemoveConstProperty (const char *key)
void	RemoveProperty (const char *key)
G4double	GetConstProperty (const char *key) const
G4bool	ConstPropertyExists (const char *key) const
G4MaterialPropertyVector *	GetProperty (const char *key)
void	AddEntry (const char *key, G4double aPhotonEnergy, G4double aPropertyValue)
void	DumpTable ()
const std::map< G4String, G4MaterialPropertyVector *, std::less< G4String > > *	GetPropertiesMap () const
const std::map< G4String, G4double, std::less< G4String > > *	GetPropertiesCMap () const

Detailed Description

Definition at line 70 of file G4MaterialPropertiesTable.hh.

Constructor & Destructor Documentation

G4MaterialPropertiesTable::G4MaterialPropertiesTable

(

)

Definition at line 58 of file G4MaterialPropertiesTable.cc.

{
}

G4MaterialPropertiesTable::~G4MaterialPropertiesTable ( )

virtual

Definition at line 66 of file G4MaterialPropertiesTable.cc.

{
  MPTiterator i;
  for (i = MPT.begin(); i != MPT.end(); ++i)
  {
    delete (*i).second;
  }
  MPT.clear();
  MPTC.clear();
}

Member Function Documentation

void G4MaterialPropertiesTable::AddConstProperty ( const char *  key, G4double  PropertyValue  )

inline

Here is the caller graph for this function:

void G4MaterialPropertiesTable::AddEntry	(	const char *	key,
		G4double	aPhotonEnergy,
		G4double	aPropertyValue
	)

Definition at line 139 of file G4MaterialPropertiesTable.cc.

{
  // Allows to add an entry pair directly to the Material Property Vector
  // given a key

  G4MaterialPropertyVector *targetVector=MPT [G4String(key)];
  if (targetVector != nullptr)
  {
    targetVector->InsertValues(aPhotonEnergy, aPropertyValue);
  }
  else
  {
    G4Exception("G4MaterialPropertiesTable::AddEntry()", "mat203",
                FatalException, "Material Property Vector not found.");
  }
}

Here is the call graph for this function:

G4MaterialPropertyVector* G4MaterialPropertiesTable::AddProperty ( const char *  key, G4double *  PhotonEnergies, G4double *  PropertyValues, G4int  NumEntries  )

inline

Here is the caller graph for this function:

void G4MaterialPropertiesTable::AddProperty ( const char *  key, G4MaterialPropertyVector *  opv  )

inline

G4bool G4MaterialPropertiesTable::ConstPropertyExists

(

const char *

key

)

const

Definition at line 94 of file G4MaterialPropertiesTable.cc.

{
  // Returns true if a const property 'key' exists

  MPTCiterator j;
  j = MPTC.find(G4String(key));
  if ( j != MPTC.end() ) return true;
  return false;
}

Here is the caller graph for this function:

void G4MaterialPropertiesTable::DumpTable

(

)

Definition at line 158 of file G4MaterialPropertiesTable.cc.

{
  MPTiterator i;
  for (i = MPT.begin(); i != MPT.end(); ++i)
  {
    G4cout << (*i).first << G4endl;
    if ( (*i).second != 0 )
    {
      (*i).second->DumpValues();
    }
    else
    {
      G4Exception("G4MaterialPropertiesTable::DumpTable()", "mat204",
                  JustWarning, "NULL Material Property Vector Pointer.");
    }
  }
  MPTCiterator j;
  for (j = MPTC.begin(); j != MPTC.end(); ++j)
  {
    G4cout << j->first << G4endl;
    if ( j->second != 0 )
    {
      G4cout << j->second << G4endl;
    }
    else
    {
      G4Exception("G4MaterialPropertiesTable::DumpTable()", "mat202",
                  JustWarning, "No Material Constant Property.");
    }
  }
}

Here is the call graph for this function:

G4double G4MaterialPropertiesTable::GetConstProperty

(

const char *

key

)

const

Definition at line 81 of file G4MaterialPropertiesTable.cc.

{
  // Returns the constant material property corresponding to a key

  MPTCiterator j;
  j = MPTC.find(G4String(key));
  if ( j != MPTC.end() ) return j->second;
  G4cout << "key: " << G4String(key) << G4endl;
  G4Exception("G4MaterialPropertiesTable::GetConstProperty()","mat202",
              FatalException, "Constant Material Property not found.");
  return 0.;
}

Here is the call graph for this function:

Here is the caller graph for this function:

const std::map< G4String, G4double, std::less<G4String> >* G4MaterialPropertiesTable::GetPropertiesCMap ( ) const

inline

Definition at line 120 of file G4MaterialPropertiesTable.hh.

{ return &MPTC; }

Here is the caller graph for this function:

const std::map< G4String, G4MaterialPropertyVector*, std::less<G4String> >* G4MaterialPropertiesTable::GetPropertiesMap ( ) const

inline

Definition at line 118 of file G4MaterialPropertiesTable.hh.

{ return &MPT; }

Here is the caller graph for this function:

G4MaterialPropertyVector * G4MaterialPropertiesTable::GetProperty

(

const char *

key

)

Definition at line 105 of file G4MaterialPropertiesTable.cc.

{
  // Returns a Material Property Vector corresponding to a key

  //Important Note for MT. adotti 17 Feb 2016
  //In previous implementation the following line was at the bottom of the
  //function causing a rare race-condition.
  //Moving this line here from the bottom solves the problem because:
  //1- Map is accessed only via operator[] (to insert) and find() (to search),
  //   and these are thread safe if done on separate elements.
  //   See notes on data-races at:
  //   http://www.cplusplus.com/reference/map/map/operator%5B%5D/
  //   http://www.cplusplus.com/reference/map/map/find/
  //2- So we have a data race if two threads access the same element (GROUPVEL)
  //   one in read and one in write mode. This was happening with the line
  //   at the bottom of the code, one thread in SetGROUPVEL(), 
  //   and the other here
  //3- SetGROUPVEL() is protected by a mutex that ensures that only
  //   one thread at the time will execute its code
  //4- The if() statement guarantees that only if two threads are searching
  //   the same problematic key (GROUPVEL) the mutex will be used.
  //   Different keys do not lock (good for performances)
  //5- As soon as a thread acquires the mutex in SetGROUPVEL it checks again
  //   if the map has GROUPVEL key, if so returns immediately.
  //   This "double check" allows to execute the heavy code to calculate
  //   group velocity only once even if two threads enter SetGROUPVEL together
  if (G4String(key) == "GROUPVEL") return SetGROUPVEL();

  MPTiterator i;
  i = MPT.find(G4String(key));
  if ( i != MPT.end() ) return i->second;
  return nullptr;
}

Here is the caller graph for this function:

void G4MaterialPropertiesTable::RemoveConstProperty ( const char *  key )

inline

Here is the caller graph for this function:

void G4MaterialPropertiesTable::RemoveProperty ( const char *  key )

inline

---

The documentation for this class was generated from the following files:

• geant4.10.03.p01/source/materials/include/G4MaterialPropertiesTable.hh
• geant4.10.03.p01/source/materials/src/G4MaterialPropertiesTable.cc