PADForMA5tune is disable
Hello, I want to use PADForMA5tune in madanalysis v1.7 but it is disable. How can I activate it.
MA5:
MA5: *******
MA5: * *
MA5: * W E L C O M E to M A D A N A L Y S I S 5 *
MA5: * ______ ______ *
MA5: * /'\_/`\/\ __ \/\ ___\ *
MA5: * /\ \ \ \_\ \ \ \__/ *
MA5: * \ \ \__\ \ \ __ \ \___``\ *
MA5: * \ \ \_/\ \ \ \/\ \/\ \_\ \ *
MA5: * \ \_\\ \_\ \_\ \_\ \____/ *
MA5: * \/_/ \/_/\/_/\/_/\/___/ *
MA5: * *
MA5: * MA5 release : 1.7.21 2019/02/07 *
MA5: * *
MA5: * Comput. Phys. Commun. 184 (2013) 222-256 *
MA5: * Eur. Phys. J. C74 (2014) 3103 *
MA5: * *
MA5: * The MadAnalysis Development Team - Please visit us at *
MA5: * https:/
MA5: * *
MA5: * Type 'help' for in-line help. *
MA5: * *
MA5: *******
MA5: Platform: Linux 4.15.0-45-generic [Linux mode]
MA5: Reading user settings ...
MA5: Checking mandatory packages:
MA5: - Python [OK]
MA5: - GNU GCC g++ [OK]
MA5: - GNU Make [OK]
MA5: Checking optional packages devoted to data processing:
MA5: - Zlib [OK]
MA5: - FastJet [OK]
MA5: - Root [OK]
MA5: - Delphes [DEACTIVATED]
MA5: - Delphes-MA5tune [OK]
MA5: Checking the MadAnalysis 5 core library:
MA5: => MadAnalysis libraries found.
MA5: => MadAnalysis test program works.
MA5: Checking optional packages devoted to reinterpretation:
MA5: - SciPy [OK]
MA5: - PAD [OK]
MA5: - PADForMA5tune [DISABLED]
MA5: Checking optional packages devoted to histogramming:
MA5: - Root [OK]
MA5: - Matplotlib [OK]
MA5: - pdflatex [OK]
MA5: - latex [OK]
MA5: Package used for graphical rendering: Root
MA5: *******
MA5: Particle labels exported from madanalysis/
MA5: => 87 particles successfully exported.
MA5: Multiparticle labels exported from madanalysis/
MA5: => Creation of the label 'invisible' (-> missing energy).
MA5: => Creation of the label 'hadronic' (-> jet energy).
MA5: => 8 multiparticles successfully exported.
ma5>
Thank you in advance for your answer.
Question information
- Language:
- English Edit question
- Status:
- Answered
- Assignee:
- No assignee Edit question
- Last query:
- Last reply:
|
Revision history for this message
|
#1 |
Hi,
You can for instance install the missing package by typing 'install PADForMA5tune'.
Cheers,
Benjamin
|
Revision history for this message
|
#2 |
Dear Benjamin,
I already installed it but it is still disabled.
|
Revision history for this message
|
#3 |
Hi,
Please run the code in debug mode and dump me the screen output.
Regards,
Benjamin
> On 4 Mar 2019, at 22:47 , pattara angkinun <email address hidden> wrote:
>
> Question #678555 on MadAnalysis 5 changed:
> https:/
>
> pattara angkinun posted a new comment:
> Dear Benjamin,
>
> I already installed it but it is still disabled.
>
> --
> You received this question notification because you are an answer
> contact for MadAnalysis 5.
|
Revision history for this message
|
#4 |
Dear Benjamin,
pattara@
pattara@
MA5:
MA5: *******
MA5: * *
MA5: * W E L C O M E to M A D A N A L Y S I S 5 *
MA5: * ______ ______ *
MA5: * /'\_/`\/\ __ \/\ ___\ *
MA5: * /\ \ \ \_\ \ \ \__/ *
MA5: * \ \ \__\ \ \ __ \ \___``\ *
MA5: * \ \ \_/\ \ \ \/\ \/\ \_\ \ *
MA5: * \ \_\\ \_\ \_\ \_\ \____/ *
MA5: * \/_/ \/_/\/_/\/_/\/___/ *
MA5: * *
MA5: * MA5 release : 1.7.21 2019/02/07 *
MA5: * *
MA5: * Comput. Phys. Commun. 184 (2013) 222-256 *
MA5: * Eur. Phys. J. C74 (2014) 3103 *
MA5: * *
MA5: * The MadAnalysis Development Team - Please visit us at *
MA5: * https:/
MA5: * *
MA5: * Type 'help' for in-line help. *
MA5: * *
MA5: *******
MA5-DEBUG:
MA5-DEBUG: DEBUG MODE ACTIVATED
MA5-DEBUG:
MA5: Platform: Linux 4.15.0-45-generic [Linux mode]
MA5-DEBUG:
MA5-DEBUG: Machine - Cross platform information
MA5-DEBUG: Machine type: x86_64
MA5-DEBUG: Processor name: x86_64
MA5-DEBUG: Platform: Linux-4.
MA5-DEBUG: Platform release: 4.15.0-45-generic
MA5-DEBUG: System: Linux
MA5-DEBUG: Node: pattara-GL62-6QF
MA5-DEBUG: Number of cores: 8
MA5-DEBUG:
MA5-DEBUG: Machine - OS-specific information
MA5-DEBUG: Java version: ('', '', ('', '', ''), ('', '', ''))
MA5-DEBUG: Windows version: ('', '', '', '')
MA5-DEBUG: Mac Os version: ('', ('', '', ''), '')
MA5-DEBUG: Unix distribution: Linux-4.
MA5-DEBUG:
MA5: Reading user settings ...
MA5-DEBUG: Opening the file: /home/pattara/
MA5-DEBUG: Lines to interpret:
MA5-DEBUG: Closing the file: /home/pattara/
MA5-DEBUG:
MA5-DEBUG: User
MA5-DEBUG: User name: pattara
MA5-DEBUG: User ID: 1000
MA5-DEBUG: Expanding folder ~/: /home/pattara/
MA5-DEBUG: Variable $USER: pattara
MA5-DEBUG: Variable $USERNAME: pattara
MA5-DEBUG: Variable $LNAME:
MA5-DEBUG: Variable $LOGNAME: pattara
MA5-DEBUG: Variable $HOME: /home/pattara
MA5-DEBUG: Variable $HOMEDRIVE:
MA5-DEBUG: Variable $posix:
MA5-DEBUG: Variable $HOMEPATH:
MA5-DEBUG:
MA5-DEBUG: Web access
MA5-DEBUG: enable
MA5-DEBUG:
MA5-DEBUG: Temporary folder
MA5-DEBUG: Variable $TMPDIR:
MA5-DEBUG: Variable $TMP:
MA5-DEBUG: Variable $TEMP:
MA5-DEBUG: Check if the folder /tmp/pattara exists ...
MA5-DEBUG: -> found
MA5-DEBUG: temporary folder will be used for MA5: /tmp/pattara
MA5-DEBUG:
MA5-DEBUG: Download dir
MA5-DEBUG: Check if the folder /tmp/pattara/
MA5-DEBUG: -> found
MA5-DEBUG: download folder will be used for MA5: /tmp/pattara/
MA5-DEBUG:
MA5-DEBUG: Text editor
MA5-DEBUG: Look for the global variable $EDITOR ...
MA5-DEBUG: -> variable not found. VI editor is set by default.
MA5-DEBUG:
MA5: Checking mandatory packages:
MA5-DEBUG: -------
MA5-DEBUG: Detect package python
MA5-DEBUG: Try to detect automatically the package ...
MA5-DEBUG: Extract more informations related to the package ...
MA5-DEBUG:
MA5-DEBUG: Python release: 2.7.15rc1
MA5-DEBUG: Python build: ('default', 'Nov 12 2018 14:31:15')
MA5-DEBUG: Python compiler: GCC 7.3.0
MA5-DEBUG: Python prefix: /usr
MA5-DEBUG: Python executable used: /usr/bin/python
MA5-DEBUG: sys.executable: /usr/bin/python
MA5-DEBUG: which: /usr/bin/python
MA5-DEBUG: which-all:
MA5-DEBUG: - /usr/bin/python
MA5-DEBUG: Python internal paths:
MA5-DEBUG: - /home/pattara/
MA5-DEBUG: - /home/pattara/
MA5-DEBUG: - /home/pattara/
MA5-DEBUG: - /home/pattara/
MA5-DEBUG: - /usr/lib/python2.7
MA5-DEBUG: - /usr/lib/
MA5-DEBUG: - /usr/lib/
MA5-DEBUG: - /usr/lib/
MA5-DEBUG: - /usr/lib/
MA5-DEBUG: - /home/pattara/
MA5-DEBUG: - /usr/local/
MA5-DEBUG: - /usr/lib/
MA5-DEBUG: $PYTHONPATH:
MA5-DEBUG: - /home/pattara/
MA5-DEBUG:
MA5-DEBUG: Saving informations ...
MA5: - Python [OK]
MA5-DEBUG: -------
MA5-DEBUG: Detect package gpp
MA5-DEBUG: Try to detect automatically the package ...
MA5-DEBUG: which: /usr/bin/g++
MA5-DEBUG: Extract more informations related to the package ...
MA5-DEBUG: which-all:
MA5-DEBUG: - /usr/bin/g++
MA5-DEBUG: version: 7
MA5-DEBUG: search path for headers:
MA5-DEBUG: - /usr/include/c++/7
MA5-DEBUG: - /usr/include/
MA5-DEBUG: - /usr/include/
MA5-DEBUG: - /usr/lib/
MA5-DEBUG: - /usr/local/include
MA5-DEBUG: - /usr/lib/
MA5-DEBUG: - /usr/include/
MA5-DEBUG: - /usr/include
MA5-DEBUG: search path for libraries:
MA5-DEBUG: - /usr/lib/
MA5-DEBUG: - /usr/lib/
MA5-DEBUG: - /usr/lib
MA5-DEBUG: - /lib/x86_
MA5-DEBUG: - /lib
MA5-DEBUG: - /usr/lib/
MA5-DEBUG: - /usr/lib
MA5-DEBUG: - /usr/lib
MA5-DEBUG: - /lib
MA5-DEBUG: - /usr/lib
MA5-DEBUG: Saving informations ...
MA5: - GNU GCC g++ [OK]
MA5-DEBUG: -------
MA5-DEBUG: Detect package make
MA5-DEBUG: Try to detect automatically the package ...
MA5-DEBUG: which: /usr/bin/make
MA5-DEBUG: Extract more informations related to the package ...
MA5-DEBUG: which-all:
MA5-DEBUG: - /usr/bin/make
MA5-DEBUG: version: GNU Make 4.1
MA5-DEBUG: Saving informations ...
MA5: - GNU Make [OK]
MA5: Checking optional packages devoted to data processing:
MA5-DEBUG: -------
MA5-DEBUG: Detect package zlib
MA5-DEBUG: Is there a veto? ...
MA5-DEBUG: no user veto
MA5-DEBUG: Detection of the package in the location specified by the user ...
MA5-DEBUG: Detection of the package in the "tools" folder ...
MA5-DEBUG: Look for zlib folder in path /home/pattara/
MA5-DEBUG: -> not found
MA5-DEBUG: Try to detect automatically the package ...
MA5-DEBUG: Search for header & libraries possible paths...
MA5-DEBUG: ->header paths=['.', '/usr/include', '/usr/local/
MA5-DEBUG: ->library paths=[
MA5-DEBUG: Look for the header file zlib.h ...
MA5-DEBUG: look for pattern zlib.h ...
MA5-DEBUG: -> no file found
MA5-DEBUG: look for pattern /usr/include/zlib.h ...
MA5-DEBUG: -> found: /usr/include/zlib.h
MA5-DEBUG: Look for the zlib libraries ...
MA5-DEBUG: look for pattern /home/pattara/
MA5-DEBUG: look for pattern /home/pattara/
MA5-DEBUG: look for pattern /home/pattara/
MA5-DEBUG: -> no file found
MA5-DEBUG: look for pattern libz.so ...
MA5-DEBUG: look for pattern libz.a ...
MA5-DEBUG: look for pattern libz.so.* ...
MA5-DEBUG: -> no file found
MA5-DEBUG: look for pattern /usr/lib/libz.so ...
MA5-DEBUG: look for pattern /usr/lib/libz.a ...
MA5-DEBUG: look for pattern /usr/lib/libz.so.* ...
MA5-DEBUG: -> no file found
MA5-DEBUG: look for pattern /usr/local/
MA5-DEBUG: look for pattern /usr/local/
MA5-DEBUG: look for pattern /usr/local/
MA5-DEBUG: -> no file found
MA5: - Zlib [DISABLED]
MA5-DEBUG: -------
MA5-DEBUG: Detect package fastjet
MA5-DEBUG: Is there a veto? ...
MA5-DEBUG: no user veto
MA5-DEBUG: Detection of the package in the location specified by the user ...
MA5-DEBUG: Detection of the package in the "tools" folder ...
MA5-DEBUG: Look for FastJet in the folder here:/home/
MA5-DEBUG: -> not found
MA5-DEBUG: Try to detect automatically the package ...
MA5: - FastJet [DISABLED]
MA5-DEBUG: -------
MA5-DEBUG: Detect package root
MA5-DEBUG: Is there a veto? ...
MA5-DEBUG: no user veto
MA5-DEBUG: Detection of the package in the location specified by the user ...
MA5-DEBUG: Detection of the package in the "tools" folder ...
MA5-DEBUG: Detecting root-config in the tools folder ...
MA5-DEBUG: Try to detect automatically the package ...
MA5-DEBUG: which: /home/pattara/
MA5-DEBUG: which-all:
MA5-DEBUG: - /home/pattara/
MA5-DEBUG: Extract more informations related to the package ...
MA5-DEBUG: Trying to get library and header paths ...
MA5-DEBUG: -> root-config found
MA5-DEBUG: -> root version: 6.16.00
MA5-DEBUG: -> root header folder: /home/pattara/
MA5-DEBUG: -> root library folder: /home/pattara/
MA5-DEBUG: Try to find /home/pattara/
MA5-DEBUG: Try to find /home/pattara/
MA5-DEBUG: features: ['asimage', 'astiff', 'builtin_
MA5-DEBUG: C++ compiler: c++
MA5-DEBUG: Saving informations ...
MA5: - Root [OK]
MA5-DEBUG: Delphes
MA5-DEBUG: Look for Delphes in the folder /home/pattara/
MA5-DEBUG: -> deactivated
MA5: - Delphes [DEACTIVATED]
MA5-DEBUG: Delphes-MA5tune
MA5-DEBUG: Look for DelphesMA5tune in the folder /home/pattara/
MA5-DEBUG: -> found
MA5-DEBUG: Look for the file /home/pattara/
MA5-DEBUG: -> found
MA5-DEBUG: Look for the libraries in folder ['/home/
MA5-DEBUG: -> result for lib paths: ['/home/
MA5-DEBUG: -> result for lib files: /home/pattara/
MA5: - Delphes-MA5tune [OK]
MA5-DEBUG: Creating symbolic link from /home/pattara/
MA5-DEBUG: to /home/pattara/
MA5-DEBUG: Creating symbolic link from /home/pattara/
MA5-DEBUG: to /home/pattara/
MA5-DEBUG: Creating symbolic link from /home/pattara/
MA5-DEBUG: to /home/pattara/
MA5-DEBUG: Creating symbolic link from /home/pattara/
MA5-DEBUG: to /home/pattara/
MA5-DEBUG: Creating symbolic link from /home/pattara/
MA5-DEBUG: to /home/pattara/
MA5-DEBUG: Creating symbolic link from /home/pattara/
MA5-DEBUG: to /home/pattara/
MA5-DEBUG: -------- BEGIN: set environment variables --------
MA5-DEBUG: before PATH=/home/
MA5-DEBUG: --------
MA5-DEBUG: after PATH=/home/
MA5-DEBUG: --------
MA5-DEBUG: before LD_LIBRARY_
MA5-DEBUG: --------
MA5-DEBUG: after LD_LIBRARY_
MA5-DEBUG: --------
MA5-DEBUG: before DYLD_LIBRARY_
MA5-DEBUG: --------
MA5-DEBUG: after DYLD_LIBRARY_
MA5-DEBUG: --------
MA5-DEBUG: -------- END: set environment variables --------
MA5: Checking the MadAnalysis 5 core library:
MA5-DEBUG: -> looking for folder: /tools/
MA5-DEBUG: -> looking for file: /home/pattara/
MA5-DEBUG: -> looking for file: /home/pattara/
MA5-DEBUG: -> looking for file: /home/pattara/
MA5-DEBUG: -> loading the architecture file.
MA5-DEBUG: Compare 2 ArchitureInfo objects:
MA5-DEBUG: The current one (number of items=50):
MA5-DEBUG: {'root_bin_path': '/home/
MA5-DEBUG: The other one (number of items=50):
MA5-DEBUG: {'root_bin_path': '/home/
MA5-DEBUG: The comparison of categorie names -> OK
MA5-DEBUG: The comparison of categorie values:
MA5-DEBUG: -> OK
MA5: => MadAnalysis libraries found.
MA5-DEBUG: Command: ./TestSampleAna
MA5-DEBUG: LogFile: /home/pattara/
MA5-DEBUG: LogFile: /home/pattara/
MA5-DEBUG: Analyzing output file: OK -> Begin Stamp found
MA5-DEBUG: Analyzing output file: OK -> End Stamp
MA5: => MadAnalysis test program works.
MA5: Checking optional packages devoted to reinterpretation:
MA5-DEBUG: -------
MA5-DEBUG: Detect package scipy
MA5-DEBUG: Is there a veto? ...
MA5-DEBUG: no user veto
MA5-DEBUG: Try to detect automatically the package ...
MA5-DEBUG: release = 1.2.0
MA5-DEBUG: where? = /home/pattara/
MA5-DEBUG: Saving informations ...
MA5: - SciPy [OK]
MA5-DEBUG: -------
MA5-DEBUG: Detect package pad
MA5-DEBUG: Is there a veto? ...
MA5-DEBUG: no user veto
MA5-DEBUG: Are dependencies installed on the machine? ...
MA5-DEBUG: Detection of the package in the location specified by the user ...
MA5-DEBUG: Detection of the package in the "tools" folder ...
MA5-DEBUG: Look for PAD in the folder here:/home/
MA5-DEBUG: -> found
MA5-DEBUG: Extract more informations related to the package ...
MA5-DEBUG: MA5 stamp found!
MA5-DEBUG: number of recast analyses: 25
MA5-DEBUG: Saving informations ...
MA5: - PAD [OK]
MA5-DEBUG: -------
MA5-DEBUG: Detect package padma5
MA5-DEBUG: Is there a veto? ...
MA5-DEBUG: no user veto
MA5-DEBUG: Are dependencies installed on the machine? ...
MA5-DEBUG: Detection of the package in the location specified by the user ...
MA5-DEBUG: Detection of the package in the "tools" folder ...
MA5-DEBUG: Look for PADForMA5tune in the folder here:/home/
MA5-DEBUG: -> not found
MA5: - PADForMA5tune [DISABLED]
MA5: Checking optional packages devoted to histogramming:
MA5-DEBUG: -------
MA5-DEBUG: Detect package root_graphical
MA5-DEBUG: Is there a veto? ...
MA5-DEBUG: no user veto
MA5-DEBUG: Are dependencies installed on the machine? ...
MA5-DEBUG: Try to detect automatically the package ...
MA5-DEBUG: Saving informations ...
MA5: - Root [OK]
MA5-DEBUG: -------
MA5-DEBUG: Detect package matplotlib
MA5-DEBUG: Is there a veto? ...
MA5-DEBUG: no user veto
MA5-DEBUG: Try to detect automatically the package ...
** DEBUG: $HOME=/home/pattara
** DEBUG: matplotlib data path /home/pattara/
** DEBUG: loaded rc file /home/pattara/
** DEBUG: matplotlib version 2.2.3
** DEBUG: interactive is False
** DEBUG: platform is linux2
** DEBUG: loaded modules: ['madanalysis.
MA5-DEBUG: release = 2.2.3
MA5-DEBUG: where? = /home/pattara/
MA5-DEBUG: Saving informations ...
MA5: - Matplotlib [OK]
MA5-DEBUG: -------
MA5-DEBUG: Detect package pdflatex
MA5-DEBUG: Is there a veto? ...
MA5-DEBUG: no user veto
MA5-DEBUG: Try to detect automatically the package ...
MA5-DEBUG: which: /usr/bin/pdflatex
MA5-DEBUG: Extract more informations related to the package ...
MA5-DEBUG: which-all:
MA5-DEBUG: - /usr/bin/pdflatex
MA5-DEBUG: Saving informations ...
MA5: - pdflatex [OK]
MA5-DEBUG: -------
MA5-DEBUG: Detect package latex
MA5-DEBUG: Is there a veto? ...
MA5-DEBUG: no user veto
MA5-DEBUG: Try to detect automatically the package ...
MA5-DEBUG: which: /usr/bin/latex
MA5-DEBUG: Extract more informations related to the package ...
MA5-DEBUG: which-all:
MA5-DEBUG: - /usr/bin/latex
MA5-DEBUG: Saving informations ...
MA5: - latex [OK]
MA5-DEBUG: Function AutoSetGraphica
MA5-DEBUG: - ROOT is there: True
MA5-DEBUG: - Matplotlib is there: True
MA5: Package used for graphical rendering: Root
MA5: *******
MA5: Particle labels exported from madanalysis/
MA5-DEBUG: Extracting a particle labelled by [met] with a PDG-id : 100
MA5-DEBUG: Extracting a particle labelled by [mht] with a PDG-id : 99
MA5-DEBUG: Extracting a particle labelled by [d] with a PDG-id : 1
MA5-DEBUG: Extracting a particle labelled by [d~] with a PDG-id : -1
MA5-DEBUG: Extracting a particle labelled by [u] with a PDG-id : 2
MA5-DEBUG: Extracting a particle labelled by [u~] with a PDG-id : -2
MA5-DEBUG: Extracting a particle labelled by [s] with a PDG-id : 3
MA5-DEBUG: Extracting a particle labelled by [s~] with a PDG-id : -3
MA5-DEBUG: Extracting a particle labelled by [c] with a PDG-id : 4
MA5-DEBUG: Extracting a particle labelled by [c~] with a PDG-id : -4
MA5-DEBUG: Extracting a particle labelled by [b] with a PDG-id : 5
MA5-DEBUG: Extracting a particle labelled by [b~] with a PDG-id : -5
MA5-DEBUG: Extracting a particle labelled by [t] with a PDG-id : 6
MA5-DEBUG: Extracting a particle labelled by [t~] with a PDG-id : -6
MA5-DEBUG: Extracting a particle labelled by [e-] with a PDG-id : 11
MA5-DEBUG: Extracting a particle labelled by [e+] with a PDG-id : -11
MA5-DEBUG: Extracting a particle labelled by [ve] with a PDG-id : 12
MA5-DEBUG: Extracting a particle labelled by [ve~] with a PDG-id : -12
MA5-DEBUG: Extracting a particle labelled by [mu-] with a PDG-id : 13
MA5-DEBUG: Extracting a particle labelled by [mu+] with a PDG-id : -13
MA5-DEBUG: Extracting a particle labelled by [vm] with a PDG-id : 14
MA5-DEBUG: Extracting a particle labelled by [vm~] with a PDG-id : -14
MA5-DEBUG: Extracting a particle labelled by [ta-] with a PDG-id : 15
MA5-DEBUG: Extracting a particle labelled by [ta+] with a PDG-id : -15
MA5-DEBUG: Extracting a particle labelled by [vt] with a PDG-id : 16
MA5-DEBUG: Extracting a particle labelled by [vt~] with a PDG-id : -16
MA5-DEBUG: Extracting a particle labelled by [g] with a PDG-id : 21
MA5-DEBUG: Extracting a particle labelled by [a] with a PDG-id : 22
MA5-DEBUG: Extracting a particle labelled by [z] with a PDG-id : 23
MA5-DEBUG: Extracting a particle labelled by [w+] with a PDG-id : 24
MA5-DEBUG: Extracting a particle labelled by [w-] with a PDG-id : -24
MA5-DEBUG: Extracting a particle labelled by [h1] with a PDG-id : 25
MA5-DEBUG: Extracting a particle labelled by [h2] with a PDG-id : 35
MA5-DEBUG: Extracting a particle labelled by [h3] with a PDG-id : 36
MA5-DEBUG: Extracting a particle labelled by [h+] with a PDG-id : 37
MA5-DEBUG: Extracting a particle labelled by [h-] with a PDG-id : -37
MA5-DEBUG: Extracting a particle labelled by [dl] with a PDG-id : 1000001
MA5-DEBUG: Extracting a particle labelled by [dl~] with a PDG-id : -1000001
MA5-DEBUG: Extracting a particle labelled by [dr] with a PDG-id : 2000001
MA5-DEBUG: Extracting a particle labelled by [dr~] with a PDG-id : -2000001
MA5-DEBUG: Extracting a particle labelled by [ul] with a PDG-id : 1000002
MA5-DEBUG: Extracting a particle labelled by [ul~] with a PDG-id : -1000002
MA5-DEBUG: Extracting a particle labelled by [ur] with a PDG-id : 2000002
MA5-DEBUG: Extracting a particle labelled by [ur~] with a PDG-id : -2000002
MA5-DEBUG: Extracting a particle labelled by [sl] with a PDG-id : 1000003
MA5-DEBUG: Extracting a particle labelled by [sl~] with a PDG-id : -1000003
MA5-DEBUG: Extracting a particle labelled by [sr] with a PDG-id : 2000003
MA5-DEBUG: Extracting a particle labelled by [sr~] with a PDG-id : -2000003
MA5-DEBUG: Extracting a particle labelled by [cl] with a PDG-id : 1000004
MA5-DEBUG: Extracting a particle labelled by [cl~] with a PDG-id : -1000004
MA5-DEBUG: Extracting a particle labelled by [cr] with a PDG-id : 2000004
MA5-DEBUG: Extracting a particle labelled by [cr~] with a PDG-id : -2000004
MA5-DEBUG: Extracting a particle labelled by [b1] with a PDG-id : 1000005
MA5-DEBUG: Extracting a particle labelled by [b1~] with a PDG-id : -1000005
MA5-DEBUG: Extracting a particle labelled by [b2] with a PDG-id : 2000005
MA5-DEBUG: Extracting a particle labelled by [b2~] with a PDG-id : -2000005
MA5-DEBUG: Extracting a particle labelled by [t1] with a PDG-id : 1000006
MA5-DEBUG: Extracting a particle labelled by [t1~] with a PDG-id : -1000006
MA5-DEBUG: Extracting a particle labelled by [t2] with a PDG-id : 2000006
MA5-DEBUG: Extracting a particle labelled by [t2~] with a PDG-id : -2000006
MA5-DEBUG: Extracting a particle labelled by [el-] with a PDG-id : 1000011
MA5-DEBUG: Extracting a particle labelled by [el+] with a PDG-id : -1000011
MA5-DEBUG: Extracting a particle labelled by [er-] with a PDG-id : 2000011
MA5-DEBUG: Extracting a particle labelled by [er+] with a PDG-id : -2000011
MA5-DEBUG: Extracting a particle labelled by [sve] with a PDG-id : 1000012
MA5-DEBUG: Extracting a particle labelled by [sve~] with a PDG-id : -1000012
MA5-DEBUG: Extracting a particle labelled by [mul-] with a PDG-id : 1000013
MA5-DEBUG: Extracting a particle labelled by [mul+] with a PDG-id : -1000013
MA5-DEBUG: Extracting a particle labelled by [mur-] with a PDG-id : 2000013
MA5-DEBUG: Extracting a particle labelled by [mur+] with a PDG-id : -2000013
MA5-DEBUG: Extracting a particle labelled by [svm] with a PDG-id : 1000014
MA5-DEBUG: Extracting a particle labelled by [svm~] with a PDG-id : -1000014
MA5-DEBUG: Extracting a particle labelled by [ta1-] with a PDG-id : 1000015
MA5-DEBUG: Extracting a particle labelled by [ta1+] with a PDG-id : -1000015
MA5-DEBUG: Extracting a particle labelled by [ta2-] with a PDG-id : 2000015
MA5-DEBUG: Extracting a particle labelled by [ta2+] with a PDG-id : -2000015
MA5-DEBUG: Extracting a particle labelled by [svt] with a PDG-id : 1000016
MA5-DEBUG: Extracting a particle labelled by [svt~] with a PDG-id : -1000016
MA5-DEBUG: Extracting a particle labelled by [go] with a PDG-id : 1000021
MA5-DEBUG: Extracting a particle labelled by [n1] with a PDG-id : 1000022
MA5-DEBUG: Extracting a particle labelled by [n2] with a PDG-id : 1000023
MA5-DEBUG: Extracting a particle labelled by [n3] with a PDG-id : 1000025
MA5-DEBUG: Extracting a particle labelled by [n4] with a PDG-id : 1000035
MA5-DEBUG: Extracting a particle labelled by [x1+] with a PDG-id : 1000024
MA5-DEBUG: Extracting a particle labelled by [x1-] with a PDG-id : -1000024
MA5-DEBUG: Extracting a particle labelled by [x2+] with a PDG-id : 1000037
MA5-DEBUG: Extracting a particle labelled by [x2-] with a PDG-id : -1000037
MA5: => 87 particles successfully exported.
MA5: Multiparticle labels exported from madanalysis/
MA5-DEBUG: Extracting a multiparticle labelled by [p] with a PDG-id : ['g', 'u', 'c', 'd', 's', 'u~', 'c~', 'd~', 's~']
MA5-DEBUG: Extracting a multiparticle labelled by [j] with a PDG-id : ['g', 'u', 'c', 'd', 's', 'u~', 'c~', 'd~', 's~']
MA5-DEBUG: Extracting a multiparticle labelled by [l+] with a PDG-id : ['e+', 'mu+']
MA5-DEBUG: Extracting a multiparticle labelled by [l-] with a PDG-id : ['e-', 'mu-']
MA5-DEBUG: Extracting a multiparticle labelled by [vl] with a PDG-id : ['ve', 'vm', 'vt']
MA5-DEBUG: Extracting a multiparticle labelled by [vl~] with a PDG-id : ['ve~', 'vm~', 'vt~']
MA5: => Creation of the label 'invisible' (-> missing energy).
MA5: => Creation of the label 'hadronic' (-> jet energy).
MA5: => 8 multiparticles successfully exported.
ma5>
|
Revision history for this message
|
#5 |
Hi Pattara,
Can you check that the directory
/home/
exist. If yes, the compilation of the PADForMA5tune has probably failed for a reason to be determined. Do you mind checking the various log files?
Cheers,
Benjamin
> On 5 Mar 2019, at 12:56 , pattara angkinun <email address hidden> wrote:
>
> Question #678555 on MadAnalysis 5 changed:
> https:/
>
> pattara angkinun posted a new comment:
> Dear Benjamin,
>
> pattara@
> pattara@
> MA5:
> MA5: *******
> MA5: * *
> MA5: * W E L C O M E to M A D A N A L Y S I S 5 *
> MA5: * ______ ______ *
> MA5: * /'\_/`\/\ __ \/\ ___\ *
> MA5: * /\ \ \ \_\ \ \ \__/ *
> MA5: * \ \ \__\ \ \ __ \ \___``\ *
> MA5: * \ \ \_/\ \ \ \/\ \/\ \_\ \ *
> MA5: * \ \_\\ \_\ \_\ \_\ \____/ *
> MA5: * \/_/ \/_/\/_/\/_/\/___/ *
> MA5: * *
> MA5: * MA5 release : 1.7.21 2019/02/07 *
> MA5: * *
> MA5: * Comput. Phys. Commun. 184 (2013) 222-256 *
> MA5: * Eur. Phys. J. C74 (2014) 3103 *
> MA5: * *
> MA5: * The MadAnalysis Development Team - Please visit us at *
> MA5: * https:/
> MA5: * *
> MA5: * Type 'help' for in-line help. *
> MA5: * *
> MA5: *******
> MA5-DEBUG:
> MA5-DEBUG: DEBUG MODE ACTIVATED
> MA5-DEBUG:
> MA5: Platform: Linux 4.15.0-45-generic [Linux mode]
> MA5-DEBUG:
> MA5-DEBUG: Machine - Cross platform information
> MA5-DEBUG: Machine type: x86_64
> MA5-DEBUG: Processor name: x86_64
> MA5-DEBUG: Platform: Linux-4.
> MA5-DEBUG: Platform release: 4.15.0-45-generic
> MA5-DEBUG: System: Linux
> MA5-DEBUG: Node: pattara-GL62-6QF
> MA5-DEBUG: Number of cores: 8
> MA5-DEBUG:
> MA5-DEBUG: Machine - OS-specific information
> MA5-DEBUG: Java version: ('', '', ('', '', ''), ('', '', ''))
> MA5-DEBUG: Windows version: ('', '', '', '')
> MA5-DEBUG: Mac Os version: ('', ('', '', ''), '')
> MA5-DEBUG: Unix distribution: Linux-4.
> MA5-DEBUG:
> MA5: Reading user settings ...
> MA5-DEBUG: Opening the file: /home/pattara/
> MA5-DEBUG: Lines to interpret:
> MA5-DEBUG: Closing the file: /home/pattara/
> MA5-DEBUG:
> MA5-DEBUG: User
> MA5-DEBUG: User name: pattara
> MA5-DEBUG: User ID: 1000
> MA5-DEBUG: Expanding folder ~/: /home/pattara/
> MA5-DEBUG: Variable $USER: pattara
> MA5-DEBUG: Variable $USERNAME: pattara
> MA5-DEBUG: Variable $LNAME:
> MA5-DEBUG: Variable $LOGNAME: pattara
> MA5-DEBUG: Variable $HOME: /home/pattara
> MA5-DEBUG: Variable $HOMEDRIVE:
> MA5-DEBUG: Variable $posix:
> MA5-DEBUG: Variable $HOMEPATH:
> MA5-DEBUG:
> MA5-DEBUG: Web access
> MA5-DEBUG: enable
> MA5-DEBUG:
> MA5-DEBUG: Temporary folder
> MA5-DEBUG: Variable $TMPDIR:
> MA5-DEBUG: Variable $TMP:
> MA5-DEBUG: Variable $TEMP:
> MA5-DEBUG: Check if the folder /tmp/pattara exists ...
> MA5-DEBUG: -> found
> MA5-DEBUG: temporary folder will be used for MA5: /tmp/pattara
> MA5-DEBUG:
> MA5-DEBUG: Download dir
> MA5-DEBUG: Check if the folder /tmp/pattara/
> MA5-DEBUG: -> found
> MA5-DEBUG: download folder will be used for MA5: /tmp/pattara/
> MA5-DEBUG:
> MA5-DEBUG: Text editor
> MA5-DEBUG: Look for the global variable $EDITOR ...
> MA5-DEBUG: -> variable not found. VI editor is set by default.
> MA5-DEBUG:
> MA5: Checking mandatory packages:
> MA5-DEBUG: -------
> MA5-DEBUG: Detect package python
> MA5-DEBUG: Try to detect automatically the package ...
> MA5-DEBUG: Extract more informations related to the package ...
> MA5-DEBUG:
> MA5-DEBUG: Python release: 2.7.15rc1
> MA5-DEBUG: Python build: ('default', 'Nov 12 2018 14:31:15')
> MA5-DEBUG: Python compiler: GCC 7.3.0
> MA5-DEBUG: Python prefix: /usr
> MA5-DEBUG: Python executable used: /usr/bin/python
> MA5-DEBUG: sys.executable: /usr/bin/python
> MA5-DEBUG: which: /usr/bin/python
> MA5-DEBUG: which-all:
> MA5-DEBUG: - /usr/bin/python
> MA5-DEBUG: Python internal paths:
> MA5-DEBUG: - /home/pattara/
> MA5-DEBUG: - /home/pattara/
> MA5-DEBUG: - /home/pattara/
> MA5-DEBUG: - /home/pattara/
> MA5-DEBUG: - /usr/lib/python2.7
> MA5-DEBUG: - /usr/lib/
> MA5-DEBUG: - /usr/lib/
> MA5-DEBUG: - /usr/lib/
> MA5-DEBUG: - /usr/lib/
> MA5-DEBUG: - /home/pattara/
> MA5-DEBUG: - /usr/local/
> MA5-DEBUG: - /usr/lib/
> MA5-DEBUG: $PYTHONPATH:
> MA5-DEBUG: - /home/pattara/
> MA5-DEBUG:
> MA5-DEBUG: Saving informations ...
> MA5: - Python [OK]
> MA5-DEBUG: -------
> MA5-DEBUG: Detect package gpp
> MA5-DEBUG: Try to detect automatically the package ...
> MA5-DEBUG: which: /usr/bin/g++
> MA5-DEBUG: Extract more informations related to the package ...
> MA5-DEBUG: which-all:
> MA5-DEBUG: - /usr/bin/g++
> MA5-DEBUG: version: 7
> MA5-DEBUG: search path for headers:
> MA5-DEBUG: - /usr/include/c++/7
> MA5-DEBUG: - /usr/include/
> MA5-DEBUG: - /usr/include/
> MA5-DEBUG: - /usr/lib/
> MA5-DEBUG: - /usr/local/include
> MA5-DEBUG: - /usr/lib/
> MA5-DEBUG: - /usr/include/
> MA5-DEBUG: - /usr/include
> MA5-DEBUG: search path for libraries:
> MA5-DEBUG: - /usr/lib/
> MA5-DEBUG: - /usr/lib/
> MA5-DEBUG: - /usr/lib
> MA5-DEBUG: - /lib/x86_
> MA5-DEBUG: - /lib
> MA5-DEBUG: - /usr/lib/
> MA5-DEBUG: - /usr/lib
> MA5-DEBUG: - /usr/lib
> MA5-DEBUG: - /lib
> MA5-DEBUG: - /usr/lib
> MA5-DEBUG: Saving informations ...
> MA5: - GNU GCC g++ [OK]
> MA5-DEBUG: -------
> MA5-DEBUG: Detect package make
> MA5-DEBUG: Try to detect automatically the package ...
> MA5-DEBUG: which: /usr/bin/make
> MA5-DEBUG: Extract more informations related to the package ...
> MA5-DEBUG: which-all:
> MA5-DEBUG: - /usr/bin/make
> MA5-DEBUG: version: GNU Make 4.1
> MA5-DEBUG: Saving informations ...
> MA5: - GNU Make [OK]
> MA5: Checking optional packages devoted to data processing:
> MA5-DEBUG: -------
> MA5-DEBUG: Detect package zlib
> MA5-DEBUG: Is there a veto? ...
> MA5-DEBUG: no user veto
> MA5-DEBUG: Detection of the package in the location specified by the user ...
> MA5-DEBUG: Detection of the package in the "tools" folder ...
> MA5-DEBUG: Look for zlib folder in path /home/pattara/
> MA5-DEBUG: -> not found
> MA5-DEBUG: Try to detect automatically the package ...
> MA5-DEBUG: Search for header & libraries possible paths...
> MA5-DEBUG: ->header paths=['.', '/usr/include', '/usr/local/
> MA5-DEBUG: ->library paths=[
> MA5-DEBUG: Look for the header file zlib.h ...
> MA5-DEBUG: look for pattern zlib.h ...
> MA5-DEBUG: -> no file found
> MA5-DEBUG: look for pattern /usr/include/zlib.h ...
> MA5-DEBUG: -> found: /usr/include/zlib.h
> MA5-DEBUG: Look for the zlib libraries ...
> MA5-DEBUG: look for pattern /home/pattara/
> MA5-DEBUG: look for pattern /home/pattara/
> MA5-DEBUG: look for pattern /home/pattara/
> MA5-DEBUG: -> no file found
> MA5-DEBUG: look for pattern libz.so ...
> MA5-DEBUG: look for pattern libz.a ...
> MA5-DEBUG: look for pattern libz.so.* ...
> MA5-DEBUG: -> no file found
> MA5-DEBUG: look for pattern /usr/lib/libz.so ...
> MA5-DEBUG: look for pattern /usr/lib/libz.a ...
> MA5-DEBUG: look for pattern /usr/lib/libz.so.* ...
> MA5-DEBUG: -> no file found
> MA5-DEBUG: look for pattern /usr/local/
> MA5-DEBUG: look for pattern /usr/local/
> MA5-DEBUG: look for pattern /usr/local/
> MA5-DEBUG: -> no file found
> MA5: - Zlib [DISABLED]
> MA5-DEBUG: -------
> MA5-DEBUG: Detect package fastjet
> MA5-DEBUG: Is there a veto? ...
> MA5-DEBUG: no user veto
> MA5-DEBUG: Detection of the package in the location specified by the user ...
> MA5-DEBUG: Detection of the package in the "tools" folder ...
> MA5-DEBUG: Look for FastJet in the folder here:/home/
> MA5-DEBUG: -> not found
> MA5-DEBUG: Try to detect automatically the package ...
> MA5: - FastJet [DISABLED]
> MA5-DEBUG: -------
> MA5-DEBUG: Detect package root
> MA5-DEBUG: Is there a veto? ...
> MA5-DEBUG: no user veto
> MA5-DEBUG: Detection of the package in the location specified by the user ...
> MA5-DEBUG: Detection of the package in the "tools" folder ...
> MA5-DEBUG: Detecting root-config in the tools folder ...
> MA5-DEBUG: Try to detect automatically the package ...
> MA5-DEBUG: which: /home/pattara/
> MA5-DEBUG: which-all:
> MA5-DEBUG: - /home/pattara/
> MA5-DEBUG: Extract more informations related to the package ...
> MA5-DEBUG: Trying to get library and header paths ...
> MA5-DEBUG: -> root-config found
> MA5-DEBUG: -> root version: 6.16.00
> MA5-DEBUG: -> root header folder: /home/pattara/
> MA5-DEBUG: -> root library folder: /home/pattara/
> MA5-DEBUG: Try to find /home/pattara/
> MA5-DEBUG: Try to find /home/pattara/
> MA5-DEBUG: features: ['asimage', 'astiff', 'builtin_
> MA5-DEBUG: C++ compiler: c++
> MA5-DEBUG: Saving informations ...
> MA5: - Root [OK]
> MA5-DEBUG: Delphes
> MA5-DEBUG: Look for Delphes in the folder /home/pattara/
> MA5-DEBUG: -> deactivated
> MA5: - Delphes [DEACTIVATED]
> MA5-DEBUG: Delphes-MA5tune
> MA5-DEBUG: Look for DelphesMA5tune in the folder /home/pattara/
> MA5-DEBUG: -> found
> MA5-DEBUG: Look for the file /home/pattara/
> MA5-DEBUG: -> found
> MA5-DEBUG: Look for the libraries in folder ['/home/
> MA5-DEBUG: -> result for lib paths: ['/home/
> MA5-DEBUG: -> result for lib files: /home/pattara/
> MA5: - Delphes-MA5tune [OK]
> MA5-DEBUG: Creating symbolic link from /home/pattara/
> MA5-DEBUG: to /home/pattara/
> MA5-DEBUG: Creating symbolic link from /home/pattara/
> MA5-DEBUG: to /home/pattara/
> MA5-DEBUG: Creating symbolic link from /home/pattara/
> MA5-DEBUG: to /home/pattara/
> MA5-DEBUG: Creating symbolic link from /home/pattara/
> MA5-DEBUG: to /home/pattara/
> MA5-DEBUG: Creating symbolic link from /home/pattara/
> MA5-DEBUG: to /home/pattara/
> MA5-DEBUG: Creating symbolic link from /home/pattara/
> MA5-DEBUG: to /home/pattara/
> MA5-DEBUG: -------- BEGIN: set environment variables --------
> MA5-DEBUG: before PATH=/home/
> MA5-DEBUG: --------
> MA5-DEBUG: after PATH=/home/
> MA5-DEBUG: --------
> MA5-DEBUG: before LD_LIBRARY_
> MA5-DEBUG: --------
> MA5-DEBUG: after LD_LIBRARY_
> MA5-DEBUG: --------
> MA5-DEBUG: before DYLD_LIBRARY_
> MA5-DEBUG: --------
> MA5-DEBUG: after DYLD_LIBRARY_
> MA5-DEBUG: --------
> MA5-DEBUG: -------- END: set environment variables --------
> MA5: Checking the MadAnalysis 5 core library:
> MA5-DEBUG: -> looking for folder: /tools/
> MA5-DEBUG: -> looking for file: /home/pattara/
> MA5-DEBUG: -> looking for file: /home/pattara/
> MA5-DEBUG: -> looking for file: /home/pattara/
> MA5-DEBUG: -> loading the architecture file.
> MA5-DEBUG: Compare 2 ArchitureInfo objects:
> MA5-DEBUG: The current one (number of items=50):
> MA5-DEBUG: {'root_bin_path': '/home/
> MA5-DEBUG: The other one (number of items=50):
> MA5-DEBUG: {'root_bin_path': '/home/
> MA5-DEBUG: The comparison of categorie names -> OK
> MA5-DEBUG: The comparison of categorie values:
> MA5-DEBUG: -> OK
> MA5: => MadAnalysis libraries found.
> MA5-DEBUG: Command: ./TestSampleAna
> MA5-DEBUG: LogFile: /home/pattara/
> MA5-DEBUG: LogFile: /home/pattara/
> MA5-DEBUG: Analyzing output file: OK -> Begin Stamp found
> MA5-DEBUG: Analyzing output file: OK -> End Stamp
> MA5: => MadAnalysis test program works.
> MA5: Checking optional packages devoted to reinterpretation:
> MA5-DEBUG: -------
> MA5-DEBUG: Detect package scipy
> MA5-DEBUG: Is there a veto? ...
> MA5-DEBUG: no user veto
> MA5-DEBUG: Try to detect automatically the package ...
> MA5-DEBUG: release = 1.2.0
> MA5-DEBUG: where? = /home/pattara/
> MA5-DEBUG: Saving informations ...
> MA5: - SciPy [OK]
> MA5-DEBUG: -------
> MA5-DEBUG: Detect package pad
> MA5-DEBUG: Is there a veto? ...
> MA5-DEBUG: no user veto
> MA5-DEBUG: Are dependencies installed on the machine? ...
> MA5-DEBUG: Detection of the package in the location specified by the user ...
> MA5-DEBUG: Detection of the package in the "tools" folder ...
> MA5-DEBUG: Look for PAD in the folder here:/home/
> MA5-DEBUG: -> found
> MA5-DEBUG: Extract more informations related to the package ...
> MA5-DEBUG: MA5 stamp found!
> MA5-DEBUG: number of recast analyses: 25
> MA5-DEBUG: Saving informations ...
> MA5: - PAD [OK]
> MA5-DEBUG: -------
> MA5-DEBUG: Detect package padma5
> MA5-DEBUG: Is there a veto? ...
> MA5-DEBUG: no user veto
> MA5-DEBUG: Are dependencies installed on the machine? ...
> MA5-DEBUG: Detection of the package in the location specified by the user ...
> MA5-DEBUG: Detection of the package in the "tools" folder ...
> MA5-DEBUG: Look for PADForMA5tune in the folder here:/home/
> MA5-DEBUG: -> not found
> MA5: - PADForMA5tune [DISABLED]
> MA5: Checking optional packages devoted to histogramming:
> MA5-DEBUG: -------
> MA5-DEBUG: Detect package root_graphical
> MA5-DEBUG: Is there a veto? ...
> MA5-DEBUG: no user veto
> MA5-DEBUG: Are dependencies installed on the machine? ...
> MA5-DEBUG: Try to detect automatically the package ...
> MA5-DEBUG: Saving informations ...
> MA5: - Root [OK]
> MA5-DEBUG: -------
> MA5-DEBUG: Detect package matplotlib
> MA5-DEBUG: Is there a veto? ...
> MA5-DEBUG: no user veto
> MA5-DEBUG: Try to detect automatically the package ...
> ** DEBUG: $HOME=/home/pattara
> ** DEBUG: matplotlib data path /home/pattara/
> ** DEBUG: loaded rc file /home/pattara/
> ** DEBUG: matplotlib version 2.2.3
> ** DEBUG: interactive is False
> ** DEBUG: platform is linux2
> ** DEBUG: loaded modules: ['madanalysis.
> MA5-DEBUG: release = 2.2.3
> MA5-DEBUG: where? = /home/pattara/
> MA5-DEBUG: Saving informations ...
> MA5: - Matplotlib [OK]
> MA5-DEBUG: -------
> MA5-DEBUG: Detect package pdflatex
> MA5-DEBUG: Is there a veto? ...
> MA5-DEBUG: no user veto
> MA5-DEBUG: Try to detect automatically the package ...
> MA5-DEBUG: which: /usr/bin/pdflatex
> MA5-DEBUG: Extract more informations related to the package ...
> MA5-DEBUG: which-all:
> MA5-DEBUG: - /usr/bin/pdflatex
> MA5-DEBUG: Saving informations ...
> MA5: - pdflatex [OK]
> MA5-DEBUG: -------
> MA5-DEBUG: Detect package latex
> MA5-DEBUG: Is there a veto? ...
> MA5-DEBUG: no user veto
> MA5-DEBUG: Try to detect automatically the package ...
> MA5-DEBUG: which: /usr/bin/latex
> MA5-DEBUG: Extract more informations related to the package ...
> MA5-DEBUG: which-all:
> MA5-DEBUG: - /usr/bin/latex
> MA5-DEBUG: Saving informations ...
> MA5: - latex [OK]
> MA5-DEBUG: Function AutoSetGraphica
> MA5-DEBUG: - ROOT is there: True
> MA5-DEBUG: - Matplotlib is there: True
> MA5: Package used for graphical rendering: Root
> MA5: *******
> MA5: Particle labels exported from madanalysis/
> MA5-DEBUG: Extracting a particle labelled by [met] with a PDG-id : 100
> MA5-DEBUG: Extracting a particle labelled by [mht] with a PDG-id : 99
> MA5-DEBUG: Extracting a particle labelled by [d] with a PDG-id : 1
> MA5-DEBUG: Extracting a particle labelled by [d~] with a PDG-id : -1
> MA5-DEBUG: Extracting a particle labelled by [u] with a PDG-id : 2
> MA5-DEBUG: Extracting a particle labelled by [u~] with a PDG-id : -2
> MA5-DEBUG: Extracting a particle labelled by [s] with a PDG-id : 3
> MA5-DEBUG: Extracting a particle labelled by [s~] with a PDG-id : -3
> MA5-DEBUG: Extracting a particle labelled by [c] with a PDG-id : 4
> MA5-DEBUG: Extracting a particle labelled by [c~] with a PDG-id : -4
> MA5-DEBUG: Extracting a particle labelled by [b] with a PDG-id : 5
> MA5-DEBUG: Extracting a particle labelled by [b~] with a PDG-id : -5
> MA5-DEBUG: Extracting a particle labelled by [t] with a PDG-id : 6
> MA5-DEBUG: Extracting a particle labelled by [t~] with a PDG-id : -6
> MA5-DEBUG: Extracting a particle labelled by [e-] with a PDG-id : 11
> MA5-DEBUG: Extracting a particle labelled by [e+] with a PDG-id : -11
> MA5-DEBUG: Extracting a particle labelled by [ve] with a PDG-id : 12
> MA5-DEBUG: Extracting a particle labelled by [ve~] with a PDG-id : -12
> MA5-DEBUG: Extracting a particle labelled by [mu-] with a PDG-id : 13
> MA5-DEBUG: Extracting a particle labelled by [mu+] with a PDG-id : -13
> MA5-DEBUG: Extracting a particle labelled by [vm] with a PDG-id : 14
> MA5-DEBUG: Extracting a particle labelled by [vm~] with a PDG-id : -14
> MA5-DEBUG: Extracting a particle labelled by [ta-] with a PDG-id : 15
> MA5-DEBUG: Extracting a particle labelled by [ta+] with a PDG-id : -15
> MA5-DEBUG: Extracting a particle labelled by [vt] with a PDG-id : 16
> MA5-DEBUG: Extracting a particle labelled by [vt~] with a PDG-id : -16
> MA5-DEBUG: Extracting a particle labelled by [g] with a PDG-id : 21
> MA5-DEBUG: Extracting a particle labelled by [a] with a PDG-id : 22
> MA5-DEBUG: Extracting a particle labelled by [z] with a PDG-id : 23
> MA5-DEBUG: Extracting a particle labelled by [w+] with a PDG-id : 24
> MA5-DEBUG: Extracting a particle labelled by [w-] with a PDG-id : -24
> MA5-DEBUG: Extracting a particle labelled by [h1] with a PDG-id : 25
> MA5-DEBUG: Extracting a particle labelled by [h2] with a PDG-id : 35
> MA5-DEBUG: Extracting a particle labelled by [h3] with a PDG-id : 36
> MA5-DEBUG: Extracting a particle labelled by [h+] with a PDG-id : 37
> MA5-DEBUG: Extracting a particle labelled by [h-] with a PDG-id : -37
> MA5-DEBUG: Extracting a particle labelled by [dl] with a PDG-id : 1000001
> MA5-DEBUG: Extracting a particle labelled by [dl~] with a PDG-id : -1000001
> MA5-DEBUG: Extracting a particle labelled by [dr] with a PDG-id : 2000001
> MA5-DEBUG: Extracting a particle labelled by [dr~] with a PDG-id : -2000001
> MA5-DEBUG: Extracting a particle labelled by [ul] with a PDG-id : 1000002
> MA5-DEBUG: Extracting a particle labelled by [ul~] with a PDG-id : -1000002
> MA5-DEBUG: Extracting a particle labelled by [ur] with a PDG-id : 2000002
> MA5-DEBUG: Extracting a particle labelled by [ur~] with a PDG-id : -2000002
> MA5-DEBUG: Extracting a particle labelled by [sl] with a PDG-id : 1000003
> MA5-DEBUG: Extracting a particle labelled by [sl~] with a PDG-id : -1000003
> MA5-DEBUG: Extracting a particle labelled by [sr] with a PDG-id : 2000003
> MA5-DEBUG: Extracting a particle labelled by [sr~] with a PDG-id : -2000003
> MA5-DEBUG: Extracting a particle labelled by [cl] with a PDG-id : 1000004
> MA5-DEBUG: Extracting a particle labelled by [cl~] with a PDG-id : -1000004
> MA5-DEBUG: Extracting a particle labelled by [cr] with a PDG-id : 2000004
> MA5-DEBUG: Extracting a particle labelled by [cr~] with a PDG-id : -2000004
> MA5-DEBUG: Extracting a particle labelled by [b1] with a PDG-id : 1000005
> MA5-DEBUG: Extracting a particle labelled by [b1~] with a PDG-id : -1000005
> MA5-DEBUG: Extracting a particle labelled by [b2] with a PDG-id : 2000005
> MA5-DEBUG: Extracting a particle labelled by [b2~] with a PDG-id : -2000005
> MA5-DEBUG: Extracting a particle labelled by [t1] with a PDG-id : 1000006
> MA5-DEBUG: Extracting a particle labelled by [t1~] with a PDG-id : -1000006
> MA5-DEBUG: Extracting a particle labelled by [t2] with a PDG-id : 2000006
> MA5-DEBUG: Extracting a particle labelled by [t2~] with a PDG-id : -2000006
> MA5-DEBUG: Extracting a particle labelled by [el-] with a PDG-id : 1000011
> MA5-DEBUG: Extracting a particle labelled by [el+] with a PDG-id : -1000011
> MA5-DEBUG: Extracting a particle labelled by [er-] with a PDG-id : 2000011
> MA5-DEBUG: Extracting a particle labelled by [er+] with a PDG-id : -2000011
> MA5-DEBUG: Extracting a particle labelled by [sve] with a PDG-id : 1000012
> MA5-DEBUG: Extracting a particle labelled by [sve~] with a PDG-id : -1000012
> MA5-DEBUG: Extracting a particle labelled by [mul-] with a PDG-id : 1000013
> MA5-DEBUG: Extracting a particle labelled by [mul+] with a PDG-id : -1000013
> MA5-DEBUG: Extracting a particle labelled by [mur-] with a PDG-id : 2000013
> MA5-DEBUG: Extracting a particle labelled by [mur+] with a PDG-id : -2000013
> MA5-DEBUG: Extracting a particle labelled by [svm] with a PDG-id : 1000014
> MA5-DEBUG: Extracting a particle labelled by [svm~] with a PDG-id : -1000014
> MA5-DEBUG: Extracting a particle labelled by [ta1-] with a PDG-id : 1000015
> MA5-DEBUG: Extracting a particle labelled by [ta1+] with a PDG-id : -1000015
> MA5-DEBUG: Extracting a particle labelled by [ta2-] with a PDG-id : 2000015
> MA5-DEBUG: Extracting a particle labelled by [ta2+] with a PDG-id : -2000015
> MA5-DEBUG: Extracting a particle labelled by [svt] with a PDG-id : 1000016
> MA5-DEBUG: Extracting a particle labelled by [svt~] with a PDG-id : -1000016
> MA5-DEBUG: Extracting a particle labelled by [go] with a PDG-id : 1000021
> MA5-DEBUG: Extracting a particle labelled by [n1] with a PDG-id : 1000022
> MA5-DEBUG: Extracting a particle labelled by [n2] with a PDG-id : 1000023
> MA5-DEBUG: Extracting a particle labelled by [n3] with a PDG-id : 1000025
> MA5-DEBUG: Extracting a particle labelled by [n4] with a PDG-id : 1000035
> MA5-DEBUG: Extracting a particle labelled by [x1+] with a PDG-id : 1000024
> MA5-DEBUG: Extracting a particle labelled by [x1-] with a PDG-id : -1000024
> MA5-DEBUG: Extracting a particle labelled by [x2+] with a PDG-id : 1000037
> MA5-DEBUG: Extracting a particle labelled by [x2-] with a PDG-id : -1000037
> MA5: => 87 particles successfully exported.
> MA5: Multiparticle labels exported from madanalysis/
> MA5-DEBUG: Extracting a multiparticle labelled by [p] with a PDG-id : ['g', 'u', 'c', 'd', 's', 'u~', 'c~', 'd~', 's~']
> MA5-DEBUG: Extracting a multiparticle labelled by [j] with a PDG-id : ['g', 'u', 'c', 'd', 's', 'u~', 'c~', 'd~', 's~']
> MA5-DEBUG: Extracting a multiparticle labelled by [l+] with a PDG-id : ['e+', 'mu+']
> MA5-DEBUG: Extracting a multiparticle labelled by [l-] with a PDG-id : ['e-', 'mu-']
> MA5-DEBUG: Extracting a multiparticle labelled by [vl] with a PDG-id : ['ve', 'vm', 'vt']
> MA5-DEBUG: Extracting a multiparticle labelled by [vl~] with a PDG-id : ['ve~', 'vm~', 'vt~']
> MA5: => Creation of the label 'invisible' (-> missing energy).
> MA5: => Creation of the label 'hadronic' (-> jet energy).
> MA5: => 8 multiparticles successfully exported.
> ma5>
>
> --
> You received this question notification because you are an answer
> contact for MadAnalysis 5.
|
Revision history for this message
|
#6 |
Dear Benjamin,
the PADForMA5tune directory exist. But, how can I check the log files? Sorry for the question, I am new to Linux.
|
Revision history for this message
|
#7 |
Hi,
Please go into the Build subfolder. There are various files with a .log extension. You can also try to reinstall PADForMA5tune and check the screen output (there should be a crash somewhere).
Cheers,
Benjamin
> On 5 Mar 2019, at 14:17 , pattara angkinun <email address hidden> wrote:
>
> Question #678555 on MadAnalysis 5 changed:
> https:/
>
> pattara angkinun posted a new comment:
> Dear Benjamin,
>
> the PADForMA5tune directory exist. But, how can I check the log files?
> Sorry for the question, I am new to Linux.
>
> --
> You received this question notification because you are an answer
> contact for MadAnalysis 5.
|
Revision history for this message
|
#8 |
Dear Benjamin,
sorry for asking a lot, I have tried to reinstall PADForMA5tune but I don't find any bug warning on the screen. In the Build sub-folder I found only one log file, namely compilation.log. What should I do?
Here is the log file:
-e [1;33m-
-e [1;33m-
-e Building MadAnalysis Job
-e Compilation
c++ -Wall -O3 -fPIC -I/home/
-e -------
-e -------
c++ -Wall -O3 -fPIC -I/home/
c++ -Wall -O3 -fPIC -I/home/
c++ -Wall -O3 -fPIC -I/home/
c++ -Wall -O3 -fPIC -I/home/
c++ -Wall -O3 -fPIC -I/home/
c++ -Wall -O3 -fPIC -I/home/
c++ -Wall -O3 -fPIC -I/home/
SampleAnalyzer/
SampleAnalyzer/
double MET = pTmiss.Pt();
^~~
SampleAnalyzer/
SampleAnalyzer/
double meteff1J = 0.0 ;
SampleAnalyzer/
double meteff2J = 0.0 ;
SampleAnalyzer/
}
^
c++ -Wall -O3 -fPIC -I/home/
c++ -Wall -O3 -fPIC -I/home/
c++ -Wall -O3 -fPIC -I/home/
c++ -Wall -O3 -fPIC -I/home/
c++ -Wall -O3 -fPIC -I/home/
-e [1;33m-
-e Linking
-e -------
SampleAnalyzer/
SampleAnalyzer/
const RecJetFormat* BSeed_3Jet;
SampleAnalyzer/
SampleAnalyzer/
double MET_old = pTmiss.Pt();
^~~~~~~
c++ Main/main.o SampleAnalyzer/
Here is an installation output screen in case you want to check:
pattara@
pattara@
MA5:
MA5: *******
MA5: * *
MA5: * W E L C O M E to M A D A N A L Y S I S 5 *
MA5: * ______ ______ *
MA5: * /'\_/`\/\ __ \/\ ___\ *
MA5: * /\ \ \ \_\ \ \ \__/ *
MA5: * \ \ \__\ \ \ __ \ \___``\ *
MA5: * \ \ \_/\ \ \ \/\ \/\ \_\ \ *
MA5: * \ \_\\ \_\ \_\ \_\ \____/ *
MA5: * \/_/ \/_/\/_/\/_/\/___/ *
MA5: * *
MA5: * MA5 release : 1.7.21 2019/02/07 *
MA5: * *
MA5: * Comput. Phys. Commun. 184 (2013) 222-256 *
MA5: * Eur. Phys. J. C74 (2014) 3103 *
MA5: * *
MA5: * The MadAnalysis Development Team - Please visit us at *
MA5: * https:/
MA5: * *
MA5: * Type 'help' for in-line help. *
MA5: * *
MA5: *******
MA5: Platform: Linux 4.15.0-45-generic [Linux mode]
MA5: Reading user settings ...
MA5: Checking mandatory packages:
MA5: - Python [OK]
MA5: - GNU GCC g++ [OK]
MA5: - GNU Make [OK]
MA5: Checking optional packages devoted to data processing:
MA5: - Zlib [DISABLED]
MA5: - FastJet [DISABLED]
MA5: - Root [OK]
MA5: - Delphes [DEACTIVATED]
MA5: - Delphes-MA5tune [OK]
MA5: Checking the MadAnalysis 5 core library:
MA5: => MadAnalysis libraries found.
MA5: => MadAnalysis test program works.
MA5: Checking optional packages devoted to reinterpretation:
MA5: - SciPy [OK]
MA5: - PAD [OK]
MA5: - PADForMA5tune [DISABLED]
MA5: Checking optional packages devoted to histogramming:
MA5: - Root [OK]
MA5: - Matplotlib [OK]
MA5: - pdflatex [OK]
MA5: - latex [OK]
MA5: Package used for graphical rendering: Root
MA5: *******
MA5: Particle labels from input/reco_
MA5: => 14 particles successfully exported.
MA5: Multiparticle labels from madanalysis/
MA5: => 9 multiparticles successfully exported.
MA5: => 9 multiparticles successfully exported.
ma5>install PADForMA5tune
MA5:
MA5: *******
MA5: Installing PADForMA5tune
MA5: *******
MA5: Detecting a previous installation ...
MA5: => found
MA5: Removing the previous installation ...
MA5: => Backuping the previous installation: padforma5tune-
MA5: => Backup done
MA5-WARNING: Are you sure to remove the directory called '/home/
Answer: y
MA5: How many cores would you like to use for the compilation ? default = max = 8
=> Answer: 8
MA5: => Number of cores used for the compilation = 8
MA5: *******
MA5: Creating a devoted folder ...
MA5: Creating folder '/home/
MA5: Copying required 'SampleAnalyzer' source files...
MA5: Writing an empty analysis...
A new class called 'cms_sus_13_011' will be created.
Done !
MA5: Writing a 'Makefile'...
MA5: Downloading the package ...
MA5: - 1/2 http://
--> Download 7.17K of 7.17K (100.0%)
MA5: - 2/2 http://
--> Download 2.51K of 2.51K (100.0%)
MA5: --> Downloading the files for atlas_susy_2013_02
MA5: - 1/4 http://
--> Download 18.58K of 18.58K (100.0%)
MA5: - 2/4 http://
--> Download 2.36K of 2.36K (100.0%)
MA5: - 3/4 http://
--> Download 553.00b of 553.00b (100.0%)
MA5: - 4/4 http://
--> Download 31.50K of 31.50K (100.0%)
MA5: --> Downloading the files for atlas_higg_2013_03
MA5: - 1/3 http://
--> Download 569.00b of 569.00b (100.0%)
MA5: - 2/3 http://
--> Download 12.17K of 12.17K (100.0%)
MA5: - 3/3 http://
--> Download 583.00b of 583.00b (100.0%)
MA5: --> Downloading the files for atlas_susy_2013_04
MA5: - 1/4 http://
--> Download 21.05K of 21.05K (100.0%)
MA5: - 2/4 http://
--> Download 588.00b of 588.00b (100.0%)
MA5: - 3/4 http://
--> Download 13.06K of 13.06K (100.0%)
MA5: - 4/4 http://
--> Download 2.33K of 2.33K (100.0%)
MA5: --> Downloading the files for atlas_susy_2013_11
MA5: - 1/3 http://
--> Download 2.55K of 2.55K (100.0%)
MA5: - 2/3 http://
--> Download 569.00b of 569.00b (100.0%)
MA5: - 3/3 http://
--> Download 23.17K of 23.17K (100.0%)
MA5: --> Downloading the files for atlas_susy_2013_21
MA5: - 1/4 http://
--> Download 1.09K of 1.09K (100.0%)
MA5: - 2/4 http://
--> Download 16.68K of 16.68K (100.0%)
MA5: - 3/4 http://
--> Download 588.00b of 588.00b (100.0%)
MA5: - 4/4 http://
--> Download 20.73K of 20.73K (100.0%)
MA5: --> Downloading the files for atlas_susy_2014_10
MA5: - 1/4 http://
--> Download 565.00b of 565.00b (100.0%)
MA5: - 2/4 http://
--> Download 21.00K of 21.00K (100.0%)
MA5: - 3/4 http://
--> Download 18.62K of 18.62K (100.0%)
MA5: - 4/4 http://
--> Download 2.05K of 2.05K (100.0%)
MA5: --> Downloading the files for atlas_susy_2013_05
MA5: - 1/3 http://
--> Download 1.62K of 1.62K (100.0%)
MA5: - 2/3 http://
--> Download 32.20K of 32.20K (100.0%)
MA5: - 3/3 http://
--> Download 2.47K of 2.47K (100.0%)
MA5: --> Downloading the files for cms_sus_13_011
MA5: - 1/4 http://
--> Download 3.01K of 3.01K (100.0%)
MA5: - 2/4 http://
--> Download 40.29K of 40.29K (100.0%)
MA5: - 3/4 http://
--> Download 549.00b of 549.00b (100.0%)
MA5: - 4/4 http://
--> Download 18.96K of 18.96K (100.0%)
MA5: --> Downloading the files for cms_sus_13_012
MA5: - 1/3 http://
--> Download 549.00b of 549.00b (100.0%)
MA5: - 2/3 http://
--> Download 18.42K of 18.42K (100.0%)
MA5: - 3/3 http://
--> Download 5.59K of 5.59K (100.0%)
MA5: --> Downloading the files for cms_sus_13_016
MA5: - 1/3 http://
--> Download 632.00b of 632.00b (100.0%)
MA5: - 2/3 http://
--> Download 548.00b of 548.00b (100.0%)
MA5: - 3/3 http://
--> Download 9.11K of 9.11K (100.0%)
MA5: --> Downloading the files for cms_sus_
MA5: - 1/3 http://
--> Download 589.00b of 589.00b (100.0%)
MA5: - 2/3 http://
--> Download 11.91K of 11.91K (100.0%)
MA5: - 3/3 http://
--> Download 1.74K of 1.74K (100.0%)
MA5: --> Downloading the files for cms_sus_
MA5: - 1/4 http://
--> Download 21.67K of 21.67K (100.0%)
MA5: - 2/4 http://
--> Download 19.99K of 19.99K (100.0%)
MA5: - 3/4 http://
--> Download 986.00b of 986.00b (100.0%)
MA5: - 4/4 http://
--> Download 1007.00b of 1007.00b (100.0%)
MA5: Unpacking the package ...
MA5: Configuring the package ...
MA5: Building the package ...
MA5: Checking the installation ...
MA5: Installation complete.
MA5: => Status: [OK]
MA5: *******
MA5:
ma5>
|
Revision history for this message
|
#9 |
Is the executable available in the Build folder (the MadAnalysis5job file)? It looks everything went smooothly. What is happening when you restart the program? is the PadForMA5tune detected this time?
Cheers,
Benjamimn
> On 5 Mar 2019, at 16:17 , pattara angkinun <email address hidden> wrote:
>
> Question #678555 on MadAnalysis 5 changed:
> https:/
>
> pattara angkinun posted a new comment:
> Dear Benjamin,
>
> sorry for asking a lot, I have tried to reinstall PADForMA5tune but I
> don't find any bug warning on the screen. In the Build sub-folder I
> found only one log file, namely compilation.log. What should I do?
>
> Here is the log file:
>
> -e [1;33m-
> -e [1;33m-
> -e Building MadAnalysis Job
> -e Compilation
> c++ -Wall -O3 -fPIC -I/home/
> -e -------
> -e -------
> c++ -Wall -O3 -fPIC -I/home/
> c++ -Wall -O3 -fPIC -I/home/
> c++ -Wall -O3 -fPIC -I/home/
> c++ -Wall -O3 -fPIC -I/home/
> c++ -Wall -O3 -fPIC -I/home/
> c++ -Wall -O3 -fPIC -I/home/
> c++ -Wall -O3 -fPIC -I/home/
> SampleAnalyzer/
> SampleAnalyzer/
> double MET = pTmiss.Pt();
> ^~~
> SampleAnalyzer/
> SampleAnalyzer/
> double meteff1J = 0.0 ;
> ^~~~~~~~
> SampleAnalyzer/
> double meteff2J = 0.0 ;
> ^~~~~~~~
> SampleAnalyzer/
> }
> ^
> c++ -Wall -O3 -fPIC -I/home/
> c++ -Wall -O3 -fPIC -I/home/
> c++ -Wall -O3 -fPIC -I/home/
> c++ -Wall -O3 -fPIC -I/home/
> c++ -Wall -O3 -fPIC -I/home/
> -e [1;33m-
> -e Linking
> -e -------
> SampleAnalyzer/
> SampleAnalyzer/
> const RecJetFormat* BSeed_3Jet;
> ^~~~~~~~~~
> SampleAnalyzer/
> SampleAnalyzer/
> double MET_old = pTmiss.Pt();
> ^~~~~~~
> c++ Main/main.o SampleAnalyzer/
>
>
> Here is an installation output screen in case you want to check:
>
> pattara@
> pattara@
> MA5:
> MA5: *******
> MA5: * *
> MA5: * W E L C O M E to M A D A N A L Y S I S 5 *
> MA5: * ______ ______ *
> MA5: * /'\_/`\/\ __ \/\ ___\ *
> MA5: * /\ \ \ \_\ \ \ \__/ *
> MA5: * \ \ \__\ \ \ __ \ \___``\ *
> MA5: * \ \ \_/\ \ \ \/\ \/\ \_\ \ *
> MA5: * \ \_\\ \_\ \_\ \_\ \____/ *
> MA5: * \/_/ \/_/\/_/\/_/\/___/ *
> MA5: * *
> MA5: * MA5 release : 1.7.21 2019/02/07 *
> MA5: * *
> MA5: * Comput. Phys. Commun. 184 (2013) 222-256 *
> MA5: * Eur. Phys. J. C74 (2014) 3103 *
> MA5: * *
> MA5: * The MadAnalysis Development Team - Please visit us at *
> MA5: * https:/
> MA5: * *
> MA5: * Type 'help' for in-line help. *
> MA5: * *
> MA5: *******
> MA5: Platform: Linux 4.15.0-45-generic [Linux mode]
> MA5: Reading user settings ...
> MA5: Checking mandatory packages:
> MA5: - Python [OK]
> MA5: - GNU GCC g++ [OK]
> MA5: - GNU Make [OK]
> MA5: Checking optional packages devoted to data processing:
> MA5: - Zlib [DISABLED]
> MA5: - FastJet [DISABLED]
> MA5: - Root [OK]
> MA5: - Delphes [DEACTIVATED]
> MA5: - Delphes-MA5tune [OK]
> MA5: Checking the MadAnalysis 5 core library:
> MA5: => MadAnalysis libraries found.
> MA5: => MadAnalysis test program works.
> MA5: Checking optional packages devoted to reinterpretation:
> MA5: - SciPy [OK]
> MA5: - PAD [OK]
> MA5: - PADForMA5tune [DISABLED]
> MA5: Checking optional packages devoted to histogramming:
> MA5: - Root [OK]
> MA5: - Matplotlib [OK]
> MA5: - pdflatex [OK]
> MA5: - latex [OK]
> MA5: Package used for graphical rendering: Root
> MA5: *******
> MA5: Particle labels from input/reco_
> MA5: => 14 particles successfully exported.
> MA5: Multiparticle labels from madanalysis/
> MA5: => 9 multiparticles successfully exported.
> MA5: => 9 multiparticles successfully exported.
> ma5>install PADForMA5tune
> MA5:
> MA5: *******
> MA5: Installing PADForMA5tune
> MA5: *******
> MA5: Detecting a previous installation ...
> MA5: => found
> MA5: Removing the previous installation ...
> MA5: => Backuping the previous installation: padforma5tune-
> MA5: => Backup done
> MA5-WARNING: Are you sure to remove the directory called '/home/
> Answer: y
> MA5: How many cores would you like to use for the compilation ? default = max = 8
> => Answer: 8
> MA5: => Number of cores used for the compilation = 8
> MA5: *******
> MA5: Creating a devoted folder ...
> MA5: Creating folder '/home/
> MA5: Copying required 'SampleAnalyzer' source files...
> MA5: Writing an empty analysis...
> A new class called 'cms_sus_13_011' will be created.
> Done !
> MA5: Writing a 'Makefile'...
> MA5: Downloading the package ...
> MA5: - 1/2 http://
> --> Download 7.17K of 7.17K (100.0%)
> MA5: - 2/2 http://
> --> Download 2.51K of 2.51K (100.0%)
> MA5: --> Downloading the files for atlas_susy_2013_02
> MA5: - 1/4 http://
> --> Download 18.58K of 18.58K (100.0%)
> MA5: - 2/4 http://
> --> Download 2.36K of 2.36K (100.0%)
> MA5: - 3/4 http://
> --> Download 553.00b of 553.00b (100.0%)
> MA5: - 4/4 http://
> --> Download 31.50K of 31.50K (100.0%)
> MA5: --> Downloading the files for atlas_higg_2013_03
> MA5: - 1/3 http://
> --> Download 569.00b of 569.00b (100.0%)
> MA5: - 2/3 http://
> --> Download 12.17K of 12.17K (100.0%)
> MA5: - 3/3 http://
> --> Download 583.00b of 583.00b (100.0%)
> MA5: --> Downloading the files for atlas_susy_2013_04
> MA5: - 1/4 http://
> --> Download 21.05K of 21.05K (100.0%)
> MA5: - 2/4 http://
> --> Download 588.00b of 588.00b (100.0%)
> MA5: - 3/4 http://
> --> Download 13.06K of 13.06K (100.0%)
> MA5: - 4/4 http://
> --> Download 2.33K of 2.33K (100.0%)
> MA5: --> Downloading the files for atlas_susy_2013_11
> MA5: - 1/3 http://
> --> Download 2.55K of 2.55K (100.0%)
> MA5: - 2/3 http://
> --> Download 569.00b of 569.00b (100.0%)
> MA5: - 3/3 http://
> --> Download 23.17K of 23.17K (100.0%)
> MA5: --> Downloading the files for atlas_susy_2013_21
> MA5: - 1/4 http://
> --> Download 1.09K of 1.09K (100.0%)
> MA5: - 2/4 http://
> --> Download 16.68K of 16.68K (100.0%)
> MA5: - 3/4 http://
> --> Download 588.00b of 588.00b (100.0%)
> MA5: - 4/4 http://
> --> Download 20.73K of 20.73K (100.0%)
> MA5: --> Downloading the files for atlas_susy_2014_10
> MA5: - 1/4 http://
> --> Download 565.00b of 565.00b (100.0%)
> MA5: - 2/4 http://
> --> Download 21.00K of 21.00K (100.0%)
> MA5: - 3/4 http://
> --> Download 18.62K of 18.62K (100.0%)
> MA5: - 4/4 http://
> --> Download 2.05K of 2.05K (100.0%)
> MA5: --> Downloading the files for atlas_susy_2013_05
> MA5: - 1/3 http://
> --> Download 1.62K of 1.62K (100.0%)
> MA5: - 2/3 http://
> --> Download 32.20K of 32.20K (100.0%)
> MA5: - 3/3 http://
> --> Download 2.47K of 2.47K (100.0%)
> MA5: --> Downloading the files for cms_sus_13_011
> MA5: - 1/4 http://
> --> Download 3.01K of 3.01K (100.0%)
> MA5: - 2/4 http://
> --> Download 40.29K of 40.29K (100.0%)
> MA5: - 3/4 http://
> --> Download 549.00b of 549.00b (100.0%)
> MA5: - 4/4 http://
> --> Download 18.96K of 18.96K (100.0%)
> MA5: --> Downloading the files for cms_sus_13_012
> MA5: - 1/3 http://
> --> Download 549.00b of 549.00b (100.0%)
> MA5: - 2/3 http://
> --> Download 18.42K of 18.42K (100.0%)
> MA5: - 3/3 http://
> --> Download 5.59K of 5.59K (100.0%)
> MA5: --> Downloading the files for cms_sus_13_016
> MA5: - 1/3 http://
> --> Download 632.00b of 632.00b (100.0%)
> MA5: - 2/3 http://
> --> Download 548.00b of 548.00b (100.0%)
> MA5: - 3/3 http://
> --> Download 9.11K of 9.11K (100.0%)
> MA5: --> Downloading the files for cms_sus_
> MA5: - 1/3 http://
> --> Download 589.00b of 589.00b (100.0%)
> MA5: - 2/3 http://
> --> Download 11.91K of 11.91K (100.0%)
> MA5: - 3/3 http://
> --> Download 1.74K of 1.74K (100.0%)
> MA5: --> Downloading the files for cms_sus_
> MA5: - 1/4 http://
> --> Download 21.67K of 21.67K (100.0%)
> MA5: - 2/4 http://
> --> Download 19.99K of 19.99K (100.0%)
> MA5: - 3/4 http://
> --> Download 986.00b of 986.00b (100.0%)
> MA5: - 4/4 http://
> --> Download 1007.00b of 1007.00b (100.0%)
> MA5: Unpacking the package ...
> MA5: Configuring the package ...
> MA5: Building the package ...
> MA5: Checking the installation ...
> MA5: Installation complete.
> MA5: => Status: [OK]
> MA5: *******
> MA5:
> ma5>
>
> --
> You received this question notification because you are an answer
> contact for MadAnalysis 5.
|
Revision history for this message
|
#10 |
Dear Benjamin,
the MadAnalysis5job file exist in the Build sub-folder but PADForMA5Tune is still disable after restarting the program.
|
Revision history for this message
|
#11 |
If the file /home/pattara/
Cheers,
Benjamin
> On 5 Mar 2019, at 17:32 , pattara angkinun <email address hidden> wrote:
>
> Question #678555 on MadAnalysis 5 changed:
> https:/
>
> pattara angkinun posted a new comment:
> Dear Benjamin,
>
> the MadAnalysis5job file exist in the Build sub-folder but PADForMA5Tune
> is still disable after restarting the program.
>
> --
> You received this question notification because you are an answer
> contact for MadAnalysis 5.
|
Revision history for this message
|
#12 |
Dear Benjamin,
thank a lot for your reply. I have no problem with that but I have to tell you first that I really don't know about programming and Linux system so I am not sure if I can help. For my work I found that the v1.6 is working on my university computer so I can work with that, it's just a bit inconvenient. But if you have time and want to fix the problem as a study case we can have a skype meeting.
regards,
Pattara Angkinun
|
Revision history for this message
|
#13 |
Hi Pattara,
The PADForMA5tune does not work with v1.6 (except if you have root 5). Therefore, I am a bit puzzled how this could solve your issue. This being said, I really want to fix the issue.
Cheers,
Benjamin
> On 6 Mar 2019, at 24:12 , pattara angkinun <email address hidden> wrote:
>
> Question #678555 on MadAnalysis 5 changed:
> https:/
>
> pattara angkinun posted a new comment:
> Dear Benjamin,
>
> thank a lot for your reply. I have no problem with that but I have to
> tell you first that I really don't know about programming and Linux
> system so I am not sure if I can help. For my work I found that the v1.6
> is working on my university computer so I can work with that, it's just
> a bit inconvenient. But if you have time and want to fix the problem as
> a study case we can have a skype meeting.
>
> regards,
>
> Pattara Angkinun
>
> --
> You received this question notification because you are an answer
> contact for MadAnalysis 5.
|
Revision history for this message
|
#14 |
Dear, Benjamin
The computer that I mentioned is using root5. By the way, when would be convenient for you to meet.
best regards,
Pattara Angkinun
|
Revision history for this message
|
#15 |
Hi,
Compatibility with root5 is not ensure anymore from v1.7 onwards. This is probably the reason of the issue.
Cheers,
Benjamin
PS: I am free on Friday morning. Please drop me a direct e-mail with your skype information
> On 6 Mar 2019, at 08:47 , pattara angkinun <email address hidden> wrote:
>
> Question #678555 on MadAnalysis 5 changed:
> https:/
>
> pattara angkinun posted a new comment:
> Dear, Benjamin
>
> The computer that I mentioned is using root5. By the way, when would be
> convenient for you to meet.
>
> best regards,
>
> Pattara Angkinun
>
> --
> You received this question notification because you are an answer
> contact for MadAnalysis 5.
|
Revision history for this message
|
#16 |
Dear Benjamin,
My e-mail: <email address hidden>
Skype name: live:d4ed238543
regards,
Pattara Angkinun
|
Revision history for this message
|
#17 |
Dear pattara and Benjamin,
As I have also gone through the similar problem, I have solved my problem using a simple trick. So after I have installed the PADForMA5tune and Delphes including the DelphesMA5tune via madanalysis5's install command, I realized that the folder naming of the PADForMA5tune is all in CAPITAL LETTERS, i.e. PADFORMA5TUNE which i guess when the Madanalysis5 is running an searching for the package, it does not recognize the folder that is already built successfully. When I changed the name of the file to PADForMA5tune, Madanalysis5 recognize its existence and I was able to use "$set main.recast = on/off" option. I guess you may have solved the issue a month ago, but I think some people who are having trouble with the similar problem may find this useful.
For the environment setup, I downloaded v1.7 madanalysis5 and using ROOT6 for the analysis.
Best regards,
Dongwon Kim
|
Revision history for this message
|
#18 |
Hi Dong Won,
It is not very clear to me how the folder ended up to be in capital letters. Can you please tell me what you exactly did?
Cheers,
Benj
> On 23 Apr 2019, at 19:52 , Dong Won Kim <email address hidden> wrote:
>
> Question #678555 on MadAnalysis 5 changed:
> https:/
>
> Dong Won Kim posted a new comment:
> Dear pattara and Benjamin,
>
> As I have also gone through the similar problem, I have solved my
> problem using a simple trick. So after I have installed the
> PADForMA5tune and Delphes including the DelphesMA5tune via
> madanalysis5's install command, I realized that the folder naming of the
> PADForMA5tune is all in CAPITAL LETTERS, i.e. PADFORMA5TUNE which i
> guess when the Madanalysis5 is running an searching for the package, it
> does not recognize the folder that is already built successfully. When
> I changed the name of the file to PADForMA5tune, Madanalysis5 recognize
> its existence and I was able to use "$set main.recast = on/off" option.
> I guess you may have solved the issue a month ago, but I think some
> people who are having trouble with the similar problem may find this
> useful.
>
> For the environment setup, I downloaded v1.7 madanalysis5 and using
> ROOT6 for the analysis.
>
> Best regards,
> Dongwon Kim
>
> --
> You received this question notification because you are an answer
> contact for MadAnalysis 5.
|
Revision history for this message
|
#19 |
Dear Benjamin,
I followed the installation procedure given by the tutorial(which is available online, but do not know which one it is). So here is the general procedure. When I downloaded the madanalysis5 and tar the file, I ran the madanalysis5 using
$./bin/ma5
Then, inside the madanalysis5, I installed the packages one by one, say starting with zlib, delphes, PAD, PADForMA5tune, and delphes-ma5tune. After doing this procedure, I have noticed that the PADForMA5tune was marked [disabled] even though I downloaded the package and it was successfully installed. So, I checked the folder inside tools/PADFORMA5TUNE ,which was named like this. So, I changed the folder name to PADForMA5tune and afterwards, the madanalysis5 recognizes the package and it is indicated as [OK] at the prompt at the start of the program.
If any of the wording is unclear, let me know.
Bests,
Dongwon Kim
|
Revision history for this message
|
#20 |
Dear Benjamin and Dong Won,
Thank you for the solution. I have checked what Dong Won mention and found that this is the cause of the problem. I don’t know why the folder name is written in capital letter like that but I didn’t do any thing extra while installing it, just using the command “install PADForMA5tune”
Best regards,
Pattara Angkinun
|
Revision history for this message
|
#21 |
You can install both 'delphes' and 'delphes-MA5tune' but what I have found that at a time one will be active and other one will be in de-active mode. I have done this quite a few times in my system ubuntu-22.04.
Can you help with this problem?
Provide an answer of your own, or ask pattara angkinun for more information if necessary.
