diff --git a/first-analysis-steps/analysis-productions.md b/first-analysis-steps/analysis-productions.md index 5f099dcb..a211540c 100644 --- a/first-analysis-steps/analysis-productions.md +++ b/first-analysis-steps/analysis-productions.md @@ -86,6 +86,10 @@ IOHelper().inputFiles([ ``` +{% callout "Reminder" %} +`automatically_configure` will not overwrite your existing configuration of `DataType`, `CondDBtag`, `DDDBtag`, et cetera. Your settings take precedence. +{% endcallout %} + If you don't have your options file from earlier available, or are having trouble, you can [use this options file](code/analysis-productions/ntuple_options.py). The next file needed is a `.yaml` file, which will be used to configure the jobs. Create a new file named `info.yaml`, and add the following to it: @@ -112,7 +116,7 @@ Here, the unindented lines are the names of jobs (although `defaults` has a spec * **application**: the version of DaVinci to use. Here we choose v46r10, the latest for Run 2 at the time of writing (see [here](http://lhcbdoc.web.cern.ch/lhcbdoc/davinci/) to check what versions are available). * **wg**: the working group this production is a part of. Since this is a `$ D^{0} \to K^{-}K^{+} $` decay, we'll set this to `Charm`. * **inform**: optionally, you can enter your email address to receive updates on the status of your jobs. -* **automatically_configure**: setting this to `yes` is what allowed us to remove all of those configuration lines from the options file. This is very useful when creating productions that use multiple years, or both data and MC. +* **automatically_configure**: setting this to `yes` causes the input-data-specific application configuration, e.g. year, `CondDBtag`, `DDDBtag`, and so on to be generated automatically, according to the input data. * **turbo**: Setting this to `yes` indicates `automatically_configure` should configure the application for reading turbo data. * **options**: the list of options files to use. Behind the scenes, these will get passed to DaVinci. * **output**: the name of the output `.root` ntuples. These will get registered in bookkeeping as well.