recrods: fix record 5500

* Fixes wrong link & adds a prominent link to record 5501 (closes cernopendata#2517)

Signed-off-by: Artemis Lavasa <[email protected]>

cernopendata/modules/fixtures/data/records/cms-tools-higgsexample20112012.json

@@ -119,7 +119,7 @@
       ]
     },
     "usage": {
-      "description": " <p>In addition to the instructions below which guide you through the example in detail, <a href=\"https://github.com/cms-opendata-analyses/HiggsExample20112012\">a github repository</a> based on this original example is also provided</p>\n <p> There are four levels of increasing complexity for this example:</p> <p><ol><li><strong>Compare</strong> the provided final output plot <a href=\"/record/5500/files/mass4l_combine.pdf\">mass4l_combine.pdf</a> or  <a href=\"/record/5500/files/mass4l_combine.png\">mass4l_combine.png</a> to <a href=\"https://inspirehep.net/record/1124338/files/H4l_mass_v3.png\">the published one</a>, keeping in mind the caveats mentioned in this record.</li>\n  <li><strong>Reproduce</strong> the final output plot from the predefined histogram files using a root macro (~few minutes - ~few hours, depending on setup and proficiency)</li>\n  <ul><li> if a ROOT version on the local computer compatible with ROOT 5.32/00 is running, use the local version (avoids installation of VM). Otherwise, follow the instructions in <a href=\"/docs/cms-virtual-machine-2011\">CMS 2011 Virtual Machines: How to install</a> up to and including the command 'cmsenv', in order to install the VirtualBox and the CMS Open Data VM, and run ROOT there (the validation step with the Demo example may be skipped)</li>\n <li>if not already proficient in ROOT, consider doing <a href=\"https://root.cern.ch/introductory-tutorials\"> a brief ROOT introductory tutorial</a> in order to understand what the root macro will do</li>\n <li>create a new directory, e.g. rootfiles <code>mkdir rootfiles</code></li>\n <li>switch to that directory <code>cd rootfiles</code> and download the preproduced *.root histogram files given in <a href=\"/record/5501\"> this record</a> for all relevant samples to this directory</li>\n<ul><li>Alternatively, on the command line in the directory <code>rootfiles</code>, type <code>wget http://opendata.web.cern.ch/record/5501/files/rootfilelist.txt</code> and then <code>wget -i rootfilelist.txt</code></li>\n <li>If you wish, you may look at the content of these files using ROOT: e.g. type <code>root</code>, and on the root promt, type <code>TBrowser t</code>, then double-click on the relevant file</li></ul>\n <li>download the root macro <a href=\"/record/5500/files/M4Lnormdatall.cc\">M4Lnormdatall.cc</a> from this record into the same directory</li>\n <li> on the linux prompt, type <code>root -l M4Lnormdatall.cc</code></li>\n <ul><li> you will get the output plot on the screen</li></ul>\n <li> either, on the ROOT canvas (picture) click <code>file->Quit ROOT</code> or, on the root [] prompt, type <code>.q</code></li>\n <ul><li>you will exit ROOT and find the output plot in mass4l_combined_user.pdf</li></ul>\n  <li> you can compare this plot with the plots provided in 1.</li></ul>\n  <li><strong>Produce</strong> a root data input file from original data and MC files for one Higgs signal candidate and for the simulated Higgs signal with reduced statistics (for speed reasons) and reproduce the final output plot containing your own input using a root macro (~1 hour if Virtual machine is already installed, depending on internet connection and computer performance, up to ~few hours otherwise)</li>\n  <ul><li>if not already done, follow instructions for steps 1 and 2 in <a href=\"/docs/cms-virtual-machine-2011\"> CMS 2011 Virtual Machines: How to install</a>, including the installation of the demo analyzer</li>\n <li> in the <code>Demo/DemoAnalyzer/</code> directory, which is created following Step 2: How to test and validate, replace <code>BuildFile.xml</code> by <a href=\"/record/5500/files/BuildFile.xml\">the version</a> downloaded from this record</li>\n <li> download <a href=\"/record/5500/files/HiggsDemoAnalyzer.cc\">HiggsDemoAnalyzer.cc</a> from this record to the <code>Demo/Demoanalyzer/src</code> subdirectory</li>\n <li> in <code>Demo/DemoAnalyzer/</code>, recompile <code>scram b</code></li>\n <li> download <a href=\"/record/5500/files/demoanalyzer_cfg_level3data.py\">demoanalyzer_cfg_level3data.py</a> (data example) and <a href=\"/record/5500/files/demoanalyzer_cfg_level3MC.py\">demoanalyzer_cfg_level3MC.py</a> (Higgs simulation example)</li>\n <li> create datasets directory <code>mkdir datasets</code> and change to this directory <code>cd datasets</code></li>\n <li> download the 2012 JSON validation file from <a href=\"/record/1002\">the corresponding record</a> to this directory</li>\n <li>if not yet done at level 2, create the directory <code>rootfiles</code> and download all the level 2 root files to this directory (see level 2)</li>\n <li>run the two analysis jobs (one on data, one on MC, the input files are already predefined)</li>\n <ul>      <li><code>cmsRun demoanalyzer_cfg_level3data.py</code> will produce output file <code>DoubleMuParked2012C_10000_Higgs.root</code> containing 1 Higgs candidate from the data</li>\n <li><code>cmsRun demoanalyzer_cfg_level3MC.py</code> will produce output file <code>Higgs4L1file.root</code> containing the Higgs signal distributions with reduced statistics</li></ul>\n <li> move the two .root files above to the <code>rootfiles</code> directory, together with the predefined files</li>\n <ul><li><code>mv DoubleMuParked2012C_10000_Higgs.root rootfiles/.</code></li>\n <li><code>mv Higgs4L1file.root rootfiles/.</code></li></ul>\n <li> change directory <code>cd rootfiles</code> and download the macro <a href=\"/record/5500/files/M4Lnormdatall_lvl3.cc\">M4Lnormdatall_lvl3.cc</a> to this directory</li>\n <li> on the linux prompt, type <code>root -l M4Lnormdatall_lvl3.cc</code></li>\n <ul><li>you will get the output plot on the screen; the magenta Higgs signal histogram will now be the one you produced, and the one data event which you have selected will be shown as a blue triangle. All other parts of the plot are the same as in 2.</li></ul>\n <li> either, on the ROOT canvas (picture) click <code>file->Quit ROOT</code> or, on the root [] prompt, type <code>.q</code></li>\n <ul><li>you will exit ROOT and find the output plot in mass4l_combined_user3.pdf </li></ul>\n</ul>\n  <li><strong>Reproduce the full example analysis</strong> (up to ~1 month or more on single CPU with fast internet connection, depending on internet connection speed and computer performance)</li>\n <ul><li>start by running level 3 and understand what you have done</li>\n <li> download <a href=\"/record/5500/files/demoanalyzer_cfg_level4data.py\">demoanalyzer_cfg_level4data.py</a> and <a href=\"/record/5500/files/demoanalyzer_cfg_level4MC.py\">demoanalyzer_cfg_level4MC.py</a> from this record</li>\n <li>at this level, instead of running over a single file, you will run over so-called index files which contain chains of files</li>\n <li> download all the data index files for the datasets listed in <a href=\"/record/5500/files/List_indexfile.txt\">List_indexfile.txt</a> to the <code>datasets</code> directory (you can find the links to the datasets in this record)</li>\n <li> download <a href=\"/record/1001\">the 2011 JSON validation file</a> to the <code>datasets</code> directory (in which you should already have the 2012 one)</li>\n <li> download all the MC index files for the MC sets listed in <code>List_indexfile.txt</code> to the <code>MCsets</code> directory (after having created it)</li>\n <li> edit the relevant demoanalyzer_cfg file and insert the index file you want; for data, make sure to use the correct JSON validation file in each case; set an output file name of your choice for each sample which you will recognise</li>\n <li> run the analysis job (<code>cmsRun demoanalyzer_cfg_level4...</code>) sequentially on all the input samples listed in <code>List_indexfile.txt</code>, i.e. produce all root output files yourself. If you have access to a computer farm with local support for the installation of the CMS software (the Open Data team can only provide support for the single virtual machine mode), you may also run the analysis in parallel on different CPUs, correspondingly speeding up the result.</li>\n <li> merge all the files from different index files of a dataset by using root tools</li>\n <ul><li>If everything ran correctly, at this stage the content of your rootfiles should be identical to the one in the predefined rootfiles. If you don't want to run everything, you can also run only some of the datasets (but all events of all index files of a dataset must be treated and merged), and use the predefined ones for the others. </li> </ul>\n <li> go to 2., using your own root output files instead of the predefined ones, i.e. edit the file <a href=\"/record/5500/files/M4Lnormdatall.cc\">M4Lnormdatall.cc</a> accordingly. If everything worked correctly you should get an output identical to mass4lcombine.pdf, but now using your own files.</li>\n </ul></ol>\n </p> "
+      "description": " <p>In addition to the instructions below which guide you through the example in detail, <a href=\"https://github.com/cms-opendata-analyses/HiggsExample20112012\">a github repository</a> based on this original example is also provided. The root files needed for the Level 3 exercise can be found <a href=\"/record/5501\">here</a>.</p>\n <p> There are four levels of increasing complexity for this example:</p> <p><ol><li><strong>Compare</strong> the provided final output plot <a href=\"/record/5500/files/mass4l_combine.pdf\">mass4l_combine.pdf</a> or <a href=\"/record/5500/files/mass4l_combine.png\">mass4l_combine.png</a> to <a href=\"https://inspirehep.net/record/1124338/files/H4l_mass_v3.png\">the published one</a>, keeping in mind the caveats mentioned in this record.</li>\n  <li><strong>Reproduce</strong> the final output plot from the predefined histogram files using a root macro (~few minutes - ~few hours, depending on setup and proficiency)</li>\n  <ul><li> if a ROOT version on the local computer compatible with ROOT 5.32/00 is running, use the local version (avoids installation of VM). Otherwise, follow the instructions in <a href=\"/docs/cms-virtual-machine-2011\">CMS 2011 Virtual Machines: How to install</a> up to and including the command 'cmsenv', in order to install the VirtualBox and the CMS Open Data VM, and run ROOT there (the validation step with the Demo example may be skipped)</li>\n <li>if not already proficient in ROOT, consider doing <a href=\"https://root.cern.ch/introductory-tutorials\"> a brief ROOT introductory tutorial</a> in order to understand what the root macro will do</li>\n <li>create a new directory, e.g. rootfiles <code>mkdir rootfiles</code></li>\n <li>switch to that directory <code>cd rootfiles</code> and download the preproduced *.root histogram files given in <a href=\"/record/5501\"> this record</a> for all relevant samples to this directory</li>\n<ul><li>Alternatively, on the command line in the directory <code>rootfiles</code>, type <code>wget http://opendata.web.cern.ch/record/5501/files/rootfilelist.txt</code> and then <code>wget -i rootfilelist.txt</code></li>\n <li>If you wish, you may look at the content of these files using ROOT: e.g. type <code>root</code>, and on the root promt, type <code>TBrowser t</code>, then double-click on the relevant file</li></ul>\n <li>download the root macro <a href=\"/record/5500/files/M4Lnormdatall.cc\">M4Lnormdatall.cc</a> from this record into the same directory</li>\n <li> on the linux prompt, type <code>root -l M4Lnormdatall.cc</code></li>\n <ul><li> you will get the output plot on the screen</li></ul>\n <li> either, on the ROOT canvas (picture) click <code>file->Quit ROOT</code> or, on the root [] prompt, type <code>.q</code></li>\n <ul><li>you will exit ROOT and find the output plot in mass4l_combined_user.pdf</li></ul>\n  <li> you can compare this plot with the plots provided in 1.</li></ul>\n  <li><strong>Produce</strong> a root data input file from original data and MC files for one Higgs signal candidate and for the simulated Higgs signal with reduced statistics (for speed reasons) and reproduce the final output plot containing your own input using a root macro (~1 hour if Virtual machine is already installed, depending on internet connection and computer performance, up to ~few hours otherwise)</li>\n  <ul><li>if not already done, follow instructions for steps 1 and 2 in <a href=\"/docs/cms-virtual-machine-2011\"> CMS 2011 Virtual Machines: How to install</a>, including the installation of the demo analyzer</li>\n <li> in the <code>Demo/DemoAnalyzer/</code> directory, which is created following Step 2: How to test and validate, replace <code>BuildFile.xml</code> by <a href=\"/record/5500/files/BuildFile.xml\">the version</a> downloaded from this record</li>\n <li> download <a href=\"/record/5500/files/HiggsDemoAnalyzer.cc\">HiggsDemoAnalyzer.cc</a> from this record to the <code>Demo/Demoanalyzer/src</code> subdirectory</li>\n <li> in <code>Demo/DemoAnalyzer/</code>, recompile <code>scram b</code></li>\n <li> download <a href=\"/record/5500/files/demoanalyzer_cfg_level3data.py\">demoanalyzer_cfg_level3data.py</a> (data example) and <a href=\"/record/5500/files/demoanalyzer_cfg_level3MC.py\">demoanalyzer_cfg_level3MC.py</a> (Higgs simulation example)</li>\n <li> create datasets directory <code>mkdir datasets</code> and change to this directory <code>cd datasets</code></li>\n <li> download the 2012 JSON validation file from <a href=\"/record/1002\">the corresponding record</a> to this directory</li>\n <li>if not yet done at level 2, create the directory <code>rootfiles</code> and download all the level 2 root files to this directory (see level 2)</li>\n <li>run the two analysis jobs (one on data, one on MC, the input files are already predefined)</li>\n <ul>      <li><code>cmsRun demoanalyzer_cfg_level3data.py</code> will produce output file <code>DoubleMuParked2012C_10000_Higgs.root</code> containing 1 Higgs candidate from the data</li>\n <li><code>cmsRun demoanalyzer_cfg_level3MC.py</code> will produce output file <code>Higgs4L1file.root</code> containing the Higgs signal distributions with reduced statistics</li></ul>\n <li> move the two .root files above to the <code>rootfiles</code> directory, together with the predefined files</li>\n <ul><li><code>mv DoubleMuParked2012C_10000_Higgs.root rootfiles/.</code></li>\n <li><code>mv Higgs4L1file.root rootfiles/.</code></li></ul>\n <li> change directory <code>cd rootfiles</code> and download the macro <a href=\"/record/5500/files/M4Lnormdatall_lvl3.cc\">M4Lnormdatall_lvl3.cc</a> to this directory</li>\n <li> on the linux prompt, type <code>root -l M4Lnormdatall_lvl3.cc</code></li>\n <ul><li>you will get the output plot on the screen; the magenta Higgs signal histogram will now be the one you produced, and the one data event which you have selected will be shown as a blue triangle. All other parts of the plot are the same as in 2.</li></ul>\n <li> either, on the ROOT canvas (picture) click <code>file->Quit ROOT</code> or, on the root [] prompt, type <code>.q</code></li>\n <ul><li>you will exit ROOT and find the output plot in mass4l_combined_user3.pdf </li></ul>\n</ul>\n  <li><strong>Reproduce the full example analysis</strong> (up to ~1 month or more on single CPU with fast internet connection, depending on internet connection speed and computer performance)</li>\n <ul><li>start by running level 3 and understand what you have done</li>\n <li> download <a href=\"/record/5500/files/demoanalyzer_cfg_level4data.py\">demoanalyzer_cfg_level4data.py</a> and <a href=\"/record/5500/files/demoanalyzer_cfg_level4MC.py\">demoanalyzer_cfg_level4MC.py</a> from this record</li>\n <li>at this level, instead of running over a single file, you will run over so-called index files which contain chains of files</li>\n <li> download all the data index files for the datasets listed in <a href=\"/record/5500/files/List_indexfile.txt\">List_indexfile.txt</a> to the <code>datasets</code> directory (you can find the links to the datasets in this record)</li>\n <li> download <a href=\"/record/1001\">the 2011 JSON validation file</a> to the <code>datasets</code> directory (in which you should already have the 2012 one)</li>\n <li> download all the MC index files for the MC sets listed in <code>List_indexfile.txt</code> to the <code>MCsets</code> directory (after having created it)</li>\n <li> edit the relevant demoanalyzer_cfg file and insert the index file you want; for data, make sure to use the correct JSON validation file in each case; set an output file name of your choice for each sample which you will recognise</li>\n <li> run the analysis job (<code>cmsRun demoanalyzer_cfg_level4...</code>) sequentially on all the input samples listed in <code>List_indexfile.txt</code>, i.e. produce all root output files yourself. If you have access to a computer farm with local support for the installation of the CMS software (the Open Data team can only provide support for the single virtual machine mode), you may also run the analysis in parallel on different CPUs, correspondingly speeding up the result.</li>\n <li> merge all the files from different index files of a dataset by using root tools</li>\n <ul><li>If everything ran correctly, at this stage the content of your rootfiles should be identical to the one in the predefined rootfiles. If you don't want to run everything, you can also run only some of the datasets (but all events of all index files of a dataset must be treated and merged), and use the predefined ones for the others. </li> </ul>\n <li> go to 2., using your own root output files instead of the predefined ones, i.e. edit the file <a href=\"/record/5500/files/M4Lnormdatall.cc\">M4Lnormdatall.cc</a> accordingly. If everything worked correctly you should get an output identical to mass4lcombine.pdf, but now using your own files.</li>\n </ul></ol>\n </p> "
     },
     "use_with": {
       "description": "The example uses legacy versions of the original CMS datasets in the AOD format, which slightly differ from the ones used for the original publication due to improved calibrations. It also uses legacy versions of the corresponding Monte Carlo simulations, which are again close to, but not identical to, the ones in the original publication. These legacy data and MC sets listed below were used in practice, exactly as they are, in many later CMS publications.",
@@ -155,7 +155,7 @@
           "recid": "6004"
         },
         {
-          "recid": "6004"
+          "recid": "6030"
         },
         {
           "recid": "6003"