Enumerations | |
| enum | JobMode { GridJobMode, AnalysisJobMode, NilJobMode, GridJobMode, AnalysisJobMode, NilJobMode, GridJobMode, AnalysisJobMode, NilJobMode } |
Functions | |
| Making New Hardwired Defaults for the and how to create a specialized set of selectable by doing cmsRun mode whateverNameYouChoose The MessageLogger has a set of hardwired for use when no MessageLogger configuration appears in the config file These match the contents of the MessageLogger cfi file Although these defaults are hardwired into it is recognized that changing circumstances and experience withthe framework will make necessary changes in the defaults the defaults are kept in a clean form in one for ease of modification Multiple sets of these defaults can be corresponding to multiple modes of operation For the production | running (which is in a sense the"default"default mode) might be interested only in warnings and errors |
| Making New Hardwired Defaults for the and how to create a specialized set of selectable by doing cmsRun mode whateverNameYouChoose The MessageLogger has a set of hardwired for use when no MessageLogger configuration appears in the config file These match the contents of the MessageLogger cfi file Although these defaults are hardwired into it is recognized that changing circumstances and experience withthe framework will make necessary changes in the defaults the defaults are kept in a clean form in one for ease of modification Multiple sets of these defaults can be corresponding to multiple modes of operation For the production while occasional release validation jobs might want output concerning info messages as well In the example we will show how to a Change the default summary threshold for the existing default mode b Create a new with a different summary threshold If you are changing the main | default (that is, the one gotten wheen no mode is specified) |
| if (jm=="grid") return GridJobMode | |
| So the relevant code implementing the defaults for this mode is MessageLoggerDefaults::hardwireGridJobMode() Step 1 to statistics | push_back ("cerr_stats") |
| You can see this line in the | hardwireGridJobMode () method |
| You can see this line in the about lines after the start including every statistics can have a PSet with the options for that destination The class that corresponds to that PSet is called Destination The cerr statistics did not previously have such a PSet so now we add one Note that to avoid name clashes we always enclose the code for setting up a Destination in braces So far we are | adding (after the close brace for the section that started with Destination FrameworkJobReport) |
| b In MessageService src MessageLoggerDefaults add a method to set up that mode In the section with comment I added the line void | hardwireReleaseValidationJobMode () |
| d In MessageService src HardwiredDefaults make a copy of one of the hardwireXXXJobMode | methods (I started from hardwireGridJobMode) and change the name(and the comment at the end) to the new one |
| e Place the name of the new | mode (infos) into the decision logic in the mode() method right at the beginning of HardwiredDefaults.cc |
Variables | |
| Making New Hardwired Defaults for the | MessageLogger |
| Making New Hardwired Defaults for the and how to create a specialized set of | defaults |
| Making New Hardwired Defaults for the and how to create a specialized set of selectable by doing cmsRun mode whateverNameYouChoose The MessageLogger has a set of hardwired for use when no MessageLogger configuration appears in the config file These match the contents of the MessageLogger cfi file Although these defaults are hardwired into | code |
| Making New Hardwired Defaults for the and how to create a specialized set of selectable by doing cmsRun mode whateverNameYouChoose The MessageLogger has a set of hardwired for use when no MessageLogger configuration appears in the config file These match the contents of the MessageLogger cfi file Although these defaults are hardwired into it is recognized that changing circumstances and experience withthe framework will make necessary changes in the defaults | Therefore |
| Making New Hardwired Defaults for the and how to create a specialized set of selectable by doing cmsRun mode whateverNameYouChoose The MessageLogger has a set of hardwired for use when no MessageLogger configuration appears in the config file These match the contents of the MessageLogger cfi file Although these defaults are hardwired into it is recognized that changing circumstances and experience withthe framework will make necessary changes in the defaults the defaults are kept in a clean form in one | place |
| Making New Hardwired Defaults for the and how to create a specialized set of selectable by doing cmsRun mode whateverNameYouChoose The MessageLogger has a set of hardwired for use when no MessageLogger configuration appears in the config file These match the contents of the MessageLogger cfi file Although these defaults are hardwired into it is recognized that changing circumstances and experience withthe framework will make necessary changes in the defaults the defaults are kept in a clean form in one for ease of modification Multiple sets of these defaults can be | provided |
| Making New Hardwired Defaults for the and how to create a specialized set of selectable by doing cmsRun mode whateverNameYouChoose The MessageLogger has a set of hardwired for use when no MessageLogger configuration appears in the config file These match the contents of the MessageLogger cfi file Although these defaults are hardwired into it is recognized that changing circumstances and experience withthe framework will make necessary changes in the defaults the defaults are kept in a clean form in one for ease of modification Multiple sets of these defaults can be corresponding to multiple modes of operation For | example |
| Making New Hardwired Defaults for the and how to create a specialized set of selectable by doing cmsRun mode whateverNameYouChoose The MessageLogger has a set of hardwired for use when no MessageLogger configuration appears in the config file These match the contents of the MessageLogger cfi file Although these defaults are hardwired into it is recognized that changing circumstances and experience withthe framework will make necessary changes in the defaults the defaults are kept in a clean form in one for ease of modification Multiple sets of these defaults can be corresponding to multiple modes of operation For the production while occasional release validation jobs might want output concerning info messages as well In the example | below |
| Making New Hardwired Defaults for the and how to create a specialized set of selectable by doing cmsRun mode whateverNameYouChoose The MessageLogger has a set of hardwired for use when no MessageLogger configuration appears in the config file These match the contents of the MessageLogger cfi file Although these defaults are hardwired into it is recognized that changing circumstances and experience withthe framework will make necessary changes in the defaults the defaults are kept in a clean form in one for ease of modification Multiple sets of these defaults can be corresponding to multiple modes of operation For the production while occasional release validation jobs might want output concerning info messages as well In the example we will show how to a Change the default summary threshold for the existing default mode b Create a new | mode = is mode="grid" |
| Making New Hardwired Defaults for the and how to create a specialized set of selectable by doing cmsRun mode whateverNameYouChoose The MessageLogger has a set of hardwired for use when no MessageLogger configuration appears in the config file These match the contents of the MessageLogger cfi file Although these defaults are hardwired into it is recognized that changing circumstances and experience withthe framework will make necessary changes in the defaults the defaults are kept in a clean form in one for ease of modification Multiple sets of these defaults can be corresponding to multiple modes of operation For the production while occasional release validation jobs might want output concerning info messages as well In the example we will show how to a Change the default summary threshold for the existing default mode b Create a new with a different summary threshold If you are changing the main it is probably a good idea to change the MessageLogger_cfi py file to keep the default in step with the contents of that file All the default information is kept in three | files |
| Making New Hardwired Defaults for the and how to create a specialized set of selectable by doing cmsRun mode whateverNameYouChoose The MessageLogger has a set of hardwired for use when no MessageLogger configuration appears in the config file These match the contents of the MessageLogger cfi file Although these defaults are hardwired into it is recognized that changing circumstances and experience withthe framework will make necessary changes in the defaults the defaults are kept in a clean form in one for ease of modification Multiple sets of these defaults can be corresponding to multiple modes of operation For the production while occasional release validation jobs might want output concerning info messages as well In the example we will show how to a Change the default summary threshold for the existing default mode b Create a new with a different summary threshold If you are changing the main it is probably a good idea to change the MessageLogger_cfi py file to keep the default in step with the contents of that file All the default information is kept in three only HardwiredDefaults cc needs to change If you are creating a new then the *h and MessageLoggerDefaults cc files will need modification EXAMPLE | Change |
| Making New Hardwired Defaults for the and how to create a specialized set of selectable by doing cmsRun mode whateverNameYouChoose The MessageLogger has a set of hardwired for use when no MessageLogger configuration appears in the config file These match the contents of the MessageLogger cfi file Although these defaults are hardwired into it is recognized that changing circumstances and experience withthe framework will make necessary changes in the defaults the defaults are kept in a clean form in one for ease of modification Multiple sets of these defaults can be corresponding to multiple modes of operation For the production while occasional release validation jobs might want output concerning info messages as well In the example we will show how to a Change the default summary threshold for the existing default mode b Create a new with a different summary threshold If you are changing the main it is probably a good idea to change the MessageLogger_cfi py file to keep the default in step with the contents of that file All the default information is kept in three only HardwiredDefaults cc needs to change If you are creating a new then the *h and MessageLoggerDefaults cc files will need modification EXAMPLE in the existing default the default summary threshold for the message statistics going to cerr from INFO to WARNING Observe that currently the PSet for the statistics destination is not in the cfg | file |
| it shares cerr with the ordinary cerr output destination So we will have to give the statistics destination its own name and direct its output to cerr In _cfg py | language |
| it shares cerr with the ordinary cerr output destination So we will have to give the statistics destination its own name and direct its output to cerr In _cfg py | statistics = cms.untracked.vstring('cerr') |
| it shares cerr with the ordinary cerr output destination So we will have to give the statistics destination its own name and direct its output to cerr In _cfg py becomes | cerr_stats |
| it shares cerr with the ordinary cerr output destination So we will have to give the statistics destination its own name and direct its output to cerr In _cfg py becomes Also note that the default mode that you would get by just saying cmsRun with no which gives GridJobMode You can see this in HardwiredDefaults | cc |
| You can see this line in the about lines after the start | Step |
| You can see this line in the about lines after the start including every statistics | destination |
| Note that event though this is a statistics it goes into the map named destination we want to | add |
| Note that event though this is a statistics it goes into the map named destination we want to | output |
| b In MessageService src MessageLoggerDefaults | h |
| c Still in MessageLoggerDefaults ad a case to dispatch that method to the MessageLoggerDefaults | ctor |
| break | |
| case | ReleaseValidationJobMode |
| Enumerator | |
|---|---|
| GridJobMode | |
| AnalysisJobMode | |
| NilJobMode | |
| GridJobMode | |
| AnalysisJobMode | |
| NilJobMode | |
| GridJobMode | |
| AnalysisJobMode | |
| NilJobMode | |
Definition at line 163 of file MakingNewDefaults.txt.
| You can see this line in the about lines after the start including every statistics can have a PSet with the options for that destination The class that corresponds to that PSet is called Destination The cerr statistics did not previously have such a PSet so now we add one Note that to avoid name clashes we always enclose the code for setting up a Destination in braces So far we are adding | ( | after the close brace for the section that started with Destination | FrameworkJobReport | ) |
Definition at line 107 of file MakingNewDefaults.txt.
| Making New Hardwired Defaults for the and how to create a specialized set of selectable by doing cmsRun mode whateverNameYouChoose The MessageLogger has a set of hardwired for use when no MessageLogger configuration appears in the config file These match the contents of the MessageLogger cfi file Although these defaults are hardwired into it is recognized that changing circumstances and experience withthe framework will make necessary changes in the defaults the defaults are kept in a clean form in one for ease of modification Multiple sets of these defaults can be corresponding to multiple modes of operation For the production while occasional release validation jobs might want output concerning info messages as well In the example we will show how to a Change the default summary threshold for the existing default mode b Create a new with a different summary threshold If you are changing the main default | ( | that | is, |
| the one gotten wheen no mode is | specified | ||
| ) |
| b In MessageService src MessageLoggerDefaults add a method to set up that mode In the section with comment I added the line void hardwireReleaseValidationJobMode | ( | ) |
| if | ( | jm | = ="grid" | ) |
|
new |
Definition at line 189 of file MakingNewDefaults.txt.
| So the relevant code implementing the defaults for this mode is MessageLoggerDefaults::hardwireGridJobMode () Step 1 to statistics push_back | ( | "cerr_stats" | ) |
| Making New Hardwired Defaults for the and how to create a specialized set of selectable by doing cmsRun mode whateverNameYouChoose The MessageLogger has a set of hardwired for use when no MessageLogger configuration appears in the config file These match the contents of the MessageLogger cfi file Although these defaults are hardwired into it is recognized that changing circumstances and experience withthe framework will make necessary changes in the defaults the defaults are kept in a clean form in one for ease of modification Multiple sets of these defaults can be corresponding to multiple modes of operation For the production running | ( | which is in a sense the"default"default | mode | ) |
| Note that event though this is a statistics it goes into the map named destination we want to add |
Definition at line 115 of file MakingNewDefaults.txt.
| Making New Hardwired Defaults for the and how to create a specialized set of selectable by doing cmsRun mode whateverNameYouChoose The MessageLogger has a set of hardwired for use when no MessageLogger configuration appears in the config file These match the contents of the MessageLogger cfi file Although these defaults are hardwired into it is recognized that changing circumstances and experience withthe framework will make necessary changes in the defaults the defaults are kept in a clean form in one for ease of modification Multiple sets of these defaults can be corresponding to multiple modes of operation For the production while occasional release validation jobs might want output concerning info messages as well In the example below |
Definition at line 23 of file MakingNewDefaults.txt.
| break |
Definition at line 182 of file MakingNewDefaults.txt.
| d In MessageService src HardwiredDefaults cc |
Definition at line 69 of file MakingNewDefaults.txt.
| it shares cerr with the ordinary cerr output destination So we will have to give the statistics destination its own name and direct its output to cerr In _cfg py becomes cerr_stats |
Definition at line 63 of file MakingNewDefaults.txt.
| Making New Hardwired Defaults for the and how to create a specialized set of selectable by doing cmsRun mode whateverNameYouChoose The MessageLogger has a set of hardwired for use when no MessageLogger configuration appears in the config file These match the contents of the MessageLogger cfi file Although these defaults are hardwired into it is recognized that changing circumstances and experience withthe framework will make necessary changes in the defaults the defaults are kept in a clean form in one for ease of modification Multiple sets of these defaults can be corresponding to multiple modes of operation For the production while occasional release validation jobs might want output concerning info messages as well In the example we will show how to a Change the default summary threshold for the existing default mode b Create a new with a different summary threshold If you are changing the main it is probably a good idea to change the MessageLogger_cfi py file to keep the default in step with the contents of that file All the default information is kept in three only HardwiredDefaults cc needs to change If you are creating a new then the* h and MessageLoggerDefaults cc files will need modification EXAMPLE Change |
Definition at line 41 of file MakingNewDefaults.txt.
| Making New Hardwired Defaults for the and how to create a specialized set of selectable by doing cmsRun mode whateverNameYouChoose The MessageLogger has a set of hardwired for use when no MessageLogger configuration appears in the config file These match the contents of the MessageLogger cfi file Although these defaults are hardwired into code |
Definition at line 5 of file MakingNewDefaults.txt.
| c Still in MessageLoggerDefaults ad a case to dispatch that method to the MessageLoggerDefaults ctor |
Definition at line 177 of file MakingNewDefaults.txt.
| Making New Hardwired Defaults for the and how to create a specialized set of selectable by doing cmsRun mode whateverNameYouChoose The MessageLogger has a set of hardwired defaults |
Definition at line 5 of file MakingNewDefaults.txt.
Definition at line 102 of file MakingNewDefaults.txt.
| Making New Hardwired Defaults for the and how to create a specialized set of selectable by doing cmsRun mode whateverNameYouChoose The MessageLogger has a set of hardwired for use when no MessageLogger configuration appears in the config file These match the contents of the MessageLogger cfi file Although these defaults are hardwired into it is recognized that changing circumstances and experience withthe framework will make necessary changes in the defaults the defaults are kept in a clean form in one for ease of modification Multiple sets of these defaults can be corresponding to multiple modes of operation For example |
Definition at line 5 of file MakingNewDefaults.txt.
| Making New Hardwired Defaults for the and how to create a specialized set of selectable by doing cmsRun mode whateverNameYouChoose The MessageLogger has a set of hardwired for use when no MessageLogger configuration appears in the config file These match the contents of the MessageLogger cfi file Although these defaults are hardwired into it is recognized that changing circumstances and experience withthe framework will make necessary changes in the defaults the defaults are kept in a clean form in one for ease of modification Multiple sets of these defaults can be corresponding to multiple modes of operation For the production while occasional release validation jobs might want output concerning info messages as well In the example we will show how to a Change the default summary threshold for the existing default mode b Create a new with a different summary threshold If you are changing the main it is probably a good idea to change the MessageLogger_cfi py file to keep the default in step with the contents of that file All the default information is kept in three only HardwiredDefaults cc needs to change If you are creating a new then the* h and MessageLoggerDefaults cc files will need modification EXAMPLE in the existing default the default summary threshold for the message statistics going to cerr from INFO to WARNING Observe that currently the PSet for the statistics destination is not in the cfg file |
Definition at line 41 of file MakingNewDefaults.txt.
| Making New Hardwired Defaults for the and how to create a specialized set of selectable by doing cmsRun mode whateverNameYouChoose The MessageLogger has a set of hardwired for use when no MessageLogger configuration appears in the config file These match the contents of the MessageLogger cfi file Although these defaults are hardwired into it is recognized that changing circumstances and experience withthe framework will make necessary changes in the defaults the defaults are kept in a clean form in one for ease of modification Multiple sets of these defaults can be corresponding to multiple modes of operation For the production while occasional release validation jobs might want output concerning info messages as well In the example we will show how to a Change the default summary threshold for the existing default mode b Create a new with a different summary threshold If you are changing the main it is probably a good idea to change the MessageLogger_cfi py file to keep the default in step with the contents of that file All the default information is kept in three files |
Definition at line 41 of file MakingNewDefaults.txt.
Definition at line 170 of file MakingNewDefaults.txt.
| it shares cerr with the ordinary cerr output destination So we will have to give the statistics destination its own name and direct its output to cerr In _cfg py language |
Definition at line 56 of file MakingNewDefaults.txt.
Definition at line 5 of file MakingNewDefaults.txt.
| it shares cerr with the ordinary cerr output destination So we will have to give the statistics destination its own name and direct its output to cerr In _cfg py becomes Also note that the default mode that you would get by just saying cmsRun with no mode = is mode="grid" |
Definition at line 23 of file MakingNewDefaults.txt.
| Note that event though this is a statistics it goes into the map named destination we want to output |
Definition at line 124 of file MakingNewDefaults.txt.
| Making New Hardwired Defaults for the and how to create a specialized set of selectable by doing cmsRun mode whateverNameYouChoose The MessageLogger has a set of hardwired for use when no MessageLogger configuration appears in the config file These match the contents of the MessageLogger cfi file Although these defaults are hardwired into it is recognized that changing circumstances and experience withthe framework will make necessary changes in the defaults the defaults are kept in a clean form in one place |
Definition at line 5 of file MakingNewDefaults.txt.
| Making New Hardwired Defaults for the and how to create a specialized set of selectable by doing cmsRun mode whateverNameYouChoose The MessageLogger has a set of hardwired for use when no MessageLogger configuration appears in the config file These match the contents of the MessageLogger cfi file Although these defaults are hardwired into it is recognized that changing circumstances and experience withthe framework will make necessary changes in the defaults the defaults are kept in a clean form in one for ease of modification Multiple sets of these defaults can be provided |
Definition at line 5 of file MakingNewDefaults.txt.
| @ ReleaseValidationJobMode |
Definition at line 184 of file MakingNewDefaults.txt.
| it shares cerr with the ordinary cerr output destination So we will have to give the statistics destination its own name and direct its output to cerr In _cfg py becomes statistics = cms.untracked.vstring('cerr') |
Definition at line 58 of file MakingNewDefaults.txt.
| Note that event though this is a statistics it goes into the map named destination Step |
Definition at line 102 of file MakingNewDefaults.txt.
| Making New Hardwired Defaults for the and how to create a specialized set of selectable by doing cmsRun mode whateverNameYouChoose The MessageLogger has a set of hardwired for use when no MessageLogger configuration appears in the config file These match the contents of the MessageLogger cfi file Although these defaults are hardwired into it is recognized that changing circumstances and experience withthe framework will make necessary changes in the defaults Therefore |
Definition at line 5 of file MakingNewDefaults.txt.
1.8.11
