W polarization in Madevent/Madspin
I am are running a Madgraph ( MG5_aMC_v2_2_1 ) event production for the process is pp > W+W+j j QED=4 QCD=0 followed by Madspin for W > lv decay.
I noticed that while the W polarity information is present in the LHE file before the decay , the LHE containing the decays is missing this info !
All W’s in this LHE have a 0 in the LHE field for the polarity…
Is there a physical reason why this information is not present in the LHE file generated after Madspin decay ?
Thanks,
Andre
Question information
- Language:
- English Edit question
- Status:
- Answered
- Assignee:
- No assignee Edit question
- Last query:
- Last reply:
Revision history for this message
|
#1 |
Hi Andre,
A decayed particle (especially with full spin-correlation) can not be associate to a given helicity state. So the quantity can not be exact.
Now with a bunch of approximation, you should be able to provide a naive guess of the polarization of such particle.
(basically you create the density matrix and neglect the off diagonal term and select randomly the polarization according to the relative importance of the diagonal term).
This is not done in MadSpin for a couple of reasons.
1) We did not consider it.
2) We focus on having full spin-correlation (i.e. we want to keep off-diagonal term for the density matrix) and include those number are opposite to the philosophy of the code.
3) Adding this information requires additional book-keeping/
Cheers,
Olivier
On Nov 17, 2014, at 11:36 PM, Andre Sznajder <email address hidden> wrote:
> New question #257782 on MadGraph5_aMC@NLO:
> https:/
>
> I am are running a Madgraph ( MG5_aMC_v2_2_1 ) event production for the process is pp > W+W+j j QED=4 QCD=0 followed by Madspin for W > lv decay.
> I noticed that while the W polarity information is present in the LHE file before the decay , the LHE containing the decays is missing this info !
> All W’s in this LHE have a 0 in the LHE field for the polarity…
> Is there a physical reason why this information is not present in the LHE file generated after Madspin decay ?
> Thanks,
> Andre
>
> --
> You received this question notification because you are an answer
> contact for MadGraph5_aMC@NLO.
Revision history for this message
|
#2 |
Hi Olivier,
Is there a simple way to implement this approximation you mentioned to get a naive guess of the polarization as you say.
Would this be equivalent to use the polarization of the W's in the LHE before the decay ?
Cheers,
Andre
Revision history for this message
|
#3 |
Hi Andre,
The approximation that I point above is everything but simple to implement.
Indeed a even more naive approach (and simpler to implement) would be so use to use the polarization of the W’s in the LHE before the decay.
If that information is not present in the file, MadSpin is able to re-assign a polarization to a given event.
In the limit where the width is zero, those method should be equivalent.
Cheers,
Olivier
On Nov 19, 2014, at 1:01 AM, Andre Sznajder <email address hidden> wrote:
> Question #257782 on MadGraph5_aMC@NLO changed:
> https:/
>
> Status: Answered => Open
>
> Andre Sznajder is still having a problem:
> Hi Olivier,
> Is there a simple way to implement this approximation you mentioned to get a naive guess of the polarization as you say.
> Would this be equivalent to use the polarization of the W's in the LHE before the decay ?
> Cheers,
> Andre
>
> --
> You received this question notification because you are an answer
> contact for MadGraph5_aMC@NLO.
Revision history for this message
|
#4 |
Hi Olivier,
Is there a simple way to implement this approximation you mentioned to get a naive guess of the polarization as you say.
Would this be equivalent to use the polarization of the W's in the LHE before the decay ?
Cheers,
Andre
Revision history for this message
|
#5 |
This question was expired because it remained in the 'Open' state without activity for the last 15 days.
Revision history for this message
|
#6 |
Hi Olivier,
We have are identifying the event polarization by looking at the W polarization before the decay.
Somehow the distributions for the LL , LT and TT WW polarization modes don't make much sense !
The W polarizations present in the LHE before the decay doesn't seems to correlate with the polarization after the decay...
Is it possible that Madspin is ignoring the the W's polarization present in the LHE before the decay and is setting a new polarization for the W's when it decays them ?
I am using Madgraph v5.2.2.2.
Cheers,
Andre
Revision history for this message
|
#7 |
Hi Andre,
> Is it possible that Madspin is ignoring the the W's polarization present in the LHE before the decay and is setting a new polarization for the W's when it decays them ?
Indeed the polarization of the W is completely ignored by MadSpin.
MadSpin do not reassign a new value to the W, the polarization of the W is just not part of the computation (since we use the full matrix element with off-shell W).
> The W polarizations present in the LHE before the decay doesn't seems to correlate with the polarization after the decay...
That's really interesting. Thanks for sharing your finding with me. I was really curious to know how much of the initial spin value was kept due to the correlation with the momenta of the W. Thanks for giving me the answer to this interesting question.
Cheers,
Olivier
Revision history for this message
|
#8 |
Hi Olivier,
This brings me back to the original question that initiated this thread !
If the undecayed W polarization is ignored by Madspin , how can I "identify" in an approximate way if the WW polarization mode is of the type LL , LT or TT ?
In the past we used to Madgraph v4 we used to hack the matrix element ( matrix.f )of the process by hand remove the polarizations.
But now in Madgraph v5 this doesn't work anymore ...
Any suggestions ?
Cheers,
Andre
Revision history for this message
|
#9 |
Hi,
Why can’t you use the same method as in MG4?
Cheers,
Olivier
On 21 Mar 2015, at 22:06, Andre Sznajder <email address hidden> wrote:
> Question #257782 on MadGraph5_aMC@NLO changed:
> https:/
>
> Status: Answered => Open
>
> Andre Sznajder is still having a problem:
> Hi Olivier,
> This brings me back to the original question that initiated this thread !
> If the undecayed W polarization is ignored by Madspin , how can I "identify" in an approximate way if the WW polarization mode is of the type LL , LT or TT ?
> In the past we used to Madgraph v4 we used to hack the matrix element ( matrix.f )of the process by hand remove the polarizations.
> But now in Madgraph v5 this doesn't work anymore ...
> Any suggestions ?
> Cheers,
> Andre
>
> --
> You received this question notification because you are an answer
> contact for MadGraph5_aMC@NLO.
Revision history for this message
|
#10 |
Hi Olivier,
In Madgraph v4 we used Decay , which is not available anymore. If I understood correctly Madspin will ignore the W polarization so if I generate a sample with WW polarized in the mode LL when Madspin decays it we will obtain all 3 modes ...
Besides, we tried and it took forever to generate events , so we thought in Madgraph v5 this recipe has generation efficiency problems in the new version.
Cheers,
Andre
> On Mar 21, 2015, at 11:21 AM, Olivier Mattelaer <email address hidden> wrote:
>
> Your question #257782 on MadGraph5_aMC@NLO changed:
> https:/
>
> Status: Open => Answered
>
> Olivier Mattelaer proposed the following answer:
> Hi,
>
> Why can’t you use the same method as in MG4?
>
> Cheers,
>
> Olivier
>
> On 21 Mar 2015, at 22:06, Andre Sznajder
> <email address hidden> wrote:
>
>> Question #257782 on MadGraph5_aMC@NLO changed:
>> https:/
>>
>> Status: Answered => Open
>>
>> Andre Sznajder is still having a problem:
>> Hi Olivier,
>> This brings me back to the original question that initiated this thread !
>> If the undecayed W polarization is ignored by Madspin , how can I "identify" in an approximate way if the WW polarization mode is of the type LL , LT or TT ?
>> In the past we used to Madgraph v4 we used to hack the matrix element ( matrix.f )of the process by hand remove the polarizations.
>> But now in Madgraph v5 this doesn't work anymore ...
>> Any suggestions ?
>> Cheers,
>> Andre
>>
>> --
>> You received this question notification because you are an answer
>> contact for MadGraph5_aMC@NLO.
>
> --
> If this answers your question, please go to the following page to let us
> know that it is solved:
> https:/
>
> If you still need help, you can reply to this email or go to the
> following page to enter your feedback:
> https:/
>
> You received this question notification because you asked the question.
=======
Andre Sznajder
Professor Associado
Instituto de Fisica - Dept. DFNAE
Universidade do Estado do Rio de Janeiro ( UERJ )
Rio de Janeiro, RJ - Brasil
Tel.: (+55)(21)23340608 ramal:24 Fax: (+55)(21)23340483
Email: <email address hidden>
=======
Revision history for this message
|
#11 |
Hi Andre,
> In Madgraph v4 we used Decay , which is not available anymore.
You can download it via this tar ball:
https:/
Pointless to say that this code is not maintained anymore.
> If I understood correctly Madspin will ignore the W polarisation so if I generate a sample with WW polarized in the mode LL when Madspin decays it we will obtain all 3 modes ...
That’s the price to pay in order to have the full/real spin-correlation effect.
> Besides, we tried and it took forever to generate events , so we thought in Madgraph v5 this recipe has generation efficiency problems in the new version.
Will need more information in order to comment on that point.
Cheers,
Olivier
On 21 Mar 2015, at 23:46, Andre Sznajder <email address hidden> wrote:
> Question #257782 on MadGraph5_aMC@NLO changed:
> https:/
>
> Status: Answered => Open
>
> Andre Sznajder is still having a problem:
> Hi Olivier,
> In Madgraph v4 we used Decay , which is not available anymore. If I understood correctly Madspin will ignore the W polarization so if I generate a sample with WW polarized in the mode LL when Madspin decays it we will obtain all 3 modes ...
> Besides, we tried and it took forever to generate events , so we thought in Madgraph v5 this recipe has generation efficiency problems in the new version.
> Cheers,
> Andre
>
>> On Mar 21, 2015, at 11:21 AM, Olivier Mattelaer <email address hidden> wrote:
>>
>> Your question #257782 on MadGraph5_aMC@NLO changed:
>> https:/
>>
>> Status: Open => Answered
>>
>> Olivier Mattelaer proposed the following answer:
>> Hi,
>>
>> Why can’t you use the same method as in MG4?
>>
>> Cheers,
>>
>> Olivier
>>
>> On 21 Mar 2015, at 22:06, Andre Sznajder
>> <email address hidden> wrote:
>>
>>> Question #257782 on MadGraph5_aMC@NLO changed:
>>> https:/
>>>
>>> Status: Answered => Open
>>>
>>> Andre Sznajder is still having a problem:
>>> Hi Olivier,
>>> This brings me back to the original question that initiated this thread !
>>> If the undecayed W polarization is ignored by Madspin , how can I "identify" in an approximate way if the WW polarization mode is of the type LL , LT or TT ?
>>> In the past we used to Madgraph v4 we used to hack the matrix element ( matrix.f )of the process by hand remove the polarizations.
>>> But now in Madgraph v5 this doesn't work anymore ...
>>> Any suggestions ?
>>> Cheers,
>>> Andre
>>>
>>> --
>>> You received this question notification because you are an answer
>>> contact for MadGraph5_aMC@NLO.
>>
>> --
>> If this answers your question, please go to the following page to let us
>> know that it is solved:
>> https:/
>>
>> If you still need help, you can reply to this email or go to the
>> following page to enter your feedback:
>> https:/
>>
>> You received this question notification because you asked the question.
>
> =======
> Andre Sznajder
> Professor Associado
> Instituto de Fisica - Dept. DFNAE
> Universidade do Estado do Rio de Janeiro ( UERJ )
> Rio de Janeiro, RJ - Brasil
> Tel.: (+55)(21)23340608 ramal:24 Fax: (+55)(21)23340483
> Email: <email address hidden>
> =======
>
> --
> You received this question notification because you are an answer
> contact for MadGraph5_aMC@NLO.
Revision history for this message
|
#12 |
Hi Olivier,
If I want to use the current Madgraph version , is there a way to turn off Madspin correlation and tell it to use the the original W polarization information as Decay does ?
That would be a very useful feature for all WW scattering sensitivity studies we need to perform.
Cheers,
Andre
Revision history for this message
|
#13 |
Hi Andre,
> If I want to use the current Madgraph version
Just to be clear, I was just suggesting to take the DECAY directory from the old version.
> , is there a way to turn off Madspin correlation and tell it to use the the original W polarization information as Decay does ?
I have develop a code which was, up to my understanding a version of DECAY for the latest version of MG5.
But it is not clear if this is actually the case or not. We have a meeting this week and it will be more clear after that if my implementation
is or not what DECAY does.
Cheers,
Olivier
On 22 Mar 2015, at 21:01, Andre Sznajder <email address hidden> wrote:
> Question #257782 on MadGraph5_aMC@NLO changed:
> https:/
>
> Status: Answered => Open
>
> Andre Sznajder is still having a problem:
> Hi Olivier,
> If I want to use the current Madgraph version , is there a way to turn off Madspin correlation and tell it to use the the original W polarization information as Decay does ?
> That would be a very useful feature for all WW scattering sensitivity studies we need to perform.
> Cheers,
> Andre
>
> --
> You received this question notification because you are an answer
> contact for MadGraph5_aMC@NLO.
Revision history for this message
|
#14 |
Hi Andre,
So i discuss with Fabio to understand how DECAYS was working and this is indeed more accurate that the simple stuff that I did.
So we will not have that option in a near future.
Cheers,
Olivier
Revision history for this message
|
#15 |
Hi Olivier,
Ok, I will try to the DECAY code from the older version of Madgraph5 that you pointed to me.
Meanwhile I tried made the changes in matrix*.f files for having a single polarization and now I am having a strange compilation error.
When I test the changes running interactively I works fine but when I submit it batch using condor I get the following error:
>Generating 10000 events with run name run_01
survey run_01
INFO: compile directory
Not able to open file /storage/
ured.Please set one in ./input/
Using random number seed offset = 21
INFO: Running Survey
Creating Jobs
Working on SubProcesses
P1_qq_wpwpqq
Error detected in "generate_events "
write debug file /storage/
If you need help with this issue please contact us on https:/
MadGraph5Error : A compilation Error occurs when trying to compile /storage/
CD0/SubProcesse
The compilation fails with the following output message:
gfortran -O -w -fbounds-check -fPIC -ffixed-
gfortran -O -w -fbounds-check -fPIC -ffixed-
weight.o initcluster.o addmothers.o setscales.o idenparts.o auto_dsig.o auto_dsig1.o auto_dsig2.o auto_dsig3.o auto_dsig4.o auto_dsig5.o auto_dsig6.o auto_dsig7.
o matrix1.o matrix2.o matrix3.o matrix4.o matrix5.o matrix6.o matrix7.o -L../../lib/ -ldhelas -ldsample -lmodel -lgeneric -lpdf -lcernlib
/usr/
(.text+0x20): undefined reference to `main'
collect2: error: ld returned 1 exit status
make: *** [madevent] Error 1
Please try to fix this compilations issue and retry.
Help might be found at https:/
If you think that this is a bug, you can report this at https:/
quit
Do you see what could be going wrong ?
I have been submitting jobs in batch for ages and never had this problem. I has something to do with the mods I made to matrix*.f but I can figure out why it runs fine iteractively and not in batch …
Cheers,
Andre
On Mar 23, 2015, at 11:31 AM, Olivier Mattelaer <<email address hidden>
Your question #257782 on MadGraph5_aMC@NLO changed:
https:/
Olivier Mattelaer proposed the following answer:
Hi Andre,
So i discuss with Fabio to understand how DECAYS was working and this is indeed more accurate that the simple stuff that I did.
So we will not have that option in a near future.
Cheers,
Olivier
--
If this answers your question, please go to the following page to let us
know that it is solved:
https:/
If you still need help, you can reply to this email or go to the
following page to enter your feedback:
https:/
You received this question notification because you asked the question.
=======
Andre Sznajder
Professor Associado
Instituto de Fisica - Dept. DFNAE
Universidade do Estado do Rio de Janeiro ( UERJ )
Rio de Janeiro, RJ - Brasil
Tel.: (+55)(21)23340608 ramal:24 Fax: (+55)(21)23340483
Email: <email address hidden>
=======
Revision history for this message
|
#16 |
Hi,
Looks like a compilation error.
So this should not be related to the cluster mode.
Can you double check that you succeed to compile the code.
Cheers,
Olivier
On 24 Mar 2015, at 18:11, Andre Sznajder <email address hidden> wrote:
> Question #257782 on MadGraph5_aMC@NLO changed:
> https:/
>
> Status: Answered => Open
>
> Andre Sznajder is still having a problem:
> Hi Olivier,
> Ok, I will try to the DECAY code from the older version of Madgraph5 that you pointed to me.
> Meanwhile I tried made the changes in matrix*.f files for having a single polarization and now I am having a strange compilation error.
> When I test the changes running interactively I works fine but when I submit it batch using condor I get the following error:
>
>> Generating 10000 events with run name run_01
> survey run_01
> INFO: compile directory
> Not able to open file /storage/
> ured.Please set one in ./input/
> Using random number seed offset = 21
> INFO: Running Survey
> Creating Jobs
> Working on SubProcesses
> P1_qq_wpwpqq
> Error detected in "generate_events "
> write debug file /storage/
> If you need help with this issue please contact us on https:/
> MadGraph5Error : A compilation Error occurs when trying to compile /storage/
> CD0/SubProcesse
> The compilation fails with the following output message:
> gfortran -O -w -fbounds-check -fPIC -ffixed-
> gfortran -O -w -fbounds-check -fPIC -ffixed-
> weight.o initcluster.o addmothers.o setscales.o idenparts.o auto_dsig.o auto_dsig1.o auto_dsig2.o auto_dsig3.o auto_dsig4.o auto_dsig5.o auto_dsig6.o auto_dsig7.
> o matrix1.o matrix2.o matrix3.o matrix4.o matrix5.o matrix6.o matrix7.o -L../../lib/ -ldhelas -ldsample -lmodel -lgeneric -lpdf -lcernlib
> /usr/lib/
> (.text+0x20): undefined reference to `main'
> collect2: error: ld returned 1 exit status
> make: *** [madevent] Error 1
>
> Please try to fix this compilations issue and retry.
> Help might be found at https:/
> If you think that this is a bug, you can report this at https:/
> quit
>
>
> Do you see what could be going wrong ?
> I have been submitting jobs in batch for ages and never had this problem. I has something to do with the mods I made to matrix*.f but I can figure out why it runs fine iteractively and not in batch …
> Cheers,
> Andre
>
>
> On Mar 23, 2015, at 11:31 AM, Olivier Mattelaer
> <<email address hidden>
> wrote:
>
> Your question #257782 on MadGraph5_aMC@NLO changed:
> https:/
>
> Olivier Mattelaer proposed the following answer:
> Hi Andre,
>
> So i discuss with Fabio to understand how DECAYS was working and this is indeed more accurate that the simple stuff that I did.
> So we will not have that option in a near future.
>
> Cheers,
>
> Olivier
>
> --
> If this answers your question, please go to the following page to let us
> know that it is solved:
> https:/
>
> If you still need help, you can reply to this email or go to the
> following page to enter your feedback:
> https:/
>
> You received this question notification because you asked the question.
>
> =======
> Andre Sznajder
> Professor Associado
> Instituto de Fisica - Dept. DFNAE
> Universidade do Estado do Rio de Janeiro ( UERJ )
> Rio de Janeiro, RJ - Brasil
> Tel.: (+55)(21)23340608 ramal:24 Fax: (+55)(21)23340483
> Email: <email address hidden>
> =======
>
> --
> You received this question notification because you are an answer
> contact for MadGraph5_aMC@NLO.
Revision history for this message
|
#17 |
Hi Olivier,
I found my mistake and now the Madevent runs fine, but when it comes to run DECAY I am having the error bellow.
Would it be possible that DECAY doesn’t know how to read the parameter info from the LHE created by MG 5.2.2.3 ?
Cheers,
Andre
[sznajder@cmslpc27 DECAY]$ ./decay
******
* DECAY *
* a MadEvent program *
* for decaying unstable particles *
* in the Standar Model *
* -------
* version compliant with MG_ME_V4.0 *
* *
* 27-July-2006 *
******
Input run mode:
---------------
0 = calculates decay widths
1 = decay events in file
1
******
* reading seed from iseed.dat *
* rnd number seed = -13 *
******
******
* run_mode=1 => decaying events *
* *
* Using the param_card.dat in the banner for *
* the input params. *
* *
* >>>>>>Total widths are recalculated here<<<<< *
******
input event file: (e.g. events.lhe)
unweighted_
name for output file: (e.g. dec-events.lhe)
unweighted_
At line 484 of file decay_couplings.f
Fortran runtime error: End of file
> On Mar 24, 2015, at 7:01 AM, Olivier Mattelaer <email address hidden> wrote:
>
> Your question #257782 on MadGraph5_aMC@NLO changed:
> https:/
>
> Status: Open => Answered
>
> Olivier Mattelaer proposed the following answer:
> Hi,
>
> Looks like a compilation error.
> So this should not be related to the cluster mode.
> Can you double check that you succeed to compile the code.
>
> Cheers,
>
> Olivier
>
> On 24 Mar 2015, at 18:11, Andre Sznajder
> <email address hidden> wrote:
>
>> Question #257782 on MadGraph5_aMC@NLO changed:
>> https:/
>>
>> Status: Answered => Open
>>
>> Andre Sznajder is still having a problem:
>> Hi Olivier,
>> Ok, I will try to the DECAY code from the older version of Madgraph5 that you pointed to me.
>> Meanwhile I tried made the changes in matrix*.f files for having a single polarization and now I am having a strange compilation error.
>> When I test the changes running interactively I works fine but when I submit it batch using condor I get the following error:
>>
>>> Generating 10000 events with run name run_01
>> survey run_01
>> INFO: compile directory
>> Not able to open file /storage/
>> ured.Please set one in ./input/
>> Using random number seed offset = 21
>> INFO: Running Survey
>> Creating Jobs
>> Working on SubProcesses
>> P1_qq_wpwpqq
>> Error detected in "generate_events "
>> write debug file /storage/
>> If you need help with this issue please contact us on https:/
>> MadGraph5Error : A compilation Error occurs when trying to compile /storage/
>> CD0/SubProcesse
>> The compilation fails with the following output message:
>> gfortran -O -w -fbounds-check -fPIC -ffixed-
>> gfortran -O -w -fbounds-check -fPIC -ffixed-
>> weight.o initcluster.o addmothers.o setscales.o idenparts.o auto_dsig.o auto_dsig1.o auto_dsig2.o auto_dsig3.o auto_dsig4.o auto_dsig5.o auto_dsig6.o auto_dsig7.
>> o matrix1.o matrix2.o matrix3.o matrix4.o matrix5.o matrix6.o matrix7.o -L../../lib/ -ldhelas -ldsample -lmodel -lgeneric -lpdf -lcernlib
>> /usr/lib/
>> (.text+0x20): undefined reference to `main'
>> collect2: error: ld returned 1 exit status
>> make: *** [madevent] Error 1
>>
>> Please try to fix this compilations issue and retry.
>> Help might be found at https:/
>> If you think that this is a bug, you can report this at https:/
>> quit
>>
>>
>> Do you see what could be going wrong ?
>> I have been submitting jobs in batch for ages and never had this problem. I has something to do with the mods I made to matrix*.f but I can figure out why it runs fine iteractively and not in batch …
>> Cheers,
>> Andre
>>
>>
>> On Mar 23, 2015, at 11:31 AM, Olivier Mattelaer
>> <<email address hidden>
>> wrote:
>>
>> Your question #257782 on MadGraph5_aMC@NLO changed:
>> https:/
>>
>> Olivier Mattelaer proposed the following answer:
>> Hi Andre,
>>
>> So i discuss with Fabio to understand how DECAYS was working and this is indeed more accurate that the simple stuff that I did.
>> So we will not have that option in a near future.
>>
>> Cheers,
>>
>> Olivier
>>
>> --
>> If this answers your question, please go to the following page to let us
>> know that it is solved:
>> https:/
>>
>> If you still need help, you can reply to this email or go to the
>> following page to enter your feedback:
>> https:/
>>
>> You received this question notification because you asked the question.
>>
>> =======
>> Andre Sznajder
>> Professor Associado
>> Instituto de Fisica - Dept. DFNAE
>> Universidade do Estado do Rio de Janeiro ( UERJ )
>> Rio de Janeiro, RJ - Brasil
>> Tel.: (+55)(21)23340608 ramal:24 Fax: (+55)(21)23340483
>> Email: <email address hidden>
>> =======
>>
>> --
>> You received this question notification because you are an answer
>> contact for MadGraph5_aMC@NLO.
>
> --
> If this answers your question, please go to the following page to let us
> know that it is solved:
> https:/
>
> If you still need help, you can reply to this email or go to the
> following page to enter your feedback:
> https:/
>
> You received this question notification because you asked the question.
=======
Andre Sznajder
Professor Associado
Instituto de Fisica - Dept. DFNAE
Universidade do Estado do Rio de Janeiro ( UERJ )
Rio de Janeiro, RJ - Brasil
Tel.: (+55)(21)23340608 ramal:24 Fax: (+55)(21)23340483
Email: <email address hidden>
=======
Revision history for this message
|
#18 |
Hi Andre,
This remind me the only code I ever fix in DECAY, did you use the version which was coming from MG51.5.14?
Otherwise I do not know that much (actually I only read part of this code once). So I will be as bad as you to debug that old code.
This is one of the reason that we remove it since actually no one is able to provide support to this code, since basically no one knows how it works.
Cheers,
Olivier
On 26 Mar 2015, at 00:56, Andre Sznajder <email address hidden> wrote:
> Question #257782 on MadGraph5_aMC@NLO changed:
> https:/
>
> Status: Answered => Open
>
> Andre Sznajder is still having a problem:
> Hi Olivier,
> I found my mistake and now the Madevent runs fine, but when it comes to run DECAY I am having the error bellow.
> Would it be possible that DECAY doesn’t know how to read the parameter info from the LHE created by MG 5.2.2.3 ?
> Cheers,
> Andre
>
>
> [sznajder@cmslpc27 DECAY]$ ./decay
> *******
> * DECAY *
> * a MadEvent program *
> * for decaying unstable particles *
> * in the Standar Model *
> * -------
> * version compliant with MG_ME_V4.0 *
> * *
> * 27-July-2006 *
> *******
>
> Input run mode:
> ---------------
>
> 0 = calculates decay widths
> 1 = decay events in file
>
> 1
> *******
> * reading seed from iseed.dat *
> * rnd number seed = -13 *
> *******
> *******
> * run_mode=1 => decaying events *
> * *
> * Using the param_card.dat in the banner for *
> * the input params. *
> * *
> * >>>>>>Total widths are recalculated here<<<<< *
> *******
> input event file: (e.g. events.lhe)
> unweighted_
> name for output file: (e.g. dec-events.lhe)
> unweighted_
> At line 484 of file decay_couplings.f
> Fortran runtime error: End of file
>
>
>
>> On Mar 24, 2015, at 7:01 AM, Olivier Mattelaer <email address hidden> wrote:
>>
>> Your question #257782 on MadGraph5_aMC@NLO changed:
>> https:/
>>
>> Status: Open => Answered
>>
>> Olivier Mattelaer proposed the following answer:
>> Hi,
>>
>> Looks like a compilation error.
>> So this should not be related to the cluster mode.
>> Can you double check that you succeed to compile the code.
>>
>> Cheers,
>>
>> Olivier
>>
>> On 24 Mar 2015, at 18:11, Andre Sznajder
>> <email address hidden> wrote:
>>
>>> Question #257782 on MadGraph5_aMC@NLO changed:
>>> https:/
>>>
>>> Status: Answered => Open
>>>
>>> Andre Sznajder is still having a problem:
>>> Hi Olivier,
>>> Ok, I will try to the DECAY code from the older version of Madgraph5 that you pointed to me.
>>> Meanwhile I tried made the changes in matrix*.f files for having a single polarization and now I am having a strange compilation error.
>>> When I test the changes running interactively I works fine but when I submit it batch using condor I get the following error:
>>>
>>>> Generating 10000 events with run name run_01
>>> survey run_01
>>> INFO: compile directory
>>> Not able to open file /storage/
>>> ured.Please set one in ./input/
>>> Using random number seed offset = 21
>>> INFO: Running Survey
>>> Creating Jobs
>>> Working on SubProcesses
>>> P1_qq_wpwpqq
>>> Error detected in "generate_events "
>>> write debug file /storage/
>>> If you need help with this issue please contact us on https:/
>>> MadGraph5Error : A compilation Error occurs when trying to compile /storage/
>>> CD0/SubProcesse
>>> The compilation fails with the following output message:
>>> gfortran -O -w -fbounds-check -fPIC -ffixed-
>>> gfortran -O -w -fbounds-check -fPIC -ffixed-
>>> weight.o initcluster.o addmothers.o setscales.o idenparts.o auto_dsig.o auto_dsig1.o auto_dsig2.o auto_dsig3.o auto_dsig4.o auto_dsig5.o auto_dsig6.o auto_dsig7.
>>> o matrix1.o matrix2.o matrix3.o matrix4.o matrix5.o matrix6.o matrix7.o -L../../lib/ -ldhelas -ldsample -lmodel -lgeneric -lpdf -lcernlib
>>> /usr/lib/
>>> (.text+0x20): undefined reference to `main'
>>> collect2: error: ld returned 1 exit status
>>> make: *** [madevent] Error 1
>>>
>>> Please try to fix this compilations issue and retry.
>>> Help might be found at https:/
>>> If you think that this is a bug, you can report this at https:/
>>> quit
>>>
>>>
>>> Do you see what could be going wrong ?
>>> I have been submitting jobs in batch for ages and never had this problem. I has something to do with the mods I made to matrix*.f but I can figure out why it runs fine iteractively and not in batch …
>>> Cheers,
>>> Andre
>>>
>>>
>>> On Mar 23, 2015, at 11:31 AM, Olivier Mattelaer
>>> <<email address hidden>
>>> wrote:
>>>
>>> Your question #257782 on MadGraph5_aMC@NLO changed:
>>> https:/
>>>
>>> Olivier Mattelaer proposed the following answer:
>>> Hi Andre,
>>>
>>> So i discuss with Fabio to understand how DECAYS was working and this is indeed more accurate that the simple stuff that I did.
>>> So we will not have that option in a near future.
>>>
>>> Cheers,
>>>
>>> Olivier
>>>
>>> --
>>> If this answers your question, please go to the following page to let us
>>> know that it is solved:
>>> https:/
>>>
>>> If you still need help, you can reply to this email or go to the
>>> following page to enter your feedback:
>>> https:/
>>>
>>> You received this question notification because you asked the question.
>>>
>>> =======
>>> Andre Sznajder
>>> Professor Associado
>>> Instituto de Fisica - Dept. DFNAE
>>> Universidade do Estado do Rio de Janeiro ( UERJ )
>>> Rio de Janeiro, RJ - Brasil
>>> Tel.: (+55)(21)23340608 ramal:24 Fax: (+55)(21)23340483
>>> Email: <email address hidden>
>>> =======
>>>
>>> --
>>> You received this question notification because you are an answer
>>> contact for MadGraph5_aMC@NLO.
>>
>> --
>> If this answers your question, please go to the following page to let us
>> know that it is solved:
>> https:/
>>
>> If you still need help, you can reply to this email or go to the
>> following page to enter your feedback:
>> https:/
>>
>> You received this question notification because you asked the question.
>
> =======
> Andre Sznajder
> Professor Associado
> Instituto de Fisica - Dept. DFNAE
> Universidade do Estado do Rio de Janeiro ( UERJ )
> Rio de Janeiro, RJ - Brasil
> Tel.: (+55)(21)23340608 ramal:24 Fax: (+55)(21)23340483
> Email: <email address hidden>
> =======
>
> --
> You received this question notification because you are an answer
> contact for MadGraph5_aMC@NLO.
Revision history for this message
|
#19 |
Hi Olivier,
Yes , I used the DECAY version you provided me from MG1.5.14 !
But the LHE was generated by MG 5.2.2.3.
Cheers,
Andre
> On Mar 25, 2015, at 1:31 PM, Olivier Mattelaer <email address hidden> wrote:
>
> Your question #257782 on MadGraph5_aMC@NLO changed:
> https:/
>
> Status: Open => Answered
>
> Olivier Mattelaer proposed the following answer:
> Hi Andre,
>
>
> This remind me the only code I ever fix in DECAY, did you use the version which was coming from MG51.5.14?
> Otherwise I do not know that much (actually I only read part of this code once). So I will be as bad as you to debug that old code.
> This is one of the reason that we remove it since actually no one is able to provide support to this code, since basically no one knows how it works.
>
> Cheers,
>
> Olivier
>
> On 26 Mar 2015, at 00:56, Andre Sznajder
> <email address hidden> wrote:
>
>> Question #257782 on MadGraph5_aMC@NLO changed:
>> https:/
>>
>> Status: Answered => Open
>>
>> Andre Sznajder is still having a problem:
>> Hi Olivier,
>> I found my mistake and now the Madevent runs fine, but when it comes to run DECAY I am having the error bellow.
>> Would it be possible that DECAY doesn’t know how to read the parameter info from the LHE created by MG 5.2.2.3 ?
>> Cheers,
>> Andre
>>
>>
>> [sznajder@cmslpc27 DECAY]$ ./decay
>> *******
>> * DECAY *
>> * a MadEvent program *
>> * for decaying unstable particles *
>> * in the Standar Model *
>> * -------
>> * version compliant with MG_ME_V4.0 *
>> * *
>> * 27-July-2006 *
>> *******
>>
>> Input run mode:
>> ---------------
>>
>> 0 = calculates decay widths
>> 1 = decay events in file
>>
>> 1
>> *******
>> * reading seed from iseed.dat *
>> * rnd number seed = -13 *
>> *******
>> *******
>> * run_mode=1 => decaying events *
>> * *
>> * Using the param_card.dat in the banner for *
>> * the input params. *
>> * *
>> * >>>>>>Total widths are recalculated here<<<<< *
>> *******
>> input event file: (e.g. events.lhe)
>> unweighted_
>> name for output file: (e.g. dec-events.lhe)
>> unweighted_
>> At line 484 of file decay_couplings.f
>> Fortran runtime error: End of file
>>
>>
>>
>>> On Mar 24, 2015, at 7:01 AM, Olivier Mattelaer <email address hidden> wrote:
>>>
>>> Your question #257782 on MadGraph5_aMC@NLO changed:
>>> https:/
>>>
>>> Status: Open => Answered
>>>
>>> Olivier Mattelaer proposed the following answer:
>>> Hi,
>>>
>>> Looks like a compilation error.
>>> So this should not be related to the cluster mode.
>>> Can you double check that you succeed to compile the code.
>>>
>>> Cheers,
>>>
>>> Olivier
>>>
>>> On 24 Mar 2015, at 18:11, Andre Sznajder
>>> <email address hidden> wrote:
>>>
>>>> Question #257782 on MadGraph5_aMC@NLO changed:
>>>> https:/
>>>>
>>>> Status: Answered => Open
>>>>
>>>> Andre Sznajder is still having a problem:
>>>> Hi Olivier,
>>>> Ok, I will try to the DECAY code from the older version of Madgraph5 that you pointed to me.
>>>> Meanwhile I tried made the changes in matrix*.f files for having a single polarization and now I am having a strange compilation error.
>>>> When I test the changes running interactively I works fine but when I submit it batch using condor I get the following error:
>>>>
>>>>> Generating 10000 events with run name run_01
>>>> survey run_01
>>>> INFO: compile directory
>>>> Not able to open file /storage/
>>>> ured.Please set one in ./input/
>>>> Using random number seed offset = 21
>>>> INFO: Running Survey
>>>> Creating Jobs
>>>> Working on SubProcesses
>>>> P1_qq_wpwpqq
>>>> Error detected in "generate_events "
>>>> write debug file /storage/
>>>> If you need help with this issue please contact us on https:/
>>>> MadGraph5Error : A compilation Error occurs when trying to compile /storage/
>>>> CD0/SubProcesse
>>>> The compilation fails with the following output message:
>>>> gfortran -O -w -fbounds-check -fPIC -ffixed-
>>>> gfortran -O -w -fbounds-check -fPIC -ffixed-
>>>> weight.o initcluster.o addmothers.o setscales.o idenparts.o auto_dsig.o auto_dsig1.o auto_dsig2.o auto_dsig3.o auto_dsig4.o auto_dsig5.o auto_dsig6.o auto_dsig7.
>>>> o matrix1.o matrix2.o matrix3.o matrix4.o matrix5.o matrix6.o matrix7.o -L../../lib/ -ldhelas -ldsample -lmodel -lgeneric -lpdf -lcernlib
>>>> /usr/lib/
>>>> (.text+0x20): undefined reference to `main'
>>>> collect2: error: ld returned 1 exit status
>>>> make: *** [madevent] Error 1
>>>>
>>>> Please try to fix this compilations issue and retry.
>>>> Help might be found at https:/
>>>> If you think that this is a bug, you can report this at https:/
>>>> quit
>>>>
>>>>
>>>> Do you see what could be going wrong ?
>>>> I have been submitting jobs in batch for ages and never had this problem. I has something to do with the mods I made to matrix*.f but I can figure out why it runs fine iteractively and not in batch …
>>>> Cheers,
>>>> Andre
>>>>
>>>>
>>>> On Mar 23, 2015, at 11:31 AM, Olivier Mattelaer
>>>> <<email address hidden>
>>>> wrote:
>>>>
>>>> Your question #257782 on MadGraph5_aMC@NLO changed:
>>>> https:/
>>>>
>>>> Olivier Mattelaer proposed the following answer:
>>>> Hi Andre,
>>>>
>>>> So i discuss with Fabio to understand how DECAYS was working and this is indeed more accurate that the simple stuff that I did.
>>>> So we will not have that option in a near future.
>>>>
>>>> Cheers,
>>>>
>>>> Olivier
>>>>
>>>> --
>>>> If this answers your question, please go to the following page to let us
>>>> know that it is solved:
>>>> https:/
>>>>
>>>> If you still need help, you can reply to this email or go to the
>>>> following page to enter your feedback:
>>>> https:/
>>>>
>>>> You received this question notification because you asked the question.
>>>>
>>>> =======
>>>> Andre Sznajder
>>>> Professor Associado
>>>> Instituto de Fisica - Dept. DFNAE
>>>> Universidade do Estado do Rio de Janeiro ( UERJ )
>>>> Rio de Janeiro, RJ - Brasil
>>>> Tel.: (+55)(21)23340608 ramal:24 Fax: (+55)(21)23340483
>>>> Email: <email address hidden>
>>>> =======
>>>>
>>>> --
>>>> You received this question notification because you are an answer
>>>> contact for MadGraph5_aMC@NLO.
>>>
>>> --
>>> If this answers your question, please go to the following page to let us
>>> know that it is solved:
>>> https:/
>>>
>>> If you still need help, you can reply to this email or go to the
>>> following page to enter your feedback:
>>> https:/
>>>
>>> You received this question notification because you asked the question.
>>
>> =======
>> Andre Sznajder
>> Professor Associado
>> Instituto de Fisica - Dept. DFNAE
>> Universidade do Estado do Rio de Janeiro ( UERJ )
>> Rio de Janeiro, RJ - Brasil
>> Tel.: (+55)(21)23340608 ramal:24 Fax: (+55)(21)23340483
>> Email: <email address hidden>
>> =======
>>
>> --
>> You received this question notification because you are an answer
>> contact for MadGraph5_aMC@NLO.
>
> --
> If this answers your question, please go to the following page to let us
> know that it is solved:
> https:/
>
> If you still need help, you can reply to this email or go to the
> following page to enter your feedback:
> https:/
>
> You received this question notification because you asked the question.
=======
Andre Sznajder
Professor Associado
Instituto de Fisica - Dept. DFNAE
Universidade do Estado do Rio de Janeiro ( UERJ )
Rio de Janeiro, RJ - Brasil
Tel.: (+55)(21)23340608 ramal:24 Fax: (+55)(21)23340483
Email: <email address hidden>
=======
Revision history for this message
|
#20 |
Hi Olivier,
I found the problem with DECAY and MG5.2.2.3 LHE !
In the new version you have a blank line between blocks and decay_couplings.f in line 488 doesn’t know how to handle this.
I inserted a protection in there to skip blank lines and now it runs fine.
Thanks,
Andre
> On Mar 25, 2015, at 1:31 PM, Olivier Mattelaer <email address hidden> wrote:
>
> Your question #257782 on MadGraph5_aMC@NLO changed:
> https:/
>
> Status: Open => Answered
>
> Olivier Mattelaer proposed the following answer:
> Hi Andre,
>
>
> This remind me the only code I ever fix in DECAY, did you use the version which was coming from MG51.5.14?
> Otherwise I do not know that much (actually I only read part of this code once). So I will be as bad as you to debug that old code.
> This is one of the reason that we remove it since actually no one is able to provide support to this code, since basically no one knows how it works.
>
> Cheers,
>
> Olivier
>
> On 26 Mar 2015, at 00:56, Andre Sznajder
> <email address hidden> wrote:
>
>> Question #257782 on MadGraph5_aMC@NLO changed:
>> https:/
>>
>> Status: Answered => Open
>>
>> Andre Sznajder is still having a problem:
>> Hi Olivier,
>> I found my mistake and now the Madevent runs fine, but when it comes to run DECAY I am having the error bellow.
>> Would it be possible that DECAY doesn’t know how to read the parameter info from the LHE created by MG 5.2.2.3 ?
>> Cheers,
>> Andre
>>
>>
>> [sznajder@cmslpc27 DECAY]$ ./decay
>> *******
>> * DECAY *
>> * a MadEvent program *
>> * for decaying unstable particles *
>> * in the Standar Model *
>> * -------
>> * version compliant with MG_ME_V4.0 *
>> * *
>> * 27-July-2006 *
>> *******
>>
>> Input run mode:
>> ---------------
>>
>> 0 = calculates decay widths
>> 1 = decay events in file
>>
>> 1
>> *******
>> * reading seed from iseed.dat *
>> * rnd number seed = -13 *
>> *******
>> *******
>> * run_mode=1 => decaying events *
>> * *
>> * Using the param_card.dat in the banner for *
>> * the input params. *
>> * *
>> * >>>>>>Total widths are recalculated here<<<<< *
>> *******
>> input event file: (e.g. events.lhe)
>> unweighted_
>> name for output file: (e.g. dec-events.lhe)
>> unweighted_
>> At line 484 of file decay_couplings.f
>> Fortran runtime error: End of file
>>
>>
>>
>>> On Mar 24, 2015, at 7:01 AM, Olivier Mattelaer <email address hidden> wrote:
>>>
>>> Your question #257782 on MadGraph5_aMC@NLO changed:
>>> https:/
>>>
>>> Status: Open => Answered
>>>
>>> Olivier Mattelaer proposed the following answer:
>>> Hi,
>>>
>>> Looks like a compilation error.
>>> So this should not be related to the cluster mode.
>>> Can you double check that you succeed to compile the code.
>>>
>>> Cheers,
>>>
>>> Olivier
>>>
>>> On 24 Mar 2015, at 18:11, Andre Sznajder
>>> <email address hidden> wrote:
>>>
>>>> Question #257782 on MadGraph5_aMC@NLO changed:
>>>> https:/
>>>>
>>>> Status: Answered => Open
>>>>
>>>> Andre Sznajder is still having a problem:
>>>> Hi Olivier,
>>>> Ok, I will try to the DECAY code from the older version of Madgraph5 that you pointed to me.
>>>> Meanwhile I tried made the changes in matrix*.f files for having a single polarization and now I am having a strange compilation error.
>>>> When I test the changes running interactively I works fine but when I submit it batch using condor I get the following error:
>>>>
>>>>> Generating 10000 events with run name run_01
>>>> survey run_01
>>>> INFO: compile directory
>>>> Not able to open file /storage/
>>>> ured.Please set one in ./input/
>>>> Using random number seed offset = 21
>>>> INFO: Running Survey
>>>> Creating Jobs
>>>> Working on SubProcesses
>>>> P1_qq_wpwpqq
>>>> Error detected in "generate_events "
>>>> write debug file /storage/
>>>> If you need help with this issue please contact us on https:/
>>>> MadGraph5Error : A compilation Error occurs when trying to compile /storage/
>>>> CD0/SubProcesse
>>>> The compilation fails with the following output message:
>>>> gfortran -O -w -fbounds-check -fPIC -ffixed-
>>>> gfortran -O -w -fbounds-check -fPIC -ffixed-
>>>> weight.o initcluster.o addmothers.o setscales.o idenparts.o auto_dsig.o auto_dsig1.o auto_dsig2.o auto_dsig3.o auto_dsig4.o auto_dsig5.o auto_dsig6.o auto_dsig7.
>>>> o matrix1.o matrix2.o matrix3.o matrix4.o matrix5.o matrix6.o matrix7.o -L../../lib/ -ldhelas -ldsample -lmodel -lgeneric -lpdf -lcernlib
>>>> /usr/lib/
>>>> (.text+0x20): undefined reference to `main'
>>>> collect2: error: ld returned 1 exit status
>>>> make: *** [madevent] Error 1
>>>>
>>>> Please try to fix this compilations issue and retry.
>>>> Help might be found at https:/
>>>> If you think that this is a bug, you can report this at https:/
>>>> quit
>>>>
>>>>
>>>> Do you see what could be going wrong ?
>>>> I have been submitting jobs in batch for ages and never had this problem. I has something to do with the mods I made to matrix*.f but I can figure out why it runs fine iteractively and not in batch …
>>>> Cheers,
>>>> Andre
>>>>
>>>>
>>>> On Mar 23, 2015, at 11:31 AM, Olivier Mattelaer
>>>> <<email address hidden>
>>>> wrote:
>>>>
>>>> Your question #257782 on MadGraph5_aMC@NLO changed:
>>>> https:/
>>>>
>>>> Olivier Mattelaer proposed the following answer:
>>>> Hi Andre,
>>>>
>>>> So i discuss with Fabio to understand how DECAYS was working and this is indeed more accurate that the simple stuff that I did.
>>>> So we will not have that option in a near future.
>>>>
>>>> Cheers,
>>>>
>>>> Olivier
>>>>
>>>> --
>>>> If this answers your question, please go to the following page to let us
>>>> know that it is solved:
>>>> https:/
>>>>
>>>> If you still need help, you can reply to this email or go to the
>>>> following page to enter your feedback:
>>>> https:/
>>>>
>>>> You received this question notification because you asked the question.
>>>>
>>>> =======
>>>> Andre Sznajder
>>>> Professor Associado
>>>> Instituto de Fisica - Dept. DFNAE
>>>> Universidade do Estado do Rio de Janeiro ( UERJ )
>>>> Rio de Janeiro, RJ - Brasil
>>>> Tel.: (+55)(21)23340608 ramal:24 Fax: (+55)(21)23340483
>>>> Email: <email address hidden>
>>>> =======
>>>>
>>>> --
>>>> You received this question notification because you are an answer
>>>> contact for MadGraph5_aMC@NLO.
>>>
>>> --
>>> If this answers your question, please go to the following page to let us
>>> know that it is solved:
>>> https:/
>>>
>>> If you still need help, you can reply to this email or go to the
>>> following page to enter your feedback:
>>> https:/
>>>
>>> You received this question notification because you asked the question.
>>
>> =======
>> Andre Sznajder
>> Professor Associado
>> Instituto de Fisica - Dept. DFNAE
>> Universidade do Estado do Rio de Janeiro ( UERJ )
>> Rio de Janeiro, RJ - Brasil
>> Tel.: (+55)(21)23340608 ramal:24 Fax: (+55)(21)23340483
>> Email: <email address hidden>
>> =======
>>
>> --
>> You received this question notification because you are an answer
>> contact for MadGraph5_aMC@NLO.
>
> --
> If this answers your question, please go to the following page to let us
> know that it is solved:
> https:/
>
> If you still need help, you can reply to this email or go to the
> following page to enter your feedback:
> https:/
>
> You received this question notification because you asked the question.
=======
Andre Sznajder
Professor Associado
Instituto de Fisica - Dept. DFNAE
Universidade do Estado do Rio de Janeiro ( UERJ )
Rio de Janeiro, RJ - Brasil
Tel.: (+55)(21)23340608 ramal:24 Fax: (+55)(21)23340483
Email: <email address hidden>
=======
Revision history for this message
|
#21 |
Hi Olivier,
Concerning the Madevent (MG v2.2.2.3) generation efficiency drop for the WLWL mode, I have asked for 50000 events for the process p p > w w j j QED=4 QCD=0 for each polarization mode.
While I get 50000 events for the modes WLWT and WTWT , in the WLWL mode I get only about 400 events ( less than 1% ) !
I know 3 other people that reported the same inefficiency problem working completely independently from me …
Cheers,
Andre
> On Mar 25, 2015, at 1:31 PM, Olivier Mattelaer <email address hidden> wrote:
>
> Your question #257782 on MadGraph5_aMC@NLO changed:
> https:/
>
> Status: Open => Answered
>
> Olivier Mattelaer proposed the following answer:
> Hi Andre,
>
>
> This remind me the only code I ever fix in DECAY, did you use the version which was coming from MG51.5.14?
> Otherwise I do not know that much (actually I only read part of this code once). So I will be as bad as you to debug that old code.
> This is one of the reason that we remove it since actually no one is able to provide support to this code, since basically no one knows how it works.
>
> Cheers,
>
> Olivier
>
> On 26 Mar 2015, at 00:56, Andre Sznajder
> <email address hidden> wrote:
>
>> Question #257782 on MadGraph5_aMC@NLO changed:
>> https:/
>>
>> Status: Answered => Open
>>
>> Andre Sznajder is still having a problem:
>> Hi Olivier,
>> I found my mistake and now the Madevent runs fine, but when it comes to run DECAY I am having the error bellow.
>> Would it be possible that DECAY doesn’t know how to read the parameter info from the LHE created by MG 5.2.2.3 ?
>> Cheers,
>> Andre
>>
>>
>> [sznajder@cmslpc27 DECAY]$ ./decay
>> *******
>> * DECAY *
>> * a MadEvent program *
>> * for decaying unstable particles *
>> * in the Standar Model *
>> * -------
>> * version compliant with MG_ME_V4.0 *
>> * *
>> * 27-July-2006 *
>> *******
>>
>> Input run mode:
>> ---------------
>>
>> 0 = calculates decay widths
>> 1 = decay events in file
>>
>> 1
>> *******
>> * reading seed from iseed.dat *
>> * rnd number seed = -13 *
>> *******
>> *******
>> * run_mode=1 => decaying events *
>> * *
>> * Using the param_card.dat in the banner for *
>> * the input params. *
>> * *
>> * >>>>>>Total widths are recalculated here<<<<< *
>> *******
>> input event file: (e.g. events.lhe)
>> unweighted_
>> name for output file: (e.g. dec-events.lhe)
>> unweighted_
>> At line 484 of file decay_couplings.f
>> Fortran runtime error: End of file
>>
>>
>>
>>> On Mar 24, 2015, at 7:01 AM, Olivier Mattelaer <email address hidden> wrote:
>>>
>>> Your question #257782 on MadGraph5_aMC@NLO changed:
>>> https:/
>>>
>>> Status: Open => Answered
>>>
>>> Olivier Mattelaer proposed the following answer:
>>> Hi,
>>>
>>> Looks like a compilation error.
>>> So this should not be related to the cluster mode.
>>> Can you double check that you succeed to compile the code.
>>>
>>> Cheers,
>>>
>>> Olivier
>>>
>>> On 24 Mar 2015, at 18:11, Andre Sznajder
>>> <email address hidden> wrote:
>>>
>>>> Question #257782 on MadGraph5_aMC@NLO changed:
>>>> https:/
>>>>
>>>> Status: Answered => Open
>>>>
>>>> Andre Sznajder is still having a problem:
>>>> Hi Olivier,
>>>> Ok, I will try to the DECAY code from the older version of Madgraph5 that you pointed to me.
>>>> Meanwhile I tried made the changes in matrix*.f files for having a single polarization and now I am having a strange compilation error.
>>>> When I test the changes running interactively I works fine but when I submit it batch using condor I get the following error:
>>>>
>>>>> Generating 10000 events with run name run_01
>>>> survey run_01
>>>> INFO: compile directory
>>>> Not able to open file /storage/
>>>> ured.Please set one in ./input/
>>>> Using random number seed offset = 21
>>>> INFO: Running Survey
>>>> Creating Jobs
>>>> Working on SubProcesses
>>>> P1_qq_wpwpqq
>>>> Error detected in "generate_events "
>>>> write debug file /storage/
>>>> If you need help with this issue please contact us on https:/
>>>> MadGraph5Error : A compilation Error occurs when trying to compile /storage/
>>>> CD0/SubProcesse
>>>> The compilation fails with the following output message:
>>>> gfortran -O -w -fbounds-check -fPIC -ffixed-
>>>> gfortran -O -w -fbounds-check -fPIC -ffixed-
>>>> weight.o initcluster.o addmothers.o setscales.o idenparts.o auto_dsig.o auto_dsig1.o auto_dsig2.o auto_dsig3.o auto_dsig4.o auto_dsig5.o auto_dsig6.o auto_dsig7.
>>>> o matrix1.o matrix2.o matrix3.o matrix4.o matrix5.o matrix6.o matrix7.o -L../../lib/ -ldhelas -ldsample -lmodel -lgeneric -lpdf -lcernlib
>>>> /usr/lib/
>>>> (.text+0x20): undefined reference to `main'
>>>> collect2: error: ld returned 1 exit status
>>>> make: *** [madevent] Error 1
>>>>
>>>> Please try to fix this compilations issue and retry.
>>>> Help might be found at https:/
>>>> If you think that this is a bug, you can report this at https:/
>>>> quit
>>>>
>>>>
>>>> Do you see what could be going wrong ?
>>>> I have been submitting jobs in batch for ages and never had this problem. I has something to do with the mods I made to matrix*.f but I can figure out why it runs fine iteractively and not in batch …
>>>> Cheers,
>>>> Andre
>>>>
>>>>
>>>> On Mar 23, 2015, at 11:31 AM, Olivier Mattelaer
>>>> <<email address hidden>
>>>> wrote:
>>>>
>>>> Your question #257782 on MadGraph5_aMC@NLO changed:
>>>> https:/
>>>>
>>>> Olivier Mattelaer proposed the following answer:
>>>> Hi Andre,
>>>>
>>>> So i discuss with Fabio to understand how DECAYS was working and this is indeed more accurate that the simple stuff that I did.
>>>> So we will not have that option in a near future.
>>>>
>>>> Cheers,
>>>>
>>>> Olivier
>>>>
>>>> --
>>>> If this answers your question, please go to the following page to let us
>>>> know that it is solved:
>>>> https:/
>>>>
>>>> If you still need help, you can reply to this email or go to the
>>>> following page to enter your feedback:
>>>> https:/
>>>>
>>>> You received this question notification because you asked the question.
>>>>
>>>> =======
>>>> Andre Sznajder
>>>> Professor Associado
>>>> Instituto de Fisica - Dept. DFNAE
>>>> Universidade do Estado do Rio de Janeiro ( UERJ )
>>>> Rio de Janeiro, RJ - Brasil
>>>> Tel.: (+55)(21)23340608 ramal:24 Fax: (+55)(21)23340483
>>>> Email: <email address hidden>
>>>> =======
>>>>
>>>> --
>>>> You received this question notification because you are an answer
>>>> contact for MadGraph5_aMC@NLO.
>>>
>>> --
>>> If this answers your question, please go to the following page to let us
>>> know that it is solved:
>>> https:/
>>>
>>> If you still need help, you can reply to this email or go to the
>>> following page to enter your feedback:
>>> https:/
>>>
>>> You received this question notification because you asked the question.
>>
>> =======
>> Andre Sznajder
>> Professor Associado
>> Instituto de Fisica - Dept. DFNAE
>> Universidade do Estado do Rio de Janeiro ( UERJ )
>> Rio de Janeiro, RJ - Brasil
>> Tel.: (+55)(21)23340608 ramal:24 Fax: (+55)(21)23340483
>> Email: <email address hidden>
>> =======
>>
>> --
>> You received this question notification because you are an answer
>> contact for MadGraph5_aMC@NLO.
>
> --
> If this answers your question, please go to the following page to let us
> know that it is solved:
> https:/
>
> If you still need help, you can reply to this email or go to the
> following page to enter your feedback:
> https:/
>
> You received this question notification because you asked the question.
=======
Andre Sznajder
Professor Associado
Instituto de Fisica - Dept. DFNAE
Universidade do Estado do Rio de Janeiro ( UERJ )
Rio de Janeiro, RJ - Brasil
Tel.: (+55)(21)23340608 ramal:24 Fax: (+55)(21)23340483
Email: <email address hidden>
=======
Revision history for this message
|
#22 |
Hi Andre,
This is not a real bug of our code, just you hit in that case an efficiency limit of our code.
This is the kind of limitation that we actively discuss to see how we can beat them for a future release.
Cheers,
Olivier
On 28 Mar 2015, at 00:31, Andre Sznajder <email address hidden> wrote:
> Question #257782 on MadGraph5_aMC@NLO changed:
> https:/
>
> Andre Sznajder gave more information on the question:
> Hi Olivier,
> Concerning the Madevent (MG v2.2.2.3) generation efficiency drop for the WLWL mode, I have asked for 50000 events for the process p p > w w j j QED=4 QCD=0 for each polarization mode.
> While I get 50000 events for the modes WLWT and WTWT , in the WLWL mode I get only about 400 events ( less than 1% ) !
> I know 3 other people that reported the same inefficiency problem working completely independently from me …
> Cheers,
> Andre
>
>
>> On Mar 25, 2015, at 1:31 PM, Olivier Mattelaer <email address hidden> wrote:
>>
>> Your question #257782 on MadGraph5_aMC@NLO changed:
>> https:/
>>
>> Status: Open => Answered
>>
>> Olivier Mattelaer proposed the following answer:
>> Hi Andre,
>>
>>
>> This remind me the only code I ever fix in DECAY, did you use the version which was coming from MG51.5.14?
>> Otherwise I do not know that much (actually I only read part of this code once). So I will be as bad as you to debug that old code.
>> This is one of the reason that we remove it since actually no one is able to provide support to this code, since basically no one knows how it works.
>>
>> Cheers,
>>
>> Olivier
>>
>> On 26 Mar 2015, at 00:56, Andre Sznajder
>> <email address hidden> wrote:
>>
>>> Question #257782 on MadGraph5_aMC@NLO changed:
>>> https:/
>>>
>>> Status: Answered => Open
>>>
>>> Andre Sznajder is still having a problem:
>>> Hi Olivier,
>>> I found my mistake and now the Madevent runs fine, but when it comes to run DECAY I am having the error bellow.
>>> Would it be possible that DECAY doesn’t know how to read the parameter info from the LHE created by MG 5.2.2.3 ?
>>> Cheers,
>>> Andre
>>>
>>>
>>> [sznajder@cmslpc27 DECAY]$ ./decay
>>> *******
>>> * DECAY *
>>> * a MadEvent program *
>>> * for decaying unstable particles *
>>> * in the Standar Model *
>>> * -------
>>> * version compliant with MG_ME_V4.0 *
>>> * *
>>> * 27-July-2006 *
>>> *******
>>>
>>> Input run mode:
>>> ---------------
>>>
>>> 0 = calculates decay widths
>>> 1 = decay events in file
>>>
>>> 1
>>> *******
>>> * reading seed from iseed.dat *
>>> * rnd number seed = -13 *
>>> *******
>>> *******
>>> * run_mode=1 => decaying events *
>>> * *
>>> * Using the param_card.dat in the banner for *
>>> * the input params. *
>>> * *
>>> * >>>>>>Total widths are recalculated here<<<<< *
>>> *******
>>> input event file: (e.g. events.lhe)
>>> unweighted_
>>> name for output file: (e.g. dec-events.lhe)
>>> unweighted_
>>> At line 484 of file decay_couplings.f
>>> Fortran runtime error: End of file
>>>
>>>
>>>
>>>> On Mar 24, 2015, at 7:01 AM, Olivier Mattelaer <email address hidden> wrote:
>>>>
>>>> Your question #257782 on MadGraph5_aMC@NLO changed:
>>>> https:/
>>>>
>>>> Status: Open => Answered
>>>>
>>>> Olivier Mattelaer proposed the following answer:
>>>> Hi,
>>>>
>>>> Looks like a compilation error.
>>>> So this should not be related to the cluster mode.
>>>> Can you double check that you succeed to compile the code.
>>>>
>>>> Cheers,
>>>>
>>>> Olivier
>>>>
>>>> On 24 Mar 2015, at 18:11, Andre Sznajder
>>>> <email address hidden> wrote:
>>>>
>>>>> Question #257782 on MadGraph5_aMC@NLO changed:
>>>>> https:/
>>>>>
>>>>> Status: Answered => Open
>>>>>
>>>>> Andre Sznajder is still having a problem:
>>>>> Hi Olivier,
>>>>> Ok, I will try to the DECAY code from the older version of Madgraph5 that you pointed to me.
>>>>> Meanwhile I tried made the changes in matrix*.f files for having a single polarization and now I am having a strange compilation error.
>>>>> When I test the changes running interactively I works fine but when I submit it batch using condor I get the following error:
>>>>>
>>>>>> Generating 10000 events with run name run_01
>>>>> survey run_01
>>>>> INFO: compile directory
>>>>> Not able to open file /storage/
>>>>> ured.Please set one in ./input/
>>>>> Using random number seed offset = 21
>>>>> INFO: Running Survey
>>>>> Creating Jobs
>>>>> Working on SubProcesses
>>>>> P1_qq_wpwpqq
>>>>> Error detected in "generate_events "
>>>>> write debug file /storage/
>>>>> If you need help with this issue please contact us on https:/
>>>>> MadGraph5Error : A compilation Error occurs when trying to compile /storage/
>>>>> CD0/SubProcesse
>>>>> The compilation fails with the following output message:
>>>>> gfortran -O -w -fbounds-check -fPIC -ffixed-
>>>>> gfortran -O -w -fbounds-check -fPIC -ffixed-
>>>>> weight.o initcluster.o addmothers.o setscales.o idenparts.o auto_dsig.o auto_dsig1.o auto_dsig2.o auto_dsig3.o auto_dsig4.o auto_dsig5.o auto_dsig6.o auto_dsig7.
>>>>> o matrix1.o matrix2.o matrix3.o matrix4.o matrix5.o matrix6.o matrix7.o -L../../lib/ -ldhelas -ldsample -lmodel -lgeneric -lpdf -lcernlib
>>>>> /usr/lib/
>>>>> (.text+0x20): undefined reference to `main'
>>>>> collect2: error: ld returned 1 exit status
>>>>> make: *** [madevent] Error 1
>>>>>
>>>>> Please try to fix this compilations issue and retry.
>>>>> Help might be found at https:/
>>>>> If you think that this is a bug, you can report this at https:/
>>>>> quit
>>>>>
>>>>>
>>>>> Do you see what could be going wrong ?
>>>>> I have been submitting jobs in batch for ages and never had this problem. I has something to do with the mods I made to matrix*.f but I can figure out why it runs fine iteractively and not in batch …
>>>>> Cheers,
>>>>> Andre
>>>>>
>>>>>
>>>>> On Mar 23, 2015, at 11:31 AM, Olivier Mattelaer
>>>>> <<email address hidden>
>>>>> wrote:
>>>>>
>>>>> Your question #257782 on MadGraph5_aMC@NLO changed:
>>>>> https:/
>>>>>
>>>>> Olivier Mattelaer proposed the following answer:
>>>>> Hi Andre,
>>>>>
>>>>> So i discuss with Fabio to understand how DECAYS was working and this is indeed more accurate that the simple stuff that I did.
>>>>> So we will not have that option in a near future.
>>>>>
>>>>> Cheers,
>>>>>
>>>>> Olivier
>>>>>
>>>>> --
>>>>> If this answers your question, please go to the following page to let us
>>>>> know that it is solved:
>>>>> https:/
>>>>>
>>>>> If you still need help, you can reply to this email or go to the
>>>>> following page to enter your feedback:
>>>>> https:/
>>>>>
>>>>> You received this question notification because you asked the question.
>>>>>
>>>>> =======
>>>>> Andre Sznajder
>>>>> Professor Associado
>>>>> Instituto de Fisica - Dept. DFNAE
>>>>> Universidade do Estado do Rio de Janeiro ( UERJ )
>>>>> Rio de Janeiro, RJ - Brasil
>>>>> Tel.: (+55)(21)23340608 ramal:24 Fax: (+55)(21)23340483
>>>>> Email: <email address hidden>
>>>>> =======
>>>>>
>>>>> --
>>>>> You received this question notification because you are an answer
>>>>> contact for MadGraph5_aMC@NLO.
>>>>
>>>> --
>>>> If this answers your question, please go to the following page to let us
>>>> know that it is solved:
>>>> https:/
>>>>
>>>> If you still need help, you can reply to this email or go to the
>>>> following page to enter your feedback:
>>>> https:/
>>>>
>>>> You received this question notification because you asked the question.
>>>
>>> =======
>>> Andre Sznajder
>>> Professor Associado
>>> Instituto de Fisica - Dept. DFNAE
>>> Universidade do Estado do Rio de Janeiro ( UERJ )
>>> Rio de Janeiro, RJ - Brasil
>>> Tel.: (+55)(21)23340608 ramal:24 Fax: (+55)(21)23340483
>>> Email: <email address hidden>
>>> =======
>>>
>>> --
>>> You received this question notification because you are an answer
>>> contact for MadGraph5_aMC@NLO.
>>
>> --
>> If this answers your question, please go to the following page to let us
>> know that it is solved:
>> https:/
>>
>> If you still need help, you can reply to this email or go to the
>> following page to enter your feedback:
>> https:/
>>
>> You received this question notification because you asked the question.
>
> =======
> Andre Sznajder
> Professor Associado
> Instituto de Fisica - Dept. DFNAE
> Universidade do Estado do Rio de Janeiro ( UERJ )
> Rio de Janeiro, RJ - Brasil
> Tel.: (+55)(21)23340608 ramal:24 Fax: (+55)(21)23340483
> Email: <email address hidden>
> =======
>
> --
> You received this question notification because you are an answer
> contact for MadGraph5_aMC@NLO.
Revision history for this message
|
#23 |
Hi Olivier,
I understand this is not a bug , but an optimization problem.
I think it might be useful to report that if I don’t modify the matrix elements ( matrix*.f ) in order to separate the polarizations LL, LT and TT and generate all modes together , I end up with a higher efficiency:
LL -> 7%
LT -> 38%
TT -> 55%
So, this loss of efficiency is somehow related with having the LL,Land TT modes separated.
Cheers,
Andre
PS: I don’t really need to separate the LL , LT and TT modes because DECAY doesn’t mixes the W polarization so I can have all of them generated together in a single LHE and use the W polarization information in the LHE after the running DECAY.
Cheers,
Andre
> On Mar 27, 2015, at 12:46 PM, Olivier Mattelaer <email address hidden> wrote:
>
> Your question #257782 on MadGraph5_aMC@NLO changed:
> https:/
>
> Status: Open => Answered
>
> Olivier Mattelaer proposed the following answer:
> Hi Andre,
>
> This is not a real bug of our code, just you hit in that case an efficiency limit of our code.
> This is the kind of limitation that we actively discuss to see how we can beat them for a future release.
>
> Cheers,
>
> Olivier
>
>
> On 28 Mar 2015, at 00:31, Andre Sznajder <email address hidden> wrote:
>
>> Question #257782 on MadGraph5_aMC@NLO changed:
>> https:/
>>
>> Andre Sznajder gave more information on the question:
>> Hi Olivier,
>> Concerning the Madevent (MG v2.2.2.3) generation efficiency drop for the WLWL mode, I have asked for 50000 events for the process p p > w w j j QED=4 QCD=0 for each polarization mode.
>> While I get 50000 events for the modes WLWT and WTWT , in the WLWL mode I get only about 400 events ( less than 1% ) !
>> I know 3 other people that reported the same inefficiency problem working completely independently from me …
>> Cheers,
>> Andre
>>
>>
>>> On Mar 25, 2015, at 1:31 PM, Olivier Mattelaer <email address hidden> wrote:
>>>
>>> Your question #257782 on MadGraph5_aMC@NLO changed:
>>> https:/
>>>
>>> Status: Open => Answered
>>>
>>> Olivier Mattelaer proposed the following answer:
>>> Hi Andre,
>>>
>>>
>>> This remind me the only code I ever fix in DECAY, did you use the version which was coming from MG51.5.14?
>>> Otherwise I do not know that much (actually I only read part of this code once). So I will be as bad as you to debug that old code.
>>> This is one of the reason that we remove it since actually no one is able to provide support to this code, since basically no one knows how it works.
>>>
>>> Cheers,
>>>
>>> Olivier
>>>
>>> On 26 Mar 2015, at 00:56, Andre Sznajder
>>> <email address hidden> wrote:
>>>
>>>> Question #257782 on MadGraph5_aMC@NLO changed:
>>>> https:/
>>>>
>>>> Status: Answered => Open
>>>>
>>>> Andre Sznajder is still having a problem:
>>>> Hi Olivier,
>>>> I found my mistake and now the Madevent runs fine, but when it comes to run DECAY I am having the error bellow.
>>>> Would it be possible that DECAY doesn’t know how to read the parameter info from the LHE created by MG 5.2.2.3 ?
>>>> Cheers,
>>>> Andre
>>>>
>>>>
>>>> [sznajder@cmslpc27 DECAY]$ ./decay
>>>> *******
>>>> * DECAY *
>>>> * a MadEvent program *
>>>> * for decaying unstable particles *
>>>> * in the Standar Model *
>>>> * -------
>>>> * version compliant with MG_ME_V4.0 *
>>>> * *
>>>> * 27-July-2006 *
>>>> *******
>>>>
>>>> Input run mode:
>>>> ---------------
>>>>
>>>> 0 = calculates decay widths
>>>> 1 = decay events in file
>>>>
>>>> 1
>>>> *******
>>>> * reading seed from iseed.dat *
>>>> * rnd number seed = -13 *
>>>> *******
>>>> *******
>>>> * run_mode=1 => decaying events *
>>>> * *
>>>> * Using the param_card.dat in the banner for *
>>>> * the input params. *
>>>> * *
>>>> * >>>>>>Total widths are recalculated here<<<<< *
>>>> *******
>>>> input event file: (e.g. events.lhe)
>>>> unweighted_
>>>> name for output file: (e.g. dec-events.lhe)
>>>> unweighted_
>>>> At line 484 of file decay_couplings.f
>>>> Fortran runtime error: End of file
>>>>
>>>>
>>>>
>>>>> On Mar 24, 2015, at 7:01 AM, Olivier Mattelaer <email address hidden> wrote:
>>>>>
>>>>> Your question #257782 on MadGraph5_aMC@NLO changed:
>>>>> https:/
>>>>>
>>>>> Status: Open => Answered
>>>>>
>>>>> Olivier Mattelaer proposed the following answer:
>>>>> Hi,
>>>>>
>>>>> Looks like a compilation error.
>>>>> So this should not be related to the cluster mode.
>>>>> Can you double check that you succeed to compile the code.
>>>>>
>>>>> Cheers,
>>>>>
>>>>> Olivier
>>>>>
>>>>> On 24 Mar 2015, at 18:11, Andre Sznajder
>>>>> <email address hidden> wrote:
>>>>>
>>>>>> Question #257782 on MadGraph5_aMC@NLO changed:
>>>>>> https:/
>>>>>>
>>>>>> Status: Answered => Open
>>>>>>
>>>>>> Andre Sznajder is still having a problem:
>>>>>> Hi Olivier,
>>>>>> Ok, I will try to the DECAY code from the older version of Madgraph5 that you pointed to me.
>>>>>> Meanwhile I tried made the changes in matrix*.f files for having a single polarization and now I am having a strange compilation error.
>>>>>> When I test the changes running interactively I works fine but when I submit it batch using condor I get the following error:
>>>>>>
>>>>>>> Generating 10000 events with run name run_01
>>>>>> survey run_01
>>>>>> INFO: compile directory
>>>>>> Not able to open file /storage/
>>>>>> ured.Please set one in ./input/
>>>>>> Using random number seed offset = 21
>>>>>> INFO: Running Survey
>>>>>> Creating Jobs
>>>>>> Working on SubProcesses
>>>>>> P1_qq_wpwpqq
>>>>>> Error detected in "generate_events "
>>>>>> write debug file /storage/
>>>>>> If you need help with this issue please contact us on https:/
>>>>>> MadGraph5Error : A compilation Error occurs when trying to compile /storage/
>>>>>> CD0/SubProcesse
>>>>>> The compilation fails with the following output message:
>>>>>> gfortran -O -w -fbounds-check -fPIC -ffixed-
>>>>>> gfortran -O -w -fbounds-check -fPIC -ffixed-
>>>>>> weight.o initcluster.o addmothers.o setscales.o idenparts.o auto_dsig.o auto_dsig1.o auto_dsig2.o auto_dsig3.o auto_dsig4.o auto_dsig5.o auto_dsig6.o auto_dsig7.
>>>>>> o matrix1.o matrix2.o matrix3.o matrix4.o matrix5.o matrix6.o matrix7.o -L../../lib/ -ldhelas -ldsample -lmodel -lgeneric -lpdf -lcernlib
>>>>>> /usr/lib/
>>>>>> (.text+0x20): undefined reference to `main'
>>>>>> collect2: error: ld returned 1 exit status
>>>>>> make: *** [madevent] Error 1
>>>>>>
>>>>>> Please try to fix this compilations issue and retry.
>>>>>> Help might be found at https:/
>>>>>> If you think that this is a bug, you can report this at https:/
>>>>>> quit
>>>>>>
>>>>>>
>>>>>> Do you see what could be going wrong ?
>>>>>> I have been submitting jobs in batch for ages and never had this problem. I has something to do with the mods I made to matrix*.f but I can figure out why it runs fine iteractively and not in batch …
>>>>>> Cheers,
>>>>>> Andre
>>>>>>
>>>>>>
>>>>>> On Mar 23, 2015, at 11:31 AM, Olivier Mattelaer
>>>>>> <<email address hidden>
>>>>>> wrote:
>>>>>>
>>>>>> Your question #257782 on MadGraph5_aMC@NLO changed:
>>>>>> https:/
>>>>>>
>>>>>> Olivier Mattelaer proposed the following answer:
>>>>>> Hi Andre,
>>>>>>
>>>>>> So i discuss with Fabio to understand how DECAYS was working and this is indeed more accurate that the simple stuff that I did.
>>>>>> So we will not have that option in a near future.
>>>>>>
>>>>>> Cheers,
>>>>>>
>>>>>> Olivier
>>>>>>
>>>>>> --
>>>>>> If this answers your question, please go to the following page to let us
>>>>>> know that it is solved:
>>>>>> https:/
>>>>>>
>>>>>> If you still need help, you can reply to this email or go to the
>>>>>> following page to enter your feedback:
>>>>>> https:/
>>>>>>
>>>>>> You received this question notification because you asked the question.
>>>>>>
>>>>>> =======
>>>>>> Andre Sznajder
>>>>>> Professor Associado
>>>>>> Instituto de Fisica - Dept. DFNAE
>>>>>> Universidade do Estado do Rio de Janeiro ( UERJ )
>>>>>> Rio de Janeiro, RJ - Brasil
>>>>>> Tel.: (+55)(21)23340608 ramal:24 Fax: (+55)(21)23340483
>>>>>> Email: <email address hidden>
>>>>>> =======
>>>>>>
>>>>>> --
>>>>>> You received this question notification because you are an answer
>>>>>> contact for MadGraph5_aMC@NLO.
>>>>>
>>>>> --
>>>>> If this answers your question, please go to the following page to let us
>>>>> know that it is solved:
>>>>> https:/
>>>>>
>>>>> If you still need help, you can reply to this email or go to the
>>>>> following page to enter your feedback:
>>>>> https:/
>>>>>
>>>>> You received this question notification because you asked the question.
>>>>
>>>> =======
>>>> Andre Sznajder
>>>> Professor Associado
>>>> Instituto de Fisica - Dept. DFNAE
>>>> Universidade do Estado do Rio de Janeiro ( UERJ )
>>>> Rio de Janeiro, RJ - Brasil
>>>> Tel.: (+55)(21)23340608 ramal:24 Fax: (+55)(21)23340483
>>>> Email: <email address hidden>
>>>> =======
>>>>
>>>> --
>>>> You received this question notification because you are an answer
>>>> contact for MadGraph5_aMC@NLO.
>>>
>>> --
>>> If this answers your question, please go to the following page to let us
>>> know that it is solved:
>>> https:/
>>>
>>> If you still need help, you can reply to this email or go to the
>>> following page to enter your feedback:
>>> https:/
>>>
>>> You received this question notification because you asked the question.
>>
>> =======
>> Andre Sznajder
>> Professor Associado
>> Instituto de Fisica - Dept. DFNAE
>> Universidade do Estado do Rio de Janeiro ( UERJ )
>> Rio de Janeiro, RJ - Brasil
>> Tel.: (+55)(21)23340608 ramal:24 Fax: (+55)(21)23340483
>> Email: <email address hidden>
>> =======
>>
>> --
>> You received this question notification because you are an answer
>> contact for MadGraph5_aMC@NLO.
>
> --
> If this answers your question, please go to the following page to let us
> know that it is solved:
> https:/
>
> If you still need help, you can reply to this email or go to the
> following page to enter your feedback:
> https:/
>
> You received this question notification because you asked the question.
=======
Andre Sznajder
Professor Associado
Instituto de Fisica - Dept. DFNAE
Universidade do Estado do Rio de Janeiro ( UERJ )
Rio de Janeiro, RJ - Brasil
Tel.: (+55)(21)23340608 ramal:24 Fax: (+55)(21)23340483
Email: <email address hidden>
=======
Revision history for this message
|
#24 |
Thanks Andre,
This is indeed a useful information.
Cheers,
Olivier
On 29 Mar 2015, at 15:16, Andre Sznajder <email address hidden> wrote:
> Question #257782 on MadGraph5_aMC@NLO changed:
> https:/
>
> Status: Answered => Open
>
> Andre Sznajder is still having a problem:
> Hi Olivier,
> I understand this is not a bug , but an optimization problem.
> I think it might be useful to report that if I don’t modify the matrix elements ( matrix*.f ) in order to separate the polarizations LL, LT and TT and generate all modes together , I end up with a higher efficiency:
> LL -> 7%
> LT -> 38%
> TT -> 55%
> So, this loss of efficiency is somehow related with having the LL,Land TT modes separated.
> Cheers,
> Andre
>
> PS: I don’t really need to separate the LL , LT and TT modes because DECAY doesn’t mixes the W polarization so I can have all of them generated together in a single LHE and use the W polarization information in the LHE after the running DECAY.
> Cheers,
> Andre
>
>
>
>> On Mar 27, 2015, at 12:46 PM, Olivier Mattelaer <email address hidden> wrote:
>>
>> Your question #257782 on MadGraph5_aMC@NLO changed:
>> https:/
>>
>> Status: Open => Answered
>>
>> Olivier Mattelaer proposed the following answer:
>> Hi Andre,
>>
>> This is not a real bug of our code, just you hit in that case an efficiency limit of our code.
>> This is the kind of limitation that we actively discuss to see how we can beat them for a future release.
>>
>> Cheers,
>>
>> Olivier
>>
>>
>> On 28 Mar 2015, at 00:31, Andre Sznajder <email address hidden> wrote:
>>
>>> Question #257782 on MadGraph5_aMC@NLO changed:
>>> https:/
>>>
>>> Andre Sznajder gave more information on the question:
>>> Hi Olivier,
>>> Concerning the Madevent (MG v2.2.2.3) generation efficiency drop for the WLWL mode, I have asked for 50000 events for the process p p > w w j j QED=4 QCD=0 for each polarization mode.
>>> While I get 50000 events for the modes WLWT and WTWT , in the WLWL mode I get only about 400 events ( less than 1% ) !
>>> I know 3 other people that reported the same inefficiency problem working completely independently from me …
>>> Cheers,
>>> Andre
>>>
>>>
>>>> On Mar 25, 2015, at 1:31 PM, Olivier Mattelaer <email address hidden> wrote:
>>>>
>>>> Your question #257782 on MadGraph5_aMC@NLO changed:
>>>> https:/
>>>>
>>>> Status: Open => Answered
>>>>
>>>> Olivier Mattelaer proposed the following answer:
>>>> Hi Andre,
>>>>
>>>>
>>>> This remind me the only code I ever fix in DECAY, did you use the version which was coming from MG51.5.14?
>>>> Otherwise I do not know that much (actually I only read part of this code once). So I will be as bad as you to debug that old code.
>>>> This is one of the reason that we remove it since actually no one is able to provide support to this code, since basically no one knows how it works.
>>>>
>>>> Cheers,
>>>>
>>>> Olivier
>>>>
>>>> On 26 Mar 2015, at 00:56, Andre Sznajder
>>>> <email address hidden> wrote:
>>>>
>>>>> Question #257782 on MadGraph5_aMC@NLO changed:
>>>>> https:/
>>>>>
>>>>> Status: Answered => Open
>>>>>
>>>>> Andre Sznajder is still having a problem:
>>>>> Hi Olivier,
>>>>> I found my mistake and now the Madevent runs fine, but when it comes to run DECAY I am having the error bellow.
>>>>> Would it be possible that DECAY doesn’t know how to read the parameter info from the LHE created by MG 5.2.2.3 ?
>>>>> Cheers,
>>>>> Andre
>>>>>
>>>>>
>>>>> [sznajder@cmslpc27 DECAY]$ ./decay
>>>>> *******
>>>>> * DECAY *
>>>>> * a MadEvent program *
>>>>> * for decaying unstable particles *
>>>>> * in the Standar Model *
>>>>> * -------
>>>>> * version compliant with MG_ME_V4.0 *
>>>>> * *
>>>>> * 27-July-2006 *
>>>>> *******
>>>>>
>>>>> Input run mode:
>>>>> ---------------
>>>>>
>>>>> 0 = calculates decay widths
>>>>> 1 = decay events in file
>>>>>
>>>>> 1
>>>>> *******
>>>>> * reading seed from iseed.dat *
>>>>> * rnd number seed = -13 *
>>>>> *******
>>>>> *******
>>>>> * run_mode=1 => decaying events *
>>>>> * *
>>>>> * Using the param_card.dat in the banner for *
>>>>> * the input params. *
>>>>> * *
>>>>> * >>>>>>Total widths are recalculated here<<<<< *
>>>>> *******
>>>>> input event file: (e.g. events.lhe)
>>>>> unweighted_
>>>>> name for output file: (e.g. dec-events.lhe)
>>>>> unweighted_
>>>>> At line 484 of file decay_couplings.f
>>>>> Fortran runtime error: End of file
>>>>>
>>>>>
>>>>>
>>>>>> On Mar 24, 2015, at 7:01 AM, Olivier Mattelaer <email address hidden> wrote:
>>>>>>
>>>>>> Your question #257782 on MadGraph5_aMC@NLO changed:
>>>>>> https:/
>>>>>>
>>>>>> Status: Open => Answered
>>>>>>
>>>>>> Olivier Mattelaer proposed the following answer:
>>>>>> Hi,
>>>>>>
>>>>>> Looks like a compilation error.
>>>>>> So this should not be related to the cluster mode.
>>>>>> Can you double check that you succeed to compile the code.
>>>>>>
>>>>>> Cheers,
>>>>>>
>>>>>> Olivier
>>>>>>
>>>>>> On 24 Mar 2015, at 18:11, Andre Sznajder
>>>>>> <email address hidden> wrote:
>>>>>>
>>>>>>> Question #257782 on MadGraph5_aMC@NLO changed:
>>>>>>> https:/
>>>>>>>
>>>>>>> Status: Answered => Open
>>>>>>>
>>>>>>> Andre Sznajder is still having a problem:
>>>>>>> Hi Olivier,
>>>>>>> Ok, I will try to the DECAY code from the older version of Madgraph5 that you pointed to me.
>>>>>>> Meanwhile I tried made the changes in matrix*.f files for having a single polarization and now I am having a strange compilation error.
>>>>>>> When I test the changes running interactively I works fine but when I submit it batch using condor I get the following error:
>>>>>>>
>>>>>>>> Generating 10000 events with run name run_01
>>>>>>> survey run_01
>>>>>>> INFO: compile directory
>>>>>>> Not able to open file /storage/
>>>>>>> ured.Please set one in ./input/
>>>>>>> Using random number seed offset = 21
>>>>>>> INFO: Running Survey
>>>>>>> Creating Jobs
>>>>>>> Working on SubProcesses
>>>>>>> P1_qq_wpwpqq
>>>>>>> Error detected in "generate_events "
>>>>>>> write debug file /storage/
>>>>>>> If you need help with this issue please contact us on https:/
>>>>>>> MadGraph5Error : A compilation Error occurs when trying to compile /storage/
>>>>>>> CD0/SubProcesse
>>>>>>> The compilation fails with the following output message:
>>>>>>> gfortran -O -w -fbounds-check -fPIC -ffixed-
>>>>>>> gfortran -O -w -fbounds-check -fPIC -ffixed-
>>>>>>> weight.o initcluster.o addmothers.o setscales.o idenparts.o auto_dsig.o auto_dsig1.o auto_dsig2.o auto_dsig3.o auto_dsig4.o auto_dsig5.o auto_dsig6.o auto_dsig7.
>>>>>>> o matrix1.o matrix2.o matrix3.o matrix4.o matrix5.o matrix6.o matrix7.o -L../../lib/ -ldhelas -ldsample -lmodel -lgeneric -lpdf -lcernlib
>>>>>>> /usr/lib/
>>>>>>> (.text+0x20): undefined reference to `main'
>>>>>>> collect2: error: ld returned 1 exit status
>>>>>>> make: *** [madevent] Error 1
>>>>>>>
>>>>>>> Please try to fix this compilations issue and retry.
>>>>>>> Help might be found at https:/
>>>>>>> If you think that this is a bug, you can report this at https:/
>>>>>>> quit
>>>>>>>
>>>>>>>
>>>>>>> Do you see what could be going wrong ?
>>>>>>> I have been submitting jobs in batch for ages and never had this problem. I has something to do with the mods I made to matrix*.f but I can figure out why it runs fine iteractively and not in batch …
>>>>>>> Cheers,
>>>>>>> Andre
>>>>>>>
>>>>>>>
>>>>>>> On Mar 23, 2015, at 11:31 AM, Olivier Mattelaer
>>>>>>> <<email address hidden>
>>>>>>> wrote:
>>>>>>>
>>>>>>> Your question #257782 on MadGraph5_aMC@NLO changed:
>>>>>>> https:/
>>>>>>>
>>>>>>> Olivier Mattelaer proposed the following answer:
>>>>>>> Hi Andre,
>>>>>>>
>>>>>>> So i discuss with Fabio to understand how DECAYS was working and this is indeed more accurate that the simple stuff that I did.
>>>>>>> So we will not have that option in a near future.
>>>>>>>
>>>>>>> Cheers,
>>>>>>>
>>>>>>> Olivier
>>>>>>>
>>>>>>> --
>>>>>>> If this answers your question, please go to the following page to let us
>>>>>>> know that it is solved:
>>>>>>> https:/
>>>>>>>
>>>>>>> If you still need help, you can reply to this email or go to the
>>>>>>> following page to enter your feedback:
>>>>>>> https:/
>>>>>>>
>>>>>>> You received this question notification because you asked the question.
>>>>>>>
>>>>>>> =======
>>>>>>> Andre Sznajder
>>>>>>> Professor Associado
>>>>>>> Instituto de Fisica - Dept. DFNAE
>>>>>>> Universidade do Estado do Rio de Janeiro ( UERJ )
>>>>>>> Rio de Janeiro, RJ - Brasil
>>>>>>> Tel.: (+55)(21)23340608 ramal:24 Fax: (+55)(21)23340483
>>>>>>> Email: <email address hidden>
>>>>>>> =======
>>>>>>>
>>>>>>> --
>>>>>>> You received this question notification because you are an answer
>>>>>>> contact for MadGraph5_aMC@NLO.
>>>>>>
>>>>>> --
>>>>>> If this answers your question, please go to the following page to let us
>>>>>> know that it is solved:
>>>>>> https:/
>>>>>>
>>>>>> If you still need help, you can reply to this email or go to the
>>>>>> following page to enter your feedback:
>>>>>> https:/
>>>>>>
>>>>>> You received this question notification because you asked the question.
>>>>>
>>>>> =======
>>>>> Andre Sznajder
>>>>> Professor Associado
>>>>> Instituto de Fisica - Dept. DFNAE
>>>>> Universidade do Estado do Rio de Janeiro ( UERJ )
>>>>> Rio de Janeiro, RJ - Brasil
>>>>> Tel.: (+55)(21)23340608 ramal:24 Fax: (+55)(21)23340483
>>>>> Email: <email address hidden>
>>>>> =======
>>>>>
>>>>> --
>>>>> You received this question notification because you are an answer
>>>>> contact for MadGraph5_aMC@NLO.
>>>>
>>>> --
>>>> If this answers your question, please go to the following page to let us
>>>> know that it is solved:
>>>> https:/
>>>>
>>>> If you still need help, you can reply to this email or go to the
>>>> following page to enter your feedback:
>>>> https:/
>>>>
>>>> You received this question notification because you asked the question.
>>>
>>> =======
>>> Andre Sznajder
>>> Professor Associado
>>> Instituto de Fisica - Dept. DFNAE
>>> Universidade do Estado do Rio de Janeiro ( UERJ )
>>> Rio de Janeiro, RJ - Brasil
>>> Tel.: (+55)(21)23340608 ramal:24 Fax: (+55)(21)23340483
>>> Email: <email address hidden>
>>> =======
>>>
>>> --
>>> You received this question notification because you are an answer
>>> contact for MadGraph5_aMC@NLO.
>>
>> --
>> If this answers your question, please go to the following page to let us
>> know that it is solved:
>> https:/
>>
>> If you still need help, you can reply to this email or go to the
>> following page to enter your feedback:
>> https:/
>>
>> You received this question notification because you asked the question.
>
> =======
> Andre Sznajder
> Professor Associado
> Instituto de Fisica - Dept. DFNAE
> Universidade do Estado do Rio de Janeiro ( UERJ )
> Rio de Janeiro, RJ - Brasil
> Tel.: (+55)(21)23340608 ramal:24 Fax: (+55)(21)23340483
> Email: <email address hidden>
> =======
>
> --
> You received this question notification because you are an answer
> contact for MadGraph5_aMC@NLO.
Can you help with this problem?
Provide an answer of your own, or ask Andre Sznajder for more information if necessary.