Changes between Version 16 and Version 17 of Reweight
- Timestamp:
- Feb 1, 2016, 11:32:55 AM (9 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Reweight
v16 v17 8 8 = Reweighting of NLO sample 9 9 10 As in 2.3.3, we only offer "LO"reweighting of NLO sample (also call "kamikaze" reweighting). This consists to reweight the S events by the born matrix element and the H events by the real matrix element. We have shown that for EW EFT theory this is a correct approach. The way to run the code is the same as for the LO (see below)10 As in 2.3.3, we only offer Leading Order type reweighting of NLO sample (also call "kamikaze" reweighting). This consists to reweight the S events by the born matrix element and the H events by the real matrix element. We have shown that for EW EFT theory this is a correct approach. The way to run the code is the same as for the LO (see below) 11 11 12 12 The correct NLO reweighting is only available on alpha version so far and can be requested by email to olivier Mattelaer. This version will be available in 2.4.0 … … 14 14 In order to perform the correct NLO reweighting, you need to generate the original samples with the following options: 15 15 True = keep_rwgt_info ! keep the information for reweighting in the lhe file (huge impact on size file) 16 After the reweighting will automatically be the NLO one and everything follows the LO implementation. 17 In order to run the "kamikaze" reweighting on this sample, you can include in the reweighting_card the following command: "change mode LO" 16 After the reweighting will automatically be the NLO and, for the user point of view, the interface to run the re-weighting is the same as the LO one described below. 17 In order to run the "kamikaze" reweighting on this sample, you can include in the reweighting_card the following command (at the beginning of the file): 18 """ 19 change mode LO 20 """ 18 21 19 22 20 23 = Technical details 21 24 == Limitation 22 1. The two theoretical hypothesis should differ ONLY by difference in the model parameters. So this should be the same pdf/cut (you can change model and process definition).23 2. The scale choice for the reweighting is done events by events and is given by the value in the LHE file. The same scale is used for both Hypothesis. 24 3. In presence of decay chain the order of the particle in the events file is important. This is important if you want to use this tools with LHE events not produced by MadGraph/MadEvent. 25 26 == How to get the code27 The code is released with any Madgraph version (since 2.0)25 1. 26 27 28 The two theoretical hypothesis should differ ONLY by difference in the model parameters. So this should be the same pdf/cut (you can change model and process definition). 29 2. Note that the functional form of the hard scale can not be changed. 30 3. In presence of decay chain the order of the particle in the events file is important. This is important if you want to use this tools with LHE events not produced by MadGraph5_aMC@NLO. 28 31 29 32 == Do I need special package 30 Starting from M G5.2.3.2, you need to have f2py on your machine. The easiest way to install f2py is to install numpy (if not already done).33 Starting from MadGraph5_aMC@NLO.2.3.2, you need to have f2py on your machine. The easiest way to install f2py is to install numpy (if not already done). 31 34 32 35 == How to use the code on the flight. 36 37 --> Add comment: Same for the NLO. Here some examples. 33 38 34 39 When running the generation of events (./bin/generate_events from the local directory or "launch" via the mg5 interface) … … 77 82 The default file is basically empty and will make the re-weighting to crash since both theoretical hypothesis are identical. 78 83 79 == How to use the code afterwards. 84 == How to use the code after the generation of events as been completed. 85 86 --> Add for the NLO 80 87 81 88 You can also use the madevent interface as explained below: 82 89 83 90 1. go to the process directory. 84 2. launch the '''./bin/madevent''' script 91 2. launch the '''./bin/madevent''' script 85 92 3. type '''reweight RUN_NAME''' 86 93 4. then you will see the following question: … … 92 99 [0, done, 1, reweight, enter path][60s to answer] 93 100 }}} 94 If you didn't define the content of this filealready. You need to do it. The syntax is explained inside the file, and you can see example below (validation section). The '''important''' point, is that the first line should be launch, and then you specify which parameter, you want to modify. This is the exact same syntax has for scripting a scan over parameter.101 If you didn't define the content of reweight_card.dat already. You need to do it. The syntax is explained inside the file, and you can see example below (validation section). The '''important''' point, is that the first line should be launch, and then you specify which parameter, you want to modify. This is the exact same syntax has for scripting a scan over parameter. 95 102 5. exit the file and you are done (the script will run). 96 103 … … 102 109 103 110 = Options 104 Note all the following options will be available in M G5version 2.3.2111 Note all the following options will be available in Madgraph5_aMC@NLO since version 2.3.2 105 112 1. "change model <XXX>" performed the reweighting within a new model (you then need to profide a full param_card and not a difference) 106 113 2. "change process <XXX>" change the process definition of the process. … … 109 116 5. "change helicity <True|False>": perform reweighting for the given helicity (True --default--) or do the sum over helicity. 110 117 6. "change rwgt_dir <PATH>": change directory where the computation is performed. This can be use to avoid to recreate/recompile the fortran executable if pointing to a previously existing directory. 118 7. change mode LO: 111 119 112 120 113 121 = Input/Output format 114 122 115 1. the output format follows the Leshouches agreement (not yet published): http://phystev.in2p3.fr/wiki/2013:groups:tools_lheextension#the_proposal123 1. the output format follows the Leshouches agreement version 3 [link arxiv] 116 124 117 125 as an example the header looks like: … … 181 189 }}} 182 190 183 4. An example of the full log is:184 {{{185 ************************************************************186 * *187 * W E L C O M E to M A D G R A P H 5 *188 * M A D E V E N T *189 * *190 * * * *191 * * * * * *192 * * * * * 5 * * * * *193 * * * * * *194 * * * *195 * *196 * VERSION 2.0.0.beta3 2013-02-14 *197 * *198 * The MadGraph Development Team - Please visit us at *199 * https://server06.fynu.ucl.ac.be/projects/madgraph *200 * *201 * Type 'help' for in-line help. *202 * *203 ************************************************************204 INFO: load configuration from /Users/omatt/.mg5/mg5_configuration.txt205 INFO: load configuration from /Users/omatt/Documents/eclipse/reweight_module/PROC_sm_11/Cards/me5_configuration.txt206 INFO: load configuration from /Users/omatt/Documents/eclipse/reweight_module/input/mg5_configuration.txt207 INFO: load configuration from /Users/omatt/Documents/eclipse/reweight_module/PROC_sm_11/Cards/me5_configuration.txt208 MGME5>reweight run_01209 Do you want to edit one cards (press enter to bypass editing)?210 1 / reweight : reweight_card.dat211 you can also212 - enter the path to a valid card.213 [0, done, 1, reweight, enter path][60s to answer]214 >1215 open /Users/omatt/Documents/eclipse/reweight_module/PROC_sm_11/Cards/reweight_card.dat216 Do you want to edit one cards (press enter to bypass editing)?217 1 / reweight : reweight_card.dat218 you can also219 - enter the path to a valid card.220 [0, done, 1, reweight, enter path]221 >222 INFO: Extracting the banner ...223 INFO: process: p p > e+ e-224 INFO: options:225 INFO: Running Reweight226 launch227 INFO: detected model: sm. Loading...228 INFO: generating the square matrix element for reweighting229 INFO: generate p p > e+ e- ;230 INFO: Done 1.197231 set aewm1 100232 INFO: modify param_card information BLOCK sminputs with id (1,) set to 100.0233 Do you want to edit one cards (press enter to bypass editing)?234 1 / param : param_card.dat235 9 / plot : plot_card.dat236 you can also237 - enter the path to a valid card or banner.238 - use the 'set' command to modify a parameter directly.239 The set option works only for param_card and run_card.240 Type 'help set' for more information on this command.241 [0, done, 1, param, 9, plot, enter path]242 The answer to the previous question is not set in your input file243 Use 0 value244 INFO: starts to compute weight for events with the following modification to the param_card:245 INFO: set param_card sminputs 1 100.0246 247 INFO: Event nb 0 current time: 23h39248 INFO: Event nb 1000 0.61s249 INFO: Event nb 2000 1.1s250 INFO: Event nb 3000 1.5s251 INFO: Event nb 4000 2.1s252 INFO: Event nb 5000 2.5s253 INFO: Event nb 6000 2.9s254 INFO: Event nb 7000 3.3s255 INFO: Event nb 8000 3.8s256 INFO: Event nb 9000 4.2s257 INFO: All event done (nb_event: 10000) 4.6s258 INFO: Event /Users/omatt/Documents/eclipse/reweight_module/PROC_sm_11/Events/run_01/unweighted_events.lhe have now the additional weight259 INFO: new cross-section is : 1135.25 pb260 launch261 set aewm1 200262 INFO: modify param_card information BLOCK sminputs with id (1,) set to 200.0263 Do you want to edit one cards (press enter to bypass editing)?264 1 / param : param_card.dat265 9 / plot : plot_card.dat266 you can also267 - enter the path to a valid card or banner.268 - use the 'set' command to modify a parameter directly.269 The set option works only for param_card and run_card.270 Type 'help set' for more information on this command.271 [0, done, 1, param, 9, plot, enter path]272 The answer to the previous question is not set in your input file273 Use 0 value274 INFO: starts to compute weight for events with the following modification to the param_card:275 INFO: set param_card sminputs 1 200.0276 277 INFO: Event nb 0 current time: 23h39278 INFO: Event nb 1000 0.48s279 INFO: Event nb 2000 1s280 INFO: Event nb 3000 1.5s281 INFO: Event nb 4000 2s282 INFO: Event nb 5000 2.4s283 INFO: Event nb 6000 2.9s284 INFO: Event nb 7000 3.3s285 INFO: Event nb 8000 3.8s286 INFO: Event nb 9000 4.2s287 INFO: All event done (nb_event: 10000) 4.7s288 INFO: Event /Users/omatt/Documents/eclipse/reweight_module/PROC_sm_11/Events/run_01/unweighted_events.lhe have now the additional weight289 INFO: new cross-section is : 1095.28 pb290 launch291 set aewm1 300292 INFO: modify param_card information BLOCK sminputs with id (1,) set to 300.0293 Do you want to edit one cards (press enter to bypass editing)?294 1 / param : param_card.dat295 9 / plot : plot_card.dat296 you can also297 - enter the path to a valid card or banner.298 - use the 'set' command to modify a parameter directly.299 The set option works only for param_card and run_card.300 Type 'help set' for more information on this command.301 [0, done, 1, param, 9, plot, enter path]302 The answer to the previous question is not set in your input file303 Use 0 value304 INFO: starts to compute weight for events with the following modification to the param_card:305 INFO: set param_card sminputs 1 300.0306 307 INFO: Event nb 0 current time: 23h39308 INFO: Event nb 1000 0.62s309 INFO: Event nb 2000 1.1s310 INFO: Event nb 3000 1.5s311 INFO: Event nb 4000 2s312 INFO: Event nb 5000 2.5s313 INFO: Event nb 6000 2.9s314 INFO: Event nb 7000 3.4s315 INFO: Event nb 8000 3.8s316 INFO: Event nb 9000 4.3s317 INFO: All event done (nb_event: 10000) 4.7s318 INFO: Event /Users/omatt/Documents/eclipse/reweight_module/PROC_sm_11/Events/run_01/unweighted_events.lhe have now the additional weight319 INFO: new cross-section is : 1329.52 pb320 INFO: Original cross-section: 949.58665707 +- 2.2589158361 pb321 INFO: Computed cross-section:322 INFO: 1 : 1135.24526333323 INFO: 2 : 1095.27584154324 INFO: 3 : 1329.51775579325 }}}326 191 = Validation 327 192