unweighted_events.lhe.gz

Bug #1856969 reported by Michael Hidayat
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MadDM
Fix Committed
Undecided
Unassigned

Bug Description

It is error that no such file or directory: ../../unweighted_events_lhe.gz

Revision history for this message
Olivier Mattelaer (olivier-mattelaer) wrote :

Ok I think the first thing you can do to fix this is ... to give more details on what type of computation you are doing and more information related to this bug. Like this I have no clue of which tool you are using that can crash with such error. (I actually do not see any code using such path to access the events in the zipped format).

In general providing the debug file is a good starting point to give me the information that I need (often not enough unfortunatly but already much more than this)

Cheers,

Olivier

Revision history for this message
Michael Hidayat (michaelhidayat270595) wrote :
Download full text (6.4 KiB)

Oh, I'm sorry.
So I use:
- import model DMsimp_s_spin0
- define darkmatter xd
- add direct_detection
- add relic_density
- add indirect_detection
For the output, I give name "output ex"
- Launch ex
Here's the output:
/=========================================================================\
| 1. Compute the Relic Density relic = ON |
| 2. Compute direct(ional) detection direct = directional |
| 3. Compute indirect detection/flux indirect = sigmav |
| 4. Run Multinest scan nestscan = OFF |
\=========================================================================/
 You can also edit the various input card:
 * Enter the name/number to open the editor
 * Enter a path to a file to replace the card
 * Enter set NAME value to change any parameter to the requested value
 /=============================================================================\
 | 5. Edit the model parameters [param] |
 | 6. Edit the MadDM options [maddm] |
 \=============================================================================/
[60s to answer]

INFO: Start computing indirect,relic,direct
maddm_card missed argument print_sigmas. Takes default: False
INFO: compilation done
 Freezeout occurs too early! Relic density too big to comprehend. Seeting Omegah^2 = -1.0 \n
INFO: Running indirect detection
************************************************************
* *
* W E L C O M E to *
* M A D G R A P H 5 _ a M C @ N L O *
* M A D E V E N T *
* *
* * * *
* * * * * *
* * * * * 5 * * * * *
* * * * * *
* * * *
* *
* VERSION 2.6.7 2019-10-16 *
* *
* The MadGraph5_aMC@NLO Development Team - Find us at *
* https://server06.fynu.ucl.ac.be/projects/madgraph *
* *
* Type 'help' for in-line help. *
* *
************************************************************
INFO: load configuration from /home/michael/Desktop/Programs/MG5_aMC_v2_6_6/ex/Indirect/Cards/me5_configuration.txt
INFO: load configuration from /home/michael/Desktop/Programs/MG5_aMC_v2_6_6/input/mg5_configuration.txt
INFO: load configuration from /home/michael/Desktop/Programs/MG5_aMC_v2_6_6/ex/Indirect/Cards/me5_configuration.txt
Using default text editor "vi". Set another one in ./input/mg5_configuration.txt
INFO: Computing sigmav with method: reshuffling
The following switches deter...

Read more...

affects: mg5amcnlo → maddm
Revision history for this message
Olivier Mattelaer (olivier-mattelaer) wrote :

Thanks this make a lot more sense now.

Could you attach the MG5_debug file?
and maybe do an "ls" for the following directory:
/home/michael/Desktop/Programs/MG5_aMC_v2_6_6/ex/Indirect/Events/run_01/

Cheers,

Olivier

Revision history for this message
Michael Hidayat (michaelhidayat270595) wrote : Re: [Bug 1856969] Re: unweighted_events.lhe.gz
  • MG5_debug Edit (8.0 KiB, application/octet-stream; name=MG5_debug)

Here I attach MG5_debug file.

That is the result of ls:
~/Desktop/Programs/MG5_aMC_v2_6_6/ex/Indirect/Events/run_01$ ls
run_01_DM_banner.txt rwgt_events_rwgt_1.lhe.gz unweighted_events.lhe

On Thu, Dec 19, 2019 at 5:35 PM Olivier Mattelaer <
<email address hidden>> wrote:

> Thanks this make a lot more sense now.
>
> Could you attach the MG5_debug file?
> and maybe do an "ls" for the following directory:
> /home/michael/Desktop/Programs/MG5_aMC_v2_6_6/ex/Indirect/Events/run_01/
>
> Cheers,
>
> Olivier
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1856969
>
> Title:
> unweighted_events.lhe.gz
>
> Status in MadDM:
> New
>
> Bug description:
> It is error that no such file or directory:
> ../../unweighted_events_lhe.gz
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/maddm/+bug/1856969/+subscriptions
>

--
Sincerly,

Michael Hidayat

Revision history for this message
Michael Hidayat (michaelhidayat270595) wrote :

That is the result of ls:
~/Desktop/Programs/MG5_aMC_v2_6_6/ex/Indirect/Events/run_01$ ls
run_01_DM_banner.txt rwgt_events_rwgt_1.lhe.gz unweighted_events.lhe

Revision history for this message
Olivier Mattelaer (olivier-mattelaer) wrote :

Hi,

Looks like the issue is related to ExRootAnalysis which has some side effect with maddm.
Can you remove that package? This should solve your issue.
I will create a patch for maddm to avoid to call ExRoot when running indirect detection.
I will post it here (probably today) but the easiest will be anyway to remove that package.

Thanks for the usefull bug report,

Cheers,

Olivier

Revision history for this message
Olivier Mattelaer (olivier-mattelaer) wrote :

patch that should fix the issue.

Cheers,

Olivier

Changed in maddm:
status: New → Fix Committed
Revision history for this message
Michael Hidayat (michaelhidayat270595) wrote :

Anyway, I'm still a beginner using MadDM and Ubuntu.
How can I remove ExRootAnalysis package? Should I open MG5_debug file and just delete this path " exrootanalysis_path : ./ExRootAnalysis"?
And you send exroot.patch, what should I do to that file?
Thanks in advance.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.