Bugs when trying specific coupling mass combinations in t-channel DM model

Bug #1900089 reported by Shyam Balaji
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MadDM
New
Undecided
Unassigned

Bug Description

Hi Olivier,

We are trying to once again generate limits for the DM model given in https://feynrules.irmp.ucl.ac.be/wiki/DMsimpt from UFO_all_mq.zip, however we get the following error when trying to proceed with the attached param_card.dat, we get the following bug. Would appreciate any help!

Command "launch output_UFO_all_mq_maddm" interrupted with error:
IOError : [Errno 2] No such file or directory: '/workarea/MG5_aMC_v2_8_1/output_UFO_all_mq_maddm/output/run_16/maddm.out'
Please report this bug on https://bugs.launchpad.net/mg5amcnlo
More information is found in 'MG5_debug'.
Please attach this file to your report.

This is the debug file content

#************************************************************
# MadGraph5_aMC@NLO
#
#
#
# 5
#
#
#
#
# VERSION 2.8.1 2020-09-28
#
# The MadGraph5_aMC@NLO Development Team - Find us at
# https://server06.fynu.ucl.ac.be/projects/madgraph
#
#************************************************************
#
# Command File for MadGraph5_aMC@NLO
#
# run as ./bin/mg5_aMC filename
#
#************************************************************
set group_subprocesses Auto
set ignore_six_quark_processes False
set max_t_for_channel 99
set loop_optimized_output True
set low_mem_multicore_nlo_generation False
set default_unset_couplings 99
set zerowidth_tchannel True
set loop_color_flows False
set gauge unitary
set complex_mass_scheme False
set max_npoint_for_channel 0
import model sm
define p = g u c d s u c d s
define j = g u c d s u c d s
define l+ = e+ mu+
define l- = e- mu-
define vl = ve vm vt
define vl = ve vm vt
launch output_UFO_all_mq_maddm
Traceback (most recent call last):
File "/workarea/MG5_aMC_v2_8_1/madgraph/interface/extended_cmd.py", line 1541, in onecmd
return self.onecmd_orig(line, **opt)
File "/workarea/MG5_aMC_v2_8_1/madgraph/interface/extended_cmd.py", line 1490, in onecmd_orig
return func(arg, **opt)
File "/workarea/MG5_aMC_v2_8_1/PLUGIN/maddm/maddm_interface.py", line 752, in do_launch
self._MDM.exec_cmd('launch ' + line.replace(args[1], ''))
File "/workarea/MG5_aMC_v2_8_1/madgraph/interface/extended_cmd.py", line 1570, in exec_cmd
stop = Cmd.onecmd_orig(current_interface, line, **opt)
File "/workarea/MG5_aMC_v2_8_1/madgraph/interface/extended_cmd.py", line 1490, in onecmd_orig
return func(arg, **opt)
File "/workarea/MG5_aMC_v2_8_1/PLUGIN/maddm/maddm_run_interface.py", line 813, in do_launch
for line in open(pjoin(self.dir_path, output)):
IOError: [Errno 2] No such file or directory: '/workarea/MG5_aMC_v2_8_1/output_UFO_all_mq_maddm/output/run_16/maddm.out'
Related File: /workarea/MG5_aMC_v2_8_1/output_UFO_all_mq_maddm/output/run_16/maddm.out
MadGraph5_aMC@NLO Options
----------------
complex_mass_scheme : False
default_unset_couplings : 99
gauge : unitary
group_subprocesses : Auto
ignore_six_quark_processes : False
loop_color_flows : False
loop_optimized_output : True
low_mem_multicore_nlo_generation : False
max_npoint_for_channel : 0
max_t_for_channel : 99
stdout_level : 20 (user set)
zerowidth_tchannel : True

MadEvent Options
----------------
automatic_html_opening : True
nb_core : None
notification_center : True
run_mode : 2

Configuration Options
---------------------
OLP : MadLoop
amcfast : amcfast-config
applgrid : applgrid-config
auto_update : 7
cluster_local_path : None
cluster_nb_retry : 1
cluster_queue : None (user set)
cluster_retry_wait : 300
cluster_size : 100
cluster_status_update : (600, 30)
cluster_temp_path : None
cluster_type : condor
collier : ./HEPTools/lib
cpp_compiler : None
crash_on_error : False
delphes_path : ./Delphes
dragon_path : None
eps_viewer : None
exrootanalysis_path : ./ExRootAnalysis
f2py_compiler : None
f2py_compiler_py2 : None
f2py_compiler_py3 : None
fastjet : None (user set)
fortran_compiler : None
golem : None (user set)
hepmc_path : None (user set)
hwpp_path : None (user set)
lhapdf : lhapdf-config
lhapdf_py2 : None
lhapdf_py3 : None
madanalysis5_path : None (user set)
madanalysis_path : ./MadAnalysis
maddm_first_indirect : True
mg5amc_py8_interface_path : None (user set)
ninja : ./HEPTools/lib
output_dependencies : external
pppc4dmid_path : None (user set)
pythia-pgs_path : ./pythia-pgs
pythia8_path : None (user set)
samurai : None
syscalc_path : ./SysCalc
td_path : ./td
text_editor : None
thepeg_path : None (user set)
timeout : 60
web_browser : None

Regards,

Shyam

Revision history for this message
Shyam Balaji (shyambalaji) wrote :
Revision history for this message
Olivier Mattelaer (olivier-mattelaer) wrote : Re: [Bug 1900089] [NEW] Bugs when trying specific coupling mass combinations in t-channel DM model
Download full text (10.2 KiB)

Hi,

I did not face such issue.
Are you doing only relic density?

The best might be to recreate an output directory and relaunch.

This being said, I have a couple of serrious warning when running with yourr param_card
that some parameter of the param_card are not recognised and/or missing.

Cheers,

Olivier

> On 16 Oct 2020, at 07:27, Shyam Balaji <email address hidden> wrote:
>
> Public bug reported:
>
> Hi Olivier,
>
> We are trying to once again generate limits for the DM model given in
> https://feynrules.irmp.ucl.ac.be/wiki/DMsimpt from UFO_all_mq.zip,
> however we get the following error when trying to proceed with the
> attached param_card.dat, we get the following bug. Would appreciate any
> help!
>
> Command "launch output_UFO_all_mq_maddm" interrupted with error:
> IOError : [Errno 2] No such file or directory: '/workarea/MG5_aMC_v2_8_1/output_UFO_all_mq_maddm/output/run_16/maddm.out'
> Please report this bug on https://bugs.launchpad.net/mg5amcnlo
> More information is found in 'MG5_debug'.
> Please attach this file to your report.
>
> This is the debug file content
>
> #************************************************************
> # MadGraph5_aMC@NLO
> #
> #
> #
> # 5
> #
> #
> #
> #
> # VERSION 2.8.1 2020-09-28
> #
> # The MadGraph5_aMC@NLO Development Team - Find us at
> # https://server06.fynu.ucl.ac.be/projects/madgraph
> #
> #************************************************************
> #
> # Command File for MadGraph5_aMC@NLO
> #
> # run as ./bin/mg5_aMC filename
> #
> #************************************************************
> set group_subprocesses Auto
> set ignore_six_quark_processes False
> set max_t_for_channel 99
> set loop_optimized_output True
> set low_mem_multicore_nlo_generation False
> set default_unset_couplings 99
> set zerowidth_tchannel True
> set loop_color_flows False
> set gauge unitary
> set complex_mass_scheme False
> set max_npoint_for_channel 0
> import model sm
> define p = g u c d s u c d s
> define j = g u c d s u c d s
> define l+ = e+ mu+
> define l- = e- mu-
> define vl = ve vm vt
> define vl = ve vm vt
> launch output_UFO_all_mq_maddm
> Traceback (most recent call last):
> File "/workarea/MG5_aMC_v2_8_1/madgraph/interface/extended_cmd.py", line 1541, in onecmd
> return self.onecmd_orig(line, **opt)
> File "/workarea/MG5_aMC_v2_8_1/madgraph/interface/extended_cmd.py", line 1490, in onecmd_orig
> return func(arg, **opt)
> File "/workarea/MG5_aMC_v2_8_1/PLUGIN/maddm/maddm_interface.py", line 752, in do_launch
> self._MDM.exec_cmd('launch ' + line.replace(args[1], ''))
> File "/workarea/MG5_aMC_v2_8_1/madgraph/interface/extended_cmd.py", line 1570, in exec_cmd
> stop = Cmd.onecmd_orig(current_interface, line, **opt)
> File "/workarea/MG5_aMC_v2_8_1/madgraph/interface/extended_cmd.py", line 1490, in onecmd_orig
> return func(arg, **opt)
> File "/workarea/MG5_aMC_v2_8_1/PLUGIN/maddm/maddm_run_interface.py", line 813, in do_launch
> for line in open(pjoin(self.dir_path, output)):
> IOError: [Errno 2] No such file or directory: '/workarea/MG5_aMC_v2_8_1/output_UFO_all_mq_maddm/output/run_16/maddm.out'
> Related File: /workarea/MG5_aMC_v2_8_1/output_UFO_all_mq_maddm/output/run_16/ma...

Revision history for this message
Shyam Balaji (shyambalaji) wrote :
Download full text (16.0 KiB)

Hi Olivier,

Could you please share the commands you used to generate the output directory?

Regards,

Shyam
________________________________
From: <email address hidden> <email address hidden> on behalf of Olivier Mattelaer <email address hidden>
Sent: 16 October 2020 17:49
To: Shyam Balaji <email address hidden>
Subject: Re: [Bug 1900089] [NEW] Bugs when trying specific coupling mass combinations in t-channel DM model

Hi,

I did not face such issue.
Are you doing only relic density?

The best might be to recreate an output directory and relaunch.

This being said, I have a couple of serrious warning when running with yourr param_card
that some parameter of the param_card are not recognised and/or missing.

Cheers,

Olivier

> On 16 Oct 2020, at 07:27, Shyam Balaji <email address hidden> wrote:
>
> Public bug reported:
>
> Hi Olivier,
>
> We are trying to once again generate limits for the DM model given in
> https://protect-au.mimecast.com/s/MVL_Cr81nytPQrwQT78NwY?domain=feynrules.irmp.ucl.ac.be from UFO_all_mq.zip,
> however we get the following error when trying to proceed with the
> attached param_card.dat, we get the following bug. Would appreciate any
> help!
>
> Command "launch output_UFO_all_mq_maddm" interrupted with error:
> IOError : [Errno 2] No such file or directory: '/workarea/MG5_aMC_v2_8_1/output_UFO_all_mq_maddm/output/run_16/maddm.out'
> Please report this bug on https://protect-au.mimecast.com/s/RM5yCvl1rKipwEOwHXRI9X?domain=bugs.launchpad.net
> More information is found in 'MG5_debug'.
> Please attach this file to your report.
>
> This is the debug file content
>
> #************************************************************
> # MadGraph5_aMC@NLO
> #
> #
> #
> # 5
> #
> #
> #
> #
> # VERSION 2.8.1 2020-09-28
> #
> # The MadGraph5_aMC@NLO Development Team - Find us at
> # https://protect-au.mimecast.com/s/keFvCwV1vMfJlv0lh9KH04?domain=server06.fynu.ucl.ac.be
> #
> #************************************************************
> #
> # Command File for MadGraph5_aMC@NLO
> #
> # run as ./bin/mg5_aMC filename
> #
> #************************************************************
> set group_subprocesses Auto
> set ignore_six_quark_processes False
> set max_t_for_channel 99
> set loop_optimized_output True
> set low_mem_multicore_nlo_generation False
> set default_unset_couplings 99
> set zerowidth_tchannel True
> set loop_color_flows False
> set gauge unitary
> set complex_mass_scheme False
> set max_npoint_for_channel 0
> import model sm
> define p = g u c d s u c d s
> define j = g u c d s u c d s
> define l+ = e+ mu+
> define l- = e- mu-
> define vl = ve vm vt
> define vl = ve vm vt
> launch output_UFO_all_mq_maddm
> Traceback (most recent call last):
> File "/workarea/MG5_aMC_v2_8_1/madgraph/interface/extended_cmd.py", line 1541, in onecmd
> return self.onecmd_orig(line, **opt)
> File "/workarea/MG5_aMC_v2_8_1/madgraph/interface/extended_cmd.py", line 1490, in onecmd_orig
> return func(arg, **opt)
> File "/workarea/MG5_aMC_v2_8_1/PLUGIN/maddm/maddm_interface.py", line 752, in do_launch
> self._MDM.exec_cmd('launch ' + line.replace(args[1], ''))
> File "/workarea/MG5_aMC_v2_8_1/madgraph/interface/extended_c...

Revision history for this message
Olivier Mattelaer (olivier-mattelaer) wrote :
Download full text (23.2 KiB)

Here they are:

import model UFO_all_mq
generate relic_density
output
launch
https://protect-au.mimecast.com/s/omUkCxngwOfnELmEcwBRyx?domain=bugs.launchpad.net <https://protect-au.mimecast.com/s/omUkCxngwOfnELmEcwBRyx?domain=bugs.launchpad.net>

Cheers,

Olivier

> On 16 Oct 2020, at 09:34, Shyam Balaji <email address hidden> wrote:
>
> Hi Olivier,
>
> Could you please share the commands you used to generate the output
> directory?
>
> Regards,
>
> Shyam
> ________________________________
> From: <email address hidden> <mailto:<email address hidden>> <<email address hidden> <mailto:<email address hidden>>> on behalf of Olivier Mattelaer <<email address hidden> <mailto:<email address hidden>>>
> Sent: 16 October 2020 17:49
> To: Shyam Balaji <<email address hidden> <mailto:<email address hidden>>>
> Subject: Re: [Bug 1900089] [NEW] Bugs when trying specific coupling mass combinations in t-channel DM model
>
> Hi,
>
> I did not face such issue.
> Are you doing only relic density?
>
> The best might be to recreate an output directory and relaunch.
>
> This being said, I have a couple of serrious warning when running with yourr param_card
> that some parameter of the param_card are not recognised and/or missing.
>
> Cheers,
>
> Olivier
>
>> On 16 Oct 2020, at 07:27, Shyam Balaji <email address hidden> wrote:
>>
>> Public bug reported:
>>
>> Hi Olivier,
>>
>> We are trying to once again generate limits for the DM model given in
>> https://protect-au.mimecast.com/s/MVL_Cr81nytPQrwQT78NwY?domain=feynrules.irmp.ucl.ac.be <https://protect-au.mimecast.com/s/MVL_Cr81nytPQrwQT78NwY?domain=feynrules.irmp.ucl.ac.be> from UFO_all_mq.zip,
>> however we get the following error when trying to proceed with the
>> attached param_card.dat, we get the following bug. Would appreciate any
>> help!
>>
>> Command "launch output_UFO_all_mq_maddm" interrupted with error:
>> IOError : [Errno 2] No such file or directory: '/workarea/MG5_aMC_v2_8_1/output_UFO_all_mq_maddm/output/run_16/maddm.out'
>> Please report this bug on https://protect-au.mimecast.com/s/RM5yCvl1rKipwEOwHXRI9X?domain=bugs.launchpad.net <https://protect-au.mimecast.com/s/RM5yCvl1rKipwEOwHXRI9X?domain=bugs.launchpad.net>
>> More information is found in 'MG5_debug'.
>> Please attach this file to your report.
>>
>> This is the debug file content
>>
>> #************************************************************
>> # MadGraph5_aMC@NLO
>> #
>> #
>> #
>> # 5
>> #
>> #
>> #
>> #
>> # VERSION 2.8.1 2020-09-28
>> #
>> # The MadGraph5_aMC@NLO Development Team - Find us at
>> # https://protect-au.mimecast.com/s/keFvCwV1vMfJlv0lh9KH04?domain=server06.fynu.ucl.ac.be <https://protect-au.mimecast.com/s/keFvCwV1vMfJlv0lh9KH04?domain=server06.fynu.ucl.ac.be>
>> #
>> #************************************************************
>> #
>> # Command File for MadGraph5_aMC@NLO
>> #
>> # run as ./bin/mg5_aMC filename
>> #
>> #************************************************************
>> set group_subprocesses Auto
>> set ignore_six_quark_processes False
>> set max_t_for_channel 99
>> set loop_optimized_output True
>> set low_mem_multicore_nlo_generation False
>> set default_unset_co...

Revision history for this message
Shyam Balaji (shyambalaji) wrote :
Download full text (29.4 KiB)

Hi Olivier,

OK, I think the way you are running it is slightly different to what we are doing, which is why you are getting no errors, we wanted to run the same commands we ran in the last bug report with the attached param card in this thread i.e. with only specific co-annihilators turned on, so to be specific

import UFO_all_mq
define darkmatter xd
define coannihilator 1000001 1000002 1000003 1000004 1000005 1000006 2000001 2000002 2000003 2000004 2000005 2000006 --usepdg
generate relic_density
generate direct_detection
output output_UFO_all_mq_maddm

Could you please try this and let me know how you go?

Regards,

Shyam

________________________________
From: <email address hidden> <email address hidden> on behalf of Olivier Mattelaer <email address hidden>
Sent: 16 October 2020 18:42
To: Shyam Balaji <email address hidden>
Subject: Re: [Bug 1900089] [NEW] Bugs when trying specific coupling mass combinations in t-channel DM model

Here they are:

import model UFO_all_mq
generate relic_density
output
launch
https://protect-au.mimecast.com/s/wO6UC6XQ4LfjLZLvUpHAeh?domain=bugs.launchpad.net <https://protect-au.mimecast.com/s/wO6UC6XQ4LfjLZLvUpHAeh?domain=bugs.launchpad.net>

Cheers,

Olivier

> On 16 Oct 2020, at 09:34, Shyam Balaji <email address hidden> wrote:
>
> Hi Olivier,
>
> Could you please share the commands you used to generate the output
> directory?
>
> Regards,
>
> Shyam
> ________________________________
> From: <email address hidden> <mailto:<email address hidden>> <<email address hidden> <mailto:<email address hidden>>> on behalf of Olivier Mattelaer <<email address hidden> <mailto:<email address hidden>>>
> Sent: 16 October 2020 17:49
> To: Shyam Balaji <<email address hidden> <mailto:<email address hidden>>>
> Subject: Re: [Bug 1900089] [NEW] Bugs when trying specific coupling mass combinations in t-channel DM model
>
> Hi,
>
> I did not face such issue.
> Are you doing only relic density?
>
> The best might be to recreate an output directory and relaunch.
>
> This being said, I have a couple of serrious warning when running with yourr param_card
> that some parameter of the param_card are not recognised and/or missing.
>
> Cheers,
>
> Olivier
>
>> On 16 Oct 2020, at 07:27, Shyam Balaji <email address hidden> wrote:
>>
>> Public bug reported:
>>
>> Hi Olivier,
>>
>> We are trying to once again generate limits for the DM model given in
>> https://protect-au.mimecast.com/s/FntOC71R2NT4GnGKfWvKHV?domain=feynrules.irmp.ucl.ac.be <https://protect-au.mimecast.com/s/FntOC71R2NT4GnGKfWvKHV?domain=feynrules.irmp.ucl.ac.be> from UFO_all_mq.zip,
>> however we get the following error when trying to proceed with the
>> attached param_card.dat, we get the following bug. Would appreciate any
>> help!
>>
>> Command "launch output_UFO_all_mq_maddm" interrupted with error:
>> IOError : [Errno 2] No such file or directory: '/workarea/MG5_aMC_v2_8_1/output_UFO_all_mq_maddm/output/run_16/maddm.out'
>> Please report this bug on https://protect-au.mimecast.com/s/AH1fC81V0PTDNBN0u2bIG3?domain=bugs.launchpad.net <https://protect-au.mimecast.com/s/AH1fC81V0PTDNBN0u2bIG3?domain=bugs.launchpad.net>
>> More informat...

Revision history for this message
Shyam Balaji (shyambalaji) wrote :

Hi Olivier,

Just wondering if you received my above response? I think the way you are running it is slightly different to what we are doing, which is why you are getting no errors, we wanted to run the same commands we ran in the last bug report with the attached param card in this thread i.e. with only specific co-annihilators turned on, so to be specific

import UFO_all_mq
define darkmatter xd
define coannihilator 1000001 1000002 1000003 1000004 1000005 1000006 2000001 2000002 2000003 2000004 2000005 2000006 --usepdg
generate relic_density
generate direct_detection
output output_UFO_all_mq_maddm

Could you please try this and let me know how you go?

Regards,

Shyam

Revision history for this message
Olivier Mattelaer (olivier-mattelaer) wrote :
Download full text (36.3 KiB)

I have no crash at all with that syntax (but it takes hours to generate so do not expect fast answer for such process).

For directional detection, i have the following:

WARNING: Dark matter mass value 0.5 is outside the range of SD limit
INFO:
***** Direct detection [cm^2]:
INFO: SigmaN_SI_p All DM = 1.21e-34 ALLOWED Xenon1ton ul = inf
INFO: SigmaN_SI_n All DM = 1.21e-34 ALLOWED Xenon1ton ul = inf
INFO: SigmaN_SD_p All DM = 4.39e-36 ALLOWED Pico60 ul = inf
INFO: SigmaN_SD_n All DM = 4.38e-36 ALLOWED Lux2017 ul = inf
INFO: Results written in: /Users/omattelaer/Documents/workspace/2.8.2.py2/output_UFO_all_mq_maddm/output/run_01/MadDM_results.txt

What surprise me, is that relic detection is not run at all in this mode.
and if I want to rerun that directory it does not allow me to run relic density.

But no i do not reproduce your issue.

Cheers,

Olivier

> On 19 Oct 2020, at 06:26, Shyam Balaji <email address hidden> wrote:
>
> Hi Olivier,
>
> OK, I think the way you are running it is slightly different to what we
> are doing, which is why you are getting no errors, we wanted to run the
> same commands we ran in the last bug report with the attached param card
> in this thread i.e. with only specific co-annihilators turned on, so to
> be specific
>
> import UFO_all_mq
> define darkmatter xd
> define coannihilator 1000001 1000002 1000003 1000004 1000005 1000006 2000001 2000002 2000003 2000004 2000005 2000006 --usepdg
> generate relic_density
> generate direct_detection
> output output_UFO_all_mq_maddm
>
> Could you please try this and let me know how you go?
>
> Regards,
>
> Shyam
>
> ________________________________
> From: <email address hidden> <email address hidden> on behalf of Olivier Mattelaer <email address hidden>
> Sent: 16 October 2020 18:42
> To: Shyam Balaji <email address hidden>
> Subject: Re: [Bug 1900089] [NEW] Bugs when trying specific coupling mass combinations in t-channel DM model
>
> Here they are:
>
> import model UFO_all_mq
> generate relic_density
> output
> launch
> https://protect-au.mimecast.com/s/wO6UC6XQ4LfjLZLvUpHAeh?domain=bugs.launchpad.net <https://protect-au.mimecast.com/s/wO6UC6XQ4LfjLZLvUpHAeh?domain=bugs.launchpad.net>
>
> Cheers,
>
> Olivier
>
>
>> On 16 Oct 2020, at 09:34, Shyam Balaji <email address hidden> wrote:
>>
>> Hi Olivier,
>>
>> Could you please share the commands you used to generate the output
>> directory?
>>
>> Regards,
>>
>> Shyam
>> ________________________________
>> From: <email address hidden> <mailto:<email address hidden>> <<email address hidden> <mailto:<email address hidden>>> on behalf of Olivier Mattelaer <<email address hidden> <mailto:<email address hidden>>>
>> Sent: 16 October 2020 17:49
>> To: Shyam Balaji <<email address hidden> <mailto:<email address hidden>>>
>> Subject: Re: [Bug 1900089] [NEW] Bugs when trying specific coupling mass combinations in t-channel DM model
>>
>> Hi,
>>
>> I did not face such issue.
>> Are you doing only relic density?
>>
>> The best might be to recreate an output directory and relaunch.
>>
>> This ...

Revision history for this message
Olivier Mattelaer (olivier-mattelaer) wrote :
Download full text (37.6 KiB)

Hi,

I have re-run relic density alone and that one crashed:

INFO: compilation done
At line 263 of file init.f
Fortran runtime error: Index '2501' of dimension 1 of array 'betas' above upper bound of 2500

This is likely due to too many resonances in your model or too much structure in your model.

Cheers,

Olivier

PS: Can you avoid to modify the httml link of the email when you reply this trigger a lot of issue on my side.

> On 20 Oct 2020, at 08:56, Olivier Mattelaer <email address hidden> wrote:
>
> I have no crash at all with that syntax (but it takes hours to generate so do not expect fast answer for such process).
>
> For directional detection, i have the following:
>
> WARNING: Dark matter mass value 0.5 is outside the range of SD limit
> INFO:
> ***** Direct detection [cm^2]:
> INFO: SigmaN_SI_p All DM = 1.21e-34 ALLOWED Xenon1ton ul = inf
> INFO: SigmaN_SI_n All DM = 1.21e-34 ALLOWED Xenon1ton ul = inf
> INFO: SigmaN_SD_p All DM = 4.39e-36 ALLOWED Pico60 ul = inf
> INFO: SigmaN_SD_n All DM = 4.38e-36 ALLOWED Lux2017 ul = inf
> INFO: Results written in: /Users/omattelaer/Documents/workspace/2.8.2.py2/output_UFO_all_mq_maddm/output/run_01/MadDM_results.txt
>
> What surprise me, is that relic detection is not run at all in this mode.
> and if I want to rerun that directory it does not allow me to run relic density.
>
> But no i do not reproduce your issue.
>
> Cheers,
>
> Olivier
>
>
>> On 19 Oct 2020, at 06:26, Shyam Balaji <email address hidden> wrote:
>>
>> Hi Olivier,
>>
>> OK, I think the way you are running it is slightly different to what we
>> are doing, which is why you are getting no errors, we wanted to run the
>> same commands we ran in the last bug report with the attached param card
>> in this thread i.e. with only specific co-annihilators turned on, so to
>> be specific
>>
>> import UFO_all_mq
>> define darkmatter xd
>> define coannihilator 1000001 1000002 1000003 1000004 1000005 1000006 2000001 2000002 2000003 2000004 2000005 2000006 --usepdg
>> generate relic_density
>> generate direct_detection
>> output output_UFO_all_mq_maddm
>>
>> Could you please try this and let me know how you go?
>>
>> Regards,
>>
>> Shyam
>>
>> ________________________________
>> From: <email address hidden> <email address hidden> on behalf of Olivier Mattelaer <email address hidden>
>> Sent: 16 October 2020 18:42
>> To: Shyam Balaji <email address hidden>
>> Subject: Re: [Bug 1900089] [NEW] Bugs when trying specific coupling mass combinations in t-channel DM model
>>
>> Here they are:
>>
>> import model UFO_all_mq
>> generate relic_density
>> output
>> launch
>> https://protect-au.mimecast.com/s/wO6UC6XQ4LfjLZLvUpHAeh?domain=bugs.launchpad.net <https://protect-au.mimecast.com/s/wO6UC6XQ4LfjLZLvUpHAeh?domain=bugs.launchpad.net>
>>
>> Cheers,
>>
>> Olivier
>>
>>
>>> On 16 Oct 2020, at 09:34, Shyam Balaji <email address hidden> wrote:
>>>
>>> Hi Olivier,
>>>
>>> Could you please share the commands you used to generate the output
>>> directory?
>>>
>>> Regards,
>>>
>>> Shyam
>>> _____________________...

Revision history for this message
Shyam Balaji (shyambalaji) wrote :
Download full text (43.6 KiB)

Thanks Olivier, our setup runs as yours now. However we do indeed have 6 resonances because we have 6 coloured mediators that couple to each flavour of u and d quark as per the param card. This is a feature of our model. Have you got any ideas how we can by pass this problem with the relic density in MG?

Maybe the error we are getting is due too many unwanted particles such as other DM candidates e.g. xm, xv etc. We don't know how to turn these off though, so we just made them very heavy e.g 1e09.

Regards,

Shyam

________________________________
From: <email address hidden> <email address hidden> on behalf of Olivier Mattelaer <email address hidden>
Sent: 21 October 2020 06:30
To: Shyam Balaji <email address hidden>
Subject: Re: [Bug 1900089] [NEW] Bugs when trying specific coupling mass combinations in t-channel DM model

Hi,

I have re-run relic density alone and that one crashed:

INFO: compilation done
At line 263 of file init.f
Fortran runtime error: Index '2501' of dimension 1 of array 'betas' above upper bound of 2500

This is likely due to too many resonances in your model or too much
structure in your model.

Cheers,

Olivier

PS: Can you avoid to modify the httml link of the email when you reply
this trigger a lot of issue on my side.

> On 20 Oct 2020, at 08:56, Olivier Mattelaer <email address hidden> wrote:
>
> I have no crash at all with that syntax (but it takes hours to generate so do not expect fast answer for such process).
>
> For directional detection, i have the following:
>
> WARNING: Dark matter mass value 0.5 is outside the range of SD limit
> INFO:
> ***** Direct detection [cm^2]:
> INFO: SigmaN_SI_p All DM = 1.21e-34 ALLOWED Xenon1ton ul = inf
> INFO: SigmaN_SI_n All DM = 1.21e-34 ALLOWED Xenon1ton ul = inf
> INFO: SigmaN_SD_p All DM = 4.39e-36 ALLOWED Pico60 ul = inf
> INFO: SigmaN_SD_n All DM = 4.38e-36 ALLOWED Lux2017 ul = inf
> INFO: Results written in: /Users/omattelaer/Documents/workspace/2.8.2.py2/output_UFO_all_mq_maddm/output/run_01/MadDM_results.txt
>
> What surprise me, is that relic detection is not run at all in this mode.
> and if I want to rerun that directory it does not allow me to run relic density.
>
> But no i do not reproduce your issue.
>
> Cheers,
>
> Olivier
>
>
>> On 19 Oct 2020, at 06:26, Shyam Balaji <email address hidden> wrote:
>>
>> Hi Olivier,
>>
>> OK, I think the way you are running it is slightly different to what we
>> are doing, which is why you are getting no errors, we wanted to run the
>> same commands we ran in the last bug report with the attached param card
>> in this thread i.e. with only specific co-annihilators turned on, so to
>> be specific
>>
>> import UFO_all_mq
>> define darkmatter xd
>> define coannihilator 1000001 1000002 1000003 1000004 1000005 1000006 2000001 2000002 2000003 2000004 2000005 2000006 --usepdg
>> generate relic_density
>> generate direct_detection
>> output output_UFO_all_mq_maddm
>>
>> Could you please try this and let me know how you go?
>>
>> Regards,
>>
>> Shyam
>>
>> ________________________________
>> From: bounces@canon...

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

If this is only a problem of the number of resonances, then changing the file maddm.inc
and modify the line
parameter (fitsize=2500)
to
parameter (fitsize=25000)

should fix the issue. If the problem is deeper than that, then this is likely months of work.

Cheers,

Olivier

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.