CMS 3D CMS Logo

 All Classes Namespaces Files Functions Variables Typedefs Enumerations Enumerator Properties Friends Macros Pages
MagFieldConfig.h
Go to the documentation of this file.
1 #ifndef MagFieldConfig_h
2 #define MagFieldConfig_h
3 
13 
14 #include <string>
15 #include <vector>
16 #include <map>
17 
18 namespace edm {class ParameterSet;}
19 
20 namespace magneticfield {
21  typedef std::map<int, std::pair<std::string, int> > TableFileMap;
22 }
23 
24 
26 public:
27 
29 
31  MagFieldConfig(const edm::ParameterSet& pset, bool debug=false);
32 
33  // Operations
34 public:
35  std::vector<unsigned> expandList(const std::string& list);
36 
39 
42 
45 
47  std::vector<int> keys;
48  std::vector<double> values;
49 
52 
56  std::vector<double> slaveFieldParameters;
57 
59 };
60 #endif
61 
62 
std::vector< double > values
magneticfield::TableFileMap gridFiles
Specification of which data table is to be used for each volume.
std::string slaveFieldVersion
Label or type of the tracker parametrization.
std::vector< int > keys
Scaling factors for the field in specific volumes.
#define debug
Definition: HDRShower.cc:19
std::string version
Version of the data tables to be used.
#define COND_SERIALIZABLE
Definition: Serializable.h:37
int geometryVersion
Version of the geometry to be used.
std::map< int, std::pair< std::string, int > > TableFileMap
std::vector< unsigned > expandList(const std::string &list)
std::vector< double > slaveFieldParameters
How EventSelector::AcceptEvent() decides whether to accept an event for output otherwise it is excluding the probing of A single or multiple positive and the trigger will pass if any such matching triggers are PASS or EXCEPTION[A criterion thatmatches no triggers at all is detected and causes a throw.] A single negative with an expectation of appropriate bit checking in the decision and the trigger will pass if any such matching triggers are FAIL or EXCEPTION A wildcarded negative criterion that matches more than one trigger in the trigger list("!*","!HLTx*"if it matches 2 triggers or more) will accept the event if all the matching triggers are FAIL.It will reject the event if any of the triggers are PASS or EXCEPTION(this matches the behavior of"!*"before the partial wildcard feature was incorporated).Triggers which are in the READY state are completely ignored.(READY should never be returned since the trigger paths have been run