print_results options

Hi Raquel,

This is actually the long format.

If you use the latest scan method (the one introduced in 2.3.3, the latest entry of the following link:
https://blueprints.launchpad.net/mg5amcnlo/+spec/scan-in-mass)
Then you have an automatic file created with all the value of the param_card which differ between the runs.
This might be what you want.

Cheers,

Olivier

On 22 Jan 2018, at 13:47, Raquel Gomez Ambrosio <<email address hidden><mailto:<email address hidden>>> wrote:

New question #663389 on MadGraph5_aMC@NLO:
https://answers.launchpad.net/mg5amcnlo/+question/663389

Dear experts, I'm running a a scan over different parameters, using the commands "launch - set" and it seems to work properly. My only problem is with the output, since I would like to name each run after the parameter scan, or at least get the value of the scanned parameter next to each cross section.

The syntax I am using is:

print_results --path=./xsec_scan_param.txt

and the output is of the form:

 === Results Summary for run: run_01 tag: tag_1 process: t_all_all_mssm ===
    Width : 1.407 +- 0.0003 GeV
    Nb of events : 10000

 === Results Summary for run: run_02 tag: tag_1 process: t_all_all_mssm ===
    Width : 1.558 +- 1.516e-05 GeV
    Nb of events : 10000

I tried to add the option "--format=long" but the .txt output is empty in that case.... do you know how could I get a bit more of feedback on each run in the final txt file?

Thanks a lot!

--
You received this question notification because you are an answer
contact for MadGraph5_aMC@NLO.