MadGraph5_aMC@NLO

Merge lp:~maddevelopers/mg5amcnlo/FKS5 into lp:mg5amcnlo/lts

FKS5
Merge into series2.0

Proposed by Olivier Mattelaer on 2012-03-15

Status:	Merged
Merged at revision:	182
Proposed branch:	lp:~maddevelopers/mg5amcnlo/FKS5
Merge into:	lp:mg5amcnlo/lts
Diff against target:	341349 lines
To merge this branch:	bzr merge lp:~maddevelopers/mg5amcnlo/FKS5
Related bugs:	Link a bug report

Reviewer	Review Type	Date Requested	Status
Johan Alwall (community)			Needs Fixing on 2012-09-28
Olivier Mattelaer			Needs Fixing on 2012-09-19
Review via email: mp+97762@code.launchpad.net

Description of the change

Hi guys,

Since I start to implement things in the code, I start to have a bunch of comment.
So I propose to open a merge discussion on the current situation. I realize that this is not in the merge status but this will allow to better keep track of the (probably long) e-change of email.

When you will be ready for the real merge. We can open thread if you like. (or continue on this one, this is as you want.

Revision history for this message

Olivier Mattelaer (olivier-mattelaer) wrote on 2012-03-15:

Download full text (6.5 KiB)

Hi guys,

So this is my first round of observation:

If you read the review that I did in the past, you will not be surprise that I have usually A LOT of comment, since you did a lot of (great) work, this will means a huge numbers of comments.

So In each email, I will put a number with each comment and will keep those number unique.
Let's try to future email to keep track of the un-resolve comment at the end of the mails.
This will ensure that we will not drop some comments in the flow.

So let's start:

1) in loop_exporters, will not makes sense to have one routine by file written?
2) dans loop_num.inc, they are text after the column 77 (with a lot of space in the line)
3) Why using LW and not explicitely ZERO?
4) ALL the HELP/ Completion
   --> Help are VERY important and are for the moment only LO...
5) in master_cmd:
   I think that we need to separate the dummy function from those which are really modified.
   (this will be much more clear and much more easy to see what happen in the future)
6) Error in the input format should raised self.InvalidCmd and NOT MadGraph5Error!!!
(in debug mode this doesn't change anything but in production mode it does)

7) in master_cmd:
You have:
def do_generate(self, line, *args, **opts):

    Two points here:
    a) this should be a self.InvalidCmd and not MadGraph5Error (as point above)
    b) the last line should be % (nlo_mode, ' '.join(self._valid_nlo_modes))

8) File "/Users/omatt/Documents/Eclipse/CMS_NLO/madgraph/core/base_objects.py", line 2529, in has_multiparticle_label
return false
should be False

Hi guys,

So this is my first round of observation:

If you read the review that I did in the past, you will not be surprise that I have usually A LOT of comment, since you did a lot of (great) work, this will means a huge numbers of comments.

So let's start:

7) in master_cmd:
   You have:
    def do_generate(self, line, *args, **opts):

argss = cmd.Cmd.split_arg(line)
        # Make sure to switch to the right interface.
        if len(argss)>=1:            
            proc_line = ' '.join(argss[1:])
            (type,nlo_mode,orders)=self.extract_process_type(proc_line)
            if type=='NLO':
                if not nlo_mode in self._valid_nlo_modes: raise MadGraph5Error, \
                    'The NLO mode %s is not valid. Please chose one among: %s' \
                    % (nlo_mode, ' '.join(valid_nlo_modes))
                    
    Two points here: 
    a) this should be a self.InvalidCmd and not MadGraph5Error (as point above)
    b) the last line should be % (nlo_mode, ' '.join(self._valid_nlo_modes))
    
8) File "/Users/omatt/Documents/Eclipse/CMS_NLO/madgraph/core/base_objects.py", line 2529, in has_multiparticle_label
    return false
should be False

9) one error that I don't understand:
generate p p > u u~ [virt=QCD]
Traceback (most recent call last):
  File "/Users/omatt/Documents/Eclipse/CMS_NLO/madgraph/interface/extended_cmd.py", line 518, in onecmd
    return cmd.Cmd.onecmd(self, line)
  File "/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/cmd.py", line 219, in onecmd
    return func(arg)
  File "/Users/omatt/Documents/Eclipse/CMS_NLO/madgraph/interface/master_interface.py", line 338, in do_generate
    return self.cmd.do_generate(self, line, *args, **opts)
  File "/Users/omatt/Documents/Eclipse/CMS_NLO/madgraph/interface/Loop_interface.py", line 58, in do_generate
    mg_interface.MadGraphCmd.do_generate(self, *args,**opt)
  File "/Users/omatt/Documents/Eclipse/CMS_NLO/madgraph/interface/madgraph_interface.py", line 2275, in do_generate
    self.do_add(" ".join(args))
  File "/Users/omatt/Documents/Eclipse/CMS_NLO/madgraph/interface/master_interface.py", line 287, in do_add
    return self.cmd.do_add(self, line, *args, **opts)
  File "/Users/omatt/Documents/Eclipse/CMS_NLO/madgraph/interface/Loop_interface.py", line 293, in do_add
    ignore_six_quark_processes = False)
  File "/Users/omatt/Documents/Eclipse/CMS_NLO/madgraph/core/diagram_generation.py", line 1246, in __init__
    self.get('amplitudes')
  File "/Users/omatt/Documents/Eclipse/CMS_NLO/madgraph/core/diagram_generation.py", line 1290, in get
    self.get('ignore_six_quark_processes')))
  File "/Users/omatt/Documents/Eclipse/CMS_NLO/madgraph/core/diagram_generation.py", line 1449, in generate_multi_amplitudes
    permutation)
  File "/Users/omatt/Documents/Eclipse/CMS_NLO/madgraph/core/diagram_generation.py", line 1678, in cross_amplitude
    d in new_amp.get('diagrams')])
  File "/Users/omatt/Documents/Eclipse/CMS_NLO/madgraph/core/base_objects.py", line 1819, in renumber_legs
    leg.set('number', min_dict[leg.get('number')])
KeyError: 5

10) generate g g > g g []
generate LO (I would prefer an error)

11) generate g g > g g [virt] fails and return a weird message:
MadGraph5Error : FKS for reals only available in QCD for now, you asked virt

12) ML5>launch fails
import model sm
generate g g > g g [virt=QCD]
output standalone
launch
Traceback (most recent call last):
  File "/Users/omatt/Documents/Eclipse/CMS_NLO/madgraph/interface/extended_cmd.py", line 518, in onecmd
    return cmd.Cmd.onecmd(self, line)
  File "/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/cmd.py", line 219, in onecmd
    return func(arg)
  File "/Users/omatt/Documents/Eclipse/CMS_NLO/madgraph/interface/master_interface.py", line 363, in do_launch
    return self.cmd.do_launch(self, *args, **opts)
  File "/Users/omatt/Documents/Eclipse/CMS_NLO/madgraph/interface/madgraph_interface.py", line 3125, in do_launch
    **options)
TypeError: __init__() takes exactly 4 arguments (3 given)

13) is there a test for the writing of the loop part (I changed the way to write the argument and no test indicates me that this is problematic)

I will also put here the previous email in order to keep track of those coments also.

14) You should think to refactorize your unit-test
25 min for the unitest suite is much too-long (the unit-test cann't be longer than a couple of minuts)
it's in fact event longer that the acceptance suite, which doesn't really makes sense.
(This one should takes around 20 mins)

15) I've pointed those lines in madgraph_cmd line 1651
       # Set where to look for CutTools installation.
       # In further versions, it will be set in the same manner as _mgme_dir so that
       # the user can chose its own CutTools distribution.
       self._cuttools_dir=str(os.path.join(self._mgme_dir,'loop_material','CutTools'))
       if not os.path.isdir(os.path.join(self._cuttools_dir, 'src','cts')):
           logger.warning(('Warning: Directory %s is not a valid CutTools directory.'+\
                          'Using default CutTools instead.') % \
                            self._cuttools_dir)
           self._cuttools_dir=str(os.path.join(self._mgme_dir,'loop_material','CutTools'))

Those lines shouldn't be in the LO part.

16) We should have only one Template directory. They should all be inside The current Template
(I force Pierre to do the same for MW files)
With a subdirectory for LO / MW / FKSReal / FKSborn / ...

17) We should think about a NLO tutorial
something like tutorial NLO

18) the directory loop_material/CutTools/includects/ should not be include in bzr.

That's it for today.

Thanks,

Olivier

review: Needs Fixing

lp:~maddevelopers/mg5amcnlo/FKS5 updated on 2012-03-16

177. By mattelaer-olivier on 2012-03-16: fix the drawing (after an output is done)
remove the versioned file present in loop_material/CutTools/includects/

Revision history for this message

Olivier Mattelaer (olivier-mattelaer) wrote on 2012-03-16:

Hi again, here is some additional points:

19) in file process_check at line 406 you have:
        from tests.parallel_tests.loop_me_comparator import LoopMG5Runner
    I don't like the idea to have some code present in the tests directory.
    In fact, we should be able to remove this directory for any release. We didn't do that yet,
    but we should. so please re-factorize that.

20) File "/Users/omatt/Documents/Eclipse/CMS_NLO/tests/parallel_tests/loop_me_comparator.py"
    line 39, in <module>
    import madgraph.iolibs.misc as misc
   this files is now madgraph.various.misc.py (this probably passes the 1.4.3 merging)
   I checked that's the only wrong import related

21) the routine def has_multiparticle_label(self):
in core/base_objects
returns either None or False.... this does not seems right. (So this is the routine that need to be checked). Will also be useful to add a simple unit test for this routine ;-)

Note: concerning my comment #9
a) this might be due to the point 21
b) I obtained the same error if I call
HelasMatrixElement
instead of LoopHelasMatrixElement.

lp:~maddevelopers/mg5amcnlo/FKS5 updated on 2012-03-19

178. By Valentin Hirschi <email address hidden> on 2012-03-19: 1. Fixed Olivier's latest push
2. Now FKS5 can generate the real only starting from a tree-level model.
179. By Valentin Hirschi <email address hidden> on 2012-03-19: 1. Fixing 1) to 11) of Olivier's review points (except for 4) )

Revision history for this message

Olivier Mattelaer (olivier-mattelaer) wrote on 2012-03-19:

Download full text (9.2 KiB)

Hi Valentin,

Thanks for your prompt reply and fix. ( your reply didn't appear on
launchpad,... don't know why....)

> 1)
> It is the case no? I mean, practically there is one function per
> file output. The structure is a bit less trivial that at LO because
> there is the possibility of putting all files relevant to
> loop_matrix.f into a single fortran source code if the user asks for
> the matrix output.
> Also, if the number of helas calls gets too large, there is the
> possibility of splitting both the HelasCalls and the JAMP definition
> to make the compilation possible.
> But, besides these complications, there is one function per file
> written out.

Yes and no, in fact the .inc are define in the same time as the file
which calling those.
But ok.

> 2)
> Ok, this is funny. My aim is to output the following code:

Since I don't think this is f77 compatible, I don't want to include
such code in LO part ;-)
In your case, I would say that it makes a lot of sense to modify the
FortranWriter

> 4) (concerning help/completion)
>
> Mhh, I know they matter, but ok, later ^^.

To my experience, the sooner is the better for that.
Also for Johan and I this help us to learn the code otherwise this is
very hard to know what is allowed.

> 9) Ok, now LoopInterface correctly forbids processes containing
> multiple particles labels. FKS5 is meant for that after all.

I think that multiparticles are very usefull for the user.
generate p p > W+ j j is something quite natural and very important to
support (at all level). This is something very important
since this simplifies a lot to life for the user.

> 10) Mhh my idea about this was that maybe we would like to specify
> the squared order for tree-level processes as well (for the HIG
> order for example). And then the [] plays the role of a delimiter
> just fine. So I'd prefer to keep it like this.

Not really like this syntax, since this is far to be readable...
why not something like that then
p p > g g QCD=2 {NP=2}

which will do the following syntqx
PROCESS RESTRICTION ORDER [LOOP_INFO] {AMP_ORDER} @#
with all option can be switched in order?
(by restriction I mean / $ $$)

We can maybe have a skype meeting on this.

> 11) The logic goes like this:
> a) There are no specified options with the '=' delimiter, so
> that the default is that both real and virtual corrections are
> applied.
> b) Given a), it is now the FKS5 interface which treats the
> process and first check that the perturbation order asked for is
> exactly QCD (as none other is supported so far). FKS5 interfaces
> reckognizes that the perturbation order asked for is 'virt' (which
> is correct as this is exactly what you would put if you had a model
> with a 'virt' order defined and being perturbed) and therefore
> complains.
>
> So tell me at which point you would like this kind of request
> to be handled differently. Because apart from a dedicated check for
> this special form of input line, i don't see how we could do it
> differently.

I will just handle two special tag for [virt] and [real]

Otherwise some additional points:

19) Marco, Do you nee...

Hi Valentin,

Thanks for your prompt reply and fix. ( your reply didn't appear on  
launchpad,... don't know why....)

> 1)
>    It is the case no? I mean, practically there is one function per  
> file output. The structure is a bit less trivial that at LO because  
> there is the possibility of putting all files relevant to  
> loop_matrix.f into a single fortran source code if the user asks for  
> the matrix output.
> Also, if the number of helas calls gets too large, there is the  
> possibility of splitting both the HelasCalls and the JAMP definition  
> to make the compilation possible.
> But, besides these complications, there is one function per file  
> written out.

Yes and no, in fact the .inc are define in the same time as the file  
which calling those.
But ok.

> 2)
> Ok, this is funny. My aim is to output the following code:

Since I don't think this is f77 compatible, I don't want to include  
such code in LO part ;-)
In your case, I would say that it makes a lot of sense to modify the   
FortranWriter

> 4) (concerning help/completion)
>
> Mhh, I know they matter, but ok, later ^^.

To my experience, the sooner is the better for that.
Also for Johan and I this help us to learn the code otherwise this is  
very hard to know what is allowed.

> 9) Ok, now LoopInterface correctly forbids processes containing  
> multiple particles labels. FKS5 is meant for that after all.

I think that multiparticles are very usefull for the user.
generate p p > W+ j j is something quite natural and very important to  
support (at all level). This is something very important
since  this simplifies a lot to life for the user.

> 10) Mhh my idea about this was that maybe we would like to specify  
> the squared order for tree-level processes as well (for the HIG  
> order for example). And then the [] plays the role of a delimiter  
> just fine. So I'd prefer to keep it like this.

Not really like this syntax, since this is far to be readable...
why not something like that then
p p > g g QCD=2  {NP=2}

which will do the following syntqx
PROCESS RESTRICTION ORDER [LOOP_INFO] {AMP_ORDER} @#
with all option can be switched in order?
(by restriction I mean / $ $$)

We can maybe have a skype meeting on this.

> 11) The logic goes like this:
>       a) There are no specified options with the '=' delimiter, so  
> that the default is that both real and virtual corrections are  
> applied.
>       b) Given a), it is now the FKS5 interface which treats the  
> process and first check that the perturbation order asked for is  
> exactly QCD (as none other is supported so far). FKS5 interfaces  
> reckognizes that the perturbation order asked for is 'virt' (which  
> is correct as this is exactly what you would put if you had a model  
> with a 'virt' order defined and being perturbed) and therefore  
> complains.
>
>      So tell me at which point you would like this kind of request  
> to be handled differently. Because apart from a dedicated check for  
> this special form of input line, i don't see how we could do it  
> differently.

I will just handle two special tag for [virt] and [real]

Otherwise some additional points:

19) Marco, Do you need to have the Delphes Card in the FKS Template?  
those files are already present in the MadEvent Template.
It's pointless to have two times the same files present (but if they  
are a reason off course)

20) The command display diagrams crashes for NLO processes:
import model sm
generate g g > g g [QCD]
display diagrams
Command "display diagrams" interrupted with error:
InvalidCmd : No process generated, please generate a process!
(This was working on the NLO branch before)

21) The same after an output (We can look together for those two if  
you want)

22) They are no file index.html.
        Those are a very nice feature of MG, since this gives  
information of what was generated and helped a lot the user to find  
relevant information.
        (what are the subproceses, what are the diagram, how many  
diagrams are present, ...)
        (worse the info.html indicates that the processes is still  
generating or that an error was produced....)

Done: 1,3, 5-8,10

Cheers,

Olivier

On Mar 19, 2012, at 9:23 AM, Valentin Hirschi wrote:

> Hi, Let me start to attend these points:
>
> 1)
>    It is the case no? I mean, practically there is one function per  
> file output. The structure is a bit less trivial that at LO because  
> there is the possibility of putting all files relevant to  
> loop_matrix.f into a single fortran source code if the user asks for  
> the matrix output.
> Also, if the number of helas calls gets too large, there is the  
> possibility of splitting both the HelasCalls and the JAMP definition  
> to make the compilation possible.
> But, besides these complications, there is one function per file  
> written out.
>
> 2)
> Ok, this is funny. My aim is to output the following code:
>
>       INCLUDE 'cts_mpc.h'
>      $ , INTENT(IN), DIMENSION(0:3) :: Q
>
> (here cts_mpc.h contains the quadrupole definition of the variables  
> used, i.e."TYPE(MP_COMPLEX)")
> Because it turns out that this does not work:
>       INCLUDE 'cts_mpc.h' , INTENT(IN), DIMENSION(0:3) :: Q
>
> as I believe that fortran can use the include statement to import a  
> single line in the actual code but not part of a line.
> So I did not see any other way to force the FortranWriter to do  
> this. But maybe there is and I would be happy to update this.
>
> Now it is much better to use this form instead of hardcoding  
> TYPE(MP_COMPLEX) because it allows to change the precision of all the
> floating point variable of the program by changing one single file!
> In fact, if we had designed the MG5 output like this from the  
> beginning, then I could have had the MP output for CutTools right  
> away, and I will
> anyway have to upgrade the whole MG5 output (model_v4, aloha,  
> matrix.f, etc..) with this format to have the MP.
> Again, if you know how to easily achieve this, I'm all ears.
>
> 3)
> For some reason, I thought one day we would have liked to have the  
> width in the loop particles. But it's true it will never be the case  
> as the complex mass scheme is used instead. (I though for a while we  
> might use it to pass the imaginary component of the mass, but I now  
> realize it is not the way to go). So I changed it now.
>
> 4)
>
> Mhh, I know they matter, but ok, later ^^.
>
> 5) True and done.
>
> 6) Done
>
> 7) Done
>
> 8) Done
>
> 9) Ok, now LoopInterface correctly forbids processes containing  
> multiple particles labels. FKS5 is meant for that after all.
>
> 10) Mhh my idea about this was that maybe we would like to specify  
> the squared order for tree-level processes as well (for the HIG  
> order for example). And then the [] plays the role of a delimiter  
> just fine. So I'd prefer to keep it like this.
>
> 11) The logic goes like this:
>       a) There are no specified options with the '=' delimiter, so  
> that the default is that both real and virtual corrections are  
> applied.
>       b) Given a), it is now the FKS5 interface which treats the  
> process and first check that the perturbation order asked for is  
> exactly QCD (as none other is supported so far). FKS5 interfaces  
> reckognizes that the perturbation order asked for is 'virt' (which  
> is correct as this is exactly what you would put if you had a model  
> with a 'virt' order defined and being perturbed) and therefore  
> complains.
>
>      So tell me at which point you would like this kind of request  
> to be handled differently. Because apart from a dedicated check for  
> this special form of input line, i don't see how we could do it  
> differently.
>
> Ok that is half of them so far. I'll check the others later. Tell me  
> already the points you agree with and then list them as
>
> Solved 1)-3), 5)-11)
>
> the rest being still pending.
>
> Cheers,
>
> On Fri, Mar 16, 2012 at 11:34 PM, Olivier Mattelaer <olivier.mattelaer@uclouvain.be 
> > wrote:
> Hi again, here is some additional points:
>
> 19) in file process_check at line 406 you have:
>        from tests.parallel_tests.loop_me_comparator import  
> LoopMG5Runner
>    I don't like the idea to have some code present in the tests  
> directory.
>    In fact, we should be able to remove this directory for any  
> release. We didn't do that yet,
>    but we should. so please re-factorize that.
>
> 20) File "/Users/omatt/Documents/Eclipse/CMS_NLO/tests/ 
> parallel_tests/loop_me_comparator.py"
>    line 39, in <module>
>    import madgraph.iolibs.misc as misc
>   this files is now madgraph.various.misc.py (this probably passes  
> the 1.4.3 merging)
>   I checked that's the only wrong import related
>
> 21) the routine     def has_multiparticle_label(self):
>    in core/base_objects
> returns either None or False.... this does not seems right. (So this  
> is the routine that need to be checked). Will also be useful to  add  
> a simple unit test for this routine ;-)
>
>
> Note: concerning my comment #9
> a) this might be due to the point 21
> b) I obtained the same error if I call
> HelasMatrixElement
> instead of LoopHelasMatrixElement.
>
>
>
>
> --
> https://code.launchpad.net/~maddevelopers/madgraph5/FKS5/+merge/97762
> Your team MadDevelopers is subscribed to branch lp:~maddevelopers/ 
> madgraph5/FKS5.
>
>
>
> -- 
> Valentin

Revision history for this message

marco zaro (marco-zaro) wrote on 2012-03-20:

Download full text (10.2 KiB)

ciao olivier
i'll have a more detailed look at the points later
so far, there is no index.html/diagram drawing in madfks
it is something we would like to have, of course, but to which i did not pay much attention so far
i will look at it

i think the issue/fix was maybe related with the loop_material dir that has been removed from versioning, but i am not 100% sure
so this morning i try to fix the vbfnnlo page, so that we can continue on mg5 later
cheers
marco

On 19 Mar 2012, at 23:28, Olivier Mattelaer wrote:

ciao olivier
i'll have a more detailed  look at the points later
so far, there is no index.html/diagram drawing in madfks 
it is something we would like to have, of course, but to which i did not pay much attention so far
i will look at it

On 19 Mar 2012, at 23:28, Olivier Mattelaer wrote:

> Hi Valentin,
> 
> Thanks for your prompt reply and fix. ( your reply didn't appear on  
> launchpad,... don't know why....)
> 
>> 1)
>>   It is the case no? I mean, practically there is one function per  
>> file output. The structure is a bit less trivial that at LO because  
>> there is the possibility of putting all files relevant to  
>> loop_matrix.f into a single fortran source code if the user asks for  
>> the matrix output.
>> Also, if the number of helas calls gets too large, there is the  
>> possibility of splitting both the HelasCalls and the JAMP definition  
>> to make the compilation possible.
>> But, besides these complications, there is one function per file  
>> written out.
> 
> Yes and no, in fact the .inc are define in the same time as the file  
> which calling those.
> But ok.
> 
> 
>> 2)
>> Ok, this is funny. My aim is to output the following code:
> 
> Since I don't think this is f77 compatible, I don't want to include  
> such code in LO part ;-)
> In your case, I would say that it makes a lot of sense to modify the   
> FortranWriter
> 
>> 4) (concerning help/completion)
>> 
>> Mhh, I know they matter, but ok, later ^^.
> 
> 
> To my experience, the sooner is the better for that.
> Also for Johan and I this help us to learn the code otherwise this is  
> very hard to know what is allowed.
> 
> 
>> 9) Ok, now LoopInterface correctly forbids processes containing  
>> multiple particles labels. FKS5 is meant for that after all.
> 
> 
> I think that multiparticles are very usefull for the user.
> generate p p > W+ j j is something quite natural and very important to  
> support (at all level). This is something very important
> since  this simplifies a lot to life for the user.
> 
>> 10) Mhh my idea about this was that maybe we would like to specify  
>> the squared order for tree-level processes as well (for the HIG  
>> order for example). And then the [] plays the role of a delimiter  
>> just fine. So I'd prefer to keep it like this.
> 
> Not really like this syntax, since this is far to be readable...
> why not something like that then
> p p > g g QCD=2  {NP=2}
> 
> which will do the following syntqx
> PROCESS RESTRICTION ORDER [LOOP_INFO] {AMP_ORDER} @#
> with all option can be switched in order?
> (by restriction I mean / $ $$)
> 
> We can maybe have a skype meeting on this.
> 
>> 11) The logic goes like this:
>>      a) There are no specified options with the '=' delimiter, so  
>> that the default is that both real and virtual corrections are  
>> applied.
>>      b) Given a), it is now the FKS5 interface which treats the  
>> process and first check that the perturbation order asked for is  
>> exactly QCD (as none other is supported so far). FKS5 interfaces  
>> reckognizes that the perturbation order asked for is 'virt' (which  
>> is correct as this is exactly what you would put if you had a model  
>> with a 'virt' order defined and being perturbed) and therefore  
>> complains.
>> 
>>     So tell me at which point you would like this kind of request  
>> to be handled differently. Because apart from a dedicated check for  
>> this special form of input line, i don't see how we could do it  
>> differently.
> 
> 
> I will just handle two special tag for [virt] and [real]
> 
> 
> Otherwise some additional points:
> 
> 19) Marco, Do you need to have the Delphes Card in the FKS Template?  
> those files are already present in the MadEvent Template.
> It's pointless to have two times the same files present (but if they  
> are a reason off course)
> 
> 20) The command display diagrams crashes for NLO processes:
> import model sm
> generate g g > g g [QCD]
> display diagrams
> Command "display diagrams" interrupted with error:
> InvalidCmd : No process generated, please generate a process!
> (This was working on the NLO branch before)
> 
> 21) The same after an output (We can look together for those two if  
> you want)
> 
> 22) They are no file index.html.
>        Those are a very nice feature of MG, since this gives  
> information of what was generated and helped a lot the user to find  
> relevant information.
>        (what are the subproceses, what are the diagram, how many  
> diagrams are present, ...)
>        (worse the info.html indicates that the processes is still  
> generating or that an error was produced....)
> 
> 
> 
> 
> Done: 1,3, 5-8,10
> 
> Cheers,
> 
> Olivier
> 
> 
> 
> 
> On Mar 19, 2012, at 9:23 AM, Valentin Hirschi wrote:
> 
>> Hi, Let me start to attend these points:
>> 
>> 1)
>>   It is the case no? I mean, practically there is one function per  
>> file output. The structure is a bit less trivial that at LO because  
>> there is the possibility of putting all files relevant to  
>> loop_matrix.f into a single fortran source code if the user asks for  
>> the matrix output.
>> Also, if the number of helas calls gets too large, there is the  
>> possibility of splitting both the HelasCalls and the JAMP definition  
>> to make the compilation possible.
>> But, besides these complications, there is one function per file  
>> written out.
>> 
>> 2)
>> Ok, this is funny. My aim is to output the following code:
>> 
>>      INCLUDE 'cts_mpc.h'
>>     $ , INTENT(IN), DIMENSION(0:3) :: Q
>> 
>> (here cts_mpc.h contains the quadrupole definition of the variables  
>> used, i.e."TYPE(MP_COMPLEX)")
>> Because it turns out that this does not work:
>>      INCLUDE 'cts_mpc.h' , INTENT(IN), DIMENSION(0:3) :: Q
>> 
>> as I believe that fortran can use the include statement to import a  
>> single line in the actual code but not part of a line.
>> So I did not see any other way to force the FortranWriter to do  
>> this. But maybe there is and I would be happy to update this.
>> 
>> Now it is much better to use this form instead of hardcoding  
>> TYPE(MP_COMPLEX) because it allows to change the precision of all the
>> floating point variable of the program by changing one single file!
>> In fact, if we had designed the MG5 output like this from the  
>> beginning, then I could have had the MP output for CutTools right  
>> away, and I will
>> anyway have to upgrade the whole MG5 output (model_v4, aloha,  
>> matrix.f, etc..) with this format to have the MP.
>> Again, if you know how to easily achieve this, I'm all ears.
>> 
>> 3)
>> For some reason, I thought one day we would have liked to have the  
>> width in the loop particles. But it's true it will never be the case  
>> as the complex mass scheme is used instead. (I though for a while we  
>> might use it to pass the imaginary component of the mass, but I now  
>> realize it is not the way to go). So I changed it now.
>> 
>> 4)
>> 
>> Mhh, I know they matter, but ok, later ^^.
>> 
>> 5) True and done.
>> 
>> 6) Done
>> 
>> 7) Done
>> 
>> 8) Done
>> 
>> 9) Ok, now LoopInterface correctly forbids processes containing  
>> multiple particles labels. FKS5 is meant for that after all.
>> 
>> 10) Mhh my idea about this was that maybe we would like to specify  
>> the squared order for tree-level processes as well (for the HIG  
>> order for example). And then the [] plays the role of a delimiter  
>> just fine. So I'd prefer to keep it like this.
>> 
>> 11) The logic goes like this:
>>      a) There are no specified options with the '=' delimiter, so  
>> that the default is that both real and virtual corrections are  
>> applied.
>>      b) Given a), it is now the FKS5 interface which treats the  
>> process and first check that the perturbation order asked for is  
>> exactly QCD (as none other is supported so far). FKS5 interfaces  
>> reckognizes that the perturbation order asked for is 'virt' (which  
>> is correct as this is exactly what you would put if you had a model  
>> with a 'virt' order defined and being perturbed) and therefore  
>> complains.
>> 
>>     So tell me at which point you would like this kind of request  
>> to be handled differently. Because apart from a dedicated check for  
>> this special form of input line, i don't see how we could do it  
>> differently.
>> 
>> Ok that is half of them so far. I'll check the others later. Tell me  
>> already the points you agree with and then list them as
>> 
>> Solved 1)-3), 5)-11)
>> 
>> the rest being still pending.
>> 
>> Cheers,
>> 
>> On Fri, Mar 16, 2012 at 11:34 PM, Olivier Mattelaer <olivier.mattelaer@uclouvain.be 
>>> wrote:
>> Hi again, here is some additional points:
>> 
>> 19) in file process_check at line 406 you have:
>>       from tests.parallel_tests.loop_me_comparator import  
>> LoopMG5Runner
>>   I don't like the idea to have some code present in the tests  
>> directory.
>>   In fact, we should be able to remove this directory for any  
>> release. We didn't do that yet,
>>   but we should. so please re-factorize that.
>> 
>> 20) File "/Users/omatt/Documents/Eclipse/CMS_NLO/tests/ 
>> parallel_tests/loop_me_comparator.py"
>>   line 39, in <module>
>>   import madgraph.iolibs.misc as misc
>>  this files is now madgraph.various.misc.py (this probably passes  
>> the 1.4.3 merging)
>>  I checked that's the only wrong import related
>> 
>> 21) the routine     def has_multiparticle_label(self):
>>   in core/base_objects
>> returns either None or False.... this does not seems right. (So this  
>> is the routine that need to be checked). Will also be useful to  add  
>> a simple unit test for this routine ;-)
>> 
>> 
>> Note: concerning my comment #9
>> a) this might be due to the point 21
>> b) I obtained the same error if I call
>> HelasMatrixElement
>> instead of LoopHelasMatrixElement.
>> 
>> 
>> 
>> 
>> --
>> https://code.launchpad.net/~maddevelopers/madgraph5/FKS5/+merge/97762
>> Your team MadDevelopers is subscribed to branch lp:~maddevelopers/ 
>> madgraph5/FKS5.
>> 
>> 
>> 
>> -- 
>> Valentin
> 
> 
> -- 
> https://code.launchpad.net/~maddevelopers/madgraph5/FKS5/+merge/97762
> Your team MadDevelopers is subscribed to branch lp:~maddevelopers/madgraph5/FKS5.

Revision history for this message

marco zaro (marco-zaro) wrote on 2012-03-20:

Download full text (11.2 KiB)

Hi Olivier
i fixed the display processes / diagrams for the fks interface

actually in the fks interface, it looked reasonable to me, that one may ask born/real/virt_diagrams (or processes)
so if you type display diagrams after the generation of a nlo process you 'll receive an error sayng to type real/virt/born_diagrams instead
if you type them (also auto-completion works) you will have the ones that you need
let me know if you agree with this choice
(the same as for processes)

cheers
Marco

On 20 Mar 2012, at 08:49, marco zaro wrote:

Hi Olivier
i fixed the display processes  / diagrams for the fks interface

cheers
Marco

On 20 Mar 2012, at 08:49, marco zaro wrote:

> ciao olivier
> i'll have a more detailed  look at the points later
> so far, there is no index.html/diagram drawing in madfks 
> it is something we would like to have, of course, but to which i did not pay much attention so far
> i will look at it 
> 
> i think the issue/fix was maybe related with the loop_material dir that has been removed from versioning, but i am not 100% sure
> so this morning i try to fix the vbfnnlo page, so that we can continue on mg5 later
> cheers
> marco
> 
> 
> 
> 
> On 19 Mar 2012, at 23:28, Olivier Mattelaer wrote:
> 
>> Hi Valentin,
>> 
>> Thanks for your prompt reply and fix. ( your reply didn't appear on  
>> launchpad,... don't know why....)
>> 
>>> 1)
>>>  It is the case no? I mean, practically there is one function per  
>>> file output. The structure is a bit less trivial that at LO because  
>>> there is the possibility of putting all files relevant to  
>>> loop_matrix.f into a single fortran source code if the user asks for  
>>> the matrix output.
>>> Also, if the number of helas calls gets too large, there is the  
>>> possibility of splitting both the HelasCalls and the JAMP definition  
>>> to make the compilation possible.
>>> But, besides these complications, there is one function per file  
>>> written out.
>> 
>> Yes and no, in fact the .inc are define in the same time as the file  
>> which calling those.
>> But ok.
>> 
>> 
>>> 2)
>>> Ok, this is funny. My aim is to output the following code:
>> 
>> Since I don't think this is f77 compatible, I don't want to include  
>> such code in LO part ;-)
>> In your case, I would say that it makes a lot of sense to modify the   
>> FortranWriter
>> 
>>> 4) (concerning help/completion)
>>> 
>>> Mhh, I know they matter, but ok, later ^^.
>> 
>> 
>> To my experience, the sooner is the better for that.
>> Also for Johan and I this help us to learn the code otherwise this is  
>> very hard to know what is allowed.
>> 
>> 
>>> 9) Ok, now LoopInterface correctly forbids processes containing  
>>> multiple particles labels. FKS5 is meant for that after all.
>> 
>> 
>> I think that multiparticles are very usefull for the user.
>> generate p p > W+ j j is something quite natural and very important to  
>> support (at all level). This is something very important
>> since  this simplifies a lot to life for the user.
>> 
>>> 10) Mhh my idea about this was that maybe we would like to specify  
>>> the squared order for tree-level processes as well (for the HIG  
>>> order for example). And then the [] plays the role of a delimiter  
>>> just fine. So I'd prefer to keep it like this.
>> 
>> Not really like this syntax, since this is far to be readable...
>> why not something like that then
>> p p > g g QCD=2  {NP=2}
>> 
>> which will do the following syntqx
>> PROCESS RESTRICTION ORDER [LOOP_INFO] {AMP_ORDER} @#
>> with all option can be switched in order?
>> (by restriction I mean / $ $$)
>> 
>> We can maybe have a skype meeting on this.
>> 
>>> 11) The logic goes like this:
>>>     a) There are no specified options with the '=' delimiter, so  
>>> that the default is that both real and virtual corrections are  
>>> applied.
>>>     b) Given a), it is now the FKS5 interface which treats the  
>>> process and first check that the perturbation order asked for is  
>>> exactly QCD (as none other is supported so far). FKS5 interfaces  
>>> reckognizes that the perturbation order asked for is 'virt' (which  
>>> is correct as this is exactly what you would put if you had a model  
>>> with a 'virt' order defined and being perturbed) and therefore  
>>> complains.
>>> 
>>>    So tell me at which point you would like this kind of request  
>>> to be handled differently. Because apart from a dedicated check for  
>>> this special form of input line, i don't see how we could do it  
>>> differently.
>> 
>> 
>> I will just handle two special tag for [virt] and [real]
>> 
>> 
>> Otherwise some additional points:
>> 
>> 19) Marco, Do you need to have the Delphes Card in the FKS Template?  
>> those files are already present in the MadEvent Template.
>> It's pointless to have two times the same files present (but if they  
>> are a reason off course)
>> 
>> 20) The command display diagrams crashes for NLO processes:
>> import model sm
>> generate g g > g g [QCD]
>> display diagrams
>> Command "display diagrams" interrupted with error:
>> InvalidCmd : No process generated, please generate a process!
>> (This was working on the NLO branch before)
>> 
>> 21) The same after an output (We can look together for those two if  
>> you want)
>> 
>> 22) They are no file index.html.
>>       Those are a very nice feature of MG, since this gives  
>> information of what was generated and helped a lot the user to find  
>> relevant information.
>>       (what are the subproceses, what are the diagram, how many  
>> diagrams are present, ...)
>>       (worse the info.html indicates that the processes is still  
>> generating or that an error was produced....)
>> 
>> 
>> 
>> 
>> Done: 1,3, 5-8,10
>> 
>> Cheers,
>> 
>> Olivier
>> 
>> 
>> 
>> 
>> On Mar 19, 2012, at 9:23 AM, Valentin Hirschi wrote:
>> 
>>> Hi, Let me start to attend these points:
>>> 
>>> 1)
>>>  It is the case no? I mean, practically there is one function per  
>>> file output. The structure is a bit less trivial that at LO because  
>>> there is the possibility of putting all files relevant to  
>>> loop_matrix.f into a single fortran source code if the user asks for  
>>> the matrix output.
>>> Also, if the number of helas calls gets too large, there is the  
>>> possibility of splitting both the HelasCalls and the JAMP definition  
>>> to make the compilation possible.
>>> But, besides these complications, there is one function per file  
>>> written out.
>>> 
>>> 2)
>>> Ok, this is funny. My aim is to output the following code:
>>> 
>>>     INCLUDE 'cts_mpc.h'
>>>    $ , INTENT(IN), DIMENSION(0:3) :: Q
>>> 
>>> (here cts_mpc.h contains the quadrupole definition of the variables  
>>> used, i.e."TYPE(MP_COMPLEX)")
>>> Because it turns out that this does not work:
>>>     INCLUDE 'cts_mpc.h' , INTENT(IN), DIMENSION(0:3) :: Q
>>> 
>>> as I believe that fortran can use the include statement to import a  
>>> single line in the actual code but not part of a line.
>>> So I did not see any other way to force the FortranWriter to do  
>>> this. But maybe there is and I would be happy to update this.
>>> 
>>> Now it is much better to use this form instead of hardcoding  
>>> TYPE(MP_COMPLEX) because it allows to change the precision of all the
>>> floating point variable of the program by changing one single file!
>>> In fact, if we had designed the MG5 output like this from the  
>>> beginning, then I could have had the MP output for CutTools right  
>>> away, and I will
>>> anyway have to upgrade the whole MG5 output (model_v4, aloha,  
>>> matrix.f, etc..) with this format to have the MP.
>>> Again, if you know how to easily achieve this, I'm all ears.
>>> 
>>> 3)
>>> For some reason, I thought one day we would have liked to have the  
>>> width in the loop particles. But it's true it will never be the case  
>>> as the complex mass scheme is used instead. (I though for a while we  
>>> might use it to pass the imaginary component of the mass, but I now  
>>> realize it is not the way to go). So I changed it now.
>>> 
>>> 4)
>>> 
>>> Mhh, I know they matter, but ok, later ^^.
>>> 
>>> 5) True and done.
>>> 
>>> 6) Done
>>> 
>>> 7) Done
>>> 
>>> 8) Done
>>> 
>>> 9) Ok, now LoopInterface correctly forbids processes containing  
>>> multiple particles labels. FKS5 is meant for that after all.
>>> 
>>> 10) Mhh my idea about this was that maybe we would like to specify  
>>> the squared order for tree-level processes as well (for the HIG  
>>> order for example). And then the [] plays the role of a delimiter  
>>> just fine. So I'd prefer to keep it like this.
>>> 
>>> 11) The logic goes like this:
>>>     a) There are no specified options with the '=' delimiter, so  
>>> that the default is that both real and virtual corrections are  
>>> applied.
>>>     b) Given a), it is now the FKS5 interface which treats the  
>>> process and first check that the perturbation order asked for is  
>>> exactly QCD (as none other is supported so far). FKS5 interfaces  
>>> reckognizes that the perturbation order asked for is 'virt' (which  
>>> is correct as this is exactly what you would put if you had a model  
>>> with a 'virt' order defined and being perturbed) and therefore  
>>> complains.
>>> 
>>>    So tell me at which point you would like this kind of request  
>>> to be handled differently. Because apart from a dedicated check for  
>>> this special form of input line, i don't see how we could do it  
>>> differently.
>>> 
>>> Ok that is half of them so far. I'll check the others later. Tell me  
>>> already the points you agree with and then list them as
>>> 
>>> Solved 1)-3), 5)-11)
>>> 
>>> the rest being still pending.
>>> 
>>> Cheers,
>>> 
>>> On Fri, Mar 16, 2012 at 11:34 PM, Olivier Mattelaer <olivier.mattelaer@uclouvain.be 
>>>> wrote:
>>> Hi again, here is some additional points:
>>> 
>>> 19) in file process_check at line 406 you have:
>>>      from tests.parallel_tests.loop_me_comparator import  
>>> LoopMG5Runner
>>>  I don't like the idea to have some code present in the tests  
>>> directory.
>>>  In fact, we should be able to remove this directory for any  
>>> release. We didn't do that yet,
>>>  but we should. so please re-factorize that.
>>> 
>>> 20) File "/Users/omatt/Documents/Eclipse/CMS_NLO/tests/ 
>>> parallel_tests/loop_me_comparator.py"
>>>  line 39, in <module>
>>>  import madgraph.iolibs.misc as misc
>>> this files is now madgraph.various.misc.py (this probably passes  
>>> the 1.4.3 merging)
>>> I checked that's the only wrong import related
>>> 
>>> 21) the routine     def has_multiparticle_label(self):
>>>  in core/base_objects
>>> returns either None or False.... this does not seems right. (So this  
>>> is the routine that need to be checked). Will also be useful to  add  
>>> a simple unit test for this routine ;-)
>>> 
>>> 
>>> Note: concerning my comment #9
>>> a) this might be due to the point 21
>>> b) I obtained the same error if I call
>>> HelasMatrixElement
>>> instead of LoopHelasMatrixElement.
>>> 
>>> 
>>> 
>>> 
>>> --
>>> https://code.launchpad.net/~maddevelopers/madgraph5/FKS5/+merge/97762
>>> Your team MadDevelopers is subscribed to branch lp:~maddevelopers/ 
>>> madgraph5/FKS5.
>>> 
>>> 
>>> 
>>> -- 
>>> Valentin
>> 
>> 
>> -- 
>> https://code.launchpad.net/~maddevelopers/madgraph5/FKS5/+merge/97762
>> Your team MadDevelopers is subscribed to branch lp:~maddevelopers/madgraph5/FKS5.
> 
> 
> -- 
> https://code.launchpad.net/~maddevelopers/madgraph5/FKS5/+merge/97762
> Your team MadDevelopers is subscribed to branch lp:~maddevelopers/madgraph5/FKS5.

Revision history for this message

Olivier Mattelaer (olivier-mattelaer) wrote on 2012-03-20:

Download full text (12.3 KiB)

Hi Marco,

> i fixed the display processes / diagrams for the fks interface
Thanks

> actually in the fks interface, it looked reasonable to me, that one
> may ask born/real/virt_diagrams (or processes)
> so if you type display diagrams after the generation of a nlo
> process you 'll receive an error sayng to type real/virt/
> born_diagrams instead
> if you type them (also auto-completion works) you will have the ones
> that you need
> let me know if you agree with this choice
> (the same as for processes)

Sure that's perfect.
Just maybe display diagrams might either
a) not be proposed anymore in the auto-completion
b) simply return the three above output

Valentin could you fix this also in the ML5 interface?

Cheers,

Olivier

On Mar 20, 2012, at 10:58 AM, marco zaro wrote:

Hi Marco,

> i fixed the display processes  / diagrams for the fks interface
Thanks

> actually in the fks interface, it looked reasonable to me, that one  
> may ask born/real/virt_diagrams (or processes)
> so if you type display diagrams after the generation of a nlo  
> process you 'll receive an error sayng to type real/virt/ 
> born_diagrams instead
> if you type them (also auto-completion works) you will have the ones  
> that you need
> let me know if you agree with this choice
> (the same as for processes)

Sure that's perfect.
Just maybe display diagrams might either
a) not be proposed anymore in the auto-completion
b) simply return the three above output

Valentin could you fix this also in the ML5 interface?

Cheers,

Olivier

On Mar 20, 2012, at 10:58 AM, marco zaro wrote:

> Hi Olivier
> i fixed the display processes  / diagrams for the fks interface
>
> actually in the fks interface, it looked reasonable to me, that one  
> may ask born/real/virt_diagrams (or processes)
> so if you type display diagrams after the generation of a nlo  
> process you 'll receive an error sayng to type real/virt/ 
> born_diagrams instead
> if you type them (also auto-completion works) you will have the ones  
> that you need
> let me know if you agree with this choice
> (the same as for processes)
>
> cheers
> Marco
>
>
>
> On 20 Mar 2012, at 08:49, marco zaro wrote:
>
>> ciao olivier
>> i'll have a more detailed  look at the points later
>> so far, there is no index.html/diagram drawing in madfks
>> it is something we would like to have, of course, but to which i  
>> did not pay much attention so far
>> i will look at it
>>
>> i think the issue/fix was maybe related with the loop_material dir  
>> that has been removed from versioning, but i am not 100% sure
>> so this morning i try to fix the vbfnnlo page, so that we can  
>> continue on mg5 later
>> cheers
>> marco
>>
>>
>>
>>
>> On 19 Mar 2012, at 23:28, Olivier Mattelaer wrote:
>>
>>> Hi Valentin,
>>>
>>> Thanks for your prompt reply and fix. ( your reply didn't appear on
>>> launchpad,... don't know why....)
>>>
>>>> 1)
>>>> It is the case no? I mean, practically there is one function per
>>>> file output. The structure is a bit less trivial that at LO because
>>>> there is the possibility of putting all files relevant to
>>>> loop_matrix.f into a single fortran source code if the user asks  
>>>> for
>>>> the matrix output.
>>>> Also, if the number of helas calls gets too large, there is the
>>>> possibility of splitting both the HelasCalls and the JAMP  
>>>> definition
>>>> to make the compilation possible.
>>>> But, besides these complications, there is one function per file
>>>> written out.
>>>
>>> Yes and no, in fact the .inc are define in the same time as the file
>>> which calling those.
>>> But ok.
>>>
>>>
>>>> 2)
>>>> Ok, this is funny. My aim is to output the following code:
>>>
>>> Since I don't think this is f77 compatible, I don't want to include
>>> such code in LO part ;-)
>>> In your case, I would say that it makes a lot of sense to modify the
>>> FortranWriter
>>>
>>>> 4) (concerning help/completion)
>>>>
>>>> Mhh, I know they matter, but ok, later ^^.
>>>
>>>
>>> To my experience, the sooner is the better for that.
>>> Also for Johan and I this help us to learn the code otherwise this  
>>> is
>>> very hard to know what is allowed.
>>>
>>>
>>>> 9) Ok, now LoopInterface correctly forbids processes containing
>>>> multiple particles labels. FKS5 is meant for that after all.
>>>
>>>
>>> I think that multiparticles are very usefull for the user.
>>> generate p p > W+ j j is something quite natural and very  
>>> important to
>>> support (at all level). This is something very important
>>> since  this simplifies a lot to life for the user.
>>>
>>>> 10) Mhh my idea about this was that maybe we would like to specify
>>>> the squared order for tree-level processes as well (for the HIG
>>>> order for example). And then the [] plays the role of a delimiter
>>>> just fine. So I'd prefer to keep it like this.
>>>
>>> Not really like this syntax, since this is far to be readable...
>>> why not something like that then
>>> p p > g g QCD=2  {NP=2}
>>>
>>> which will do the following syntqx
>>> PROCESS RESTRICTION ORDER [LOOP_INFO] {AMP_ORDER} @#
>>> with all option can be switched in order?
>>> (by restriction I mean / $ $$)
>>>
>>> We can maybe have a skype meeting on this.
>>>
>>>> 11) The logic goes like this:
>>>>    a) There are no specified options with the '=' delimiter, so
>>>> that the default is that both real and virtual corrections are
>>>> applied.
>>>>    b) Given a), it is now the FKS5 interface which treats the
>>>> process and first check that the perturbation order asked for is
>>>> exactly QCD (as none other is supported so far). FKS5 interfaces
>>>> reckognizes that the perturbation order asked for is 'virt' (which
>>>> is correct as this is exactly what you would put if you had a model
>>>> with a 'virt' order defined and being perturbed) and therefore
>>>> complains.
>>>>
>>>>   So tell me at which point you would like this kind of request
>>>> to be handled differently. Because apart from a dedicated check for
>>>> this special form of input line, i don't see how we could do it
>>>> differently.
>>>
>>>
>>> I will just handle two special tag for [virt] and [real]
>>>
>>>
>>> Otherwise some additional points:
>>>
>>> 19) Marco, Do you need to have the Delphes Card in the FKS Template?
>>> those files are already present in the MadEvent Template.
>>> It's pointless to have two times the same files present (but if they
>>> are a reason off course)
>>>
>>> 20) The command display diagrams crashes for NLO processes:
>>> import model sm
>>> generate g g > g g [QCD]
>>> display diagrams
>>> Command "display diagrams" interrupted with error:
>>> InvalidCmd : No process generated, please generate a process!
>>> (This was working on the NLO branch before)
>>>
>>> 21) The same after an output (We can look together for those two if
>>> you want)
>>>
>>> 22) They are no file index.html.
>>>      Those are a very nice feature of MG, since this gives
>>> information of what was generated and helped a lot the user to find
>>> relevant information.
>>>      (what are the subproceses, what are the diagram, how many
>>> diagrams are present, ...)
>>>      (worse the info.html indicates that the processes is still
>>> generating or that an error was produced....)
>>>
>>>
>>>
>>>
>>> Done: 1,3, 5-8,10
>>>
>>> Cheers,
>>>
>>> Olivier
>>>
>>>
>>>
>>>
>>> On Mar 19, 2012, at 9:23 AM, Valentin Hirschi wrote:
>>>
>>>> Hi, Let me start to attend these points:
>>>>
>>>> 1)
>>>> It is the case no? I mean, practically there is one function per
>>>> file output. The structure is a bit less trivial that at LO because
>>>> there is the possibility of putting all files relevant to
>>>> loop_matrix.f into a single fortran source code if the user asks  
>>>> for
>>>> the matrix output.
>>>> Also, if the number of helas calls gets too large, there is the
>>>> possibility of splitting both the HelasCalls and the JAMP  
>>>> definition
>>>> to make the compilation possible.
>>>> But, besides these complications, there is one function per file
>>>> written out.
>>>>
>>>> 2)
>>>> Ok, this is funny. My aim is to output the following code:
>>>>
>>>>    INCLUDE 'cts_mpc.h'
>>>>   $ , INTENT(IN), DIMENSION(0:3) :: Q
>>>>
>>>> (here cts_mpc.h contains the quadrupole definition of the variables
>>>> used, i.e."TYPE(MP_COMPLEX)")
>>>> Because it turns out that this does not work:
>>>>    INCLUDE 'cts_mpc.h' , INTENT(IN), DIMENSION(0:3) :: Q
>>>>
>>>> as I believe that fortran can use the include statement to import a
>>>> single line in the actual code but not part of a line.
>>>> So I did not see any other way to force the FortranWriter to do
>>>> this. But maybe there is and I would be happy to update this.
>>>>
>>>> Now it is much better to use this form instead of hardcoding
>>>> TYPE(MP_COMPLEX) because it allows to change the precision of all  
>>>> the
>>>> floating point variable of the program by changing one single file!
>>>> In fact, if we had designed the MG5 output like this from the
>>>> beginning, then I could have had the MP output for CutTools right
>>>> away, and I will
>>>> anyway have to upgrade the whole MG5 output (model_v4, aloha,
>>>> matrix.f, etc..) with this format to have the MP.
>>>> Again, if you know how to easily achieve this, I'm all ears.
>>>>
>>>> 3)
>>>> For some reason, I thought one day we would have liked to have the
>>>> width in the loop particles. But it's true it will never be the  
>>>> case
>>>> as the complex mass scheme is used instead. (I though for a while  
>>>> we
>>>> might use it to pass the imaginary component of the mass, but I now
>>>> realize it is not the way to go). So I changed it now.
>>>>
>>>> 4)
>>>>
>>>> Mhh, I know they matter, but ok, later ^^.
>>>>
>>>> 5) True and done.
>>>>
>>>> 6) Done
>>>>
>>>> 7) Done
>>>>
>>>> 8) Done
>>>>
>>>> 9) Ok, now LoopInterface correctly forbids processes containing
>>>> multiple particles labels. FKS5 is meant for that after all.
>>>>
>>>> 10) Mhh my idea about this was that maybe we would like to specify
>>>> the squared order for tree-level processes as well (for the HIG
>>>> order for example). And then the [] plays the role of a delimiter
>>>> just fine. So I'd prefer to keep it like this.
>>>>
>>>> 11) The logic goes like this:
>>>>    a) There are no specified options with the '=' delimiter, so
>>>> that the default is that both real and virtual corrections are
>>>> applied.
>>>>    b) Given a), it is now the FKS5 interface which treats the
>>>> process and first check that the perturbation order asked for is
>>>> exactly QCD (as none other is supported so far). FKS5 interfaces
>>>> reckognizes that the perturbation order asked for is 'virt' (which
>>>> is correct as this is exactly what you would put if you had a model
>>>> with a 'virt' order defined and being perturbed) and therefore
>>>> complains.
>>>>
>>>>   So tell me at which point you would like this kind of request
>>>> to be handled differently. Because apart from a dedicated check for
>>>> this special form of input line, i don't see how we could do it
>>>> differently.
>>>>
>>>> Ok that is half of them so far. I'll check the others later. Tell  
>>>> me
>>>> already the points you agree with and then list them as
>>>>
>>>> Solved 1)-3), 5)-11)
>>>>
>>>> the rest being still pending.
>>>>
>>>> Cheers,
>>>>
>>>> On Fri, Mar 16, 2012 at 11:34 PM, Olivier Mattelaer <olivier.mattelaer@uclouvain.be
>>>>> wrote:
>>>> Hi again, here is some additional points:
>>>>
>>>> 19) in file process_check at line 406 you have:
>>>>     from tests.parallel_tests.loop_me_comparator import
>>>> LoopMG5Runner
>>>> I don't like the idea to have some code present in the tests
>>>> directory.
>>>> In fact, we should be able to remove this directory for any
>>>> release. We didn't do that yet,
>>>> but we should. so please re-factorize that.
>>>>
>>>> 20) File "/Users/omatt/Documents/Eclipse/CMS_NLO/tests/
>>>> parallel_tests/loop_me_comparator.py"
>>>> line 39, in <module>
>>>> import madgraph.iolibs.misc as misc
>>>> this files is now madgraph.various.misc.py (this probably passes
>>>> the 1.4.3 merging)
>>>> I checked that's the only wrong import related
>>>>
>>>> 21) the routine     def has_multiparticle_label(self):
>>>> in core/base_objects
>>>> returns either None or False.... this does not seems right. (So  
>>>> this
>>>> is the routine that need to be checked). Will also be useful to   
>>>> add
>>>> a simple unit test for this routine ;-)
>>>>
>>>>
>>>> Note: concerning my comment #9
>>>> a) this might be due to the point 21
>>>> b) I obtained the same error if I call
>>>> HelasMatrixElement
>>>> instead of LoopHelasMatrixElement.
>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> https://code.launchpad.net/~maddevelopers/madgraph5/FKS5/+merge/ 
>>>> 97762
>>>> Your team MadDevelopers is subscribed to branch lp:~maddevelopers/
>>>> madgraph5/FKS5.
>>>>
>>>>
>>>>
>>>> -- 
>>>> Valentin
>>>
>>>
>>> -- 
>>> https://code.launchpad.net/~maddevelopers/madgraph5/FKS5/+merge/ 
>>> 97762
>>> Your team MadDevelopers is subscribed to branch lp:~maddevelopers/ 
>>> madgraph5/FKS5.
>>
>>
>> -- 
>> https://code.launchpad.net/~maddevelopers/madgraph5/FKS5/+merge/97762
>> Your team MadDevelopers is subscribed to branch lp:~maddevelopers/ 
>> madgraph5/FKS5.
>
>
> -- 
> https://code.launchpad.net/~maddevelopers/madgraph5/FKS5/+merge/97762
> You proposed lp:~maddevelopers/madgraph5/FKS5 for merging.

lp:~maddevelopers/mg5amcnlo/FKS5 updated on 2012-04-11

180. By Valentin Hirschi <email address hidden> on 2012-03-19

1. Fixed the launch standalone function.

181. By Valentin Hirschi <email address hidden> on 2012-03-21

1. Implemented special fonctions cond(a,b,c) and reglog(a) available for
   loop UFO model. It can be exported to fortran without problem but not
   to C++ (not implemented but could be without too much effort).
   The advantage is that no ill-expression like log(0) appear anymore and
   that one can easily switch from loop_sm to loop_sm-zerobmass simply with
   the corresponding restrict card.

182. By Valentin Hirschi <email address hidden> on 2012-03-21

1. Upgraded the display for the ML5 interface. The user can now ask for
   display diagrams -> display all diagrams
   display diagrams born -> display born diagrams
   display diagrams loop -> display virtuals diagrams

And for this function, the completion and help is up to date.

183. By Valentin Hirschi <email address hidden> on 2012-03-21

1. Fixed the help of the new display_diagrams in the LoopInterface

184. By Valentin Hirschi <email address hidden> on 2012-03-23

1. Fixed an issue with the new functions 'COND' and 'REGLOG' for the
loop UFO model which were not well behaved when dealing with
complex arguments.

185. By Valentin Hirschi <email address hidden> on 2012-03-23

1. Fixed the definition of the fonction 'COND' in model_functions.f

186. By Valentin Hirschi <email address hidden> on 2012-03-23

1. Merged with latest revision from Marco before my push.

187. By Valentin Hirschi <email address hidden> on 2012-03-23

1. Fixed many of the first series of points from Olivier's review

188. By marco zaro on 2012-03-23

moved the templateFKSxxxx dirs to Template/FKS-xxxx
exporters modified accordingly

189. By marco zaro on 2012-03-26

modified the madgraph_interface.extract_process function so that now
if the orders are not defined they are set equal to the squared_orders in the process definition
with this
generate p p > t t~ QED=0 [QCD]
and
generate p p > t t~ [QCD] QED=0
return the same diagrams, as expected

190. By Valentin Hirschi <email address hidden> on 2012-03-29

1. Update commit

191. By Valentin Hirschi <email address hidden> on 2012-04-10

1. Upgraded the ML5 standalone output so that it now handles loop induced
   processes.
2. Added some warning during diagram generation for the cases where some
   non perturbed order do not factorize the same power in all born diagrams
   and when mixed QCD-QED loops are discarded because the user asked only
   for QCD corrections (of course the warning is general and not limited
   to this case.).

192. By Valentin Hirschi <email address hidden> on 2012-04-11

1. Small fix in the warnings for discarded loops.

193. By Valentin Hirschi <email address hidden> on 2012-04-11

1. Small fix for the initialization of 'GOODAMP' for the split output.

Revision history for this message

Olivier Mattelaer (olivier-mattelaer) wrote on 2012-04-19:

Hi guys,

I started the systematics review file by file.
I hope to do one file each one/two days such that it can move quite fast on this.

So today it is loop_base_objects.py

So first a global comment: This file is quite clear and very well documented.
Good work!

23) A quite global comment. The PEP08 is not respected by far.
Using up to 80 character should be follow as much as possible.
Even if this is boring at the stage of writing the code, this is quite
usefull for
1) comparing two version of the code
2) editing on a small screen (my laptop for example)
3) for the web

In your case, a lot of comment line are bigger than 80 char.
This should be reduced to 80) Looks like you split around 120.

Also concerning PEP08 the space before/after the equal/sum/...
This improves the readibility of the code.

24) The routine next_loop_leg is very long and with a lot of sub-level (loop of loop of loop).
I think it might be interesting to re-factor it in order to have it calling multiple functions.
This might make the structure more clear. ( this is only a suggestion)

25) The name "next_loop_leg" and the way this function is call is quite confusing to me.
I don't really that a function in a if, modify/creates a lot structures. and given the name I was expecting that this returns the next leg, but this is an iterative call so clearly this should be done outside the if.

26)For the fun (I like those stupid optimization) the function get_loop_line_types can be optimized by returning
return set([abs(l['id']) for l in v['legs'] for v in self['vertices'] if l['loop_line']])

27) At line 702 you perform the following:
        # Make a local copy (since we will act on the leg object of the tag)
        revTag=copy.deepcopy(atag)
    But If I'm correct, you copy a object of the following type # [(Leg,[Structure_IDs],Vertex), (...), ...]
    That means that you duplicate all the Leg/Vertex and all the content of those.
    I would prefer that you create an optimize routine to copy only the required part.
    I don't think you need to duplicate Leg/Vertex.

28) One point that I don't understand is why you need to "recreate" the vertex for the FDstructure. I would have expect that you have to "copy" those from one of the diagram.
Why is it not working?

I like your way to code, very well documented :-)

Cheers,

Olivier

Hi guys,

I started the systematics review file by file. 
I hope to do one file each one/two days such that it can move quite fast on this.

So today it is loop_base_objects.py

So first a global comment: This file is quite clear and very well documented. 
Good work!

23) A quite global comment. The PEP08 is not respected by far.
Using up to 80 character should be follow as much as possible.
Even if this is boring at the stage of writing the code, this is quite 
usefull for 
1) comparing two version of the code
2) editing on a small screen (my laptop for example)
3) for the web

In your case, a lot of comment line are bigger than 80 char. 
This should be reduced to 80) Looks like you split around 120.

Also concerning PEP08 the space before/after the equal/sum/...
This improves the readibility of the code.

27) At line 702 you perform the following:
        # Make a local copy (since we will act on the leg object of the tag)
        revTag=copy.deepcopy(atag)
    But If I'm correct, you copy a object of the following type #   [(Leg,[Structure_IDs],Vertex), (...), ...]
    That means that you duplicate all the Leg/Vertex and all the content of those. 
    I would prefer that you create an optimize routine to copy only the required part.
    I don't think you need to duplicate Leg/Vertex.

28) One point that I don't understand is why you need to "recreate" the vertex for the FDstructure. I would have expect that you have to "copy" those from one of the diagram.
Why is it not working?

I like your way to code, very well documented :-)

Cheers,

Olivier

review: Needs Information

Revision history for this message

Olivier Mattelaer (olivier-mattelaer) wrote on 2012-04-23:

Download full text (7.7 KiB)

Hi Valentin,

looks like launchpad doesn't like your email account (or your email account doesn't like launchpad)
since your message didn't pass through it. Could you check your configuration?

Otherwise, the file for today is loop_diagram (only half of it).
Nothing very deep a lot of small optimization, question, check to perform.

Cheers,

Olivier

29) One minor detail:
at line 284:
        elif argument != None:
            # call the mother routine
            super(Amplitude, self).__init__(argument)
        else:
            # call the mother routine
            super(Amplitude, self).__init__()
can be replace by:
        else:
            # call the mother routine
            super(Amplitude, self).__init__(argument)
(the elif is pointless.

30) at line 77:
def get_sorted_keys(self):
"""Return diagram property names as a nicely sorted list."""

        return ['process', 'diagrams', 'has_mirror_process', 'born_diagrams',
                'loop_diagrams','has_born',
                'structure_repository']
    Would it makes sense to return here diagrams since this is always empty?
    Not sure what this changes in fact, could you try/check?

31) Not sure it worth the time but at line 131:
                self['born_diagrams']=base_objects.DiagramList([diag for diag in value if \
                  not isinstance(diag,loop_base_objects.LoopUVCTDiagram) and diag['type']==0])
                self['loop_diagrams']=base_objects.DiagramList([diag for diag in value if \
                  not isinstance(diag,loop_base_objects.LoopUVCTDiagram) and diag['type']!=0])
                self['loop_UVCT_diagrams']=base_objects.DiagramList([diag for diag in value if \
                  isinstance(diag,loop_base_objects.LoopUVCTDiagram)])
you loop three times over the full list, while a single loop should be enough.

32)at line 147:
            if self['process'] and self['loop_diagrams'] == None:
                self.generate_diagrams()
   This breaks PEP08(not important rule)
"Comparisons to singletons like None should always be done with 'is' or 'is not', never the equality operators.".By reading this article: http://jaredgrubb.blogspot.com/2009/04/python-is-none-vs-none.html, you will see that this is not that important but I pointed such that you will use the correct one in the future.

33)at line 188:
# This is a bool controlling the verbosity of this subroutine only
loopGenInfo=False

        old_logger_level=logger.getEffectiveLevel()
        if loopGenInfo:
            # Disable the basic info if using the extended one
            logger.setLevel(logging.WARNING)
        ...
                if loopGenInfo: print "LoopGenInfo:: User input born orders = ",self['process']['orders']
        if loopGenInfo: print "LoopGenInfo:: User input squared orders = ",self['process']['squared_orders']
        if loopGenInfo: print "LoopGenInfo:: User input perturbation = ",self['process']['perturbation_couplings']
        ...
        if loopGenInfo:
            logger.setLevel(old_logger_level)

That's a weird way to treat the logger.
I see two poss...

Hi Valentin,

looks like launchpad doesn't like your email account (or your email account doesn't like launchpad)
since your message didn't pass through it. Could you check your configuration?

Otherwise, the file for today is loop_diagram (only half of it).
Nothing very deep a lot of small optimization, question, check to perform.

Cheers,

Olivier

29) One minor detail:
at line 284: 
        elif argument != None:
            # call the mother routine
            super(Amplitude, self).__init__(argument)
        else:
            # call the mother routine
            super(Amplitude, self).__init__()
can be replace by: 
        else:
            # call the mother routine
            super(Amplitude, self).__init__(argument)
(the elif is pointless.

30) at line 77:
    def get_sorted_keys(self):
        """Return diagram property names as a nicely sorted list."""

32)at line 147:
            if self['process'] and self['loop_diagrams'] == None:            
                self.generate_diagrams()
   This breaks PEP08(not important rule)
"Comparisons to singletons like None should always be done with 'is' or 'is not', never the equality operators.".By reading this article: http://jaredgrubb.blogspot.com/2009/04/python-is-none-vs-none.html, you will see that this is not that important but I pointed such that you will use the correct one in the future.

33)at line 188:
        # This is a bool controlling the verbosity of this subroutine only
        loopGenInfo=False
        
        old_logger_level=logger.getEffectiveLevel()
        if loopGenInfo:
            # Disable the basic info if using the extended one
            logger.setLevel(logging.WARNING)
        ...
                if loopGenInfo: print "LoopGenInfo:: User input born orders                  = ",self['process']['orders']
        if loopGenInfo: print "LoopGenInfo:: User input squared orders               = ",self['process']['squared_orders']
        if loopGenInfo: print "LoopGenInfo:: User input perturbation                 = ",self['process']['perturbation_couplings']
        ...
        if loopGenInfo:
            logger.setLevel(old_logger_level)

That's a weird way to treat the logger.
        I see two possibilities:
        1) you put replace those print by logger.debug() (and remove all the if of course)
        2) you remove/or comment all those print

34) You can pass a find replace for wether --> whether

35) line 236:
                            logger.warning("All born diagrams do not factorize "+\
                              "the same power of the order %s which is not"%order+\
                              " perturbed. This is potentially dangerous as the "+\
                              " real-emission diagrams will not be consistent "+\
                              "with these virtual contributions.")
    This warning seems very serious to me. So serious that it looks like to me that rather
    1) We should stop the computation (pointless to compute smthg wrong).
    2) Check this point in the virtual (maybe it's done) to check if this is dangerous or not.
       And Therefore not put the error message here. 
    
36) In base_object.py line 1890: the function get_min_order (same for max)
    What happen for empty list? 
    It looks like you cann't call this routine with empty list. (the ouptut doesn't seems well define) so wouldn't make sense to add a line
assert self, 'get_min_order cann\'t be called on empty Diagram list'
    Also it might be better to set the min to 99 by default (this simplifies the condition by
    removing the max_order==-1 [which is by the way pointless for the max])

37) at line 307:
                if order in self['process']['perturbation_couplings']:
                    neworder+=2
    Why is it a 2? Is it supposing that the hierarchy of QCD [or the dominant] is always one? What about QCD->2 QED-> 3 Yukawa->4?

38) at line 263:
        if (not [1 for elem in self['process']['squared_orders'].items() if \
                elem[0].upper()!='WEIGHTED']) and hierarchy and self['process']['has_born']:
I would put instead:
        if (not any(order.upper()!='WEIGHTED' for order in self['process']['squared_orders']) and hierarchy and self['process']['has_born']

39) Do you really need the upper?
since then you could use
        if 'WEIGHTED' not in self['process']['squared_orders'] and hierarchy and self['process']['has_born']
   This upper stuff is not always used in your code. ( I mean sometimes you assume that its uppercase and sometimes not) Might be better to put it upper-case in the interface ans suppose it uppercase in all the code.

40) at line 315 you have
                self['process']['orders'][order]=user_orders[order]+2

First they are the same argument as 37.
    But it looks like to me (but I can be wrong) that you might pass both at line 307 and to 315.
    Therefor it seems to me that you add a +4 in this case. Could you check?

41) One point is not clear to me by reading the code. Do you take care about the maximal value allow by the model builder for a given coupling? I might have miss that part in your code.

42) The function generate_diagrams should be split in smaller functions.
    For example the automatic choice for the order should be one specific functions.
    Allowing to have some dedicated unit-test for the choice of the ordering (This will be helpfull)

43) at line 328:
                        logger.warning("Some loop diagrams contributing to this process"+\
                          " might be discarded because they are not pure "+\
                          '+'.join(self['process']['perturbation_couplings'])+\
                          " perturbation. Make sure there are none or that you did not"+\
                          " want to include them.")
   Would it be possible to put this warning , ONLY if some diagram are indeed discarded?
   This seemed to be the case at line 388 in fact

Also concerning those two warnings:
   Make sure there are none or that you did not want to include them.
   Is it currently possible to include it? Your message should be more clear on this point.
   Maybe the level should be put on non critical error rather than warning?

44) line 475: 
        # This is a bool controlling the verbosity of this subroutine only
        partGenInfo=False
same comment as above

45) line 491: line commented to be removed

46) line 529: 
                    self.lcutpartemployed.append(part.get_anti_pdg_code())
    Why do you need that line, I was understanding that only particle can be in l_cut following one of your previous comment.

47) line 539: you return loopsuccesfull.
This sounds weird to me, could you check that this is indeed the variable that you want to return and not totloopsuccessful

Ok That's it for today the rest of the file for tomorrow.

review: Needs Fixing

Revision history for this message

Olivier Mattelaer (olivier-mattelaer) wrote on 2012-04-24:

I'm back on this file, and I have only comment remaining on this one:

48) line 786, you define
    def copy_leglist(self, leglist):
        """ Returns a DGLoopLeg list instead of the default copy_leglist
            defined in base_objects.Amplitude """

        dgloopleglist=base_objects.LegList()
        for leg in leglist:
            dgloopleglist.append(loop_base_objects.DGLoopLeg(leg))

return dgloopleglist
But this should be equivalent of base_objects.LegList(leglist)
So I don't think that you need such function.

I'm going to wait for your green light before reviewing the helas file.

Cheers,

Olivier

review: Needs Fixing

lp:~maddevelopers/mg5amcnlo/FKS5 updated on 2012-08-22

194. By Valentin Hirschi <email address hidden> on 2012-05-02: 1. Merged with ML5_faster bringing in the 'loop_optimized_output' which
   brings many optimization and flexibility in the code, as:
   a. Control the initialization of the Loop and Hel filters and save them
   b. Control run time parameteres with the card MadLoopParams.dat
   c. Optimization of summing over the helicity before cuttoolizing the
      diagrams as well as constructing the loop lorentz trace directly from
   a helas wavefunction which brings a speed up factor 2 for massless fermion
   L-cut diagrams and 3 fort the massive one.
   Overall gain is usually more than a factor 5 already!
195. By Valentin Hirschi <email address hidden> on 2012-05-16: 1. Fixed small bug when setting 'USELOOPFILTER' to false.
196. By Valentin Hirschi <email address hidden> on 2012-05-16: 1. Merged with Marco's latest push.
197. By Valentin Hirschi <email address hidden> on 2012-05-23: 1. Small fix in the definition of ML in the loop numerator.
198. By Valentin Hirschi <email address hidden> on 2012-05-29: 1. Upgraded the model v4 output in order to factor out the multiple precision
   parameters and couplings and also promote mu_r to the same status as alpha_s
   meaning that UPDATE_AS_PARAM correctly update all variables depending on
   mu_r and alpha_s.
199. By Valentin Hirschi <email address hidden> on 2012-05-29: 1. Small fix so that the parameter ZeroThres in the MadLoopParamCard
is indeed used in favor of the old hardcoded value vtiny in ISZERO().
200. By Valentin Hirschi <email address hidden> on 2012-06-08: 1. Fixed an issue occurring for loops with more external wavefunctions than
loop lines.
2. Fixed the MadLoopParams.dat file which was not up to date.
201. By Valentin Hirschi <email address hidden> on 2012-06-08: 1. Merged with latest push of this branch on launchpad.
202. By marco zaro on 2012-07-05: merged with FKS5_new_born branch v 323
203. By marco zaro on 2012-07-05: merged with FKS5_new_born branch v 324
204. By marco zaro on 2012-07-05: added a function to get Nf (the number of light flavors) from the model.
In this way Nf is written in coupl.inc, and does not need anymore to be specified (and changed) inside fks_singular.f
Also setcuts.f is changed so that if maxjetflavor is set in the run_card to a value > Nf, it takes the value Nf
205. By Valentin Hirschi <email address hidden> on 2012-07-09: 1. Small fix for the path of the template LO banner.
206. By Valentin Hirschi <email address hidden> on 2012-07-11: 1. Major upgrade of the branch including the latest developments in ML5,
   among which is the implementation of the open loop method for faster
   loop matrix element evaluation. In order to obtain such output, you
   must set the 'loop_optimized_output' flag from the madgraph interface
   to true.
2. Notice that when this flag is set to False, the default output is now
   what was the optimized one before (in which the sum over helicities is
   performed before calling CutTools) which means that the color ordered
   amplitudes for loop processes are no longer obtainable. For this reason
   the old branch which had this information with the raw output is kept
   under the name FKS5_legacy but it as its name suggests it will not be
   maintained or upgraded anymore.
3. Finally the loop-induced processes do no benefit of the loop optimized
   output for now.
207. By Valentin Hirschi <email address hidden> on 2012-07-11: 1. Added Olivier's latest modification to ML5_faster_merged_1.4.6
208. By marco zaro on 2012-07-11: updated the fks exporer so that the non-optimized version of MadLoop works
also commented an harmless error in avh_olo.f90
ERROR in OneLOop box13: p12=m3, returning 0
to be done: modify fks exporter for optimized loop
209. By marco zaro on 2012-07-12: write_ajob modified so that MadLoopParams.dat is copied to the node
210. By marco zaro on 2012-07-12: ColorNum/DenFactors.dat and HelConfigs.dat are now copied to the cluster node
211. By marco zaro on 2012-07-12: modified exporters in order to deal with optimized mode (not yet working)
Also, problem with poles cancelation in MadFKS, maybe due to points too close to threshold
212. By Valentin Hirschi <email address hidden> on 2012-07-19: 1. Merged with ML5_faster which implements several improvements and bug
fixes.
a) A new command 'check timing' for loop processes. (not loop-induced)
b) Parallel tests which can be run with './test/test_manager -p P ML5Test'
c) The other 'check' commands no also full working both for optimized and default output.
d) A new kind of Helicity filter for the optimized output which allow to set
the helicity dependence from CP for example. Normally automatically setup, but
not validated/fully-working yet. Can still easily be edited by hand though.
213. By Rikkert Frederix on 2012-07-24: DECAY and HELAS made to work with the new Template directory
214. By Paolo Torrielli on 2012-07-26: updated montecarlocounter.f
215. By marco zaro on 2012-07-30: MP is used for HELAS routines only if virtuals have been generated
216. By Rikkert Frederix on 2012-08-02: fixed a bug in the azimuthal correlations because the order of the
spinor/polarization vector and the momentum changed in the
wave-functions in the aloha/HELAS code. (Also a bug fixed in the
oxxxxx.f spinor: the order was not changed consistently there).
217. By Rikkert Frederix on 2012-08-04: 1. Small fix in add_write_info.f related to the assignment of the color
information when there are 4-point interactions around.
2. Change the MC damp factors to be between 0.1 and 1 (like in v4)
3. Added the Higgs+1j virtuals to the virt.tar.gz tar-ball.
218. By Rikkert Frederix on 2012-08-06: Put the boostwdir2 subroutine in a separate file for easier linking to
the reweight_xsec_events (which doesn't need the genps_fks.f)
219. By marco zaro on 2012-08-06: fixed bug/redundancies in the computation of the color links.
now they are computed after the combination of identical matrix elements.
g g > u u~ g g [real=QCD] now does not raise errors anymore at output time
220. By marco zaro on 2012-08-06: fix in the previous commit
only half of the color links are generated, those for which #leg1 <= #leg2
updated unit tests
soft/coll tests checked for p p > 3j and p p > t t~, OK
221. By Rikkert Frederix on 2012-08-07: Added a new value for the renormalization scale (not used by default),
useful for "alphaS reweighting"
222. By marco zaro on 2012-08-07: fixed bug: Error occurring when one exported [real=QCD] with loop_optimized_mode =True
223. By Rikkert Frederix on 2012-08-07: Small fix in the setscales (for the 'alpha_s reweigting')
224. By Rikkert Frederix on 2012-08-08: small fix in the assignment of the MC masses (add_write_info.f).
225. By Rikkert Frederix on 2012-08-15: Cleaning of the Template/FKS-born/bin/ directory.
All the "hidden" compilation of files is done via a makefile.
226. By Rikkert Frederix on 2012-08-15: renamed combine_plots3.sh to combine_plots_FO.sh
renamed combine_results3.sh to combine_results_FO.sh
227. By Rikkert Frederix on 2012-08-15: Removed one file too many in the previous push
228. By Rikkert Frederix on 2012-08-15: Added a couple of cuts to the run_card.dat related to the jets and to
the leptons. The values put there are used in cuts.f to apply these
cuts as well as in set_tau_min to compute the minimal required value
for tau to pass these cuts.
229. By Rikkert Frederix on 2012-08-15: renamed ./bin/compile_madfks2.sh to ./bin/compile_amcatnlo.sh
renamed ./bin/run_madfks.sh to ./bin/run_amcatnlo.sh
230. By Rikkert Frederix on 2012-08-16: Added the 'collect_events' to the makefile
231. By Rikkert Frederix on 2012-08-16: The reweight_xsec_events.sh script now reads the event files that need
reweighting from the nevents_unweighted file. Also, after running it
updates this file so that a collect_events will get the events from
the reweighted event files.
232. By marco zaro on 2012-08-22: removed print statement in helas_objects which printed many ZERO ZERO if complex mass was activated and mass/width of a particle are=0
added ZERO=0d0 statement in couplings.f (also in MP)
233. By marco zaro on 2012-08-22: fixed small bug in cuts.f
eta cuts were applied to the center of mass momenta and not to the lab frame ones

Revision history for this message

Johan Alwall (johan-alwall) wrote on 2012-08-24:

Hello guys,

This is an amazing job!

I have started slowly going through the code, and I would first like to ask about the code organization.

In Template, you now have four different directories. Looking at e.g. the Source directory in FKS-born and LO, it looks like the main differences (in the files with the same names) is that a number of updates/improvements from MG5 are not included in the FKS directory. Is there a plan for how to include developments that should be common between Lo and FKS? I could have imagined another way to do it would be to have a common Source directory for all the functionality, and try to factor out functionality that differs to use different files only where differences are really needed. Or should I interpret the present organization such that you prefer to have any modifications to the FKS code have to be explicitly implemented by you, rather than just being reviewed by you?

Another detail, but which would be nice to fix a.s.a.p. to make life easier for reviewers (i.e., me) would be to replace the useless README files (that you have just copied from the LO directory) and incomplete help texts in the mg5 interface, to include some rudimentary how-to-get-started info. I'm sure this wouldn't take more than 30 min to update, you need to do it at some point anyway, and it would save a lot of time on my side.

All the best,
Johan

review: Needs Fixing

Revision history for this message

Valentin Hirschi (valentin-hirschi) wrote on 2012-08-24:

Hi Johan,

Thanks for having started to look at the code!

On Fri, Aug 24, 2012 at 6:10 AM, Johan Alwall <email address hidden> wrote:

> Review: Needs Fixing
>
> Hello guys,
>
> This is an amazing job!
>
> I have started slowly going through the code, and I would first like to
> ask about the code organization.
>
> In Template, you now have four different directories. Looking at e.g. the
> Source directory in FKS-born and LO, it looks like the main differences (in
> the files with the same names) is that a number of updates/improvements
> from MG5 are not included in the FKS directory. Is there a plan for how to
> include developments that should be common between Lo and FKS? I could have
> imagined another way to do it would be to have a common Source directory
> for all the functionality, and try to factor out functionality that differs
> to use different files only where differences are really needed. Or should
> I interpret the present organization such that you prefer to have any
> modifications to the FKS code have to be explicitly implemented by you,
> rather than just being reviewed by you?
>
> Another detail, but which would be nice to fix a.s.a.p. to make life
> easier for reviewers (i.e., me) would be to replace the useless README
> files (that you have just copied from the LO directory) and incomplete help
> texts in the mg5 interface, to include some rudimentary how-to-get-started
> info. I'm sure this wouldn't take more than 30 min to update, you need to
> do it at some point anyway, and it would save a lot of time on my side.
>

Yes, definitely. This is the next thing on my todo list. I'm not around
later today and this weekend, but I will do it.
But already now, I can tell you that there are not many commands
NLO-related other than the generate one you already know (at list for the
virtuals only)

> display diagrams [born/loop/real]
> check timing <proc>
> check stability <nPSpoints> <proc>
> check <proc> (the default checks available also for NLO)
> launch ( for NLO SA only)

By the way, notice that you now have some virtuals-only local parallel
tests in 'test_ML5'.
I'll let you know as soon as I make progress in the user documentation
(online help + README).

Cheers,

> All the best,
> Johan
> --
> https://code.launchpad.net/~maddevelopers/madgraph5/FKS5/+merge/97762
> Your team MadDevelopers is subscribed to branch
> lp:~maddevelopers/madgraph5/FKS5.
>

--
Valentin

Hi Johan,

Thanks for having started to look at the code!

On Fri, Aug 24, 2012 at 6:10 AM, Johan Alwall <johan@alwall.net> wrote:

> display diagrams [born/loop/real]
> check timing <proc>
> check stability <nPSpoints> <proc>
> check <proc> (the default checks available also for NLO)
> launch ( for NLO SA only)

By the way, notice that you now have some virtuals-only local parallel
tests in 'test_ML5'.
I'll let you know as soon as I make progress in the user documentation
(online help + README).

Cheers,

> All the best,
> Johan
> --
> https://code.launchpad.net/~maddevelopers/madgraph5/FKS5/+merge/97762
> Your team MadDevelopers is subscribed to branch
> lp:~maddevelopers/madgraph5/FKS5.
>

-- 
Valentin

Revision history for this message

marco zaro (marco-zaro) wrote on 2012-08-24:

Hi Johan,

could you give a couple more details about the source files? Indeed we never updated them, so it would be nice to know which improvements of LO we can transfer also to NLO.
Thanks for the review!
Cheers
Marco

On 24 Aug 2012, at 00:10, Johan Alwall wrote:

> Review: Needs Fixing
>
> Hello guys,
>
> This is an amazing job!
>
> I have started slowly going through the code, and I would first like to ask about the code organization.
>
> In Template, you now have four different directories. Looking at e.g. the Source directory in FKS-born and LO, it looks like the main differences (in the files with the same names) is that a number of updates/improvements from MG5 are not included in the FKS directory. Is there a plan for how to include developments that should be common between Lo and FKS? I could have imagined another way to do it would be to have a common Source directory for all the functionality, and try to factor out functionality that differs to use different files only where differences are really needed. Or should I interpret the present organization such that you prefer to have any modifications to the FKS code have to be explicitly implemented by you, rather than just being reviewed by you?
>
> Another detail, but which would be nice to fix a.s.a.p. to make life easier for reviewers (i.e., me) would be to replace the useless README files (that you have just copied from the LO directory) and incomplete help texts in the mg5 interface, to include some rudimentary how-to-get-started info. I'm sure this wouldn't take more than 30 min to update, you need to do it at some point anyway, and it would save a lot of time on my side.
>
> All the best,
> Johan
> --
> https://code.launchpad.net/~maddevelopers/madgraph5/FKS5/+merge/97762
> Your team MadDevelopers is subscribed to branch lp:~maddevelopers/madgraph5/FKS5.

Revision history for this message

Johan Alwall (johan-alwall) wrote on 2012-08-27:

Hello Marco,

I went through the diff of the directories, and see the following modifications that have not been included in the FKS branch. The vast majority of the files seem to be just old versions of the MG4 files. So it looks like it would be possible to use a common file repository, and have separate files only where the files necessarily differ. With an appropriate set of tests, the risk for problems from improvements should be quite minimal. My worry with the present organization is that once we decide to include improvements in both LO and FKS, it might end up being a lot of work since the files have diverged so much.

pdg2pdf.f: reuse previous call if possible.

pdg2pdf_lhapdf.f: return 0 for non-parton.

cuts.inc and setrun.f (as well as setcuts.f in SubProcesses): turning off cuts for decays.

dsample.f: set minimal number of iterations, use lumi instead of #events, some speedups by Tim. Simplified/clearer version of dsample.f underway.

gen_ximprove:
- Allow splitting channels into multiple G dirs, allow any number of conflicting BW in decays (same thing in symmetry.f)
- Using lumi instead of #events (reduces risk for 2nd refine)
- Major rework of gridpack mode after reports about problems with granularity by CMS

genps.inc: Allow any number of configs, particles, etc.
kin_functions.f: Different definitions of DJ (used in clustering for matching)

ranmar.f: major improvement to guarantee up to 900M random seeds (in latest version of MG5, not yet in FKS5 branch)

transpole.f: New transformations by Tim

I'm not sure how up-to-date the LO directory in this branch is, so there might be more from the later versions (e.g. ranmar.f).

All the best,
Johan

Revision history for this message

Rikkert Frederix (frederix) wrote on 2012-08-27:

Hi Johan,

let me also explicitly write it here. I also replied to the e-mail that I received from LP, but somehow that didn't end-up here.

Thanks for giving this quick report. Let me reply to each of them. Indeed, there is a bit of work needed from our side (mostly cleaning up parts of code that we include but are never used).

> pdg2pdf.f: reuse previous call if possible.

Ok. should be updated.

> pdg2pdf_lhapdf.f: return 0 for non-parton.

Ok. should be updated.

> cuts.inc and setrun.f (as well as setcuts.f in SubProcesses): turning off cuts for decays.

Our setrun.f is quite a bit different because many of the cuts (on jets and photons) cannot easily be transported to NLO. However, as you might notice, also here the code has not been cleaned properly.

> dsample.f: set minimal number of iterations, use lumi instead of #events, some speedups by Tim. Simplified/clearer version of dsample.f underway.

> gen_ximprove:
> - Allow splitting channels into multiple G dirs, allow any number of conflicting BW in decays (same thing in symmetry.f)
> - Using lumi instead of #events (reduces risk for 2nd refine)
> - Major rework of gridpack mode after reports about problems with granularity by CMS

The integration routines for the NLO code are completely different from the LO ones. E.g. we don't use dsample anymore (and it's just there because we never cleaned this part of the code). We are using the MINT package by Paolo Nason for the importance sampling. Also the gen_ximprove we don't have as such neither do we have support for gridpacks. Also, we don't use the 'conflicting BW' stuff; maybe we should, but for early version of the MadFKS code, this was something very complicated (and we were not yet sure how the integration channels should be defined) and was never re-instated/re-implemented.

> genps.inc: Allow any number of configs, particles, etc.

Needs to be carefully updated.

> kin_functions.f: Different definitions of DJ (used in clustering for matching)

Right now they are not yet used, but I guess we should update them when I start testing the NLO CKKW stuff.

> ranmar.f: major improvement to guarantee up to 900M random seeds (in latest version of MG5, not yet in FKS5 branch)

Ok. this needs to be updated.

> transpole.f: New transformations by Tim

Phase-space and integration routines are completely different; transpole is not used.

Cheers,
Rik

Hi Johan,

let me also explicitly write it here. I also replied to the e-mail that I received from LP, but somehow that didn't end-up here.

Thanks for giving this quick report. Let me reply to each of them. Indeed, there is a bit of work needed from our side (mostly cleaning up parts of code that we include but are never used).

> pdg2pdf.f: reuse previous call if possible.

Ok. should be updated.

> pdg2pdf_lhapdf.f: return 0 for non-parton.

Ok. should be updated.

> cuts.inc and setrun.f (as well as setcuts.f in SubProcesses): turning off cuts for decays.

> dsample.f: set minimal number of iterations, use lumi instead of #events, some speedups by Tim. Simplified/clearer version of dsample.f underway.

> gen_ximprove: 
> - Allow splitting channels into multiple G dirs, allow any number of conflicting BW in decays (same thing in symmetry.f)
> - Using lumi instead of #events (reduces risk for 2nd refine)
> - Major rework of gridpack mode after reports about problems with granularity by CMS

> genps.inc: Allow any number of configs, particles, etc.

Needs to be carefully updated.

> kin_functions.f: Different definitions of DJ (used in clustering for matching)

Right now they are not yet used, but I guess we should update them when I start testing the NLO CKKW stuff.

> ranmar.f: major improvement to guarantee up to 900M random seeds (in latest version of MG5, not yet in FKS5 branch)

Ok. this needs to be updated.

> transpole.f: New transformations by Tim

Phase-space and integration routines are completely different; transpole is not used.

Cheers,
Rik

Revision history for this message

marco zaro (marco-zaro) wrote on 2012-08-27:

Hi,
I have done some modifications.
For genps.inc: maxparticle is referring to born or real emission?
Cheers
Marco

On 27 Aug 2012, at 15:12, Rikkert Frederix wrote:

> Hi Johan,
>
> let me also explicitly write it here. I also replied to the e-mail that I received from LP, but somehow that didn't end-up here.
>
>
> Thanks for giving this quick report. Let me reply to each of them. Indeed, there is a bit of work needed from our side (mostly cleaning up parts of code that we include but are never used).
>
>> pdg2pdf.f: reuse previous call if possible.
>
> Ok. should be updated.
>
>
>> pdg2pdf_lhapdf.f: return 0 for non-parton.
>
> Ok. should be updated.
>
>
>> cuts.inc and setrun.f (as well as setcuts.f in SubProcesses): turning off cuts for decays.
>
> Our setrun.f is quite a bit different because many of the cuts (on jets and photons) cannot easily be transported to NLO. However, as you might notice, also here the code has not been cleaned properly.
>
>> dsample.f: set minimal number of iterations, use lumi instead of #events, some speedups by Tim. Simplified/clearer version of dsample.f underway.
>
>> gen_ximprove:
>> - Allow splitting channels into multiple G dirs, allow any number of conflicting BW in decays (same thing in symmetry.f)
>> - Using lumi instead of #events (reduces risk for 2nd refine)
>> - Major rework of gridpack mode after reports about problems with granularity by CMS
>
>
> The integration routines for the NLO code are completely different from the LO ones. E.g. we don't use dsample anymore (and it's just there because we never cleaned this part of the code). We are using the MINT package by Paolo Nason for the importance sampling. Also the gen_ximprove we don't have as such neither do we have support for gridpacks. Also, we don't use the 'conflicting BW' stuff; maybe we should, but for early version of the MadFKS code, this was something very complicated (and we were not yet sure how the integration channels should be defined) and was never re-instated/re-implemented.
>
>> genps.inc: Allow any number of configs, particles, etc.
>
> Needs to be carefully updated.
>
>> kin_functions.f: Different definitions of DJ (used in clustering for matching)
>
>
> Right now they are not yet used, but I guess we should update them when I start testing the NLO CKKW stuff.
>
>> ranmar.f: major improvement to guarantee up to 900M random seeds (in latest version of MG5, not yet in FKS5 branch)
>
> Ok. this needs to be updated.
>
>> transpole.f: New transformations by Tim
>
> Phase-space and integration routines are completely different; transpole is not used.
>
> Cheers,
> Rik
>
>
>
> --
> https://code.launchpad.net/~maddevelopers/madgraph5/FKS5/+merge/97762
> Your team MadDevelopers is subscribed to branch lp:~maddevelopers/madgraph5/FKS5.

Hi,
I have done some modifications.
For genps.inc: maxparticle is referring to born or real emission?
Cheers
Marco

On 27 Aug 2012, at 15:12, Rikkert Frederix wrote:

> Hi Johan,
> 
> let me also explicitly write it here. I also replied to the e-mail that I received from LP, but somehow that didn't end-up here. 
> 
> 
> Thanks for giving this quick report. Let me reply to each of them. Indeed, there is a bit of work needed from our side (mostly cleaning up parts of code that we include but are never used).
> 
>> pdg2pdf.f: reuse previous call if possible.
> 
> Ok. should be updated.
> 
> 
>> pdg2pdf_lhapdf.f: return 0 for non-parton.
> 
> Ok. should be updated.
> 
> 
>> cuts.inc and setrun.f (as well as setcuts.f in SubProcesses): turning off cuts for decays.
> 
> Our setrun.f is quite a bit different because many of the cuts (on jets and photons) cannot easily be transported to NLO. However, as you might notice, also here the code has not been cleaned properly.
> 
>> dsample.f: set minimal number of iterations, use lumi instead of #events, some speedups by Tim. Simplified/clearer version of dsample.f underway.
> 
>> gen_ximprove: 
>> - Allow splitting channels into multiple G dirs, allow any number of conflicting BW in decays (same thing in symmetry.f)
>> - Using lumi instead of #events (reduces risk for 2nd refine)
>> - Major rework of gridpack mode after reports about problems with granularity by CMS
> 
> 
> The integration routines for the NLO code are completely different from the LO ones. E.g. we don't use dsample anymore (and it's just there because we never cleaned this part of the code). We are using the MINT package by Paolo Nason for the importance sampling. Also the gen_ximprove we don't have as such neither do we have support for gridpacks. Also, we don't use the 'conflicting BW' stuff; maybe we should, but for early version of the MadFKS code, this was something very complicated (and we were not yet sure how the integration channels should be defined) and was never re-instated/re-implemented.
> 
>> genps.inc: Allow any number of configs, particles, etc.
> 
> Needs to be carefully updated.
> 
>> kin_functions.f: Different definitions of DJ (used in clustering for matching)
> 
> 
> Right now they are not yet used, but I guess we should update them when I start testing the NLO CKKW stuff.
> 
>> ranmar.f: major improvement to guarantee up to 900M random seeds (in latest version of MG5, not yet in FKS5 branch)
> 
> Ok. this needs to be updated.
> 
>> transpole.f: New transformations by Tim
> 
> Phase-space and integration routines are completely different; transpole is not used.
> 
> Cheers,
> Rik
> 
> 
> 
> -- 
> https://code.launchpad.net/~maddevelopers/madgraph5/FKS5/+merge/97762
> Your team MadDevelopers is subscribed to branch lp:~maddevelopers/madgraph5/FKS5.

Revision history for this message

Johan Alwall (johan-alwall) wrote on 2012-08-28:

Hello Rikkert,

Thanks for your clarification. I would suggest to remove all files that you don't actually use from the FKS directory, to avoid having different versions of files when possible. It would also be good to have some comments ("Modif for FKS" or something) in the files that are changed to comply with FKS/NLO, to simplify updating files.

Johan

Revision history for this message

Johan Alwall (johan-alwall) wrote on 2012-08-28:

Hello Marco,

> For genps.inc: maxparticle is referring to born or real emission?

I think you will need to have it for the real emission, since this is used for array limits. It's not a problem if it's a bit too large, but it's a big problem if it's too small :-)
The main point with this modif (in LO) is that we now allow basically unlimited length of decay chains - I have done simulation with 16 final state particles without problem. I would expect this to be possible also in NLO mode, so it's better not to have any limitation. Just make sure to go through all files and remove possible hardcoded array limits.

All the best,
Johan

Revision history for this message

marco zaro (marco-zaro) wrote on 2012-08-28:

Hi,
i have removed the fixed lmaxconfigs and maxparticles in genps.inc
now the corresponding .inc files are written when exporting
Ciao
Marco

On 27 Aug 2012, at 21:17, Johan Alwall wrote:

> Hello Marco,
>
>> For genps.inc: maxparticle is referring to born or real emission?
>
> I think you will need to have it for the real emission, since this is used for array limits. It's not a problem if it's a bit too large, but it's a big problem if it's too small :-)
> The main point with this modif (in LO) is that we now allow basically unlimited length of decay chains - I have done simulation with 16 final state particles without problem. I would expect this to be possible also in NLO mode, so it's better not to have any limitation. Just make sure to go through all files and remove possible hardcoded array limits.
>
> All the best,
> Johan
>
> --
> https://code.launchpad.net/~maddevelopers/madgraph5/FKS5/+merge/97762
> Your team MadDevelopers is subscribed to branch lp:~maddevelopers/madgraph5/FKS5.

Revision history for this message

Olivier Mattelaer (olivier-mattelaer) wrote on 2012-08-30:

Hi guys,

I was discussing today with Valentin (while we moved forward on the merge with 1.5.0)
And they are four point currently missing we should be present for the official release
1) a tutorial command
2) a launch command for the computation of cross-section/events at NLO
3) the auto-completion working for the process generation
4) the help command up-to-date

For the point 2, the ideal would be to have something as close as possible of what we have for madevent. In particular this should use the files cluster.py which contains all the command in order to deal with cluster management (submission/control/...)
in madevent.py you have also two command (launch_job and control) which are useful for submitting/controlling job on various cluster/mode of submission.

If you need my help for those points, don't hesitate.

Cheers,

Olivier

review: Needs Fixing

Revision history for this message

Valentin Hirschi (valentin-hirschi) wrote on 2012-08-30:

Hi all,

On Thu, Aug 30, 2012 at 9:32 PM, Olivier Mattelaer <
<email address hidden>> wrote:

> Review: Needs Fixing
>
> Hi guys,
>
> I was discussing today with Valentin (while we moved forward on the merge
> with 1.5.0)
> And they are four point currently missing we should be present for the
> official release
> 1) a tutorial command
>
I'll take care of designing one. Ideally it would walk the user through
both a aMC@NLO run and a ML5 stand-alone one.

> 2) a launch command for the computation of cross-section/events at NLO
>
Rik, you told me that you already had a master driving bash script for
event generation working locally.
With the help of existing python function for job control over various
cluster architecture, it should not be too hard too translate this script
into a python launch command in the aMC@NLO MG interface which would do
(both locally and on clusters) both fixed order cross section computation
and event-generation, no?
Marco, could you implement this with Rik's help?

> 3) the auto-completion working for the process generation
>
This one is a pain, but eventually Marco or I will attack it.

> 4) the help command up-to-date
>
There are no new commands specific to NLO, but many have additional options
(like check, generate, display and set). So I'll update the existing helps
with the corresponding NLO info. Marco go over my modifications afterwards
and add anything missing which would be FKS-specific.

>
> For the point 2, the ideal would be to have something as close as possible
> of what we have for madevent. In particular this should use the files
> cluster.py which contains all the command in order to deal with cluster
> management (submission/control/...)
> in madevent.py you have also two command (launch_job and control) which
> are useful for submitting/controlling job on various cluster/mode of
> submission.
>
> If you need my help for those points, don't hesitate.
>
>
> Cheers,
>
> Olivier
>
> --
> https://code.launchpad.net/~maddevelopers/madgraph5/FKS5/+merge/97762
> Your team MadDevelopers is subscribed to branch
> lp:~maddevelopers/madgraph5/FKS5.
>

--
Valentin

Hi all,

On Thu, Aug 30, 2012 at 9:32 PM, Olivier Mattelaer <
olivier.mattelaer@uclouvain.be> wrote:

> 3) the auto-completion working for the process generation
>
This one is a pain, but eventually Marco or I will attack it.

-- 
Valentin

lp:~maddevelopers/mg5amcnlo/FKS5 updated on 2012-09-17

234. By Valentin Hirschi <email address hidden> on 2012-08-23

1. Merged with ML5_faster. Need to re-check and re-generated the
parallel test though.

235. By Valentin Hirschi <email address hidden> on 2012-08-23

1. Intermediate commit before merge with MG5 1.5.0

236. By Valentin Hirschi <email address hidden> on 2012-08-23

1. Regenerated the ML5 parrallel tests for a model with no widths at all.

237. By Valentin Hirschi <email address hidden> on 2012-08-24

1. Fixed a typo for loop processes in loop_exporters.py
2. This shows that I have to add some tests for the loop induced processes

238. By Valentin Hirschi <email address hidden> on 2012-08-31

1. Added the possibility of a new kind of stability check at run-time based
on the rotation of the original PS point.
2. Improved the statistics output of 'check stability' by addind the
performance of the loop reading direction stability test.

239. By Valentin Hirschi <email address hidden> on 2012-08-31

1. Merged with Rik's modifications on avh_olo.f90

240. By Rikkert Frederix on 2012-08-31

fix in the ajob_template_condor

241. By Rikkert Frederix on 2012-08-31

Another fix in the ajob_template_condor. Now also the virtual
corrections work on the cluster

242. By Valentin Hirschi <email address hidden> on 2012-09-01

1. Fixed a bug in qp evaluations of the optimized output which was introduced in
latest revision.

243. By Rikkert Frederix on 2012-09-03

Moved the fill_MC_mshell subroutine to a separate file: the Monte
Carlo masses used are written in the header of the event file by
collect_events.f.

244. By Rikkert Frederix on 2012-09-03

When running MINT mode equal to 1, the check that the nevts file has a
non-zero number of events is no longer there: with the fewer number of
integration channels and the automatic stop when the desired accuracy
has been reached, this stop is no longer needed.

245. By Rikkert Frederix on 2012-09-03

Fix in the makefiles for the reweight stuff. Introduced 2 revision ago.

246. By Rikkert Frederix on 2012-09-04

Removed possible FPEs due to missing 'save' statements.

247. By Rikkert Frederix on 2012-09-05

Allow for the correct reweighting of scale uncertainties also when the
flags fixed_XXX_scale are true.

248. By Rikkert Frederix on 2012-09-05

In the setscales.f file, moved the minimal allowed scale (2 GeV) from
the global scale setting function to the separate factorization scale
and renormalization scale setting function.

249. By Rikkert Frederix on 2012-09-06

Use the value '-1' in the run_card for not applying maximum cuts (same
as is done now for LO).

250. By marco zaro on 2012-09-07

start working on the launch command for aMC@NLO
It should be something like launch PATH MODE, MODE being NLO or aMC@NLO
so far it is implemented until compilation
it may beinteresting to add options such like -IRtests, -MCtests, ...

251. By marco zaro on 2012-09-07

acutally i forgot to uncomment the most important lines...

252. By Valentin Hirschi <email address hidden> on 2012-09-09

1. Added the '-reuse' command for loop check commands so that previously
generated output from the checks can be reused.

2. Added a progressbar for the timings of the check so that the user
does not panic for the very long one. The progress bar is also
displayed when the color computation takes long.

253. By marco zaro on 2012-09-11

small fix in setscales. set_QES_scale now has a lower bound for the scale (2gev)
the launch command works for serial run. Type help launch to see how
to do-> reweighting
-> change rnd seed
-> add options to launch command (e.g to run tests at compilation)

254. By marco zaro on 2012-09-11

re written launch function in more modular way, easily extendible to the cluster case.
randinit is updated

255. By marco zaro on 2012-09-12

small changes into FKSinterface.py

256. By Marco Zaro <email address hidden> on 2012-09-12

working on implementing cluster mode.
problem with jobs monitoring

257. By Marco Zaro <email address hidden> on 2012-09-12

cluster.py replaced with latest version from mg5 1.4.8.4
still problems with jobs monitor

258. By Marco Zaro <email address hidden> on 2012-09-12

added 2 options to the launch command:
--nocompile skip the compilation
--tests compiles and run test_ME/test_MC
details with help launch

259. By marco zaro on 2012-09-13

all parameters in the run_card are read from the run_card (also showerMC and rewight info).
reweight_xsec_event is also compiled and ran by the launch command

260. By marco zaro on 2012-09-13

fixed some bugs in previous commit

261. By Marco Zaro <email address hidden> on 2012-09-13

launch in cluster mode works!
to do-> make reweighting work in cluster mode, for now it is just bypassed

262. By Marco Zaro <email address hidden> on 2012-09-13

mg5_configuration restored to serial run

263. By marco zaro on 2012-09-13

added -c option to launch, for running on cluster without modifying the mg5_configuration file

264. By Marco Zaro <email address hidden> on 2012-09-14

reweight works also on cluster

265. By marco zaro on 2012-09-14

using misc.call and misc.Popen to launch executables in serial mode. This way, hitting ctrl + c will terminate the whole run and not only the child process

266. By marco zaro on 2012-09-14

multicore mode works

267. By marco zaro on 2012-09-14

statistics are printed also in multicore mode

268. By marco zaro on 2012-09-14

some bugs fixed

269. By Rikkert Frederix on 2012-09-17

Fix in the scale setting setscales.f

270. By Rikkert Frederix on 2012-09-17

Removed some of the print statements in driver_mintMC that were no
longer up-to-date

271. By Marco Zaro <email address hidden> on 2012-09-17

fixes in the determination of the number of cores

272. By Marco Zaro <email address hidden> on 2012-09-17

fixed multicore process, p p > e+ ev runs correctly on a 4 and 3 core machine

273. By marco zaro on 2012-09-17

the launch command automatically swithces the interface if called with NLO, aMC@NLO, aMC@LO

Revision history for this message

Johan Alwall (johan-alwall) wrote on 2012-09-18:

Download full text (7.5 KiB)

Dear FKS/Loop authors,

Please excuse my long interim in this review. I have now tested running and started on the Python review (starting with the core directory). I have to say that I am quite impressed with the level of user friendliness you have achieved so far, although there is of course still work to be done in this respect, some of which is mentioned below. Please find here a first set of comments, sorted under headers.

========================
Output to FKS:
========================
1. Why does
"INFO: Generating Helas calls for FKS process process: u u~ > e+ e- QED=2 QCD=0 [ QCD ] WEIGHTED=10"
come twice? Is it just that one of the lines could be changed to better reflect what it does, or is the same operation in fact done twice?

2. Scripts/programs in the PROC.../bin directory should only be relevant to the user, so e.g. clean_template should definitely not be there. (Internally used scripts should be in bin/internal). There should be a cleaning script however, which removes all compiled files (and perhaps additional files that are not needed between runs).

4. Looking at the regular matrix.f files, they have a list of all processes
C Process: g d~ > e+ e- d~ WEIGHTED=5 QED=2 QCD=1 [ QCD ]
C WEIGHTED=10
C Process: g d~ > mu+ mu- d~ WEIGHTED=5 QED=2 QCD=1 [ QCD ]
C WEIGHTED=10
C Process: g s~ > e+ e- s~ WEIGHTED=5 QED=2 QCD=1 [ QCD ]
C WEIGHTED=10
C Process: g s~ > mu+ mu- s~ WEIGHTED=5 QED=2 QCD=1 [ QCD ]
while the loop_matrix.f only has the first process listed:
C Process: d d~ > e+ e- QED=2 QCD=0 [ QCD ] WEIGHTED=10
It obviously doesn't really matter, but would be clearer to list all processes whose matrix elements are identical.

5. Would it be a good idea to change the name of "LesHouches" to "Binoth" or "BinothLH"? We already have leshouches for the output to lhef format, and also use the lha format for parameter files, so it can be a bit confusing... (just a suggestion)

========================
Running FKS: (using p p > l+ l- as born process)
========================
6. What does:
"Found 16 correctly terminated jobs
random seed found in 'randinit' is 33
Total cross-section: 2.58399299e+03 +- 6.7365e+00 (2.6070e-01%)
Found 16 correctly terminated jobs
Total cross-section: 2.23890720e+03 +- 7.7439e+00 (3.4588e-01%)"
mean? (why is the cross section different between the two lines?)

7. Is this something to worry about?
"gfortran -O -fno-automatic -ffixed-line-length-132 -c -o aloha_functions.o aloha_functions.f
aloha_functions.f:2220.27:

CALL ILXXXX(Q(0),M,-1,1,W(1))
1
Warning: Type mismatch in argument 'ffmass' at (1); passed COMPLEX(8) to REAL(8)"
Perhaps just pass as DBLE(M), DREAL(M), or DABS(M)?

8. Very minor point, in MadLoopParams.dat comment and value don't correspond:
! Some loop contributions my be zero for some helicities which are however
! contributing. In order to save their computing time, you can chose here to try
! to filter them out. As the gain is minimal, this option is turned off by default.
#UseLoopFilter
.TRUE.
! Default :: .TRUE.

9. I tried running with PYTHIA6PT output,...

Dear FKS/Loop authors,

========================
Output to FKS:
========================
1. Why does 
"INFO: Generating Helas calls for FKS process process: u u~ > e+ e- QED=2 QCD=0 [ QCD ] WEIGHTED=10"
come twice? Is it just that one of the lines could be changed to better reflect what it does, or is the same operation in fact done twice?

4. Looking at the regular matrix.f files, they have a list of all processes
C     Process: g d~ > e+ e- d~ WEIGHTED=5 QED=2 QCD=1 [ QCD ]
C      WEIGHTED=10
C     Process: g d~ > mu+ mu- d~ WEIGHTED=5 QED=2 QCD=1 [ QCD ]
C      WEIGHTED=10
C     Process: g s~ > e+ e- s~ WEIGHTED=5 QED=2 QCD=1 [ QCD ]
C      WEIGHTED=10
C     Process: g s~ > mu+ mu- s~ WEIGHTED=5 QED=2 QCD=1 [ QCD ]
while the loop_matrix.f only has the first process listed:
C     Process: d d~ > e+ e- QED=2 QCD=0 [ QCD ] WEIGHTED=10
It obviously doesn't really matter, but would be clearer to list all processes whose matrix elements are identical.

========================
Running FKS: (using p p > l+ l- as born process)
========================
6. What does:
"Found 16 correctly terminated jobs 
random seed found in 'randinit' is 33
Total cross-section: 2.58399299e+03 +- 6.7365e+00  (2.6070e-01%)
Found 16 correctly terminated jobs 
Total cross-section: 2.23890720e+03 +- 7.7439e+00  (3.4588e-01%)"
mean? (why is the cross section different between the two lines?)

7. Is this something to worry about?
"gfortran -O -fno-automatic  -ffixed-line-length-132  -c -o aloha_functions.o aloha_functions.f
aloha_functions.f:2220.27:

CALL ILXXXX(Q(0),M,-1,1,W(1))                                        
                           1
Warning: Type mismatch in argument 'ffmass' at (1); passed COMPLEX(8) to REAL(8)"
Perhaps just pass as DBLE(M), DREAL(M), or DABS(M)?

8. Very minor point, in MadLoopParams.dat comment and value don't correspond:
!     Some loop contributions my be zero for some helicities which are however
!     contributing. In order to save their computing time, you can chose here to try
!     to filter them out. As the gain is minimal, this option is turned off by default.
#UseLoopFilter
.TRUE.
! Default :: .TRUE.

9. I tried running with PYTHIA6PT output, and got the following result:
"Traceback (most recent call last):
  File "./sumres.py", line 118, in <module>
    (tot, math.sqrt(err), math.sqrt(err)/tot *100.)
ZeroDivisionError: float division by zero
   Computing upper envelope
ajob1.2.F.1.
1
tail: madinM1: No such file or directory
At line 497 of file driver_mintMC.f (unit = 5, file = 'stdin')
Fortran runtime error: Bad integer for item 1 in list input"
etc.

10. I tried running with PYTHIA6Q output, and everything went well until the reweight step:
...
"     Jobs completed: 8/16
At line 136 of file reweight_xsec_events.f (unit = 34, file = '')
Fortran runtime error: File 'events.lhe' does not exist
     Jobs completed: 9/16
     Jobs completed: 10/16
At line 136 of file reweight_xsec_events.f (unit = 34, file = ')
Fortran runtime error: File 'events.lhe' does not exist
     Jobs completed: 11/16
     Jobs completed: 12/16
     Jobs completed: 13/16
     Jobs completed: 14/16
At line 136 of file reweight_xsec_events.f (unit = 34, file = '
                                                               ')
Fortran runtime error: File 'events.lhe' does not exist
     Jobs completed: 15/16
     Jobs completed: 16/16
tail: P0_uxu_epem/GV1/events.lhe.rwgt: No such file or directory
Error detected in sub-command launch
write debug file MG5_debug 
If you need help with this issue please contact us on https://answers.launchpad.net/madgraph5
MadGraph5Error : An error occurred during reweight. Check /Users/alwall/MadGraph/FKS5/PROCNLO_loop_sm_1/compile_reweight.log for details"
(Also, the error message is irrelevant, since the problem isn't in the compilation).
Note: HERWIG6 output seems to work fine.

11. There is no equivalent to the "launch" command within the mg5 interface in a given PROCNLO... directory. Probably, the best would be to use the same pattern as in ME processes, to move all commands relating to launch into an FKS_run_interface.py (or something like that) corresponding to the madevent.py interface. That way, it's possible to launch a run directly from the PROC directory. Right now, the only script available are generate_amcatnlo_events.sh and run_amcatnlo.sh, which seems completely different from the (very user friendly!) launch command.

12. It would be nice to have the same system for storing events as in ME: Inside the Event directory, have one subdirectory for each run. Then a user can run pythia/herwig, plots etc (using something near-identical to the madevent interface) on each run, and the results are stored in the expected way (expected for ME users, that is). This also minimizes your work, since you can simply copy the majority of the madevent interface, just add a herwig run mode and replace the ME run commands by FKS run commands.

========================
Python code
========================

13. Please remove the files color_ordered_amplitudes.py and decay.py in the madgraph/core directory, they are not supposed to be there. color_ordered_amplitudes will be in a separate directory in the future, and decay.py should probably be in iolibs or various.

14. diagram_generation.py:
Please add a comment in the doc string about new arguments to functions, such as:
a. returndiag in generate_diagrams()
b. diaglist in trim_diagrams
Otherwise the code is quite well commented - thanks!

helas_objects.py:
15. 
+    def is_anticommutating(self):
+        """ Return if this wavefunction comes from a particle whose creation and
+        annihilation operators are anticommutating. 
+        One might think to put QCD ghosts here. (but ghost relative signs
+        proved to be correct without ghost flow tracking so far, assuming the
+        function calculate_fermion_flow is modified accordingly.)"""
+        return self.is_fermion()
I'm not so sure about the "is_anticommutating". As far as I can see, it's only used for fermion flows, and fermion flow is not the same as anticommutation. So I would suggest to change back to use is_fermion for the fermion flows, and simply keep the is_anticommuting_ghost for the special case of ghosts.

16. get_interaction_q_power: Does this work also for MSSM, or is it only for SM that this works as-is?

17. Please add a comment in the doc string about new arguments to functions, such as:
a. reverse_t_ch in get_s_and_t_channels

18. Why define the get_helas_call_dict functions here? We usually have these in the (also language independent) helas_call_writers.py, right?

19. Why define process_color_loop here rather than in the loop/loop_helas_objects.py?

review: Needs Fixing

Revision history for this message

marco zaro (marco-zaro) wrote on 2012-09-18:

Download full text (10.0 KiB)

Hi Johan,
thanks for the review.
I started working on some of the points you raised (those which looked FKS-connected)
I still have to work on the interface, in order to have the possibility to generate events outside mg5
Thanks a lot
Marco

On 18 Sep 2012, at 09:43, Johan Alwall wrote:

> Review: Needs Fixing
>
> Dear FKS/Loop authors,
>
> Please excuse my long interim in this review. I have now tested running and started on the Python review (starting with the core directory). I have to say that I am quite impressed with the level of user friendliness you have achieved so far, although there is of course still work to be done in this respect, some of which is mentioned below. Please find here a first set of comments, sorted under headers.
>
> ========================
> Output to FKS:
> ========================
> 1. Why does
> "INFO: Generating Helas calls for FKS process process: u u~ > e+ e- QED=2 QCD=0 [ QCD ] WEIGHTED=10"
> come twice? Is it just that one of the lines could be changed to better reflect what it does, or is the same operation in fact done twice?
INFO: Generating Helas calls for FKS process process: u u~ > e+ e- QED=2 QCD=0 [ QCD ] WEIGHTED=10
INFO: Processing color information for process: u u~ > e+ e- QED=2 QCD=0 [ QCD ] WEIGHTED=10
INFO: Generating Helas calls for FKS process process: c c~ > e+ e- QED=2 QCD=0 [ QCD ] WEIGHTED=10
INFO: Generating Helas calls for FKS process process: d d~ > e+ e- QED=2 QCD=0 [ QCD ] WEIGHTED=10
INFO: Reusing existing color information for process: d d~ > e+ e- QED=2 QCD=0 [ QCD ] WEIGHTED=10
INFO: Generating Helas calls for FKS process process: s s~ > e+ e- QED=2 QCD=0 [ QCD ] WEIGHTED=10
INFO: Generating Helas calls for FKS process process: u~ u > e+ e- QED=2 QCD=0 [ QCD ] WEIGHTED=10
INFO: Processing color information for process: u~ u > e+ e- QED=2 QCD=0 [ QCD ] WEIGHTED=10
INFO: Generating Helas calls for FKS process process: c~ c > e+ e- QED=2 QCD=0 [ QCD ] WEIGHTED=10
INFO: Generating Helas calls for FKS process process: d~ d > e+ e- QED=2 QCD=0 [ QCD ] WEIGHTED=10
INFO: Reusing existing color information for process: d~ d > e+ e- QED=2 QCD=0 [ QCD ] WEIGHTED=10
INFO: Generating Helas calls for FKS process process: s~ s > e+ e- QED=2 QCD=0 [ QCD ] WEIGHTED=10
it actually does not appear twice, what (i think) appear twice is u u~ and u~ u, which, so far, are treated as different
>
> 2. Scripts/programs in the PROC.../bin directory should only be relevant to the user, so e.g. clean_template should definitely not be there. (Internally used scripts should be in bin/internal). There should be a cleaning script however, which removes all compiled files (and perhaps additional files that are not needed between runs).
>
> 4. Looking at the regular matrix.f files, they have a list of all processes
> C Process: g d~ > e+ e- d~ WEIGHTED=5 QED=2 QCD=1 [ QCD ]
> C WEIGHTED=10
> C Process: g d~ > mu+ mu- d~ WEIGHTED=5 QED=2 QCD=1 [ QCD ]
> C WEIGHTED=10
> C Process: g s~ > e+ e- s~ WEIGHTED=5 QED=2 QCD=1 [ QCD ]
> C WEIGHTED=10
> C Process: g s~ > mu+ mu- s~ WEIGHTED=5 QED=2 QCD=1 [ QCD ]
> while the loop_matrix.f only has the first process listed:
...

On 18 Sep 2012, at 09:43, Johan Alwall wrote:

> Review: Needs Fixing
> 
> Dear FKS/Loop authors,
> 
> Please excuse my long interim in this review. I have now tested running and started on the Python review (starting with the core directory). I have to say that I am quite impressed with the level of user friendliness you have achieved so far, although there is of course still work to be done in this respect, some of which is mentioned below. Please find here a first set of comments, sorted under headers.
> 
> ========================
> Output to FKS:
> ========================
> 1. Why does 
> "INFO: Generating Helas calls for FKS process process: u u~ > e+ e- QED=2 QCD=0 [ QCD ] WEIGHTED=10"
> come twice? Is it just that one of the lines could be changed to better reflect what it does, or is the same operation in fact done twice?
INFO: Generating Helas calls for FKS process process: u u~ > e+ e- QED=2 QCD=0 [ QCD ] WEIGHTED=10 
INFO: Processing color information for process: u u~ > e+ e- QED=2 QCD=0 [ QCD ] WEIGHTED=10 
INFO: Generating Helas calls for FKS process process: c c~ > e+ e- QED=2 QCD=0 [ QCD ] WEIGHTED=10 
INFO: Generating Helas calls for FKS process process: d d~ > e+ e- QED=2 QCD=0 [ QCD ] WEIGHTED=10 
INFO: Reusing existing color information for process: d d~ > e+ e- QED=2 QCD=0 [ QCD ] WEIGHTED=10 
INFO: Generating Helas calls for FKS process process: s s~ > e+ e- QED=2 QCD=0 [ QCD ] WEIGHTED=10 
INFO: Generating Helas calls for FKS process process: u~ u > e+ e- QED=2 QCD=0 [ QCD ] WEIGHTED=10 
INFO: Processing color information for process: u~ u > e+ e- QED=2 QCD=0 [ QCD ] WEIGHTED=10 
INFO: Generating Helas calls for FKS process process: c~ c > e+ e- QED=2 QCD=0 [ QCD ] WEIGHTED=10 
INFO: Generating Helas calls for FKS process process: d~ d > e+ e- QED=2 QCD=0 [ QCD ] WEIGHTED=10 
INFO: Reusing existing color information for process: d~ d > e+ e- QED=2 QCD=0 [ QCD ] WEIGHTED=10 
INFO: Generating Helas calls for FKS process process: s~ s > e+ e- QED=2 QCD=0 [ QCD ] WEIGHTED=10 
it actually does not appear twice, what (i think) appear twice is u u~ and u~ u, which, so far, are treated as different
> 
> 2. Scripts/programs in the PROC.../bin directory should only be relevant to the user, so e.g. clean_template should definitely not be there. (Internally used scripts should be in bin/internal). There should be a cleaning script however, which removes all compiled files (and perhaps additional files that are not needed between runs).
> 
> 4. Looking at the regular matrix.f files, they have a list of all processes
> C     Process: g d~ > e+ e- d~ WEIGHTED=5 QED=2 QCD=1 [ QCD ]
> C      WEIGHTED=10
> C     Process: g d~ > mu+ mu- d~ WEIGHTED=5 QED=2 QCD=1 [ QCD ]
> C      WEIGHTED=10
> C     Process: g s~ > e+ e- s~ WEIGHTED=5 QED=2 QCD=1 [ QCD ]
> C      WEIGHTED=10
> C     Process: g s~ > mu+ mu- s~ WEIGHTED=5 QED=2 QCD=1 [ QCD ]
> while the loop_matrix.f only has the first process listed:
> C     Process: d d~ > e+ e- QED=2 QCD=0 [ QCD ] WEIGHTED=10
> It obviously doesn't really matter, but would be clearer to list all processes whose matrix elements are identical.
Ok, done

> 
> 5. Would it be a good idea to change the name of "LesHouches" to "Binoth" or "BinothLH"? We already have leshouches for the output to lhef format, and also use the lha format for parameter files, so it can be a bit confusing... (just a suggestion)
changed to BinothLHA.f
> 
> 
> ========================
> Running FKS: (using p p > l+ l- as born process)
> ========================
> 6. What does:
> "Found 16 correctly terminated jobs 
> random seed found in 'randinit' is 33
> Total cross-section: 2.58399299e+03 +- 6.7365e+00  (2.6070e-01%)
> Found 16 correctly terminated jobs 
> Total cross-section: 2.23890720e+03 +- 7.7439e+00  (3.4588e-01%)"
> mean? (why is the cross section different between the two lines?)
The first is the integral of the absolute value of the cross-section, the second the integral of the cross section (They are both needed since the weights are not all >0) 
I have changed the output in a clearer  way

> 
> 7. Is this something to worry about?
> "gfortran -O -fno-automatic  -ffixed-line-length-132  -c -o aloha_functions.o aloha_functions.f
> aloha_functions.f:2220.27:
> 
>          CALL ILXXXX(Q(0),M,-1,1,W(1))                                        
>                           1
> Warning: Type mismatch in argument 'ffmass' at (1); passed COMPLEX(8) to REAL(8)"
> Perhaps just pass as DBLE(M), DREAL(M), or DABS(M)?
> 
> 8. Very minor point, in MadLoopParams.dat comment and value don't correspond:
> !     Some loop contributions my be zero for some helicities which are however
> !     contributing. In order to save their computing time, you can chose here to try
> !     to filter them out. As the gain is minimal, this option is turned off by default.
> #UseLoopFilter
> .TRUE.
> ! Default :: .TRUE.
> 
> 9. I tried running with PYTHIA6PT output, and got the following result:
> "Traceback (most recent call last):
>  File "./sumres.py", line 118, in <module>
>    (tot, math.sqrt(err), math.sqrt(err)/tot *100.)
> ZeroDivisionError: float division by zero
>   Computing upper envelope
> ajob1.2.F.1.
> 1
> tail: madinM1: No such file or directory
> At line 497 of file driver_mintMC.f (unit = 5, file = 'stdin')
> Fortran runtime error: Bad integer for item 1 in list input"
> etc.
> 
It looks like Pythia6pt is not implemented yet. Checking into the logs they all terminate with "No such MonteCarlo yet".
Removed Pythia6pt from the run_card.dat

> 10. I tried running with PYTHIA6Q output, and everything went well until the reweight step:
> ...
> "     Jobs completed: 8/16
> At line 136 of file reweight_xsec_events.f (unit = 34, file = '')
> Fortran runtime error: File 'events.lhe' does not exist
>     Jobs completed: 9/16
>     Jobs completed: 10/16
> At line 136 of file reweight_xsec_events.f (unit = 34, file = ')
> Fortran runtime error: File 'events.lhe' does not exist
>     Jobs completed: 11/16
>     Jobs completed: 12/16
>     Jobs completed: 13/16
>     Jobs completed: 14/16
> At line 136 of file reweight_xsec_events.f (unit = 34, file = '
>                                                               ')
> Fortran runtime error: File 'events.lhe' does not exist
>     Jobs completed: 15/16
>     Jobs completed: 16/16
> tail: P0_uxu_epem/GV1/events.lhe.rwgt: No such file or directory
> Error detected in sub-command launch
> write debug file MG5_debug 
> If you need help with this issue please contact us on https://answers.launchpad.net/madgraph5
> MadGraph5Error : An error occurred during reweight. Check /Users/alwall/MadGraph/FKS5/PROCNLO_loop_sm_1/compile_reweight.log for details"
> (Also, the error message is irrelevant, since the problem isn't in the compilation).
> Note: HERWIG6 output seems to work fine.
> 
On my laptop everything seems to run fine, i was not able to reproduce this error.
Changed the error msg

> 11. There is no equivalent to the "launch" command within the mg5 interface in a given PROCNLO... directory. Probably, the best would be to use the same pattern as in ME processes, to move all commands relating to launch into an FKS_run_interface.py (or something like that) corresponding to the madevent.py interface. That way, it's possible to launch a run directly from the PROC directory. Right now, the only script available are generate_amcatnlo_events.sh and run_amcatnlo.sh, which seems completely different from the (very user friendly!) launch command.
> 
> 12. It would be nice to have the same system for storing events as in ME: Inside the Event directory, have one subdirectory for each run. Then a user can run pythia/herwig, plots etc (using something near-identical to the madevent interface) on each run, and the results are stored in the expected way (expected for ME users, that is). This also minimizes your work, since you can simply copy the majority of the madevent interface, just add a herwig run mode and replace the ME run commands by FKS run commands.
> 
> ========================
> Python code
> ========================
> 
> 13. Please remove the files color_ordered_amplitudes.py and decay.py in the madgraph/core directory, they are not supposed to be there. color_ordered_amplitudes will be in a separate directory in the future, and decay.py should probably be in iolibs or various.
> 
> 14. diagram_generation.py:
> Please add a comment in the doc string about new arguments to functions, such as:
> a. returndiag in generate_diagrams()
> b. diaglist in trim_diagrams
> Otherwise the code is quite well commented - thanks!
> 
> helas_objects.py:
> 15. 
> +    def is_anticommutating(self):
> +        """ Return if this wavefunction comes from a particle whose creation and
> +        annihilation operators are anticommutating. 
> +        One might think to put QCD ghosts here. (but ghost relative signs
> +        proved to be correct without ghost flow tracking so far, assuming the
> +        function calculate_fermion_flow is modified accordingly.)"""
> +        return self.is_fermion()
> I'm not so sure about the "is_anticommutating". As far as I can see, it's only used for fermion flows, and fermion flow is not the same as anticommutation. So I would suggest to change back to use is_fermion for the fermion flows, and simply keep the is_anticommuting_ghost for the special case of ghosts.
> 
> 16. get_interaction_q_power: Does this work also for MSSM, or is it only for SM that this works as-is?
> 
> 17. Please add a comment in the doc string about new arguments to functions, such as:
> a. reverse_t_ch in get_s_and_t_channels
done
> 
> 18. Why define the get_helas_call_dict functions here? We usually have these in the (also language independent) helas_call_writers.py, right?
> 
> 19. Why define process_color_loop here rather than in the loop/loop_helas_objects.py?
> 
> -- 
> https://code.launchpad.net/~maddevelopers/madgraph5/FKS5/+merge/97762
> Your team MadDevelopers is subscribed to branch lp:~maddevelopers/madgraph5/FKS5.

lp:~maddevelopers/mg5amcnlo/FKS5 updated on 2012-09-18

274. By marco zaro on 2012-09-18: some mainly aestethic improvements, according to Johan's review
275. By marco zaro on 2012-09-18: fixed shower list in the run_card with the showerMCs that are actually available now, so HW, HW++, PY-Q
276. By marco zaro on 2012-09-18: all scripts in bin directory (except for split/combine_jobs) are now in python, like for madevent
the executable ./aMCatNLO has also been added

Revision history for this message

marco zaro (marco-zaro) wrote on 2012-09-18:

Download full text (11.2 KiB)

Hi all,
> 11. There is no equivalent to the "launch" command within the mg5 interface in a given PROCNLO... directory. Probably, the best would be to use the same pattern as in ME processes, to move all commands relating to launch into an FKS_run_interface.py (or something like that) corresponding to the madevent.py interface. That way, it's possible to launch a run directly from the PROC directory. Right now, the only script available are generate_amcatnlo_events.sh and run_amcatnlo.sh, which seems completely different from the (very user friendly!) launch command.
So, now there is bin/aMCatNLO which open an interface a la madevent, where you can run launch (as in the mg5 shell), compile, generate_events, calculate_xsect. Scripts corresponding to these commands are also in the bin dir
Cheers
Marco

On 18 Sep 2012, at 11:52, marco zaro wrote:

> Hi Johan,
> thanks for the review.
> I started working on some of the points you raised (those which looked FKS-connected)
> I still have to work on the interface, in order to have the possibility to generate events outside mg5
> Thanks a lot
> Marco
> 
> On 18 Sep 2012, at 09:43, Johan Alwall wrote:
> 
>> Review: Needs Fixing
>> 
>> Dear FKS/Loop authors,
>> 
>> Please excuse my long interim in this review. I have now tested running and started on the Python review (starting with the core directory). I have to say that I am quite impressed with the level of user friendliness you have achieved so far, although there is of course still work to be done in this respect, some of which is mentioned below. Please find here a first set of comments, sorted under headers.
>> 
>> ========================
>> Output to FKS:
>> ========================
>> 1. Why does 
>> "INFO: Generating Helas calls for FKS process process: u u~ > e+ e- QED=2 QCD=0 [ QCD ] WEIGHTED=10"
>> come twice? Is it just that one of the lines could be changed to better reflect what it does, or is the same operation in fact done twice?
> INFO: Generating Helas calls for FKS process process: u u~ > e+ e- QED=2 QCD=0 [ QCD ] WEIGHTED=10 
> INFO: Processing color information for process: u u~ > e+ e- QED=2 QCD=0 [ QCD ] WEIGHTED=10 
> INFO: Generating Helas calls for FKS process process: c c~ > e+ e- QED=2 QCD=0 [ QCD ] WEIGHTED=10 
> INFO: Generating Helas calls for FKS process process: d d~ > e+ e- QED=2 QCD=0 [ QCD ] WEIGHTED=10 
> INFO: Reusing existing color information for process: d d~ > e+ e- QED=2 QCD=0 [ QCD ] WEIGHTED=10 
> INFO: Generating Helas calls for FKS process process: s s~ > e+ e- QED=2 QCD=0 [ QCD ] WEIGHTED=10 
> INFO: Generating Helas calls for FKS process process: u~ u > e+ e- QED=2 QCD=0 [ QCD ] WEIGHTED=10 
> INFO: Processing color information for process: u~ u > e+ e- QED=2 QCD=0 [ QCD ] WEIGHTED=10 
> INFO: Generating Helas calls for FKS process process: c~ c > e+ e- QED=2 QCD=0 [ QCD ] WEIGHTED=10 
> INFO: Generating Helas calls for FKS process process: d~ d > e+ e- QED=2 QCD=0 [ QCD ] WEIGHTED=10 
> INFO: Reusing existing color information for process: d~ d > e+ e- QED=2 QCD=0 [ QCD ] WEIGHTED=10 
> INFO: Generating Helas calls for FKS process process: s~ s > e+ e- QED=2 QCD=0 [ QCD ] WEIGHTED=10 
> it actually does not appear twice, what (i think) appear twice is u u~ and u~ u, which, so far, are treated as different
>> 
>> 2. Scripts/programs in the PROC.../bin directory should only be relevant to the user, so e.g. clean_template should definitely not be there. (Internally used scripts should be in bin/internal). There should be a cleaning script however, which removes all compiled files (and perhaps additional files that are not needed between runs).
>> 
>> 4. Looking at the regular matrix.f files, they have a list of all processes
>> C     Process: g d~ > e+ e- d~ WEIGHTED=5 QED=2 QCD=1 [ QCD ]
>> C      WEIGHTED=10
>> C     Process: g d~ > mu+ mu- d~ WEIGHTED=5 QED=2 QCD=1 [ QCD ]
>> C      WEIGHTED=10
>> C     Process: g s~ > e+ e- s~ WEIGHTED=5 QED=2 QCD=1 [ QCD ]
>> C      WEIGHTED=10
>> C     Process: g s~ > mu+ mu- s~ WEIGHTED=5 QED=2 QCD=1 [ QCD ]
>> while the loop_matrix.f only has the first process listed:
>> C     Process: d d~ > e+ e- QED=2 QCD=0 [ QCD ] WEIGHTED=10
>> It obviously doesn't really matter, but would be clearer to list all processes whose matrix elements are identical.
> Ok, done
> 
>> 
>> 5. Would it be a good idea to change the name of "LesHouches" to "Binoth" or "BinothLH"? We already have leshouches for the output to lhef format, and also use the lha format for parameter files, so it can be a bit confusing... (just a suggestion)
> changed to BinothLHA.f
>> 
>> 
>> ========================
>> Running FKS: (using p p > l+ l- as born process)
>> ========================
>> 6. What does:
>> "Found 16 correctly terminated jobs 
>> random seed found in 'randinit' is 33
>> Total cross-section: 2.58399299e+03 +- 6.7365e+00  (2.6070e-01%)
>> Found 16 correctly terminated jobs 
>> Total cross-section: 2.23890720e+03 +- 7.7439e+00  (3.4588e-01%)"
>> mean? (why is the cross section different between the two lines?)
> The first is the integral of the absolute value of the cross-section, the second the integral of the cross section (They are both needed since the weights are not all >0) 
> I have changed the output in a clearer  way
> 
>> 
>> 7. Is this something to worry about?
>> "gfortran -O -fno-automatic  -ffixed-line-length-132  -c -o aloha_functions.o aloha_functions.f
>> aloha_functions.f:2220.27:
>> 
>>         CALL ILXXXX(Q(0),M,-1,1,W(1))                                        
>>                          1
>> Warning: Type mismatch in argument 'ffmass' at (1); passed COMPLEX(8) to REAL(8)"
>> Perhaps just pass as DBLE(M), DREAL(M), or DABS(M)?
>> 
>> 8. Very minor point, in MadLoopParams.dat comment and value don't correspond:
>> !     Some loop contributions my be zero for some helicities which are however
>> !     contributing. In order to save their computing time, you can chose here to try
>> !     to filter them out. As the gain is minimal, this option is turned off by default.
>> #UseLoopFilter
>> .TRUE.
>> ! Default :: .TRUE.
>> 
>> 9. I tried running with PYTHIA6PT output, and got the following result:
>> "Traceback (most recent call last):
>> File "./sumres.py", line 118, in <module>
>>   (tot, math.sqrt(err), math.sqrt(err)/tot *100.)
>> ZeroDivisionError: float division by zero
>>  Computing upper envelope
>> ajob1.2.F.1.
>> 1
>> tail: madinM1: No such file or directory
>> At line 497 of file driver_mintMC.f (unit = 5, file = 'stdin')
>> Fortran runtime error: Bad integer for item 1 in list input"
>> etc.
>> 
> It looks like Pythia6pt is not implemented yet. Checking into the logs they all terminate with "No such MonteCarlo yet".
> Removed Pythia6pt from the run_card.dat
> 
>> 10. I tried running with PYTHIA6Q output, and everything went well until the reweight step:
>> ...
>> "     Jobs completed: 8/16
>> At line 136 of file reweight_xsec_events.f (unit = 34, file = '')
>> Fortran runtime error: File 'events.lhe' does not exist
>>    Jobs completed: 9/16
>>    Jobs completed: 10/16
>> At line 136 of file reweight_xsec_events.f (unit = 34, file = ')
>> Fortran runtime error: File 'events.lhe' does not exist
>>    Jobs completed: 11/16
>>    Jobs completed: 12/16
>>    Jobs completed: 13/16
>>    Jobs completed: 14/16
>> At line 136 of file reweight_xsec_events.f (unit = 34, file = '
>>                                                              ')
>> Fortran runtime error: File 'events.lhe' does not exist
>>    Jobs completed: 15/16
>>    Jobs completed: 16/16
>> tail: P0_uxu_epem/GV1/events.lhe.rwgt: No such file or directory
>> Error detected in sub-command launch
>> write debug file MG5_debug 
>> If you need help with this issue please contact us on https://answers.launchpad.net/madgraph5
>> MadGraph5Error : An error occurred during reweight. Check /Users/alwall/MadGraph/FKS5/PROCNLO_loop_sm_1/compile_reweight.log for details"
>> (Also, the error message is irrelevant, since the problem isn't in the compilation).
>> Note: HERWIG6 output seems to work fine.
>> 
> On my laptop everything seems to run fine, i was not able to reproduce this error.
> Changed the error msg
> 
> 
>> 11. There is no equivalent to the "launch" command within the mg5 interface in a given PROCNLO... directory. Probably, the best would be to use the same pattern as in ME processes, to move all commands relating to launch into an FKS_run_interface.py (or something like that) corresponding to the madevent.py interface. That way, it's possible to launch a run directly from the PROC directory. Right now, the only script available are generate_amcatnlo_events.sh and run_amcatnlo.sh, which seems completely different from the (very user friendly!) launch command.
>> 
>> 12. It would be nice to have the same system for storing events as in ME: Inside the Event directory, have one subdirectory for each run. Then a user can run pythia/herwig, plots etc (using something near-identical to the madevent interface) on each run, and the results are stored in the expected way (expected for ME users, that is). This also minimizes your work, since you can simply copy the majority of the madevent interface, just add a herwig run mode and replace the ME run commands by FKS run commands.
>> 
>> ========================
>> Python code
>> ========================
>> 
>> 13. Please remove the files color_ordered_amplitudes.py and decay.py in the madgraph/core directory, they are not supposed to be there. color_ordered_amplitudes will be in a separate directory in the future, and decay.py should probably be in iolibs or various.
>> 
>> 14. diagram_generation.py:
>> Please add a comment in the doc string about new arguments to functions, such as:
>> a. returndiag in generate_diagrams()
>> b. diaglist in trim_diagrams
>> Otherwise the code is quite well commented - thanks!
>> 
>> helas_objects.py:
>> 15. 
>> +    def is_anticommutating(self):
>> +        """ Return if this wavefunction comes from a particle whose creation and
>> +        annihilation operators are anticommutating. 
>> +        One might think to put QCD ghosts here. (but ghost relative signs
>> +        proved to be correct without ghost flow tracking so far, assuming the
>> +        function calculate_fermion_flow is modified accordingly.)"""
>> +        return self.is_fermion()
>> I'm not so sure about the "is_anticommutating". As far as I can see, it's only used for fermion flows, and fermion flow is not the same as anticommutation. So I would suggest to change back to use is_fermion for the fermion flows, and simply keep the is_anticommuting_ghost for the special case of ghosts.
>> 
>> 16. get_interaction_q_power: Does this work also for MSSM, or is it only for SM that this works as-is?
>> 
>> 17. Please add a comment in the doc string about new arguments to functions, such as:
>> a. reverse_t_ch in get_s_and_t_channels
> done
>> 
>> 18. Why define the get_helas_call_dict functions here? We usually have these in the (also language independent) helas_call_writers.py, right?
>> 
>> 19. Why define process_color_loop here rather than in the loop/loop_helas_objects.py?
>> 
>> -- 
>> https://code.launchpad.net/~maddevelopers/madgraph5/FKS5/+merge/97762
>> Your team MadDevelopers is subscribed to branch lp:~maddevelopers/madgraph5/FKS5.
> 
> 
> -- 
> https://code.launchpad.net/~maddevelopers/madgraph5/FKS5/+merge/97762
> Your team MadDevelopers is subscribed to branch lp:~maddevelopers/madgraph5/FKS5.

Revision history for this message

Johan Alwall (johan-alwall) wrote on 2012-09-19:

Download full text (4.2 KiB)

Hello Marco & Paolo,

Thanks a lot for your super-fast fixes! It's really awesome!

> > 1. Why does
> > "INFO: Generating Helas calls for FKS process process: u u~ > e+ e- QED=2
> QCD=0 [ QCD ] WEIGHTED=10"
> > come twice?
> it actually does not appear twice, what (i think) appear twice is u u~ and u~
> u, which, so far, are treated as different

You are right - I'm too used to MG5 now :-) Sorry about that!

> > while the loop_matrix.f only has the first process listed:
> > C Process: d d~ > e+ e- QED=2 QCD=0 [ QCD ] WEIGHTED=10
> processes whose matrix elements are identical.
> Ok, done

Thanks!

> > 5. Would it be a good idea to change the name of "LesHouches" to "Binoth" or
> "BinothLH"? We already have leshouches for the output to lhef format, and also
> use the lha format for parameter files, so it can be a bit confusing... (just
> a suggestion)
> changed to BinothLHA.f

Great!

> > ========================
> > Running FKS: (using p p > l+ l- as born process)
> > ========================
> > 6. What does:
> > "Found 16 correctly terminated jobs
> > random seed found in 'randinit' is 33
> > Total cross-section: 2.58399299e+03 +- 6.7365e+00 (2.6070e-01%)
> > Found 16 correctly terminated jobs
> > Total cross-section: 2.23890720e+03 +- 7.7439e+00 (3.4588e-01%)"
> > mean? (why is the cross section different between the two lines?)
> The first is the integral of the absolute value of the cross-section, the
> second the integral of the cross section (They are both needed since the
> weights are not all >0)
> I have changed the output in a clearer way

Perfect.

> > 9. I tried running with PYTHIA6PT output, and got the following result:
> It looks like Pythia6pt is not implemented yet. Checking into the logs they
> all terminate with "No such MonteCarlo yet".
> Removed Pythia6pt from the run_card.dat

Ok, thanks.

> > 10. I tried running with PYTHIA6Q output, and everything went well until the
> reweight step:
> > ...
> > Note: HERWIG6 output seems to work fine.
> >
> On my laptop everything seems to run fine, i was not able to reproduce this
> error.
> Changed the error msg

When I ran just now, it worked. Sorry for the false alarm.

> > 11. There is no equivalent to the "launch" command within the mg5 interface
> in a given PROCNLO... directory. Probably, the best would be to use the same
> pattern as in ME processes, to move all commands relating to launch into an
> FKS_run_interface.py (or something like that) corresponding to the madevent.py
> interface. That way, it's possible to launch a run directly from the PROC
> directory. Right now, the only script available are
> generate_amcatnlo_events.sh and run_amcatnlo.sh, which seems completely
> different from the (very user friendly!) launch command.
> So, now there is bin/aMCatNLO which open an interface a la madevent, where you
> can run launch (as in the mg5 shell), compile, generate_events,
> calculate_xsect. Scripts corresponding to these commands are also in the bin
> dir

Very nice. Thanks a lot!

There is a problem in the aMC@NLO interface (I'll let you know if I find more):

20. aMC@NLO interface fails to open cards:
"aMC@NLO>generate_events
Will run in mode aMC@NLO
Do you...

Hello Marco & Paolo,

Thanks a lot for your super-fast fixes! It's really awesome!

You are right - I'm too used to MG5 now :-) Sorry about that!

> > while the loop_matrix.f only has the first process listed:
> > C     Process: d d~ > e+ e- QED=2 QCD=0 [ QCD ] WEIGHTED=10
> processes whose matrix elements are identical.
> Ok, done

Thanks!

Great!

> > ========================
> > Running FKS: (using p p > l+ l- as born process)
> > ========================
> > 6. What does:
> > "Found 16 correctly terminated jobs
> > random seed found in 'randinit' is 33
> > Total cross-section: 2.58399299e+03 +- 6.7365e+00  (2.6070e-01%)
> > Found 16 correctly terminated jobs
> > Total cross-section: 2.23890720e+03 +- 7.7439e+00  (3.4588e-01%)"
> > mean? (why is the cross section different between the two lines?)
> The first is the integral of the absolute value of the cross-section, the
> second the integral of the cross section (They are both needed since the
> weights are not all >0)
> I have changed the output in a clearer  way

Perfect.

Ok, thanks.

When I ran just now, it worked. Sorry for the false alarm.

Very nice. Thanks a lot!

There is a problem in the aMC@NLO interface (I'll let you know if I find more):

20. aMC@NLO interface fails to open cards:
"aMC@NLO>generate_events 
Will run in mode aMC@NLO
Do you want to edit one cards (press enter to bypass editing)?
  1 / param   : param_card.dat (be carefull about parameter consistency, especially widths)
  2 / run     : run_card.dat
  Path to a valid card.
 [0, done, 1, param, 2, run, enter path][20s to answer] 
2
open /Users/alwall/MadGraph/FKS5/PROCNLO_loop_sm_4/Cards/run_card.dat
Command "open" not recognized, please try again"

It seems that the "open" command is not implemented (I thought this would be in the command_interface).
I would suggest to reuse as much as possible from the existing interfaces (you can include the madevent_interface.py in the bin/internal directory and include it if necessary), so we avoid the same bugs in multiple files due to copy/paste. Olivier, do you agree? Alternatively (perhaps even better) move commands that are needed in multiple interfaces to a higher level interface.

Just to check: When I do "launch" inside the bin/mg5 interface, it uses directly the aMCatNLO_run_interface.py, right? Again, we don't want the same code in multiple places.

I'll continue posting as I proceed with the review.

Thanks a lot!
Johan

review: Needs Fixing

lp:~maddevelopers/mg5amcnlo/FKS5 updated on 2012-09-19

277. By marco zaro on 2012-09-19: bug related to editing the cards after launch fixed. added do_open /check_open command to the aCMatNLO_run_interface

Revision history for this message

marco zaro (marco-zaro) wrote on 2012-09-19:

Download full text (4.8 KiB)

Hi Johan,
i just fixed the issue with the open command (cp-ed the do_open and check_open from madevent_interface to amcatnlo_run_interface)
the command used by launch are all from the amcatnlo_run_interface none of them is written inside the FKS one
Cheers
Marco

On 19 Sep 2012, at 09:44, Johan Alwall wrote:

On 19 Sep 2012, at 09:44, Johan Alwall wrote:

> Review: Needs Fixing
> 
> Hello Marco & Paolo,
> 
> Thanks a lot for your super-fast fixes! It's really awesome!
> 
>>> 1. Why does
>>> "INFO: Generating Helas calls for FKS process process: u u~ > e+ e- QED=2
>> QCD=0 [ QCD ] WEIGHTED=10"
>>> come twice?
>> it actually does not appear twice, what (i think) appear twice is u u~ and u~
>> u, which, so far, are treated as different
> 
> You are right - I'm too used to MG5 now :-) Sorry about that!
> 
>>> while the loop_matrix.f only has the first process listed:
>>> C     Process: d d~ > e+ e- QED=2 QCD=0 [ QCD ] WEIGHTED=10
>> processes whose matrix elements are identical.
>> Ok, done
> 
> Thanks!
> 
>>> 5. Would it be a good idea to change the name of "LesHouches" to "Binoth" or
>> "BinothLH"? We already have leshouches for the output to lhef format, and also
>> use the lha format for parameter files, so it can be a bit confusing... (just
>> a suggestion)
>> changed to BinothLHA.f
> 
> Great!
> 
>>> ========================
>>> Running FKS: (using p p > l+ l- as born process)
>>> ========================
>>> 6. What does:
>>> "Found 16 correctly terminated jobs
>>> random seed found in 'randinit' is 33
>>> Total cross-section: 2.58399299e+03 +- 6.7365e+00  (2.6070e-01%)
>>> Found 16 correctly terminated jobs
>>> Total cross-section: 2.23890720e+03 +- 7.7439e+00  (3.4588e-01%)"
>>> mean? (why is the cross section different between the two lines?)
>> The first is the integral of the absolute value of the cross-section, the
>> second the integral of the cross section (They are both needed since the
>> weights are not all >0)
>> I have changed the output in a clearer  way
> 
> Perfect.
> 
>>> 9. I tried running with PYTHIA6PT output, and got the following result:
>> It looks like Pythia6pt is not implemented yet. Checking into the logs they
>> all terminate with "No such MonteCarlo yet".
>> Removed Pythia6pt from the run_card.dat
> 
> Ok, thanks.
> 
>>> 10. I tried running with PYTHIA6Q output, and everything went well until the
>> reweight step:
>>> ...
>>> Note: HERWIG6 output seems to work fine.
>>> 
>> On my laptop everything seems to run fine, i was not able to reproduce this
>> error.
>> Changed the error msg
> 
> When I ran just now, it worked. Sorry for the false alarm.
> 
>>> 11. There is no equivalent to the "launch" command within the mg5 interface
>> in a given PROCNLO... directory. Probably, the best would be to use the same
>> pattern as in ME processes, to move all commands relating to launch into an
>> FKS_run_interface.py (or something like that) corresponding to the madevent.py
>> interface. That way, it's possible to launch a run directly from the PROC
>> directory. Right now, the only script available are
>> generate_amcatnlo_events.sh and run_amcatnlo.sh, which seems completely
>> different from the (very user friendly!) launch command.
>> So, now there is bin/aMCatNLO which open an interface a la madevent, where you
>> can run launch (as in the mg5 shell), compile, generate_events,
>> calculate_xsect. Scripts corresponding to these commands are also in the bin
>> dir
> 
> Very nice. Thanks a lot! 
> 
> There is a problem in the aMC@NLO interface (I'll let you know if I find more):
> 
> 20. aMC@NLO interface fails to open cards:
> "aMC@NLO>generate_events 
> Will run in mode aMC@NLO
> Do you want to edit one cards (press enter to bypass editing)?
>  1 / param   : param_card.dat (be carefull about parameter consistency, especially widths)
>  2 / run     : run_card.dat
>  Path to a valid card.
> [0, done, 1, param, 2, run, enter path][20s to answer] 
> 2
> open /Users/alwall/MadGraph/FKS5/PROCNLO_loop_sm_4/Cards/run_card.dat
> Command "open" not recognized, please try again"
> 
> It seems that the "open" command is not implemented (I thought this would be in the command_interface).
> I would suggest to reuse as much as possible from the existing interfaces (you can include the madevent_interface.py in the bin/internal directory and include it if necessary), so we avoid the same bugs in multiple files due to copy/paste. Olivier, do you agree? Alternatively (perhaps even better) move commands that are needed in multiple interfaces to a higher level interface.
> 
> Just to check: When I do "launch" inside the bin/mg5 interface, it uses directly the aMCatNLO_run_interface.py, right? Again, we don't want the same code in multiple places.
> 
> I'll continue posting as I proceed with the review.
> 
> Thanks a lot!
> Johan
> -- 
> https://code.launchpad.net/~maddevelopers/madgraph5/FKS5/+merge/97762
> Your team MadDevelopers is subscribed to branch lp:~maddevelopers/madgraph5/FKS5.

Revision history for this message

Johan Alwall (johan-alwall) wrote on 2012-09-19:

Hi Marco,

Awesome, thanks!

> i just fixed the issue with the open command (cp-ed the do_open and check_open
> from madevent_interface to amcatnlo_run_interface)
> the command used by launch are all from the amcatnlo_run_interface none of
> them is written inside the FKS one
> Cheers
> Marco

Revision history for this message

Johan Alwall (johan-alwall) wrote on 2012-09-19:

Download full text (5.7 KiB)

Ok, here is my second batch of comments, sorted by header. I keep running numbering just like Olivier, so it's easy for you to tick off everything that is answered or tested. This time, I think most of the comments are to Valentin.

========================
Output to FKS:
========================

21. Where is the g g > l+ l- in the p p > l+ l- process? I see it (in the permutation check) when I run check full p p > l+ l- [QCD] in the aMC@NLO interface (inside bin/mg5), but I can't find any mention of it in the NLO output directory.

========================
Models
========================

22. "aMC@NLO>generate p p > l+ l- [QCD QED]
Command "generate p p > l+ l- [QCD QED]" interrupted with error:
InvalidCmd : Perturbation order QED is not among the perturbation orders allowed for by the loop model."
Is the plan to include QED already for the release, or do we keep that "secret" until we have done some pheno with it?

========================
Python code
========================

base_objects.py:

23.
+ #
+ # ___34_____ The ';' line is a u-quark with ID 21
+ # 45/ ; The '|' line is a gluon with ID 1
+ # ------< ; The numbers are the interactions ID
+ # \___;______ The tag for this loop would be:
+ # 12 ((21,34),(1,45),(1,12))
+ #
I believe you mean "The ';' line is a gluon with ID 21" and "The '|' line is a u quark with ID 1" :-)
I have to say though that I love your extremely clear comments. Thanks!

24.
+ # PS: Notice that in the UFO model, the tag-information is limited to
+ # the minimally relevant one which are the loop particles specified in
+ # in the attribute below.
+ # 'loop_particles' is the list of all the loops giving this same
+ # counterterm contribution. Each loop being represented by a list of the
+ # PDG of the particles (not repeated) constituting it. If the loop particles
+ # are not specified then MG5 will account for this counterterm only once
+ # per concerned vertex.
I don't understand how you get from the loop particles only to the full loop tag (or is this not needed?). I also don't fully understand the last part about MG5 accounting for the counterterm only once - what happens if the loop tag is defined?

25. Model attribute "gauge": I think this warrants a comment to describe how to interpret this information. [0, 1] is quite cryptic...

export_v4.py:

26. create_couplings_main, create_couplings_part, etc: When you have a lot of lines to write that are the same for every output, perhaps it's nicer to use a template file and a replacement dictionary?

27. Please check correspondance between comments and class names, e.g.:
+#===============================================================================
+# ProcessExporterFortranMEGroup
+#===============================================================================
+class ProcessExporterFortranMEGroupComplexMass(ProcessExporterFortranMEGroup):

helas_call_writers.py:

28. get_loop_amp_helas_calls, get_loop_amplitude_helas_calls, FortranUFOHelasCallWrite...

========================
Output to FKS:
========================

========================
Models
========================

========================
Python code
========================

base_objects.py:

23.
+        #
+        #             ___34_____   The ';' line is a u-quark with ID 21
+        #          45/   ;         The '|' line is a gluon with ID 1
+        #     ------<    ;         The numbers are the interactions ID
+        #            \___;______   The tag for this loop would be:
+        #                12          ((21,34),(1,45),(1,12))
+        #                         
I believe you mean "The ';' line is a gluon with ID 21" and "The '|' line is a u quark with ID 1" :-)
I have to say though that I love your extremely clear comments. Thanks!

24.
+        # PS: Notice that in the UFO model, the tag-information is limited to 
+        # the minimally relevant one which are the loop particles specified in
+        # in the attribute below.
+        # 'loop_particles' is the list of all the loops giving this same
+        # counterterm contribution. Each loop being represented by a list of the 
+        # PDG of the particles (not repeated) constituting it. If the loop particles
+        # are not specified then MG5 will account for this counterterm only once
+        # per concerned vertex.
I don't understand how you get from the loop particles only to the full loop tag (or is this not needed?). I also don't fully understand the last part about MG5 accounting for the counterterm only once - what happens if the loop tag is defined?

25. Model attribute "gauge": I think this warrants a comment to describe how to interpret this information. [0, 1] is quite cryptic...

export_v4.py:

helas_call_writers.py:

28. get_loop_amp_helas_calls, get_loop_amplitude_helas_calls, FortranUFOHelasCallWriterOptimized, etc.: Why are these in the iolibs/ file, rather than in the loop specific files? It looks like they could be easily extracted to a separate file. This would perhaps also allow more elegant treatment of the W(1,i,H)?

29. Note that the lines about BGHelasCurrent around line 990 should be removed for now.

madgraph/iolibs/template_files:

30. I would suggest to keep fks-specific template files in madgraph/fks/template_files rather than in madgraph/iolibs/template_files. That way, it's easy to find all FKS-related files.

31. I would suggest to keep loop-specific template files in madgraph/loop/template_files rather than in madgraph/iolibs/template_files/loop and loop_optimized. That way it's easy to find all LOOP-specific files.

madgraph/various:

32. madgraph/various/process_checks.py: Also here, I's suggest to move the loop specific classes LoopMatrixElementEvaluator etc., as well as the loop-specific checks, to a loop-specific file in the madgraph/loop directory. Mainly to make it easy to find everything loop related, and avoid mixing LO and NLO more than necessary from the DRY point of view. This should be fine, since any NLO-specific operations are anyway done from within the FKS_interface and Loop_interface. We also don't want the full set of checks displayed in the madgraph interface, since the loop-specific ones are meaningless for LO processes (or not?).

========================
Process checks
========================

33. How about some help text explaining the meaning of "timing/stability/profile"? It's not obvious that "profile" means "timing and stability"...

34. Trying to run the check command inside the NLO interface:
"check timing u u~ > e+ e- [QCD]
INFO: Generating process: u~ > e+ e- [ all = QCD ] 
Command "check timing u u~ > e+ e- [QCD]" interrupted with error:
InvalidCmd : The number of fermion is odd
Please report this bug on https://bugs.launchpad.net/madgraph5
More information is found in 'MG5_debug'.
Please attach this file to your report."
Is the problem is that it thinks "u" is a param_card? Perhaps place the param_card at the end, or as a --param_card=... tag. 
Apart from this, the check timing command is really nice!

35. Strangely, the above problem doesn't happen when I run
"aMC@NLO>check timing g g > e+ e- [QCD]
INFO: Generating process: g g > e+ e- [ all = QCD ] 
ERROR: Could not find a contributing helicity configuration for process 0_gg_epem. 
INFO: Cleaning old temporary TMP_CHECK* check runs."
Is it reasonable that there are no valid helicity configurations for this process? Or is the output just not working for no-born processes?

Cheers,
Johan

review: Needs Fixing

Revision history for this message

marco zaro (marco-zaro) wrote on 2012-09-19:

Download full text (6.6 KiB)

Ciao Johan,
so a quick answer wrt two issues you pointed:

g g > l+ l- should not be there, as it is loop induced and formally NNLO (order alpha_s^2). also, if if comes from a Z boson (on shell), it is zero because of somebody's theorem (I do not remeber the name...)

I do not think we are planning to support QED as perturbation in the first release of the code, we have not developed it yet...
I'll look through the other poinst
Thanks a lot

Cheers
Marco

On 19 Sep 2012, at 11:17, Johan Alwall wrote:

Ciao Johan,
so a quick answer wrt two issues you pointed:

I do not think we are planning to support QED as perturbation in the first release of the code, we have not developed it yet...
I'll look through the other poinst
Thanks a lot

Cheers
Marco

On 19 Sep 2012, at 11:17, Johan Alwall wrote:

> Review: Needs Fixing
> 
> Ok, here is my second batch of comments, sorted by header. I keep running numbering just like Olivier, so it's easy for you to tick off everything that is answered or tested. This time, I think most of the comments are to Valentin.
> 
> ========================
> Output to FKS:
> ========================
> 
> 21. Where is the g g > l+ l- in the p p > l+ l- process? I see it (in the permutation check) when I run check full p p > l+ l- [QCD] in the aMC@NLO interface (inside bin/mg5), but I can't find any mention of it in the NLO output directory.
> 
> ========================
> Models
> ========================
> 
> 22. "aMC@NLO>generate p p > l+ l- [QCD QED]
> Command "generate p p > l+ l- [QCD QED]" interrupted with error:
> InvalidCmd : Perturbation order QED is not among the perturbation orders allowed for by the loop model."
> Is the plan to include QED already for the release, or do we keep that "secret" until we have done some pheno with it?
> 
> ========================
> Python code
> ========================
> 
> base_objects.py:
> 
> 23.
> +        #
> +        #             ___34_____   The ';' line is a u-quark with ID 21
> +        #          45/   ;         The '|' line is a gluon with ID 1
> +        #     ------<    ;         The numbers are the interactions ID
> +        #            \___;______   The tag for this loop would be:
> +        #                12          ((21,34),(1,45),(1,12))
> +        #                         
> I believe you mean "The ';' line is a gluon with ID 21" and "The '|' line is a u quark with ID 1" :-)
> I have to say though that I love your extremely clear comments. Thanks!
> 
> 24.
> +        # PS: Notice that in the UFO model, the tag-information is limited to 
> +        # the minimally relevant one which are the loop particles specified in
> +        # in the attribute below.
> +        # 'loop_particles' is the list of all the loops giving this same
> +        # counterterm contribution. Each loop being represented by a list of the 
> +        # PDG of the particles (not repeated) constituting it. If the loop particles
> +        # are not specified then MG5 will account for this counterterm only once
> +        # per concerned vertex.
> I don't understand how you get from the loop particles only to the full loop tag (or is this not needed?). I also don't fully understand the last part about MG5 accounting for the counterterm only once - what happens if the loop tag is defined?
> 
> 25. Model attribute "gauge": I think this warrants a comment to describe how to interpret this information. [0, 1] is quite cryptic...
> 
> export_v4.py:
> 
> 26. create_couplings_main, create_couplings_part, etc: When you have a lot of lines to write that are the same for every output, perhaps it's nicer to use a template file and a replacement dictionary?
> 
> 27. Please check correspondance between comments and class names, e.g.:
> +#===============================================================================
> +# ProcessExporterFortranMEGroup
> +#===============================================================================
> +class ProcessExporterFortranMEGroupComplexMass(ProcessExporterFortranMEGroup):
> 
> helas_call_writers.py:
> 
> 28. get_loop_amp_helas_calls, get_loop_amplitude_helas_calls, FortranUFOHelasCallWriterOptimized, etc.: Why are these in the iolibs/ file, rather than in the loop specific files? It looks like they could be easily extracted to a separate file. This would perhaps also allow more elegant treatment of the W(1,i,H)?
> 
> 29. Note that the lines about BGHelasCurrent around line 990 should be removed for now.
> 
> madgraph/iolibs/template_files:
> 
> 30. I would suggest to keep fks-specific template files in madgraph/fks/template_files rather than in madgraph/iolibs/template_files. That way, it's easy to find all FKS-related files.
> 
> 31. I would suggest to keep loop-specific template files in madgraph/loop/template_files rather than in madgraph/iolibs/template_files/loop and loop_optimized. That way it's easy to find all LOOP-specific files.
> 
> madgraph/various:
> 
> 32. madgraph/various/process_checks.py: Also here, I's suggest to move the loop specific classes LoopMatrixElementEvaluator etc., as well as the loop-specific checks, to a loop-specific file in the madgraph/loop directory. Mainly to make it easy to find everything loop related, and avoid mixing LO and NLO more than necessary from the DRY point of view. This should be fine, since any NLO-specific operations are anyway done from within the FKS_interface and Loop_interface. We also don't want the full set of checks displayed in the madgraph interface, since the loop-specific ones are meaningless for LO processes (or not?).
> 
> ========================
> Process checks
> ========================
> 
> 33. How about some help text explaining the meaning of "timing/stability/profile"? It's not obvious that "profile" means "timing and stability"...
> 
> 34. Trying to run the check command inside the NLO interface:
> "check timing u u~ > e+ e- [QCD]
> INFO: Generating process: u~ > e+ e- [ all = QCD ] 
> Command "check timing u u~ > e+ e- [QCD]" interrupted with error:
> InvalidCmd : The number of fermion is odd
> Please report this bug on https://bugs.launchpad.net/madgraph5
> More information is found in 'MG5_debug'.
> Please attach this file to your report."
> Is the problem is that it thinks "u" is a param_card? Perhaps place the param_card at the end, or as a --param_card=... tag. 
> Apart from this, the check timing command is really nice!
> 
> 35. Strangely, the above problem doesn't happen when I run
> "aMC@NLO>check timing g g > e+ e- [QCD]
> INFO: Generating process: g g > e+ e- [ all = QCD ] 
> ERROR: Could not find a contributing helicity configuration for process 0_gg_epem. 
> INFO: Cleaning old temporary TMP_CHECK* check runs."
> Is it reasonable that there are no valid helicity configurations for this process? Or is the output just not working for no-born processes?
> 
> Cheers,
> Johan
> -- 
> https://code.launchpad.net/~maddevelopers/madgraph5/FKS5/+merge/97762
> Your team MadDevelopers is subscribed to branch lp:~maddevelopers/madgraph5/FKS5.

lp:~maddevelopers/mg5amcnlo/FKS5 updated on 2012-09-19

278. By marco zaro on 2012-09-19: added MCatNLO in Template/NLO/Source, corresponding to v. 404 op lp:madfks
279. By marco zaro on 2012-09-19: moved MCatNLO folder, started automatizing also the shower part
280. By marco zaro on 2012-09-19: some MCatNLO fortran source files were marked as executables. done chmod -x on them
created a command run_mcatnlo in amcatnlo_run_interface
281. By Olivier Mattelaer on 2012-09-19: temporary fix in order to make FKS5 runable.
Please Marco check my modif and look if you agree with it.

Revision history for this message

Olivier Mattelaer (olivier-mattelaer) wrote on 2012-09-19:

Hi,

As Johan, said this is very impressive, especially by the accuracy of the warning.

36. (I just fix it in fact) in the revision 280, Mg5 crash on loading the file (since one variable was not define) I fix it in a simple way in 281. Pleas Marco check that this is indeed what you had in mind.

37. In aMCatNLO_run_interface.
In MG mode you do:
from madgraph import InvalidCmd, aMCatNLOError
while in ME mode you import:
from internal import InvalidCmd, MadGraph5Error
meaning that aMCatNLOError is not define in that mode.

38. You use aMCatNLOError as configuration error.
Meaning that such error is not a bug but a configuration error of the machine. This was designed for no internet connection, no g77/gfortran compiler,…
But looks like you raise it for kind of large type of error:
(like line 819, 948, 983, …)
Might be better to set another error as configuration error then (since those one should ask to report a bug report and not suggest to deal the problem by themselves and if needed ask a question).

39. when compiling Cuttools. What do you think about changing the message:
INFO: Compiling CutTools
by
INFO: Compiling CutTools (this might takes a couple minutes)

40. I crash with this error:
Command "output " interrupted in sub-command:
"output" with error:
AttributeError : 'MasterCmd' object has no attribute 'fastjet_config'
Please report this bug on https://bugs.launchpad.net/madgraph5
More information is found in 'MG5_debug'.
Please attach this file to your report.

This is a typical example of Configuration error. And which require a bit of information on
1) where to find the program to use.
2) How to link it.

41. In general (also in MG5), I found that we write too many information on the screen.
But in particular here:
INFO: Writing files in P0_ucx_ucx
INFO: Creating files in directory V0_ucx_ucx
INFO: Computing diagram color coefficients
INFO: Generating born Feynman diagrams for Process: u c~ > u c~ QED=0 QCD=2 [ QCD ] WEIGHTED=6

Would it be possible to reduce to:
INFO: Generating output for Process: u c~ > u c~ QED=0 QCD=2 [ QCD ] WEIGHTED=6

42. the help of generate/add should be updated as well as the autocompletion.

Otherwise what do you think about a wiki page for this merge.
Just including the number associated to the point that Johan and I (or other made)
and the status (pending, done,…) This will need a bit of work (to keep this up-to-date) but this can help us. If you agree I will made it.

Cheers,

Olivier

Hi,

As Johan, said this is very impressive, especially by the accuracy of the warning.

39. when compiling Cuttools. What do you think about changing the message:
INFO: Compiling CutTools
by
INFO: Compiling CutTools (this might takes a couple minutes)

This is a typical example of Configuration error. And which require a bit of information on 
1) where to find the program to use.
2) How to link it.

41. In general (also in MG5), I found that we write too many information on the screen.
But in particular here:
INFO: Writing files in P0_ucx_ucx 
INFO: Creating files in directory V0_ucx_ucx 
INFO: Computing diagram color coefficients 
INFO: Generating born Feynman diagrams for Process: u c~ > u c~ QED=0 QCD=2 [ QCD ] WEIGHTED=6

Would it be possible to reduce to:
INFO: Generating output for Process: u c~ > u c~ QED=0 QCD=2 [ QCD ] WEIGHTED=6

42. the help of generate/add should be updated as well as the autocompletion.

Otherwise what do you think about a wiki page for this merge. 
Just including the number associated to the point that Johan and I (or other made)
and the status (pending, done,…) This will need a bit of work (to keep this up-to-date) but this can help us. If you agree I will made it.

Cheers,

Olivier

review: Needs Fixing

Revision history for this message

Johan Alwall (johan-alwall) wrote on 2012-09-20:

Hello Olivier, all,

So we are now using a common numbering? Ok, let's try to keep up with that. :-)

> 36. (I just fix it in fact) in the revision 280, Mg5 crash on loading the file
> (since one variable was not define) I fix it in a simple way in 281. Pleas
> Marco check that this is indeed what you had in mind.

Thanks!

> 41. In general (also in MG5), I found that we write too many information on
> the screen.
> But in particular here:
> INFO: Writing files in P0_ucx_ucx
> INFO: Creating files in directory V0_ucx_ucx
> INFO: Computing diagram color coefficients
> INFO: Generating born Feynman diagrams for Process: u c~ > u c~ QED=0 QCD=2 [
> QCD ] WEIGHTED=6
>
> Would it be possible to reduce to:
> INFO: Generating output for Process: u c~ > u c~ QED=0 QCD=2 [ QCD ]
> WEIGHTED=6

In fact I don't agree here. The full information is useful to give the user a quick overview of what is written and where to find it (it is certainly very helpful for me!). For the user who doesn't care, he won't look anyway. So I would suggest to keep it exactly as it is. Just make sure that any warning/important info messages are output at the end, so they don't disappear in the flood.

> Otherwise what do you think about a wiki page for this merge.
> Just including the number associated to the point that Johan and I (or other
> made)
> and the status (pending, done,…) This will need a bit of work (to keep this
> up-to-date) but this can help us. If you agree I will made it.

This is a very good idea. Let's keep the discussion/posting of comments here (so it's all in one place, and also for future reference), but you keep a wiki page with the progress to make sure you don't miss anything important.

Cheers,
Johan

Revision history for this message

Johan Alwall (johan-alwall) wrote on 2012-09-20:

Download full text (3.2 KiB)

Ok I'm continuing my review.

========================
Interfaces
========================

43. Commands that should be used in all interfaces (in particular open, but perhaps also the main do_set routine) should be put in a common place, most naturally extended_cmd.py.

44. Commands that are common to all process generation interfaces (madgraph_interface, FKS_interface, etc.) and where we want to switch interface depending on the command, would be most natural to keep in a common interface. Examples are do_generate, do_launch, and perhaps also do_output (or we just assume that the user is not stupid enough to switch interface between a generate and an output command). Probably also set should be defined here, since we should be able to set all options in all interfaces. I'm not sure if the best is to put these in the master_interface or to have them in a separate mother interface. What do you think, Olivier?

45. When doing "launch ./DIR" from the bin/mg5 (or other) interface, it should be possible to automatically switch interface to the correct one (by looking at the directory). Marco had written something about this in rev. 273, but it doesn't seem to work.

46. For the check timing (as well, in fact, as all other commands whose main result is to display information) we should use Olivier's technique to display the result both in the page view mode and on the screen after exiting page view. I just ran a timing check, and when I pressed "q", it disappeared and isn't saved anywhere. This is also a comment to Olivier, since I think we should have the same functionality e.g. for display diagrams_text. Olivier, I think you figured out some way to do that, right? Let's use the same standard command everywhere (defined in extended_cmd.py).

47. Let's use a common standard for the capitalization of interface names in the switch command (it's funny with ML5 but mg5). I would suggest MG5, ML5, aMC@NLO, except that at this point everything is MG5... But perhaps that is clear enough.

48. Let's use a common standard also for capitalization of python modules. It looks nicer if all modules are all-lowercase (and might possibly avoid some problems in non-case-sensitive systems?), i.e., loop_interface.py, fks_interface.py. Or did you have some other thought about this?

49. There seems to be some problem with the storing of the command history between runs - when I close and restart the bin/mg5 interface, it doesn't remember any commands I entered in the FKS5 branch directory.

fks_interface.py:

50. When I do
display diagrams_text
there is no output. This can be quite useful in certain situations.

51. When I do
display diagrams
there is nothing in the resulting ps files indicating what is born and what is real. How about something like "Real process u~ u > mu+ mu- g corresponding to born process u~ u > mu+ mu- WEIGHTED=... [QCD] WEIGHTED=..."? Also for the virtual, although it's obvious from the presence of a loop, it could still be indicated. Also, why does it say [tree=QCD] for the reals and virtuals?

52. Same as above for display processes. There is no indication which processes have which function.

Sorry for the cosmetics, but I guess this is the...

Ok I'm continuing my review.

========================
Interfaces
========================

43. Commands that should be used in all interfaces (in particular open, but perhaps also the main do_set routine) should be put in a common place, most naturally extended_cmd.py.

fks_interface.py:

50. When I do
display diagrams_text
there is no output. This can be quite useful in certain situations.

52. Same as above for display processes. There is no indication which processes have which function.

Sorry for the cosmetics, but I guess this is the right time to bring it up (and it only takes seconds to fix). :-)

review: Needs Fixing

lp:~maddevelopers/mg5amcnlo/FKS5 updated on 2012-09-20

282. By marco zaro on 2012-09-20: renamed FKS_interface -> amcatnlo_interface
display diagrams_text works (point 50 of the review list) in amcatnlo_interface, and, as display processes, if no other argument is given (real,born,virt), prints a line explaining if the processes are born/real/virt (point 52). To be done (I do not really know how to) for display diagrams (51)
added amcatnlo_launcher in launch external program, so that now launch PATH works from mg5> also for a NLO process (point 45)

Revision history for this message

marco zaro (marco-zaro) wrote on 2012-09-20:

Download full text (3.6 KiB)

Hi,
i have fixed points 45 48 50 and 52 in rev 282 on lp
Cheers
Marco

On 20 Sep 2012, at 08:24, Johan Alwall wrote:

> Review: Needs Fixing
>
> Ok I'm continuing my review.
>
> ========================
> Interfaces
> ========================
>
> 43. Commands that should be used in all interfaces (in particular open, but perhaps also the main do_set routine) should be put in a common place, most naturally extended_cmd.py.
>
> 44. Commands that are common to all process generation interfaces (madgraph_interface, FKS_interface, etc.) and where we want to switch interface depending on the command, would be most natural to keep in a common interface. Examples are do_generate, do_launch, and perhaps also do_output (or we just assume that the user is not stupid enough to switch interface between a generate and an output command). Probably also set should be defined here, since we should be able to set all options in all interfaces. I'm not sure if the best is to put these in the master_interface or to have them in a separate mother interface. What do you think, Olivier?
>
> 45. When doing "launch ./DIR" from the bin/mg5 (or other) interface, it should be possible to automatically switch interface to the correct one (by looking at the directory). Marco had written something about this in rev. 273, but it doesn't seem to work.
>
> 46. For the check timing (as well, in fact, as all other commands whose main result is to display information) we should use Olivier's technique to display the result both in the page view mode and on the screen after exiting page view. I just ran a timing check, and when I pressed "q", it disappeared and isn't saved anywhere. This is also a comment to Olivier, since I think we should have the same functionality e.g. for display diagrams_text. Olivier, I think you figured out some way to do that, right? Let's use the same standard command everywhere (defined in extended_cmd.py).
>
> 47. Let's use a common standard for the capitalization of interface names in the switch command (it's funny with ML5 but mg5). I would suggest MG5, ML5, aMC@NLO, except that at this point everything is MG5... But perhaps that is clear enough.
>
> 48. Let's use a common standard also for capitalization of python modules. It looks nicer if all modules are all-lowercase (and might possibly avoid some problems in non-case-sensitive systems?), i.e., loop_interface.py, fks_interface.py. Or did you have some other thought about this?
>
> 49. There seems to be some problem with the storing of the command history between runs - when I close and restart the bin/mg5 interface, it doesn't remember any commands I entered in the FKS5 branch directory.
>
> fks_interface.py:
>
> 50. When I do
> display diagrams_text
> there is no output. This can be quite useful in certain situations.
>
> 51. When I do
> display diagrams
> there is nothing in the resulting ps files indicating what is born and what is real. How about something like "Real process u~ u > mu+ mu- g corresponding to born process u~ u > mu+ mu- WEIGHTED=... [QCD] WEIGHTED=..."? Also for the virtual, although it's obvious from the presence of a loop, it could still be indicated. Also, why ...

Hi,
i have fixed points 45 48 50 and 52 in rev 282 on lp
Cheers
Marco

On 20 Sep 2012, at 08:24, Johan Alwall wrote:

> Review: Needs Fixing
> 
> Ok I'm continuing my review.
> 
> ========================
> Interfaces
> ========================
> 
> 43. Commands that should be used in all interfaces (in particular open, but perhaps also the main do_set routine) should be put in a common place, most naturally extended_cmd.py.
> 
> 44. Commands that are common to all process generation interfaces (madgraph_interface, FKS_interface, etc.) and where we want to switch interface depending on the command, would be most natural to keep in a common interface. Examples are do_generate, do_launch, and perhaps also do_output (or we just assume that the user is not stupid enough to switch interface between a generate and an output command). Probably also set should be defined here, since we should be able to set all options in all interfaces. I'm not sure if the best is to put these in the master_interface or to have them in a separate mother interface. What do you think, Olivier?
> 
> 45. When doing "launch ./DIR" from the bin/mg5 (or other) interface, it should be possible to automatically switch interface to the correct one (by looking at the directory). Marco had written something about this in rev. 273, but it doesn't seem to work.
> 
> 46. For the check timing (as well, in fact, as all other commands whose main result is to display information) we should use Olivier's technique to display the result both in the page view mode and on the screen after exiting page view. I just ran a timing check, and when I pressed "q", it disappeared and isn't saved anywhere. This is also a comment to Olivier, since I think we should have the same functionality e.g. for display diagrams_text. Olivier, I think you figured out some way to do that, right? Let's use the same standard command everywhere (defined in extended_cmd.py).
> 
> 47. Let's use a common standard for the capitalization of interface names in the switch command (it's funny with ML5 but mg5). I would suggest MG5, ML5, aMC@NLO, except that at this point everything is MG5... But perhaps that is clear enough.
> 
> 48. Let's use a common standard also for capitalization of python modules. It looks nicer if all modules are all-lowercase (and might possibly avoid some problems in non-case-sensitive systems?), i.e., loop_interface.py, fks_interface.py. Or did you have some other thought about this?
> 
> 49. There seems to be some problem with the storing of the command history between runs - when I close and restart the bin/mg5 interface, it doesn't remember any commands I entered in the FKS5 branch directory.
> 
> fks_interface.py:
> 
> 50. When I do
> display diagrams_text
> there is no output. This can be quite useful in certain situations.
> 
> 51. When I do
> display diagrams
> there is nothing in the resulting ps files indicating what is born and what is real. How about something like "Real process u~ u > mu+ mu- g corresponding to born process u~ u > mu+ mu- WEIGHTED=... [QCD] WEIGHTED=..."? Also for the virtual, although it's obvious from the presence of a loop, it could still be indicated. Also, why does it say [tree=QCD] for the reals and virtuals?
> 
> 52. Same as above for display processes. There is no indication which processes have which function.
> 
> Sorry for the cosmetics, but I guess this is the right time to bring it up (and it only takes seconds to fix). :-)
> -- 
> https://code.launchpad.net/~maddevelopers/madgraph5/FKS5/+merge/97762
> Your team MadDevelopers is subscribed to branch lp:~maddevelopers/madgraph5/FKS5.

lp:~maddevelopers/mg5amcnlo/FKS5 updated on 2012-09-20

283. By Paolo Torrielli on 2012-09-20: updates in the scripts that run mcatnlo for pythia6 and herwig6

Revision history for this message

marco zaro (marco-zaro) wrote on 2012-09-20:

Download full text (3.5 KiB)

Hi Olivier,
thanks for the fixes 36/37
they are perfect.
Can we talk a bit about the errors?In amcatnlo_run_interface i define

class aMCatNLOError(Exception):
pass
what do you mean by configuration error?
sorry but i may have done some mistakes, still i do not know what the differences are and when to raise an Error and a ConfigurationError (or at least, what the policy is about this for mg5)
furthermore
for the issue 40
i added in input/mg5_configuration.txt two lines, one for the lhapdf-config path and one for the fastjet-config path
it may be that the your mg5_configuration that is read in your case is not the one in input/ (do you have one for mg5 in ~/.mg5) and it has not those entries
Let me know if this is the case
Cheers
Marco

On 20 Sep 2012, at 01:21, Olivier Mattelaer wrote:

> Review: Needs Fixing
>
> Hi,
>
> As Johan, said this is very impressive, especially by the accuracy of the warning.
>
> 36. (I just fix it in fact) in the revision 280, Mg5 crash on loading the file (since one variable was not define) I fix it in a simple way in 281. Pleas Marco check that this is indeed what you had in mind.
>
> 37. In aMCatNLO_run_interface.
> In MG mode you do:
> from madgraph import InvalidCmd, aMCatNLOError
> while in ME mode you import:
> from internal import InvalidCmd, MadGraph5Error
> meaning that aMCatNLOError is not define in that mode.
>
> 38. You use aMCatNLOError as configuration error.
> Meaning that such error is not a bug but a configuration error of the machine. This was designed for no internet connection, no g77/gfortran compiler,…
> But looks like you raise it for kind of large type of error:
> (like line 819, 948, 983, …)
> Might be better to set another error as configuration error then (since those one should ask to report a bug report and not suggest to deal the problem by themselves and if needed ask a question).
>
> 39. when compiling Cuttools. What do you think about changing the message:
> INFO: Compiling CutTools
> by
> INFO: Compiling CutTools (this might takes a couple minutes)
>
> 40. I crash with this error:
> Command "output " interrupted in sub-command:
> "output" with error:
> AttributeError : 'MasterCmd' object has no attribute 'fastjet_config'
> Please report this bug on https://bugs.launchpad.net/madgraph5
> More information is found in 'MG5_debug'.
> Please attach this file to your report.
>
> This is a typical example of Configuration error. And which require a bit of information on
> 1) where to find the program to use.
> 2) How to link it.
>
> 41. In general (also in MG5), I found that we write too many information on the screen.
> But in particular here:
> INFO: Writing files in P0_ucx_ucx
> INFO: Creating files in directory V0_ucx_ucx
> INFO: Computing diagram color coefficients
> INFO: Generating born Feynman diagrams for Process: u c~ > u c~ QED=0 QCD=2 [ QCD ] WEIGHTED=6
>
> Would it be possible to reduce to:
> INFO: Generating output for Process: u c~ > u c~ QED=0 QCD=2 [ QCD ] WEIGHTED=6
>
> 42. the help of generate/add should be updated as well as the autocompletion.
>
>
>
> Otherwise what do you think about a wiki page for this merge.
> Just including the numbe...

Hi Olivier,
thanks for the fixes 36/37
they are perfect.
Can we talk a bit about the errors?In amcatnlo_run_interface i define

class aMCatNLOError(Exception):
    pass
what do you mean by configuration error?
sorry but i may have done some mistakes, still i do not know what the differences are and when to raise an Error and a ConfigurationError (or at least, what the policy is  about this for mg5)
furthermore
for the issue 40
i added in input/mg5_configuration.txt two lines, one for the lhapdf-config path and one for the fastjet-config path
it may be that the your mg5_configuration that is read in your case is not the one in input/ (do you have one for mg5 in ~/.mg5) and it has not those entries
Let me know if this is the case
Cheers
Marco

On 20 Sep 2012, at 01:21, Olivier Mattelaer wrote:

> Review: Needs Fixing
> 
> Hi, 
> 
> As Johan, said this is very impressive, especially by the accuracy of the warning.
> 
> 36. (I just fix it in fact) in the revision 280, Mg5 crash on loading the file (since one variable was not define) I fix it in a simple way in 281. Pleas Marco check that this is indeed what you had in mind.
> 
> 37. In aMCatNLO_run_interface.
> In MG mode you do:
> from madgraph import InvalidCmd, aMCatNLOError
> while in ME mode you import:
> from internal import InvalidCmd, MadGraph5Error
> meaning that aMCatNLOError is not define in that mode.
> 
> 38. You use aMCatNLOError as configuration error.
> Meaning that such error is not a bug but a configuration error of the machine. This was designed for no internet connection, no g77/gfortran compiler,…
> But looks like you raise it for kind of large type of error:
> (like line 819, 948, 983, …)
> Might be better to set another error as configuration error then (since those one should ask to report a bug report and not suggest to deal the problem by themselves and if needed ask a question).
> 
> 39. when compiling Cuttools. What do you think about changing the message:
> INFO: Compiling CutTools
> by
> INFO: Compiling CutTools (this might takes a couple minutes)
> 
> 40. I crash with this error:
> Command "output " interrupted in sub-command:
> "output" with error:
> AttributeError : 'MasterCmd' object has no attribute 'fastjet_config'
> Please report this bug on https://bugs.launchpad.net/madgraph5
> More information is found in 'MG5_debug'.
> Please attach this file to your report.
> 
> This is a typical example of Configuration error. And which require a bit of information on 
> 1) where to find the program to use.
> 2) How to link it.
> 
> 41. In general (also in MG5), I found that we write too many information on the screen.
> But in particular here:
> INFO: Writing files in P0_ucx_ucx 
> INFO: Creating files in directory V0_ucx_ucx 
> INFO: Computing diagram color coefficients 
> INFO: Generating born Feynman diagrams for Process: u c~ > u c~ QED=0 QCD=2 [ QCD ] WEIGHTED=6 
> 
> Would it be possible to reduce to:
> INFO: Generating output for Process: u c~ > u c~ QED=0 QCD=2 [ QCD ] WEIGHTED=6
> 
> 42. the help of generate/add should be updated as well as the autocompletion.
> 
> 
> 
> Otherwise what do you think about a wiki page for this merge. 
> Just including the number associated to the point that Johan and I (or other made)
> and the status (pending, done,…) This will need a bit of work (to keep this up-to-date) but this can help us. If you agree I will made it. 
> 
> Cheers,
> 
> 
> Olivier
> 
> 
> 
> -- 
> https://code.launchpad.net/~maddevelopers/madgraph5/FKS5/+merge/97762
> Your team MadDevelopers is subscribed to branch lp:~maddevelopers/madgraph5/FKS5.

Revision history for this message

marco zaro (marco-zaro) wrote on 2012-09-20:

Download full text (4.5 KiB)

Hi all,
I just committed rev 284, in which also mcatnlo is automatized in the whole chain (only for hw6 for today).
The status for now is that the user should write his own analysis and write the filename in the input file.
Together with Paolo we were thinking to export the showered event in the stdhep format, so that the analysis can be done externally with madanalysis.
This requires the stdhep code installed on the computer (http://cepa.fnal.gov/psm/stdhep/getStdHep.shtml).
Now:
shall we assume that every user has it (and hence will put the path to the libraries in the mg5_configuration.txt as for fastjet/lhapdf....)
or shall we include this in the mg5 release (e.g. in vendor)?
Let me know
Cheers
Marco

On 20 Sep 2012, at 12:16, marco zaro wrote:

Hi all,
I just committed rev 284, in which also mcatnlo is automatized in the whole chain (only for hw6 for today).
The status for now is that the user should write his own analysis and write the filename in the input file.
Together with Paolo we were thinking  to export the showered event in the stdhep format, so that the analysis can be done externally with madanalysis.
This requires the stdhep code installed on the computer (http://cepa.fnal.gov/psm/stdhep/getStdHep.shtml).
Now:
shall we assume that every user has it (and hence will put the path to the libraries in the mg5_configuration.txt as for fastjet/lhapdf....)
or shall we include this in the mg5 release (e.g. in vendor)?
Let me know
Cheers
Marco

On 20 Sep 2012, at 12:16, marco zaro wrote:

> Hi Olivier,
> thanks for the fixes 36/37
> they are perfect.
> Can we talk a bit about the errors?In amcatnlo_run_interface i define
> 
> class aMCatNLOError(Exception):
>    pass
> what do you mean by configuration error?
> sorry but i may have done some mistakes, still i do not know what the differences are and when to raise an Error and a ConfigurationError (or at least, what the policy is  about this for mg5)
> furthermore
> for the issue 40
> i added in input/mg5_configuration.txt two lines, one for the lhapdf-config path and one for the fastjet-config path
> it may be that the your mg5_configuration that is read in your case is not the one in input/ (do you have one for mg5 in ~/.mg5) and it has not those entries
> Let me know if this is the case
> Cheers
> Marco
> 
> 
> 
> On 20 Sep 2012, at 01:21, Olivier Mattelaer wrote:
> 
>> Review: Needs Fixing
>> 
>> Hi, 
>> 
>> As Johan, said this is very impressive, especially by the accuracy of the warning.
>> 
>> 36. (I just fix it in fact) in the revision 280, Mg5 crash on loading the file (since one variable was not define) I fix it in a simple way in 281. Pleas Marco check that this is indeed what you had in mind.
>> 
>> 37. In aMCatNLO_run_interface.
>> In MG mode you do:
>> from madgraph import InvalidCmd, aMCatNLOError
>> while in ME mode you import:
>> from internal import InvalidCmd, MadGraph5Error
>> meaning that aMCatNLOError is not define in that mode.
>> 
>> 38. You use aMCatNLOError as configuration error.
>> Meaning that such error is not a bug but a configuration error of the machine. This was designed for no internet connection, no g77/gfortran compiler,…
>> But looks like you raise it for kind of large type of error:
>> (like line 819, 948, 983, …)
>> Might be better to set another error as configuration error then (since those one should ask to report a bug report and not suggest to deal the problem by themselves and if needed ask a question).
>> 
>> 39. when compiling Cuttools. What do you think about changing the message:
>> INFO: Compiling CutTools
>> by
>> INFO: Compiling CutTools (this might takes a couple minutes)
>> 
>> 40. I crash with this error:
>> Command "output " interrupted in sub-command:
>> "output" with error:
>> AttributeError : 'MasterCmd' object has no attribute 'fastjet_config'
>> Please report this bug on https://bugs.launchpad.net/madgraph5
>> More information is found in 'MG5_debug'.
>> Please attach this file to your report.
>> 
>> This is a typical example of Configuration error. And which require a bit of information on 
>> 1) where to find the program to use.
>> 2) How to link it.
>> 
>> 41. In general (also in MG5), I found that we write too many information on the screen.
>> But in particular here:
>> INFO: Writing files in P0_ucx_ucx 
>> INFO: Creating files in directory V0_ucx_ucx 
>> INFO: Computing diagram color coefficients 
>> INFO: Generating born Feynman diagrams for Process: u c~ > u c~ QED=0 QCD=2 [ QCD ] WEIGHTED=6 
>> 
>> Would it be possible to reduce to:
>> INFO: Generating output for Process: u c~ > u c~ QED=0 QCD=2 [ QCD ] WEIGHTED=6
>> 
>> 42. the help of generate/add should be updated as well as the autocompletion.
>> 
>> 
>> 
>> Otherwise what do you think about a wiki page for this merge. 
>> Just including the number associated to the point that Johan and I (or other made)
>> and the status (pending, done,…) This will need a bit of work (to keep this up-to-date) but this can help us. If you agree I will made it. 
>> 
>> Cheers,
>> 
>> 
>> Olivier
>> 
>> 
>> 
>> -- 
>> https://code.launchpad.net/~maddevelopers/madgraph5/FKS5/+merge/97762
>> Your team MadDevelopers is subscribed to branch lp:~maddevelopers/madgraph5/FKS5.
> 
> 
> -- 
> https://code.launchpad.net/~maddevelopers/madgraph5/FKS5/+merge/97762
> Your team MadDevelopers is subscribed to branch lp:~maddevelopers/madgraph5/FKS5.

lp:~maddevelopers/mg5amcnlo/FKS5 updated on 2012-09-25

284. By marco zaro on 2012-09-20

added command to shower generated events (included in the launch command)
run_amcatnlo + event file will shower the given event file.
works with/without lhapdf, for now only with herwig6
the analyse has still to be written by hand and written in the input file, but the idea is to generate a hepmc file to be passed to madanalisys

285. By marco zaro on 2012-09-21

also pythia6q mode works for MCatNLO

286. By marco zaro on 2012-09-21

added check to link lhapdf when launching mcatnlo (it could happen that the libs are not there)

287. By marco zaro on 2012-09-21

fixed FKS- loop optimized output. the files in bin/internal were not cp-ed

288. By Paolo Torrielli on 2012-09-21

irrelevant change in madfks_pydriver.f

289. By Paolo Torrielli on 2012-09-21

adapting the hw++ bash scripts to those for hw6 and py6. it does not work yet, working on that.
updated the Card/mcatnlo_card.dat consequently
irrelevant changes in the scripts for hw6 and py6

290. By marco zaro on 2012-09-21

fixed bug with the -h flag of the scripts in bin/
tests are always compiled, and python checks that none of them failed
V and F event order exchanged (now V first)

291. By Paolo Torrielli on 2012-09-21

a) updated the script for HWPP in order to make it maximally similar to the others
b) removed file HWPPInput.inputs
c) fixed a previous mistake in the scripts for HW6 and PY6 linked to the name of the
executable for default pdfs (mistake made in version 289)
d) updated the mcatnlo_card.dat, allowing also for hadronization on/off for PY6, HWPP
e) updated madfks_pydriver.f consequently

STATUS: for HWPP it does not work yet, cause I did not have time to try the changes out.
Working on that.

292. By Olivier Mattelaer on 2012-09-21

fixing the drawing of the diagram for Loop cases (following last loop format)

293. By marco zaro on 2012-09-24

bug fixed: jobs with no events in some channels made MG quit.

294. By marco zaro on 2012-09-24

aestethic changes in the way mcatnlo runs.
now one folder (named RUN_$MCMODE_1/2/..) per run is created, which contains executable, input and output

295. By marco zaro on 2012-09-24

bug fixed: after launch command, the working dir is now the same as before

296. By marco zaro on 2012-09-24

fixed bug in rev294: the event file was not linked correctly in the running dir.
also modified hw6 py6q and py6pt scripts in order to read infos in the header of the event file in its original position

297. By marco zaro on 2012-09-24

fixed ch-dir back to original dir after launch

298. By marco zaro on 2012-09-24

added quick tutorial for aMC@NLO (type tutorial_nlo) and completion for output in amcatnlo_interface

299. By marco zaro on 2012-09-24

fixed a character which lead to problems in the tutorial_nlo

300. By marco zaro on 2012-09-25

mcatnlo compiles with stdhep (need to be installed by hand and that the path is specified into MCatNLO_MadFKS.inputs)
The MCat_NLO_MadFKS.inputs_an correspond to the script needed to perform an analyse
updated the interface

301. By Paolo Torrielli on 2012-09-25

fixes in the hw++ script, now it compiles. still a few adjustments needed for it to work properly

302. By marco zaro on 2012-09-25

added StdHEP to the packages that can be installed via the install command.
If it is not installed, a nice warning will be printed to the user, and the generation of the event will terminate without running mcatnlo
PROBLEM: the original (parton level) event file is overwritten when showering with MC@NLO-PYQ, probably there is a conflict with the assigned files unit.
The run terminates when reading the second event

Revision history for this message

Johan Alwall (johan-alwall) wrote on 2012-09-26:

Hello Marco,

It seems something went wrong when you created the tutorial - I get tutorial text without turning it on. Also, the tutorial text is for aMC@NLO although I'm in the mg5 interface. I simply did
bin/mg5
generate p p > l+ l-

and the text appeared.

Cheers,
Johan

review: Needs Fixing

lp:~maddevelopers/mg5amcnlo/FKS5 updated on 2012-09-26

303. By Olivier Mattelaer on 2012-09-26: fix tutorial_nlo to be always printed
304. By marco zaro on 2012-09-26: removed non-NLO relevant lines from tutorial_nlo
fixed bug: error 'no amplitudes generated' was printed after display diagrams in aMC@NLO mode
305. By marco zaro on 2012-09-26: the MCatNLO folder in Template/NLO has been removed
the MCatNLO package (together with StdHep) can be installed by typing
install MCatNLO-utilities

Revision history for this message

Johan Alwall (johan-alwall) wrote on 2012-09-27:

Comments about the event output file:

53) Adding on to comment 12 about the Events/run_01/ directory structure, I would also suggest to have a more informative name for the events_1 file. How about amcatnlo_events.lhe, since it's an lhe file that can be directly run through a shower generator? I would suggest to pretty much copy (with suitable modifications) the full machinery for event file treatment and names that Olivier has implemented for LO.

54) Please create a new xml block for any information you want to keep in the header of the .lhe file. Right now, the header starts as
<LesHouchesEvents version="1.0">
  
  <header>
     1000
  <MG5ProcCard>
etc.
"HERWIG6" is crucial information, so it should absolutely be within a block (e.g. <NLOMC>) so it can easily be read by your shower MC files, which can then abort (if it's the wrong MC) or select appropriate settings (if it's PYQ/PYPT). Furthermore, the "1000" which suddenly comes at the top and bottom of the header should probably be in a block similar to the <MGGenerationInfo> block in the LO files.

Many thanks,
Johan

review: Needs Fixing

lp:~maddevelopers/mg5amcnlo/FKS5 updated on 2012-09-27

306. By marco zaro on 2012-09-27: the generated events are stored in Events/run_i (as for LO)
started some (small) work to have the html available also at NLO

Revision history for this message

marco zaro (marco-zaro) wrote on 2012-09-27:

Hi Johan,
thanks for the review
for 54) the mc is also written inside the run_card in the header, and there is where we check that it is the correct one
53) i have pushed rev 306, in which the lhe and hep file are stored in the run_i dirs under events. Also some mods towards having html working are there

this is what you get at the end of a run

The /Users/marcozaro/PhD/mg5/FKS5/FKS5/wNLO12/Events/run_01/events.lhe file has been generated.
It contains 10000 NLO events to be showered
   Prepairing MCatNLO run
   Compiling MCatNLO for HERWIG6...
                     ... done
   Running MCatNLO in /Users/marcozaro/PhD/mg5/FKS5/FKS5/wNLO12/MCATNLO/RUN_HERWIG6_1 (this may take some time)...
The file /Users/marcozaro/PhD/mg5/FKS5/FKS5/wNLO12/Events/run_01/events_HERWIG6.hep has been generated.
It contains showered and hadronized events in the StdHEP format obtained showering the parton-level event file /Users/marcozaro/PhD/mg5/FKS5/FKS5/wNLO12/Events/run_01/events.lhe

On 27 Sep 2012, at 15:23, Johan Alwall wrote:

> Review: Needs Fixing
>
> Comments about the event output file:
>
> 53) Adding on to comment 12 about the Events/run_01/ directory structure, I would also suggest to have a more informative name for the events_1 file. How about amcatnlo_events.lhe, since it's an lhe file that can be directly run through a shower generator? I would suggest to pretty much copy (with suitable modifications) the full machinery for event file treatment and names that Olivier has implemented for LO.
>
> 54) Please create a new xml block for any information you want to keep in the header of the .lhe file. Right now, the header starts as
> <LesHouchesEvents version="1.0">
> 
> <header>
> 1000
> <MG5ProcCard>
> etc.
> "HERWIG6" is crucial information, so it should absolutely be within a block (e.g. <NLOMC>) so it can easily be read by your shower MC files, which can then abort (if it's the wrong MC) or select appropriate settings (if it's PYQ/PYPT). Furthermore, the "1000" which suddenly comes at the top and bottom of the header should probably be in a block similar to the <MGGenerationInfo> block in the LO files.
>
> Many thanks,
> Johan
> --
> https://code.launchpad.net/~maddevelopers/madgraph5/FKS5/+merge/97762
> Your team MadDevelopers is subscribed to branch lp:~maddevelopers/madgraph5/FKS5.

this is what you get at the end of a run

The /Users/marcozaro/PhD/mg5/FKS5/FKS5/wNLO12/Events/run_01/events.lhe file has been generated.
It contains 10000 NLO events to be showered
   Prepairing MCatNLO run
   Compiling MCatNLO for HERWIG6...
                     ... done
   Running MCatNLO in /Users/marcozaro/PhD/mg5/FKS5/FKS5/wNLO12/MCATNLO/RUN_HERWIG6_1 (this may take some time)...
The file /Users/marcozaro/PhD/mg5/FKS5/FKS5/wNLO12/Events/run_01/events_HERWIG6.hep has been generated. 
It contains showered and hadronized events in the StdHEP format obtained showering the parton-level event file /Users/marcozaro/PhD/mg5/FKS5/FKS5/wNLO12/Events/run_01/events.lhe

On 27 Sep 2012, at 15:23, Johan Alwall wrote:

> Review: Needs Fixing
> 
> Comments about the event output file:
> 
> 53) Adding on to comment 12 about the Events/run_01/ directory structure, I would also suggest to have a more informative name for the events_1 file. How about amcatnlo_events.lhe, since it's an lhe file that can be directly run through a shower generator? I would suggest to pretty much copy (with suitable modifications) the full machinery for event file treatment and names that Olivier has implemented for LO.
> 
> 54) Please create a new xml block for any information you want to keep in the header of the .lhe file. Right now, the header starts as 
> <LesHouchesEvents version="1.0">
>  
>  <header>
>     1000
>  <MG5ProcCard>
> etc.
> "HERWIG6" is crucial information, so it should absolutely be within a block (e.g. <NLOMC>) so it can easily be read by your shower MC files, which can then abort (if it's the wrong MC) or select appropriate settings (if it's PYQ/PYPT). Furthermore, the "1000" which suddenly comes at the top and bottom of the header should probably be in a block similar to the <MGGenerationInfo> block in the LO files.
> 
> Many thanks,
> Johan
> -- 
> https://code.launchpad.net/~maddevelopers/madgraph5/FKS5/+merge/97762
> Your team MadDevelopers is subscribed to branch lp:~maddevelopers/madgraph5/FKS5.

Revision history for this message

Paolo Torrielli (paolo-torrielli) wrote on 2012-09-27:

Hi Johan,

> 54) Please create a new xml block for any information you want to keep in the header of the .lhe file. Right now, the header starts as
> <LesHouchesEvents version="1.0">
> 
> <header>
> 1000
> <MG5ProcCard>
> etc.
> "HERWIG6" is crucial information, so it should absolutely be within a block (e.g. <NLOMC>) so it can easily be read by your shower MC files, which can then abort (if it's the wrong MC) or select appropriate settings (if it's PYQ/PYPT). Furthermore, the "1000" which suddenly comes at the top and bottom of the header should probably be in a block similar to the <MGGenerationInfo> block in the LO files.
The scripts already read the header of the lhe file and perform a series of checks on the correctness of the MC used. In particular there is a "head -3" which supposes that the MC name is at line 3, and a "head -6" to read the number of events. These are the only 'delicate' things in the scripts, but I think they are ok if one keeps this structure unchanged.
If we want to change the structure, I propose something like

HERWIG6 #monte carlo
10000 #number of events

so one could grep for the strings after the '#'. But anyway, since it works well as it is, I'm not really keen on changing...
Cheers.
Paolo

> Many thanks,
> Johan
> --
> https://code.launchpad.net/~maddevelopers/madgraph5/FKS5/+merge/97762
> Your team MadDevelopers is subscribed to branch lp:~maddevelopers/madgraph5/FKS5.

Revision history for this message

Johan Alwall (johan-alwall) wrote on 2012-09-27:

Hello Paolo,

> The scripts already read the header of the lhe file and perform a series of
> checks on the correctness of the MC used. In particular there is a "head -3"
> which supposes that the MC name is at line 3, and a "head -6" to read the
> number of events. These are the only 'delicate' things in the scripts, but I
> think they are ok if one keeps this structure unchanged.

Whoa! This is very dangerous, since it's completely counterintuitive, and also completely against the whole point with the xml format that was decided upon in the LHA.

> If we want to change the structure, I propose something like
>
> HERWIG6 #monte carlo
> 10000 #number of events

You can use this, as long as you keep the two lines inside a block (e.g., <MCatNLOInfo>). Then it's up to you how you want to search for the info (but, again, the point with using xml format is to use the tags to find the relevant information). If HERWIG6 is read from the run_card line, that's also fine - in that case, the other occurrences (outside of the block structure) should simply be removed.

Cheers,
Johan

review: Needs Fixing

Revision history for this message

Paolo Torrielli (paolo-torrielli) wrote on 2012-09-27:

Hi Johan,

> If HERWIG6 is read from the run_card line, that's also fine - in that case, the other occurrences (outside of the block structure) should simply be removed.
Actually it is read twice, one from the run card, one from the third line of the file, and the two strings are compared
(to check that the file is self consistent, maybe it is useless but not bad) and also compared to the shower mode that one choses in the input file.

Anyway, if you want to change the format, I have nothing against, simply I need to know the new format soon and update the scripts.

Thank you!
Cheers.

Paolo

Revision history for this message

Johan Alwall (johan-alwall) wrote on 2012-09-28:

Hello Paolo,

Please change the format according to the guidelines I expressed above (e.g., <MCatNLOInfo>), or choose other block names as you wish. These names are defined by the MC authors (i.e., you), so I don't have any strong preference, as long as it follows the xml block structure.

Thanks a lot!
Johan

Revision history for this message

Paolo Torrielli (paolo-torrielli) wrote on 2012-09-28:

Hello Johan,
ok, I'll discuss with Marco and perform the changes.
Thanks!
Cheers.
Paolo

On Sep 28, 2012, at 8:14 AM, Johan Alwall <email address hidden>
wrote:

> Hello Paolo,
>
> Please change the format according to the guidelines I expressed above (e.g., <MCatNLOInfo>), or choose other block names as you wish. These names are defined by the MC authors (i.e., you), so I don't have any strong preference, as long as it follows the xml block structure.
>
> Thanks a lot!
> Johan
> --
> https://code.launchpad.net/~maddevelopers/madgraph5/FKS5/+merge/97762
> Your team MadDevelopers is subscribed to branch lp:~maddevelopers/madgraph5/FKS5.

Revision history for this message

Johan Alwall (johan-alwall) wrote on 2012-09-28:

Hello Marco,

Some more problems (I record them here):

54. When I generate a process in the latest version of the branch, it says:
"""MCatNLO-utilities is not installed.
If you want to shower events with MC@NLO please install it by typing "install MCatNLO-utilities" and regenerate the process"""
This should obviously not be the case. I should be able to produce the events, then install the utilities, and then use the "pythia" or "herwig" (or perhaps just "shower", since the run knows already which shower is needed) command to shower whenever I want.

55. I started a launch for an FKS directory (in the bin/mg5 interface) and then interrupted it with Ctrl-C. I get the following error:
"""Using built-in libraries for PDFs
Compiling source...
^CCommand "launch " interrupted in sub-command:
"launch" with error:
aMCatNLOError : Compilation failed, check /Users/alwall/MadGraph/FKS5/PROCNLO_loop_sm_1/compile_amcatnlo.log for details
Please report this bug on https://bugs.launchpad.net/madgraph5
More information is found in 'MG5_debug'.
Please attach this file to your report."""

56. Then, when I restart the launch, it says:
"""Command "launch " interrupted in sub-command:
"launch" with error:
NameError : global name 'MadEventAlreadyRunning' is not defined
Please report this bug on https://bugs.launchpad.net/madgraph5
More information is found in 'MG5_debug'."""

57. This one is for Olivier I guess: I try to remove some file using the "!", but when I tab complete, it crashes:
"""aMC@NLO>!rm ./PROCNLO_loop_<TAB>
OneLinePathCompletion instance has no attribute 'completion_prefix'
Traceback (most recent call last):
  File "/Users/alwall/MadGraph/FKS5/madgraph/interface/extended_cmd.py", line 61, in deco_f
    return f(*args, **opt)
  File "/Users/alwall/MadGraph/FKS5/madgraph/interface/extended_cmd.py", line 117, in print_suggestions
    longest_match_length += len(self.completion_prefix)
AttributeError: OneLinePathCompletion instance has no attribute 'completion_prefix'"""

58. When I try going into the process directory and run run_mcatnlo, I get:
"""Johan-Alwalls-MacBook-Air:PROCNLO_loop_sm_1 alwall$ bin/run_mcatnlo
No module named madgraph.interface.extended_cmd
Traceback (most recent call last):
  File "bin/run_mcatnlo", line 29, in <module>
    import amcatnlo_run_interface as run
  File "/Users/alwall/MadGraph/FKS5/PROCNLO_loop_sm_1/bin/internal/amcatnlo_run_interface.py", line 71, in <module>
    import internal.various.gen_crossxhtml as gen_crossxhtml
ImportError: No module named various.gen_crossxhtml"""
Same thing in "calculate_xsect".

Cheers,
Johan

Hello Marco,

Some more problems (I record them here):

54. When I generate a process in the latest version of the branch, it says:
"""MCatNLO-utilities is not installed. 
If you want to shower events with MC@NLO please install it by typing "install MCatNLO-utilities" and regenerate the process"""
This should obviously not be the case. I should be able to produce the events, then install the utilities, and then use the "pythia" or "herwig" (or perhaps just "shower", since the run knows already which shower is needed) command to shower whenever I want.

56. Then, when I restart the launch, it says: 
"""Command "launch " interrupted in sub-command:
"launch" with error:
NameError : global name 'MadEventAlreadyRunning' is not defined
Please report this bug on https://bugs.launchpad.net/madgraph5
More information is found in 'MG5_debug'."""

58. When I try going into the process directory and run run_mcatnlo, I get:
"""Johan-Alwalls-MacBook-Air:PROCNLO_loop_sm_1 alwall$ bin/run_mcatnlo 
No module named madgraph.interface.extended_cmd
Traceback (most recent call last):
  File "bin/run_mcatnlo", line 29, in <module>
    import amcatnlo_run_interface as run      
  File "/Users/alwall/MadGraph/FKS5/PROCNLO_loop_sm_1/bin/internal/amcatnlo_run_interface.py", line 71, in <module>
    import internal.various.gen_crossxhtml as gen_crossxhtml
ImportError: No module named various.gen_crossxhtml"""
Same thing in "calculate_xsect".

Cheers,
Johan

review: Needs Fixing

Revision history for this message

marco zaro (marco-zaro) wrote on 2012-09-28:

Download full text (3.4 KiB)

Hi Johan,
so:
On 28 Sep 2012, at 09:37, Johan Alwall wrote:

> Review: Needs Fixing
>
> Hello Marco,
>
> Some more problems (I record them here):
>
> 54. When I generate a process in the latest version of the branch, it says:
> """MCatNLO-utilities is not installed.
> If you want to shower events with MC@NLO please install it by typing "install MCatNLO-utilities" and regenerate the process"""
> This should obviously not be the case. I should be able to produce the events, then install the utilities, and then use the "pythia" or "herwig" (or perhaps just "shower", since the run knows already which shower is needed) command to shower whenever I want.
ok, this can be fixed.
however, it looks like the package_info.dat is not currently updated on the uclouvain server.
i have modified it in the www branch, and then ran the update script on the mg web page (there it correctly pulls the new revision with the modified file, but in the end the file is still the old one)

>
> 55. I started a launch for an FKS directory (in the bin/mg5 interface) and then interrupted it with Ctrl-C. I get the following error:
> """Using built-in libraries for PDFs
> Compiling source...
> ^CCommand "launch " interrupted in sub-command:
> "launch" with error:
> aMCatNLOError : Compilation failed, check /Users/alwall/MadGraph/FKS5/PROCNLO_loop_sm_1/compile_amcatnlo.log for details
> Please report this bug on https://bugs.launchpad.net/madgraph5
> More information is found in 'MG5_debug'.
> Please attach this file to your report."""

ok, there were many os. system used to launch programs.
moved to misc.call

>
> 56. Then, when I restart the launch, it says:
> """Command "launch " interrupted in sub-command:
> "launch" with error:
> NameError : global name 'MadEventAlreadyRunning' is not defined
> Please report this bug on https://bugs.launchpad.net/madgraph5
> More information is found in 'MG5_debug'."""
i forgot to rename it, fixed.
also added funcction do_quit to the amcatnlo_run_interface

>
> 57. This one is for Olivier I guess: I try to remove some file using the "!", but when I tab complete, it crashes:
> """aMC@NLO>!rm ./PROCNLO_loop_<TAB>
> OneLinePathCompletion instance has no attribute 'completion_prefix'
> Traceback (most recent call last):
> File "/Users/alwall/MadGraph/FKS5/madgraph/interface/extended_cmd.py", line 61, in deco_f
> return f(*args, **opt)
> File "/Users/alwall/MadGraph/FKS5/madgraph/interface/extended_cmd.py", line 117, in print_suggestions
> longest_match_length += len(self.completion_prefix)
> AttributeError: OneLinePathCompletion instance has no attribute 'completion_prefix'"""
>
> 58. When I try going into the process directory and run run_mcatnlo, I get:
> """Johan-Alwalls-MacBook-Air:PROCNLO_loop_sm_1 alwall$ bin/run_mcatnlo
> No module named madgraph.interface.extended_cmd
> Traceback (most recent call last):
> File "bin/run_mcatnlo", line 29, in <module>
> import amcatnlo_run_interface as run
> File "/Users/alwall/MadGraph/FKS5/PROCNLO_loop_sm_1/bin/internal/amcatnlo_run_interface.py", line 71, in <module>
> import internal.various.gen_crossxhtml as gen_crossxhtml
> ImportError: No module named various.gen...

Hi Johan,
so:
On 28 Sep 2012, at 09:37, Johan Alwall wrote:

> Review: Needs Fixing
> 
> Hello Marco,
> 
> Some more problems (I record them here):
> 
> 54. When I generate a process in the latest version of the branch, it says:
> """MCatNLO-utilities is not installed. 
> If you want to shower events with MC@NLO please install it by typing "install MCatNLO-utilities" and regenerate the process"""
> This should obviously not be the case. I should be able to produce the events, then install the utilities, and then use the "pythia" or "herwig" (or perhaps just "shower", since the run knows already which shower is needed) command to shower whenever I want.
ok, this can be fixed.
however, it looks like the package_info.dat is not currently updated on the uclouvain server.
i have modified it in the www branch, and then ran the update script on the mg web page (there it correctly pulls the new revision with the modified file, but in the end the file is still the old one)

> 
> 55. I started a launch for an FKS directory (in the bin/mg5 interface) and then interrupted it with Ctrl-C. I get the following error:
> """Using built-in libraries for PDFs
> Compiling source...
> ^CCommand "launch " interrupted in sub-command:
> "launch" with error:
> aMCatNLOError : Compilation failed, check /Users/alwall/MadGraph/FKS5/PROCNLO_loop_sm_1/compile_amcatnlo.log for details
> Please report this bug on https://bugs.launchpad.net/madgraph5
> More information is found in 'MG5_debug'.
> Please attach this file to your report."""

ok, there were many os. system used to launch programs.
moved to misc.call

> 
> 56. Then, when I restart the launch, it says: 
> """Command "launch " interrupted in sub-command:
> "launch" with error:
> NameError : global name 'MadEventAlreadyRunning' is not defined
> Please report this bug on https://bugs.launchpad.net/madgraph5
> More information is found in 'MG5_debug'."""
i forgot to rename it, fixed.
also added funcction do_quit to the amcatnlo_run_interface

> 
> 57. This one is for Olivier I guess: I try to remove some file using the "!", but when I tab complete, it crashes:
> """aMC@NLO>!rm ./PROCNLO_loop_<TAB>
> OneLinePathCompletion instance has no attribute 'completion_prefix'
> Traceback (most recent call last):
>  File "/Users/alwall/MadGraph/FKS5/madgraph/interface/extended_cmd.py", line 61, in deco_f
>    return f(*args, **opt)
>  File "/Users/alwall/MadGraph/FKS5/madgraph/interface/extended_cmd.py", line 117, in print_suggestions
>    longest_match_length += len(self.completion_prefix)
> AttributeError: OneLinePathCompletion instance has no attribute 'completion_prefix'"""
> 
> 58. When I try going into the process directory and run run_mcatnlo, I get:
> """Johan-Alwalls-MacBook-Air:PROCNLO_loop_sm_1 alwall$ bin/run_mcatnlo 
> No module named madgraph.interface.extended_cmd
> Traceback (most recent call last):
>  File "bin/run_mcatnlo", line 29, in <module>
>    import amcatnlo_run_interface as run      
>  File "/Users/alwall/MadGraph/FKS5/PROCNLO_loop_sm_1/bin/internal/amcatnlo_run_interface.py", line 71, in <module>
>    import internal.various.gen_crossxhtml as gen_crossxhtml
> ImportError: No module named various.gen_crossxhtml"""
> Same thing in "calculate_xsect".
yep, sorry, it had to be import internal.gen_crossxhtml without .various.

> Cheers,
> Johan
> -- 
> https://code.launchpad.net/~maddevelopers/madgraph5/FKS5/+merge/97762
> Your team MadDevelopers is subscribed to branch lp:~maddevelopers/madgraph5/FKS5.

lp:~maddevelopers/mg5amcnlo/FKS5 updated on 2012-09-28

307. By marco zaro on 2012-09-28: fixes in mcatnlo_run interface.
in particular all calls to os.system have been replaced to misc.call
308. By marco zaro on 2012-09-28: added MCatNLO-utilities_path in mg5_configuration.
this way the run_mcatnlo command will automatically detect if these utils have been installed, also after exporting the dir

Revision history for this message

marco zaro (marco-zaro) wrote on 2012-09-28:

Download full text (3.7 KiB)

Hi,
54 is also fixed

On 28 Sep 2012, at 10:46, marco zaro wrote:

> Hi Johan,
> so:
> On 28 Sep 2012, at 09:37, Johan Alwall wrote:
>
>> Review: Needs Fixing
>>
>> Hello Marco,
>>
>> Some more problems (I record them here):
>>
>> 54. When I generate a process in the latest version of the branch, it says:
>> """MCatNLO-utilities is not installed.
>> If you want to shower events with MC@NLO please install it by typing "install MCatNLO-utilities" and regenerate the process"""
>> This should obviously not be the case. I should be able to produce the events, then install the utilities, and then use the "pythia" or "herwig" (or perhaps just "shower", since the run knows already which shower is needed) command to shower whenever I want.
> ok, this can be fixed.
> however, it looks like the package_info.dat is not currently updated on the uclouvain server.
> i have modified it in the www branch, and then ran the update script on the mg web page (there it correctly pulls the new revision with the modified file, but in the end the file is still the old one)
>
>
>>
>> 55. I started a launch for an FKS directory (in the bin/mg5 interface) and then interrupted it with Ctrl-C. I get the following error:
>> """Using built-in libraries for PDFs
>> Compiling source...
>> ^CCommand "launch " interrupted in sub-command:
>> "launch" with error:
>> aMCatNLOError : Compilation failed, check /Users/alwall/MadGraph/FKS5/PROCNLO_loop_sm_1/compile_amcatnlo.log for details
>> Please report this bug on https://bugs.launchpad.net/madgraph5
>> More information is found in 'MG5_debug'.
>> Please attach this file to your report."""
>
> ok, there were many os. system used to launch programs.
> moved to misc.call
>
>
>>
>> 56. Then, when I restart the launch, it says:
>> """Command "launch " interrupted in sub-command:
>> "launch" with error:
>> NameError : global name 'MadEventAlreadyRunning' is not defined
>> Please report this bug on https://bugs.launchpad.net/madgraph5
>> More information is found in 'MG5_debug'."""
> i forgot to rename it, fixed.
> also added funcction do_quit to the amcatnlo_run_interface
>
>>
>> 57. This one is for Olivier I guess: I try to remove some file using the "!", but when I tab complete, it crashes:
>> """aMC@NLO>!rm ./PROCNLO_loop_<TAB>
>> OneLinePathCompletion instance has no attribute 'completion_prefix'
>> Traceback (most recent call last):
>> File "/Users/alwall/MadGraph/FKS5/madgraph/interface/extended_cmd.py", line 61, in deco_f
>> return f(*args, **opt)
>> File "/Users/alwall/MadGraph/FKS5/madgraph/interface/extended_cmd.py", line 117, in print_suggestions
>> longest_match_length += len(self.completion_prefix)
>> AttributeError: OneLinePathCompletion instance has no attribute 'completion_prefix'"""
>>
>> 58. When I try going into the process directory and run run_mcatnlo, I get:
>> """Johan-Alwalls-MacBook-Air:PROCNLO_loop_sm_1 alwall$ bin/run_mcatnlo
>> No module named madgraph.interface.extended_cmd
>> Traceback (most recent call last):
>> File "bin/run_mcatnlo", line 29, in <module>
>> import amcatnlo_run_interface as run
>> File "/Users/alwall/MadGraph/FKS5/PROCNLO_loop_sm_1/bin/internal/amcatnlo_run_...

Hi,
54 is also fixed

On 28 Sep 2012, at 10:46, marco zaro wrote:

> Hi Johan,
> so:
> On 28 Sep 2012, at 09:37, Johan Alwall wrote:
> 
>> Review: Needs Fixing
>> 
>> Hello Marco,
>> 
>> Some more problems (I record them here):
>> 
>> 54. When I generate a process in the latest version of the branch, it says:
>> """MCatNLO-utilities is not installed. 
>> If you want to shower events with MC@NLO please install it by typing "install MCatNLO-utilities" and regenerate the process"""
>> This should obviously not be the case. I should be able to produce the events, then install the utilities, and then use the "pythia" or "herwig" (or perhaps just "shower", since the run knows already which shower is needed) command to shower whenever I want.
> ok, this can be fixed.
> however, it looks like the package_info.dat is not currently updated on the uclouvain server.
> i have modified it in the www branch, and then ran the update script on the mg web page (there it correctly pulls the new revision with the modified file, but in the end the file is still the old one)
> 
> 
>> 
>> 55. I started a launch for an FKS directory (in the bin/mg5 interface) and then interrupted it with Ctrl-C. I get the following error:
>> """Using built-in libraries for PDFs
>> Compiling source...
>> ^CCommand "launch " interrupted in sub-command:
>> "launch" with error:
>> aMCatNLOError : Compilation failed, check /Users/alwall/MadGraph/FKS5/PROCNLO_loop_sm_1/compile_amcatnlo.log for details
>> Please report this bug on https://bugs.launchpad.net/madgraph5
>> More information is found in 'MG5_debug'.
>> Please attach this file to your report."""
> 
> ok, there were many os. system used to launch programs.
> moved to misc.call
> 
> 
>> 
>> 56. Then, when I restart the launch, it says: 
>> """Command "launch " interrupted in sub-command:
>> "launch" with error:
>> NameError : global name 'MadEventAlreadyRunning' is not defined
>> Please report this bug on https://bugs.launchpad.net/madgraph5
>> More information is found in 'MG5_debug'."""
> i forgot to rename it, fixed.
> also added funcction do_quit to the amcatnlo_run_interface
> 
>> 
>> 57. This one is for Olivier I guess: I try to remove some file using the "!", but when I tab complete, it crashes:
>> """aMC@NLO>!rm ./PROCNLO_loop_<TAB>
>> OneLinePathCompletion instance has no attribute 'completion_prefix'
>> Traceback (most recent call last):
>> File "/Users/alwall/MadGraph/FKS5/madgraph/interface/extended_cmd.py", line 61, in deco_f
>>   return f(*args, **opt)
>> File "/Users/alwall/MadGraph/FKS5/madgraph/interface/extended_cmd.py", line 117, in print_suggestions
>>   longest_match_length += len(self.completion_prefix)
>> AttributeError: OneLinePathCompletion instance has no attribute 'completion_prefix'"""
>> 
>> 58. When I try going into the process directory and run run_mcatnlo, I get:
>> """Johan-Alwalls-MacBook-Air:PROCNLO_loop_sm_1 alwall$ bin/run_mcatnlo 
>> No module named madgraph.interface.extended_cmd
>> Traceback (most recent call last):
>> File "bin/run_mcatnlo", line 29, in <module>
>>   import amcatnlo_run_interface as run      
>> File "/Users/alwall/MadGraph/FKS5/PROCNLO_loop_sm_1/bin/internal/amcatnlo_run_interface.py", line 71, in <module>
>>   import internal.various.gen_crossxhtml as gen_crossxhtml
>> ImportError: No module named various.gen_crossxhtml"""
>> Same thing in "calculate_xsect".
> yep, sorry, it had to be import internal.gen_crossxhtml without .various.
> 
> 
>> Cheers,
>> Johan
>> -- 
>> https://code.launchpad.net/~maddevelopers/madgraph5/FKS5/+merge/97762
>> Your team MadDevelopers is subscribed to branch lp:~maddevelopers/madgraph5/FKS5.
> 
> 
> -- 
> https://code.launchpad.net/~maddevelopers/madgraph5/FKS5/+merge/97762
> Your team MadDevelopers is subscribed to branch lp:~maddevelopers/madgraph5/FKS5.

Revision history for this message

Olivier Mattelaer (olivier-mattelaer) wrote on 2012-09-29:

Download full text (5.1 KiB)

Hi,

> """aMC@NLO>!rm ./PROCNLO_loop_<TAB>
> OneLinePathCompletion instance has no attribute 'completion_prefix'
> Traceback (most recent call last):
> File "/Users/alwall/MadGraph/FKS5/madgraph/interface/extended_cmd.py", line 61, in deco_f
> return f(*args, **opt)
> File "/Users/alwall/MadGraph/FKS5/madgraph/interface/extended_cmd.py", line 117, in print_suggestions
> longest_match_length += len(self.completion_prefix)
> AttributeError: OneLinePathCompletion instance has no attribute 'completion_prefix'"""

I fix a similar problem in 1.5.0 so maybe this will be solve when the merge will be done.
Otherwise, I need to know all the command that you type (including ctrl-c and ctrl-d) in order to be able to reproduce it.
And not sure if this is usefull or not, but do you use lib edit or the one provide by mac (for the autocompletion)

Otherwise:

59: The installation of hepmc didn't detect that I'm in 64 bit (which is important for it) that g77 is not installed.
Please look at our modif to pythia-pgs and how we install it since this is mainly the same problem.

Cheers,

Olivier

On Sep 28, 2012, at 7:30 AM, marco zaro <email address hidden> wrote:

Hi,

> """aMC@NLO>!rm ./PROCNLO_loop_<TAB>
> OneLinePathCompletion instance has no attribute 'completion_prefix'
> Traceback (most recent call last):
>  File "/Users/alwall/MadGraph/FKS5/madgraph/interface/extended_cmd.py", line 61, in deco_f
>    return f(*args, **opt)
>  File "/Users/alwall/MadGraph/FKS5/madgraph/interface/extended_cmd.py", line 117, in print_suggestions
>    longest_match_length += len(self.completion_prefix)
> AttributeError: OneLinePathCompletion instance has no attribute 'completion_prefix'"""

Otherwise:

Cheers,

Olivier

On Sep 28, 2012, at 7:30 AM, marco zaro <marco.zaro@gmail.com> wrote:

> Hi,
> 54 is also fixed 
> 
> On 28 Sep 2012, at 10:46, marco zaro wrote:
> 
>> Hi Johan,
>> so:
>> On 28 Sep 2012, at 09:37, Johan Alwall wrote:
>> 
>>> Review: Needs Fixing
>>> 
>>> Hello Marco,
>>> 
>>> Some more problems (I record them here):
>>> 
>>> 54. When I generate a process in the latest version of the branch, it says:
>>> """MCatNLO-utilities is not installed. 
>>> If you want to shower events with MC@NLO please install it by typing "install MCatNLO-utilities" and regenerate the process"""
>>> This should obviously not be the case. I should be able to produce the events, then install the utilities, and then use the "pythia" or "herwig" (or perhaps just "shower", since the run knows already which shower is needed) command to shower whenever I want.
>> ok, this can be fixed.
>> however, it looks like the package_info.dat is not currently updated on the uclouvain server.
>> i have modified it in the www branch, and then ran the update script on the mg web page (there it correctly pulls the new revision with the modified file, but in the end the file is still the old one)
>> 
>> 
>>> 
>>> 55. I started a launch for an FKS directory (in the bin/mg5 interface) and then interrupted it with Ctrl-C. I get the following error:
>>> """Using built-in libraries for PDFs
>>> Compiling source...
>>> ^CCommand "launch " interrupted in sub-command:
>>> "launch" with error:
>>> aMCatNLOError : Compilation failed, check /Users/alwall/MadGraph/FKS5/PROCNLO_loop_sm_1/compile_amcatnlo.log for details
>>> Please report this bug on https://bugs.launchpad.net/madgraph5
>>> More information is found in 'MG5_debug'.
>>> Please attach this file to your report."""
>> 
>> ok, there were many os. system used to launch programs.
>> moved to misc.call
>> 
>> 
>>> 
>>> 56. Then, when I restart the launch, it says: 
>>> """Command "launch " interrupted in sub-command:
>>> "launch" with error:
>>> NameError : global name 'MadEventAlreadyRunning' is not defined
>>> Please report this bug on https://bugs.launchpad.net/madgraph5
>>> More information is found in 'MG5_debug'."""
>> i forgot to rename it, fixed.
>> also added funcction do_quit to the amcatnlo_run_interface
>> 
>>> 
>>> 57. This one is for Olivier I guess: I try to remove some file using the "!", but when I tab complete, it crashes:
>>> """aMC@NLO>!rm ./PROCNLO_loop_<TAB>
>>> OneLinePathCompletion instance has no attribute 'completion_prefix'
>>> Traceback (most recent call last):
>>> File "/Users/alwall/MadGraph/FKS5/madgraph/interface/extended_cmd.py", line 61, in deco_f
>>>  return f(*args, **opt)
>>> File "/Users/alwall/MadGraph/FKS5/madgraph/interface/extended_cmd.py", line 117, in print_suggestions
>>>  longest_match_length += len(self.completion_prefix)
>>> AttributeError: OneLinePathCompletion instance has no attribute 'completion_prefix'"""
>>> 
>>> 58. When I try going into the process directory and run run_mcatnlo, I get:
>>> """Johan-Alwalls-MacBook-Air:PROCNLO_loop_sm_1 alwall$ bin/run_mcatnlo 
>>> No module named madgraph.interface.extended_cmd
>>> Traceback (most recent call last):
>>> File "bin/run_mcatnlo", line 29, in <module>
>>>  import amcatnlo_run_interface as run      
>>> File "/Users/alwall/MadGraph/FKS5/PROCNLO_loop_sm_1/bin/internal/amcatnlo_run_interface.py", line 71, in <module>
>>>  import internal.various.gen_crossxhtml as gen_crossxhtml
>>> ImportError: No module named various.gen_crossxhtml"""
>>> Same thing in "calculate_xsect".
>> yep, sorry, it had to be import internal.gen_crossxhtml without .various.
>> 
>> 
>>> Cheers,
>>> Johan
>>> -- 
>>> https://code.launchpad.net/~maddevelopers/madgraph5/FKS5/+merge/97762
>>> Your team MadDevelopers is subscribed to branch lp:~maddevelopers/madgraph5/FKS5.
>> 
>> 
>> -- 
>> https://code.launchpad.net/~maddevelopers/madgraph5/FKS5/+merge/97762
>> Your team MadDevelopers is subscribed to branch lp:~maddevelopers/madgraph5/FKS5.
> 
> 
> -- 
> https://code.launchpad.net/~maddevelopers/madgraph5/FKS5/+merge/97762
> You proposed lp:~maddevelopers/madgraph5/FKS5 for merging.

Preview Diff

[H/L] Next/Prev Comment, [J/K] Next/Prev File, [N/P] Next/Prev Hunk

The diff has been truncated for viewing.

Subscribers

People subscribed via source and target branches

to all changes:

Johan Alwall

MadDevelopers

MadTeam

 === modified file 'DECAY/decay.f'
 --- DECAY/decay.f	2011-06-01 21:40:33 +0000
 +++ DECAY/decay.f	2012-09-28 12:29:27 +0000
@@ -1431,6 +1431,7 @@
           if(calc_width.gt.0d0) then
              diff=(calc_width-MC_width)/(calc_width+MC_width)*100d0
           endif
++         backspace(lunout)
           write(lunout,'(a3,2x,i2,2x,e12.5,2x,e10.5,
       &              1x,f5.2,3x,e10.5,3x,f5.1)')
       &        id(ip),imode,calc_width,MC_width,diff,mxwgt,eff
 === modified file 'DECAY/makefile'
 --- DECAY/makefile	2011-07-19 08:50:59 +0000
 +++ DECAY/makefile	2012-09-28 12:29:27 +0000
@@ -1,6 +1,6 @@
  # Check for ../make_opts
--ifeq ($(wildcard ../Template/Source/make_opts), ../Template/Source/make_opts)
--  include ../Template/Source/make_opts
++ifeq ($(wildcard ../Template/LO/Source/make_opts), ../Template/LO/Source/make_opts)
++  include ../Template/LO/Source/make_opts
  else
    include ../madevent/Source/make_opts
  endif
 === modified file 'HELAS/Makefile'
 --- HELAS/Makefile	2011-07-10 19:01:23 +0000
 +++ HELAS/Makefile	2012-09-28 12:29:27 +0000
@@ -15,8 +15,8 @@
  # ----------------------------------------------------------------------------
  # Check for ../make_opts
--ifeq ($(wildcard ../Template/Source/make_opts), ../Template/Source/make_opts)
--  include ../Template/Source/make_opts
++ifeq ($(wildcard ../Template/LO/Source/make_opts), ../Template/LO/Source/make_opts)
++  include ../Template/LO/Source/make_opts
  else
    include ../madevent/Source/make_opts
  endif
 === added directory 'Template'
 === renamed directory 'Template' => 'Template/LO'
 === modified file 'Template/LO/Cards/run_card.dat'
 --- Template/Cards/run_card.dat	2011-12-10 06:11:03 +0000
 +++ Template/LO/Cards/run_card.dat	2012-09-28 12:29:27 +0000
@@ -27,7 +27,8 @@
    .false.     = gridpack  !True = setting up the grid pack
  #*********************************************************************
  # Number of events and rnd seed                                      *
--# Warning: Do not generate more than 100K event in a single run      *
++# Warning: Do not generate more than 1M events in a single run       *
++# If you want to run Pythia, avoid more than 50k events in a run.    *
  #*********************************************************************
 = nevents ! Number of unweighted events requested
 = iseed   ! rnd seed (0=assigned automatically=default))
@@ -194,6 +195,17 @@
 d5 = ptj4max ! maximum pt for the fourth jet in pt
 = cutuse  ! reject event if fails any (0) / all (1) jet pt cuts
  #*********************************************************************
++# Control the pt's of leptons sorted by pt                           *
++#*********************************************************************
++ 0   = ptl1min ! minimum pt for the leading lepton in pt
++ 0   = ptl2min ! minimum pt for the second lepton in pt
++ 0   = ptl3min ! minimum pt for the third lepton in pt
++ 0   = ptl4min ! minimum pt for the fourth lepton in pt
++ 1d5 = ptl1max ! maximum pt for the leading lepton in pt
++ 1d5 = ptl2max ! maximum pt for the second lepton in pt
++ 1d5 = ptl3max ! maximum pt for the third lepton in pt
++ 1d5 = ptl4max ! maximum pt for the fourth lepton in pt
++#*********************************************************************
  # Control the Ht(k)=Sum of k leading jets                            *
  #*********************************************************************
 = htjmin ! minimum jet HT=Sum(jet pt)
 === modified file 'Template/LO/README'
 --- Template/README	2011-07-06 23:13:41 +0000
 +++ Template/LO/README	2012-09-28 12:29:27 +0000
@@ -1,9 +1,8 @@
  MadGraph/MadEvent 5
--By Fabio Maltoni, Tim Stelzer and the CP3 development team
++By Johan Alwall, Michel Herquet, Fabio Maltoni, Olivier Mattelaer and Tim Stelzer
  http://madgraph.phys.ucl.ac.be/
  http://madgraph.hep.uiuc.edu/
--http://madgraph.roma2.infn.it/
  Information on the process to be generated is found in the file
  index.html in this directory, which should be viewed using your web
@@ -11,8 +10,14 @@
  process. Please refer to the README file one directory above this
  (MadGraph5_vx_x_x/) for instructions on how to generate a process.
++This README includes information on how
++A) generate events
++B) how to run in cluster/multi-core mode
++C) how to launch sequential run (called multi-run)
++D) How to launch Pythia/PGS/Delphes
++E) How to prevent automatic opening of html pages
--To generate events:
++A) To generate events:
  -------------------
 ) Specify the model parameters. The model parameters include masses
@@ -32,7 +37,7 @@
  example file.
  **Warning!** For several reasons, avoid running more than 100,000
  events per run. Instead perform several runs to reach the luminosity
--you need, e.g. using the bin/multi_run script. Subsequent runs
++you need, e.g. using the multi_run describe below. Subsequent runs
  automatically update the random seed, so the results from different
  runs are statistically independent.
@@ -42,10 +47,88 @@
 ) Follow the generation and look at the results in the file
  HTML/crossx.html, using your web browser.
--5) If you want to run Pythia and/or PGS/Delphes on the events,
--download the Pythia/PGS package (and Delphes) and untar one directory
--above this (the MadGraph5 directory) and run make. Make sure the cards
--pythia_card.dat and pgs_card.dat are present in the Cards/ directory.
--If this is the case, Pythia and PGS will automatically be run by
--generate_events, or, for an existing run, use bin/run_pythia and
--bin/run_pgs.
++5) If you want to run Pythia and/or PGS/Delphes on the events.
++You first need to install it. For this launch MG5 ($MG5PATH/bin/mg5)
++and type `install pythia-pgs`/ `install Delphes`.
++If they are detected, the first question asked when launching ./bin/generate_events
++should be something like:
++Which programs do you want to run?
++  0 / auto    : running existing card
++  1 / parton  :  Madevent
++  2 / pythia  : MadEvent + Pythia.
++  3 / pgs     : MadEvent + Pythia + PGS.
++ [0, 1, 2, 3, auto, parton, pythia, pgs][20s to answer]
++if this is not that means that you need to specify the path of the new program
++in the file Cards/me5_configuration.txt . By default they are
++installed in the MG5 directory.
++
++If you need to run one of those programs on some events which are already generated
++please see instructions below.
++
++
++B) Running in cluster or multicore mode:
++----------------------------------------
++
++In order to automatically run in cluster or multicore mode, please set
++the flag run_mode in the Cards/me5_configuration.txt file (or in the
++input/mg5_configuration.txt file before you generate your process):
++
++# Default Running mode
++# 0: single machine/ 1: cluster / 2: multicore
++run_mode = 0
++
++You can also specify the cluster type (for cluster mode) or your
++preferred number of CPUs (for multicore mode - note that by default,
++the maximum number of cores is used) by setting cluster_type and
++nb_core.
++
++
++C) Launch sequential runs for generation of large number of events:
++-------------------------------------------------------------------
++
++For various reason, we recommend not to generate more than 100k events
++per run. In order to simplify generating large numbers of events,
++we have created a special command 'multi_run', which is equivalent to
++running generate_events multiple times (ensuring that the random seed is
++different for each run), and also automatically combines the resulting
++lhe files into a single file.
++This command can be launched via the madevent user interface
++./bin/madevent using the following command:
++multi_run NBRUN [RUN_NAME] [options]
++For more information about this command (valid options), you can type
++`help multi_run` inside the interface.
++
++Note that you can also launch a command whithout entering the interactive mode:
++./bin/madevent multi_run NBRUN
++
++
++D) Launching pythia/pgs/delphes on a (previously) generated sample:
++-------------------------------------------------------------------
++
++In this section, I will presupose that the corresponding package is
++already installed and configured properly. (See section how to generate
++events if this is not the case)
++
++In order to launch pythia/pgs/delphes on a sample, you need first to
++launch the interactive session of madevent `./bin/madevent`
++and then you can enter of the following command
++pythia RUN [--run_options]
++pgs RUN [--run_options]
++delphes RUN [--run_options]
++where RUN is the run_name of the run. One of the convenient options is
++--tag=XXXX
++which allow to specify the tag name in case of multiple runs with
++the same program. Note that by default, a unique run tag is generated
++for each time you run.
++
++E) How to prevent automatic opening of the crossx.html page:
++------------------------------------------------------------
++
++Edit the file ./Cards/me5_configuration.txt and set
++the option automatic_html_opening to `False`.
++You can also edit the MG5 configuration card
++input/mg5_configuration.txt
++in order to have this value on False by default for all subsequently
++generated processes.
++
++
 === modified file 'Template/LO/Source/PDF/pdfwrap.f'
 --- Template/Source/PDF/pdfwrap.f	2010-10-30 03:26:37 +0000
 +++ Template/LO/Source/PDF/pdfwrap.f	2012-09-28 12:29:27 +0000
@@ -250,13 +250,13 @@
       .'cteq5f3,','cteq5f4,','cteq5m1,','ctq5hq1,','cteq5l1,',
       .'cteq6_m,','cteq6_d,','cteq6_l,','cteq6l1,'
+ c
--c
--	   write(6,*) 'Setting it to default cteq6l1'
--       pdlabel='cteq6l1'
--       asmz=0.130d0
--       nloop=1
--       Call SetCtq6(4)
--
++c     make madgraph to stop evaluating
++      stop 1
++c	   write(6,*) 'Setting it to default cteq6l1'
++c       pdlabel='cteq6l1'
++c       asmz=0.130d0
++c       nloop=1
++c       Call SetCtq6(4)
        endif
        return
        end
 === modified file 'Template/LO/Source/PDF/pdfwrap_lhapdf.f'
 --- Template/Source/PDF/pdfwrap_lhapdf.f	2010-10-30 03:26:37 +0000
 +++ Template/LO/Source/PDF/pdfwrap_lhapdf.f	2012-09-28 12:29:27 +0000
@@ -54,7 +54,7 @@
           if(exists)return
        enddo
        print*,'Could not find PDFsets directory, quitting'
--      stop
++      stop 1
        return
        end
 === modified file 'Template/LO/Source/cuts.inc'
 --- Template/Source/cuts.inc	2011-06-02 20:40:32 +0000
 +++ Template/LO/Source/cuts.inc	2012-09-28 12:29:27 +0000
@@ -29,6 +29,8 @@
        REAL*8 cutuse
        REAL*8 ptj1min,ptj2min,ptj3min,ptj4min
        REAL*8 ptj1max,ptj2max,ptj3max,ptj4max
++      REAL*8 ptl1min,ptl2min,ptl3min,ptl4min
++      REAL*8 ptl1max,ptl2max,ptl3max,ptl4max
        REAL*8 ht2min,ht3min,ht4min
        REAL*8 ht2max,ht3max,ht4max
        REAL*8 htjmin,htjmax,ihtmin,ihtmax
@@ -48,6 +50,10 @@
       &     ptj2min,ptj2max,
       &     ptj3min,ptj3max,
       &     ptj4min,ptj4max,
++     &     ptl1min,ptl1max,
++     &     ptl2min,ptl2max,
++     &     ptl3min,ptl3max,
++     &     ptl4min,ptl4max,
       &     cutuse,
       &     ht2min,ht3min,ht4min,
       &     ht2max,ht3max,ht4max,
 === modified file 'Template/LO/Source/genps.inc'
 --- Template/Source/genps.inc	2011-05-29 07:23:58 +0000
 +++ Template/LO/Source/genps.inc	2012-09-28 12:29:27 +0000
@@ -32,4 +32,4 @@
        REAL*8 LIMHEL
        PARAMETER(LIMHEL=1e-6)
        INTEGER MAXTRIES
--      PARAMETER(MAXTRIES=10)
++      PARAMETER(MAXTRIES=100)
 === modified file 'Template/LO/Source/setrun.f'
 --- Template/Source/setrun.f	2011-10-05 16:27:00 +0000
 +++ Template/LO/Source/setrun.f	2012-09-28 12:29:27 +0000
@@ -264,6 +264,19 @@
  	call get_real   (npara,param,value,"cutuse",cutuse,0d0)
  c*********************************************************************
++c Check   the pt's of leptons sorted by pt                           *
++c*********************************************************************
++
++ 	call get_real   (npara,param,value,"ptl1min",ptl1min,0d0)
++ 	call get_real   (npara,param,value,"ptl1max",ptl1max,1d5)
++ 	call get_real   (npara,param,value,"ptl2min",ptl2min,0d0)
++ 	call get_real   (npara,param,value,"ptl2max",ptl2max,1d5)
++ 	call get_real   (npara,param,value,"ptl3min",ptl3min,0d0)
++ 	call get_real   (npara,param,value,"ptl3max",ptl3max,1d5)
++ 	call get_real   (npara,param,value,"ptl4min",ptl4min,0d0)
++ 	call get_real   (npara,param,value,"ptl4max",ptl4max,1d5)
++
++c*********************************************************************
  c Check  Ht                                                          *
  c*********************************************************************
 === modified file 'Template/LO/SubProcesses/addmothers.f'
 --- Template/SubProcesses/addmothers.f	2012-02-08 08:52:30 +0000
 +++ Template/LO/SubProcesses/addmothers.f	2012-09-28 12:29:27 +0000
@@ -29,7 +29,7 @@
  c     Variables for combination of color indices (including multipart. vert)
        integer maxcolmp
        parameter(maxcolmp=20)
--      integer ncolmp,icolmp(2,maxcolmp)
++      integer ncolmp,icolmp(2,maxcolmp),is_colors(2,nincoming)
        double precision ZERO
        parameter (ZERO=0d0)
@@ -145,7 +145,19 @@
  c     Store original maxcolor to know if we have epsilon vertices
          maxorg=maxcolor
--
++c     Keep track of IS colors that go through to final state
++c     (since we shouldn't replace pop-up indices with those)
++        do i=1,nincoming
++           do j=1,2
++              is_colors(j,i)=0
++              do k=3,nexternal
++                 if (iabs(icolalt(j,i)).eq.iabs(icolalt(j,k))) then
++c                This color is going through to FS
++                    is_colors(j,i)=iabs(icolalt(j,i))
++                 endif
++              enddo
++           enddo
++        enddo
+ c
  c     Get mother information from chosen graph
+ c
@@ -212,7 +224,7 @@
  c             print *,'t-channel: ',i,ida(1),ida(2),mo_color
  c             print *,'colors: ',((icolmp(j,k),j=1,2),k=1,ncolmp)
               maxcolor=fix_tchannel_color(mo_color,maxcolor,
--     $                                   ncolmp,icolmp,i,icolalt)
++     $                        ncolmp,icolmp,i,icolalt,is_colors)
               tchannel=.true.
               cycle
            else
@@ -264,17 +276,23 @@
  c          print *,'s-channel: ',i,mo_color,ida(1),ida(2)
  c          print *,'colors: ',((icolmp(j,k),j=1,2),k=1,ncolmp)
            if(mo_color.eq.1) then ! color singlet
--             maxcolor=elim_indices(0,0,ncolmp,icolmp,i,icolalt,maxcolor)
++             maxcolor=elim_indices(0,0,ncolmp,icolmp,i,icolalt,
++     $            is_colors,maxcolor)
            elseif(mo_color.eq.-3) then ! color anti-triplet
--             maxcolor=elim_indices(0,1,ncolmp,icolmp,i,icolalt,maxcolor)
++             maxcolor=elim_indices(0,1,ncolmp,icolmp,i,icolalt,
++     $            is_colors,maxcolor)
            elseif(mo_color.eq.3) then ! color triplet
--             maxcolor=elim_indices(1,0,ncolmp,icolmp,i,icolalt,maxcolor)
++             maxcolor=elim_indices(1,0,ncolmp,icolmp,i,icolalt,
++     $            is_colors,maxcolor)
            elseif(mo_color.eq.-6) then ! color anti-sextet
--             maxcolor=elim_indices(0,2,ncolmp,icolmp,i,icolalt,maxcolor)
++             maxcolor=elim_indices(0,2,ncolmp,icolmp,i,icolalt,
++     $            is_colors,maxcolor)
            elseif(mo_color.eq.6) then ! color sextet
--             maxcolor=elim_indices(2,0,ncolmp,icolmp,i,icolalt,maxcolor)
++             maxcolor=elim_indices(2,0,ncolmp,icolmp,i,icolalt,
++     $            is_colors,maxcolor)
            elseif(mo_color.eq.8) then ! color octet
--             maxcolor=elim_indices(1,1,ncolmp,icolmp,i,icolalt,maxcolor)
++             maxcolor=elim_indices(1,1,ncolmp,icolmp,i,icolalt,
++     $            is_colors,maxcolor)
            else ! 2 indicates multipart. vertex
               da_color(1) = get_color(jpart(1,ida(1)))
               da_color(2) = get_color(jpart(1,ida(2)))
@@ -450,7 +468,7 @@
  c********************************************************************
        function fix_tchannel_color(mo_color,maxcolor,ncolmp,icolmp,ires,
--     $                            icol)
++     $                            icol,is_colors)
  c********************************************************************
  c     Successively eliminate identical pairwise color indices from the
  c     icolmp list, until only (max) one triplet and one antitriplet remains
@@ -461,6 +479,7 @@
        integer fix_tchannel_color
        integer mo_color,maxcolor,ncolmp,icolmp(2,*)
        integer ires,icol(2,-nexternal+2:2*nexternal-3)
++      integer is_colors(2,nincoming)
        integer i,j,i3,i3bar,max3,max3bar,min3,min3bar,maxcol,mincol
  c     Successively eliminate color indices in pairs until only the wanted
@@ -478,26 +497,18 @@
        i3bar=0
        icol(1,ires)=0
        icol(2,ires)=0
--      min3=1000
--      max3=0
--      min3bar=1000
--      max3bar=0
        do i=1,ncolmp
           if(icolmp(1,i).gt.0)then
              i3=i3+1
  c           color for t-channels needs to be reversed
              if(i3.eq.1) icol(2,ires)=icolmp(1,i)
              if(i3.eq.2) icol(1,ires)=-icolmp(1,i)
--            if(icolmp(1,i).gt.max3) max3=icolmp(1,i)
--            if(icolmp(1,i).lt.min3) min3=icolmp(1,i)
           endif
           if(icolmp(2,i).gt.0)then
              i3bar=i3bar+1
  c           color for t-channels needs to be reversed
              if(i3bar.eq.1) icol(1,ires)=icolmp(2,i)
              if(i3bar.eq.2) icol(2,ires)=-icolmp(2,i)
--            if(icolmp(2,i).gt.max3bar) max3bar=icolmp(2,i)
--            if(icolmp(2,i).lt.min3bar) min3bar=icolmp(2,i)
           endif
        enddo
@@ -513,7 +524,10 @@
        if(mo_color.eq.8.and.i3.eq.1.and.i3bar.eq.1) return
  c     Make sure that max and min don't come from the same octet
--      call clean_max_min(icolmp,ncolmp,max3,min3,max3bar,min3bar,i3,i3bar)
++      call find_max_min(icolmp,ncolmp,max3,min3,max3bar,min3bar,
++     $     i3,i3bar,is_colors)
++c      print *,'After finding: ',ncolmp,((icolmp(j,i),j=1,2),i=1,ncolmp)
++c      print *,'mo_color = ',mo_color
        if(mo_color.le.1.and.i3-i3bar.eq.2.or.
       $   mo_color.le.1.and.i3bar-i3.eq.2.or.
@@ -533,6 +547,17 @@
           enddo
  c         print *,'Replaced ',maxcol,' by ',mincol
        elseif(mo_color.le.1.and.i3.eq.2.and.i3bar.eq.2) then
++c     Ensure that max > min
++         if(max3bar.lt.min3)then
++            i=min3
++            min3=max3bar
++            max3bar=i
++         endif
++         if(max3.lt.min3bar)then
++            i=min3bar
++            min3bar=max3
++            max3=i
++         endif
  c     Replace the maximum indices with the minimum ones everywhere
           do i=ires+1,-1
              do j=1,2
@@ -597,7 +622,8 @@
        end
  c*******************************************************************
--      function elim_indices(n3,n3bar,ncolmp,icolmp,ires,icol,maxcolor)
++      function elim_indices(n3,n3bar,ncolmp,icolmp,ires,icol,
++     $     is_colors,maxcolor)
  c*******************************************************************
  c     Successively eliminate identical pairwise color indices from the
  c     icolmp list, until only the wanted indices remain
@@ -614,6 +640,7 @@
        integer elim_indices
        integer n3,n3bar,ncolmp,icolmp(2,*),maxcolor
        integer ires,icol(2,-nexternal+2:2*nexternal-3)
++      integer is_colors(2,nincoming)
        integer i,j,i3,i3bar
  c     Successively eliminate color indices in pairs until only the wanted
@@ -669,7 +696,8 @@
       $          n3.eq.1.and.n3bar.eq.1.and.i3-i3bar.eq.0.or.
       $          n3.eq.0.and.n3bar.eq.0.and.i3-i3bar.eq.0)then
  c        We have a previous epsilon which gives the wrong pop-up index
--            call fix_s_color_indices(n3,n3bar,i3,i3bar,ncolmp,icolmp,ires,icol)
++            call fix_s_color_indices(n3,n3bar,i3,i3bar,ncolmp,icolmp,
++     $           ires,icol,is_colors)
           else
  c           Don't know how to deal with this
              call write_error(1001,n3,n3bar)
@@ -683,7 +711,7 @@
  c*******************************************************************
        subroutine fix_s_color_indices(n3,n3bar,i3,i3bar,ncolmp,icolmp,
--     $                             ires,icol)
++     $                             ires,icol,is_colors)
  c*******************************************************************
+ c
  c     Fix color flow if some particle has got the wrong pop-up color
@@ -694,37 +722,27 @@
        include 'nexternal.inc'
        integer n3,n3bar,ncolmp,icolmp(2,*),maxcolor
        integer ires,icol(2,-nexternal+2:2*nexternal-3)
++      integer is_colors(2,nincoming)
        integer i,j,i3,i3bar
        integer max_n3,max_n3bar,min_n3,min_n3bar,maxcol,mincol
--      max_n3=0
--      max_n3bar=0
--      min_n3=1000
--      min_n3bar=1000
--      do i=1,ncolmp
--         if(icolmp(1,i).gt.max_n3)
--     $        max_n3=icolmp(1,i)
--         if(icolmp(2,i).gt.max_n3bar)
--     $        max_n3bar=icolmp(2,i)
--         if(icolmp(1,i).gt.0.and.icolmp(1,i).lt.min_n3)
--     $        min_n3=icolmp(1,i)
--         if(icolmp(2,i).gt.0.and.icolmp(2,i).lt.min_n3bar)
--     $        min_n3bar=icolmp(2,i)
--      enddo
--
        icol(1,ires)=0
        icol(2,ires)=0
++c      print *,'Colors: ',ncolmp,((icolmp(j,i),j=1,2),i=1,ncolmp)
++c      print *,'n3,n3bar,i3,i3bar: ',n3,n3bar,i3,i3bar
++
  c     Make sure that max and min don't come from the same octet
--      call clean_max_min(icolmp,ncolmp,max_n3,min_n3,
--     $                   max_n3bar,min_n3bar,i3,i3bar)
++      call find_max_min(icolmp,ncolmp,max_n3,min_n3,
++     $                   max_n3bar,min_n3bar,i3,i3bar,is_colors)
++c      print *,'max3,min3bar,min3,max3bar: ',max_n3,min_n3bar,min_n3,max_n3bar
        if(n3.eq.1.and.n3bar.eq.0.and.i3-i3bar.eq.n3.or.
       $   n3bar.eq.1.and.n3.eq.0.and.i3bar-i3.eq.n3bar.or.
       $   n3bar.eq.1.and.n3.eq.1.and.i3bar-i3.eq.0.or.
       $   n3bar.eq.0.and.n3.eq.0.and.i3bar-i3.eq.0)then
  c     Replace the highest 3bar-index with the lowest 3-index,
--c     and vice versa
++c     or vice versa
           maxcol=max(max_n3,max_n3bar)
           if(maxcol.eq.max_n3) then
              mincol=min_n3bar
@@ -754,73 +772,117 @@
        end
  c*******************************************************************************
--      subroutine clean_max_min(icolmp,ncolmp,max3,min3,max3bar,min3bar,i3,i3bar)
++      subroutine find_max_min(icolmp,ncolmp,max3,min3,max3bar,min3bar,
++     $     i3,i3bar,is_colors)
  c*******************************************************************************
        implicit none
++      include 'nexternal.inc'
        integer ncolmp,icolmp(2,*)
--      integer i,j,max3,max3bar,min3,min3bar,i3,i3bar
--
--c     Make sure that max and min don't come from the same octet
++      integer is_colors(2,nincoming)
++      integer i,j,k,max3,max3bar,min3,min3bar,i3,i3bar,i3now,i3barnow
++      integer allpairs(2,nexternal),npairs,maxcol,mincol
++
++      i3now=i3
++      i3barnow=i3bar
++
++c     Create all possible pairs (3,3bar) that
++c     1. come from different octets, 2. are different,
++c     3. don't contain any color lines passing through the event
++      npairs = 0
++      do 20 i=1,ncolmp
++         if(icolmp(1,i).eq.0) goto 20
++         do k=1,nincoming
++            if(icolmp(1,i).eq.is_colors(1,k)) goto 20
++         enddo
++         do 10 j=1,ncolmp
++            if(i.eq.j.or.icolmp(2,j).eq.0.or.
++     $           icolmp(1,i).eq.icolmp(2,j)) goto 10
++            do k=1,nincoming
++               if(icolmp(2,j).eq.is_colors(2,k)) goto 10
++            enddo
++            npairs=npairs+1
++            allpairs(1,npairs)=icolmp(1,i)
++            allpairs(2,npairs)=icolmp(2,j)
++ 10      enddo
++ 20   enddo
++
++c      print *,'is_colors: ',((is_colors(i,j),i=1,2),j=1,nincoming)
++c      print *,'pairs: ',((allpairs(i,j),i=1,2),j=1,npairs)
++
++c     Find the pairs with maximum 3 and 3bar
++      min3=1000
++      min3bar=1000
++      max3=0
++      max3bar=0
++      do i=1,npairs
++         if(allpairs(1,i).gt.max3.and.
++     $      (allpairs(2,i).lt.max3bar.or.
++     $       allpairs(1,i).gt.allpairs(2,i)))then
++            max3=allpairs(1,i)
++            min3bar=allpairs(2,i)
++         else if(allpairs(2,i).gt.max3bar.and.
++     $           (allpairs(1,i).lt.max3.or.
++     $            allpairs(2,i).gt.allpairs(1,i)))then
++            max3bar=allpairs(2,i)
++            min3=allpairs(1,i)
++         endif
++      enddo
++
++c     Find "maximum" pairs with minimum 3 and 3bar
++      do i=1,npairs
++         if(allpairs(1,i).eq.max3.and.
++     $        allpairs(2,i).lt.min3bar.and.
++     $        allpairs(2,i).ne.max3bar)
++     $        min3bar=allpairs(2,i)
++         if(allpairs(2,i).eq.max3bar.and.
++     $        allpairs(1,i).lt.min3.and.
++     $        allpairs(1,i).ne.max3)
++     $        min3=allpairs(1,i)
++      enddo
++
++      if (max3.gt.0.and.max3bar.gt.0) then
++c       We have found our two pairs, so we're done
++         return
++      endif
++
++      if(max3.gt.0.or.max3bar.gt.0)then
++         i3now=i3now-1
++         i3barnow=i3barnow-1
++      endif
++
++c     Find pair for non-maximum (where we allow all colors)
++      maxcol=max(max3,max3bar)
++      if(maxcol.eq.max3) then
++         mincol=min3bar
++      else
++         mincol=min3
++      endif
++
++      npairs=0
        do i=1,ncolmp
--         if(icolmp(1,i).eq.max3.and.icolmp(2,i).eq.min3bar)then
--            min3bar=1000
--            do j=1,ncolmp
--               if(j.eq.i) cycle
--               if(icolmp(2,j).lt.min3bar) min3bar=icolmp(2,j)
--            enddo
--         endif
--         if(icolmp(2,i).eq.max3bar.and.icolmp(1,i).eq.min3)then
--            min3=1000
--            do j=1,ncolmp
--               if(j.eq.i) cycle
--               if(icolmp(1,j).lt.min3) min3=icolmp(1,j)
--            enddo
--         endif
++         if(icolmp(1,i).eq.0.and.i3now.gt.0) cycle
++         if(icolmp(1,i).eq.maxcol.or.icolmp(1,i).eq.mincol)
++     $        cycle
++         do j=1,ncolmp
++            if(icolmp(2,j).eq.0.and.i3barnow.gt.0) cycle
++            if(i.eq.j.or.icolmp(1,i).eq.icolmp(2,j)) cycle
++            if(icolmp(2,j).eq.maxcol.or.icolmp(2,j).eq.mincol)
++     $           cycle
++            npairs=npairs+1
++            allpairs(1,npairs)=icolmp(1,i)
++            allpairs(2,npairs)=icolmp(2,j)
++         enddo
        enddo
--
--c     ...and that max and min are different
--      if(i3.gt.1.and.max3.eq.min3.or.i3bar.gt.1.and.max3bar.eq.min3bar)then
--         if(max3.gt.max3bar)then
--c        Need to change min3, while still ensuring that max3bar is ok
--            max3bar=0
--            min3=1000
--            do i=1,ncolmp
--               if(icolmp(2,i).gt.max3bar.and.icolmp(2,i).ne.min3bar)
--     $              max3bar=icolmp(2,i)
--               if(icolmp(1,i).lt.min3.and.icolmp(1,i).ne.max3)
--     $              min3=icolmp(1,i)
--            enddo
--c     Make sure that max3bar and min3 don't come from the same octet
--            do i=1,ncolmp
--               if(icolmp(2,i).eq.max3bar.and.icolmp(1,i).eq.min3)then
--                  min3=1000
--                  do j=1,ncolmp
--                     if(j.eq.i.or.icolmp(1,j).eq.max3) cycle
--                     if(icolmp(1,j).lt.min3) min3=icolmp(1,j)
--                  enddo
--               endif
--            enddo
++      if(npairs.ge.1)then
++         if(maxcol.eq.max3)then
++            min3=allpairs(1,1)
++            max3bar=allpairs(2,1)
           else
--c        Need to change min3bar, while still ensuring that max3 is ok
--            max3=0
--            min3bar=1000
--            do i=1,ncolmp
--               if(icolmp(1,i).gt.max3.and.icolmp(1,i).ne.min3)
--     $              max3=icolmp(1,i)
--               if(icolmp(2,i).lt.min3bar.and.icolmp(2,i).ne.max3bar)
--     $              min3bar=icolmp(2,i)
--            enddo
--c     Make sure that max3 and min3bar don't come from the same octet
--            do i=1,ncolmp
--               if(icolmp(1,i).eq.max3.and.icolmp(2,i).eq.min3bar)then
--                  min3bar=1000
--                  do j=1,ncolmp
--                     if(j.eq.i.or.icolmp(2,j).eq.max3bar) cycle
--                     if(icolmp(2,j).lt.min3bar) min3bar=icolmp(2,j)
--                  enddo
--               endif
--            enddo
++            max3=allpairs(1,1)
++            min3bar=allpairs(2,1)
           endif
        endif
++
++c      print *,'allpairs: ',((allpairs(i,j),i=1,2),j=1,npairs)
        end
 === modified file 'Template/LO/SubProcesses/cuts.f'
 --- Template/SubProcesses/cuts.f	2011-12-13 16:49:59 +0000
 +++ Template/LO/SubProcesses/cuts.f	2012-09-28 12:29:27 +0000
@@ -51,7 +51,7 @@
+ C
        LOGICAL FIRSTTIME,FIRSTTIME2,pass_bw,notgood,good,foundheavy
        LOGICAL DEBUG
--      integer i,j,njets,nheavyjets,hardj1,hardj2
++      integer i,j,njets,nheavyjets,nleptons,hardj1,hardj2
        REAL*8 XVAR,ptmax1,ptmax2,htj,tmp,inclht
        real*8 ptemp(0:3), ptemp2(0:3)
        character*20 formstr
@@ -74,6 +74,7 @@
        double precision ptjet(nexternal)
        double precision ptheavyjet(nexternal)
++      double precision ptlepton(nexternal)
        double precision temp
        double precision etmin(nincoming+1:nexternal),etamax(nincoming+1:nexternal)
@@ -93,6 +94,9 @@
        logical jetor
        common/to_jet_cuts/ ptjmin4,ptjmax4,htjmin4,htjmax4,jetor
++      double precision ptlmin4(4),ptlmax4(4)
++      common/to_lepton_cuts/ ptlmin4,ptlmax4
++
+ c
  c     Special cuts
+ c
@@ -545,7 +549,66 @@
           passcuts=.false.
           return
        endif
--
++
++C
++C     maximal and minimal pt of the leptons sorted by pt
++c
++      nleptons=0
++
++      if(ptl1min.gt.0.or.ptl2min.gt.0.or.ptl3min.gt.0.or.ptl4min.gt.0.or.
++     $     ptl1max.lt.1d5.or.ptl2max.lt.1d5.or.
++     $     ptl3max.lt.1d5.or.ptl4max.lt.1d5) then
++
++c     - fill ptlepton with the pt's of the leptons.
++         do i=nincoming+1,nexternal
++            if(is_a_l(i)) then
++               nleptons=nleptons+1
++               ptlepton(nleptons)=pt(p(0,i))
++            endif
++         enddo
++         if(debug) write (*,*) 'not yet ordered ',njets,'   ',ptjet
++
++c     - check existance of leptons if lepton cuts are on
++         if(nleptons.lt.1.and.ptl1min.gt.0.or.
++     $        nleptons.lt.2.and.ptl2min.gt.0.or.
++     $        nleptons.lt.3.and.ptl3min.gt.0.or.
++     $        nleptons.lt.4.and.ptl4min.gt.0)then
++            if(debug) write (*,*) i, ' too few leptons -> fails'
++            passcuts=.false.
++            return
++         endif
++
++c     - sort lepton pts
++         do i=1,nleptons-1
++            do j=i+1,nleptons
++               if(ptlepton(j).gt.ptlepton(i)) then
++                  temp=ptlepton(i)
++                  ptlepton(i)=ptlepton(j)
++                  ptlepton(j)=temp
++               endif
++            enddo
++         enddo
++         if(debug) write (*,*) 'ordered ',nleptons,'   ',ptlepton
++
++         if(nleptons.gt.0) then
++
++            notgood = .false.
++            do i=1,nleptons
++               if(debug) write (*,*) i,ptlepton(i), '   ',ptlmin4(min(i,4)),':',ptlmax4(min(i,4))
++c---  if one of the leptons does not pass, the event is rejected
++               notgood=notgood.or.(ptlepton(i).gt.ptlmax4(min(i,4))).or.
++     $              (ptlepton(i).lt.ptlmin4(min(i,4)))
++               if(debug) write (*,*) i,' notgood total:', notgood
++            enddo
++
++
++            if (notgood) then
++               if(debug) write (*,*) i, ' multiple pt -> fails'
++               passcuts=.false.
++               return
++            endif
++         endif
++      endif
  C>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
  C     SPECIAL CUTS
  C<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
 === modified file 'Template/LO/SubProcesses/myamp.f'
 --- Template/SubProcesses/myamp.f	2011-10-10 07:34:37 +0000
 +++ Template/LO/SubProcesses/myamp.f	2012-09-28 12:29:27 +0000
@@ -566,6 +566,10 @@
           xo = max(xo, ht4min**2/stot)
           xo = max(xo, misset**2/stot)
           xo = max(xo, ptllmin**2/stot)
++         xo = max(xo, ptl1min**2/stot)
++         xo = max(xo, ptl2min**2/stot)
++         xo = max(xo, ptl3min**2/stot)
++         xo = max(xo, ptl4min**2/stot)
           if (swidth(i).eq.0.and.xo.eq.1d0/stot) then
              write(*,*) 'Warning: No minimum found for integration'
              write(*,*) '         Setting minimum to ',1d0/stot
 === modified file 'Template/LO/SubProcesses/setcuts.f'
 --- Template/SubProcesses/setcuts.f	2012-02-24 08:51:01 +0000
 +++ Template/LO/SubProcesses/setcuts.f	2012-09-28 12:29:27 +0000
@@ -59,6 +59,9 @@
        logical jetor
        common/to_jet_cuts/ ptjmin4,ptjmax4,htjmin4,htjmax4,jetor
++      double precision ptlmin4(4),ptlmax4(4)
++      common/to_lepton_cuts/ ptlmin4,ptlmax4
++
        double precision xqcutij(nexternal,nexternal),xqcuti(nexternal)
        common/to_xqcuts/xqcutij,xqcuti
+ c
@@ -413,6 +416,20 @@
        inclHtmax=ihtmax
        jetor = cutuse.eq.0d0
++
++c
++c   EXTRA LEPTON CUTS
++c
++      ptlmin4(1)=ptl1min
++      ptlmin4(2)=ptl2min
++      ptlmin4(3)=ptl3min
++      ptlmin4(4)=ptl4min
++
++      ptlmax4(1)=ptl1max
++      ptlmax4(2)=ptl2max
++      ptlmax4(3)=ptl3max
++      ptlmax4(4)=ptl4max
++
+ c
  c    ERROR TRAPS
+ c
 === modified file 'Template/LO/bin/internal/addmasses.py'
 --- Template/bin/internal/addmasses.py	2011-07-26 16:15:01 +0000
 +++ Template/LO/bin/internal/addmasses.py	2012-09-28 12:29:27 +0000
@@ -174,7 +174,6 @@
              event.append(Particle(nup,t))
          counter=counter+1
--
  #default is to skip this
      if motherFlag:
@@ -223,41 +222,20 @@
                  mySub = re.compile(s1)
                  event_description = mySub.sub(str(nup),event_description)
--
      if nAdded>0:
--        totalLength = len(event)+1
--        newPosition = []
--        iPos=0
--        while iPos<totalLength:
--            for p in event:
--                if p.mo1==iPos:
--                    newPosition.append(p.no)
--            iPos=iPos+1
--
--        iUp=1
--        event0=[]
--        for ip in newPosition:
--            event0.append(event[ip-1])
--
--        iUp=0
--        for p in event0:
--            iUp=iUp+1
--            if p.no != iUp:
--                ip=iUp
--                while ip<totalLength-1:
--                    pp=event0[ip]
--                    if pp.mo1==p.no and pp.mo1>pp.no:
--                        pp.mo1=pp.mo2=iUp
--                    ip=ip+1
--            p.no=iUp
--
--        iUp=0
--        for p in event0:
--            event[iUp]=event0[iUp]
--            iUp=iUp+1
--
--
--
++        for ip in range(len(event)):
++            l=event[ip]
++            if l.mo1 > ip + 1:
++                nmo=l.mo1
++                event.insert(ip, event.pop(l.mo1-1))
++                event[ip].no = ip + 1
++                for l2 in event[ip + 1:]:
++                    if l2.no > ip and l2.no < nmo + 1:
++                        l2.no += 1
++                    if l2.mo1 == nmo:
++                        l2.mo1 = l2.mo2 = ip + 1
++                    elif l2.mo1 > ip and l2.mo1 < nmo:
++                        l2.mo1 = l2.mo2 = l2.mo1 + 1
  # identify mothers
      particleDict={}
@@ -268,14 +246,15 @@
                  pass
              else:
                  if p.mo1 in particleDict:
--                    l=[particleDict[p.mo1]]
++                    l=particleDict[p.mo1]
                      l.append(p.no)
                  else:
--                    l=p.no
++                    l=[p.no]
                  particleDict[p.mo1]=l
  # repair kinematics
      for k in particleDict:
++        if len(particleDict[k]) != 2: continue
          t=particleDict[k]
          p1=event[t[0]-1]
          p1.mom.boost(event[k-1].mom,-1)
 === modified file 'Template/LO/bin/internal/run_pythia'
 --- Template/bin/internal/run_pythia	2011-10-18 03:42:31 +0000
 +++ Template/LO/bin/internal/run_pythia	2012-09-28 12:29:27 +0000
@@ -19,4 +19,5 @@
  echo "      LHAPATH=$pydir/PDFsets" >> ../Cards/pythia_card.dat
  export PDG_MASS_TBL=$pydir/mass_width_2004.mc
--$pydir/pythia && touch pythia.done
 \ No newline at end of file
++$pydir/pythia && touch pythia.done
++
 === modified file 'Template/LO/bin/madevent'
 --- Template/bin/madevent	2012-02-08 05:31:40 +0000
 +++ Template/LO/bin/madevent	2012-09-28 12:29:27 +0000
@@ -33,18 +33,44 @@
  sys.path.insert(0, root_path)
++
++class MyOptParser(optparse.OptionParser):
++
++    class InvalidOption(Exception): pass
++
++    def error(self, msg=''):
++        raise MyOptParser.InvalidOption(msg)
++
++
++
++
  # Write out nice usage message if called with -h or --help
  usage = "usage: %prog [options] [FILE] "
--parser = optparse.OptionParser(usage=usage)
++parser = MyOptParser(usage=usage)
  parser.add_option("-l", "--logging", default='INFO',
                    help="logging level (DEBUG|INFO|WARNING|ERROR|CRITICAL) [%default]")
--parser.add_option("-f", "--file", default='',
--                    help="Use script file FILE")
  parser.add_option("","--web", action="store_true", default=False, dest='web', \
                   help='force to be in secure mode')
  parser.add_option("","--debug", action="store_true", default=False, dest='debug', \
                   help='force to launch debug mode')
--(options, args) = parser.parse_args()
++parser_error = ''
++done = False
++for i in range(len(sys.argv)-1):
++    try:
++        (options, args) = parser.parse_args(sys.argv[1:len(sys.argv)-i])
++        done = True
++    except MyOptParser.InvalidOption, error:
++        pass
++    else:
++        args += sys.argv[len(sys.argv)-i:]
++if not done:
++    # raise correct error:
++    try:
++        (options, args) = parser.parse_args()
++    except MyOptParser.InvalidOption, error:
++        print error
++        sys.exit(2)
++
  if len(args) == 0:
      args = ''
@@ -115,23 +141,33 @@
  # Call the cmd interface main loop
  try:
--    if options.file or args:
++    if (args and os.path.exists(args[0])):
          # They are an input file
--        if args:
--            input_file = args[0]
--        else:
--            input_file = options.file
++        input_file = args[0]
          if options.web:
              cmd_line = cmd_interface.MadEventCmd()
              cmd_line.debug_output = os.path.join(os.path.dirname(input_file),'generation.log')
              cmd_line.use_rawinput = False
              cmd_line.run_cmd('import command ' + input_file)
--            sys.exit()
++            cmd_line.run_cmd('quit')
          else:
              cmd_line = cmd_interface.MadEventCmdShell()
              cmd_line.use_rawinput = False
              cmd_line.run_cmd('import command ' + input_file)
--            sys.exit()
++            cmd_line.run_cmd('quit')
++    elif args:
++        # a single command is provided
++        cmd_line = cmd_interface.MadEventCmd()
++        if not hasattr(cmd_line, 'do_%s' % args[0]):
++            if parser_error:
++                print parser_error
++                print 'and %s  can not be interpreted as a valid command.' % args[0]
++            else:
++                print 'ERROR: %s  not a valid command. Please retry' % args[0]
++        else:
++            cmd_line.use_rawinput = False
++            cmd_line.run_cmd(' '.join(args))
++            cmd_line.run_cmd('quit')
      else:
          # Interactive mode
          if options.web:
@@ -158,11 +194,13 @@
  try:
      if cmd_line.history[-1] not in ['EOF','quit','exit']:
          cmd_line.results.store_result()
++except:
++    print error
++    pass
++
++
++try:
      # Remove lock file
--except:
--    pass
--
--try:
      os.remove(os.path.join(root_path,os.pardir, 'RunWeb'))
  except:
      pass
 === added directory 'Template/NLO'
 === added file 'Template/NLO/.DS_Store'
 Binary files Template/NLO/.DS_Store	1970-01-01 00:00:00 +0000 and Template/NLO/.DS_Store	2012-09-28 12:29:27 +0000 differ
 === added directory 'Template/NLO/Cards'
 === added file 'Template/NLO/Cards/README'
 --- Template/NLO/Cards/README	1970-01-01 00:00:00 +0000
 +++ Template/NLO/Cards/README	2012-09-28 12:29:27 +0000
@@ -0,0 +1,13 @@
++This directory contains samples for all the cards which are used by
++MadGraph/MadEvent during the various stages of code operation.
++
++  Card: proc_card.dat
++  Use : This is the process generation card which is used by
++        MadGraph to generate the code corresponding the user
++        request. It can be used by all user's levels.
++        It now supports multi-processes to be requested at the same
++        time. In this case the events produced are in the right relative
++        ratio also for the different procs. Inclusive samples, like W+jets,
++        are produced starting from this option.
++
++
 === added file 'Template/NLO/Cards/grid_card.dat'
 --- Template/NLO/Cards/grid_card.dat	1970-01-01 00:00:00 +0000
 +++ Template/NLO/Cards/grid_card.dat	2012-09-28 12:29:27 +0000
@@ -0,0 +1,32 @@
++#*********************************************************************
++#                       MadGraph/MadEvent                            *
++#                  http://madgraph.hep.uiuc.edu                      *
++#                                                                    *
++#                        grid_card.dat                               *
++#                                                                    *
++#  This file is used to set the parameters of the run.               *
++#                                                                    *
++#  Some notation/conventions:                                        *
++#                                                                    *
++#   Lines starting with a '# ' are info or comments                  *
++#                                                                    *
++#   mind the format:   value    = variable     ! comment             *
++#*********************************************************************
++#
++#*******************
++# Running parameters
++#*******************
++#
++#*********************************************************************
++#  Tell if this is a grid run or not, false during warm-up on the    *
++#  cluster, automatically set to true after warm-up and the gridpack *
++#  is ready. The user should not change this.                        *
++#*********************************************************************
++  .false.   = GridRun   !True = Runs in the grid mode
++#*********************************************************************
++# Number of events and rnd seed                                      *
++#*********************************************************************
++  2500       = gevents ! Number of unweighted events requested
++     1       = gseed   ! rnd seed
++    -1       = ngran   ! Granularity (minimum # events per channel)
++#*********************************************************************
 === added file 'Template/NLO/Cards/grid_card_default.dat'
 --- Template/NLO/Cards/grid_card_default.dat	1970-01-01 00:00:00 +0000
 +++ Template/NLO/Cards/grid_card_default.dat	2012-09-28 12:29:27 +0000
@@ -0,0 +1,32 @@
++#*********************************************************************
++#                       MadGraph/MadEvent                            *
++#                  http://madgraph.hep.uiuc.edu                      *
++#                                                                    *
++#                        grid_card.dat                               *
++#                                                                    *
++#  This file is used to set the parameters of the run.               *
++#                                                                    *
++#  Some notation/conventions:                                        *
++#                                                                    *
++#   Lines starting with a '# ' are info or comments                  *
++#                                                                    *
++#   mind the format:   value    = variable     ! comment             *
++#*********************************************************************
++#
++#*******************
++# Running parameters
++#*******************
++#
++#*********************************************************************
++#  Tell if this is a grid run or not, false during warm-up on the    *
++#  cluster, automatically set to true after warm-up and the gridpack *
++#  is ready. The user should not change this.                        *
++#*********************************************************************
++  .false.   = GridRun   !True = Runs in the grid mode
++#*********************************************************************
++# Number of events and rnd seed                                      *
++#*********************************************************************
++  2500       = gevents ! Number of unweighted events requested
++     1       = gseed   ! rnd seed
++    -1       = ngran   ! Granularity (minimum # events per channel)
++#*********************************************************************
 === added file 'Template/NLO/Cards/mcatnlo_card.dat'
 --- Template/NLO/Cards/mcatnlo_card.dat	1970-01-01 00:00:00 +0000
 +++ Template/NLO/Cards/mcatnlo_card.dat	2012-09-28 12:29:27 +0000
@@ -0,0 +1,34 @@
++##### HERWIG6
++LHSOFT=.FALSE.                 # Underlying event on (.TRUE.) or off (.FALSE.)
++MODBOS_1=5                     # Gauge boson decay modes
++MODBOS_2=5                     # Gauge boson decay modes
++B_STABLE_HW=.FALSE.            # .TRUE. to let weakly-decaying B hadrons stable
++PI_STABLE_HW=.TRUE.            # .TRUE. if one wants Pi0 stable
++MAXPR_HW=2                     # Number of events to be printed out
++ERR_FR_HW=0.01                 # Tolerated fraction of errors
++IS_BB_HW=.FALSE.               # .TRUE. if it is b-bbar production
++RNDEVSEED1_HW=0                # First random seed (0 for default)
++RNDEVSEED2_HW=0                # Second random seed (0 for default)
++LAMBDAHERW=-1                  # Lambda_5; negative for default
++
++##### HERWIGPP
++UE_HWPP=.FALSE.                # Underlying event on (.TRUE.) or off (.FALSE.)
++HADRONIZE_HWPP=.TRUE.          # Hadronization on (.TRUE.) or off (.FALSE.)
++B_STABLE_HWPP=.FALSE.          # .TRUE. to let weakly-decaying  B hadrons stable
++PI_STABLE_HWPP=.TRUE.          # .TRUE. if one wants Pi0 stable
++MAXPR_HWPP=2                   # Number of events to be printed out
++ERR_FR_HWPP=0.01               # Tolerated fraction of errors
++RNDEVSEED_HWPP=0               # Random seed (if negative it's reset to 0)
++
++##### PYTHIA6Q
++MSTP_81=0                      # Underlying event on (1) or off (0)
++MSTP_111=1                     # Hadronization on (1) or off (0)
++W_STABLE_PY=.FALSE.            # .TRUE. if one wants W+/- stable
++Z_STABLE_PY=.FALSE.            # .TRUE. if one wants Z0 stable
++B_STABLE_PY=.FALSE.            # .TRUE. to let weakly-decaying  B hadrons stable
++PI_STABLE_PY=.TRUE.            # .TRUE. if one wants Pi0 stable
++MAXPR_PY=2                     # Number of events to be printed out
++ERR_FR_PY=0.01                 # Tolerated fraction of errors
++IS_4L_PY=.FALSE.               # .TRUE. if it is four-lepton production
++RNDEVSEED_PY=0                 # Random seed (0 for default)
++LAMBDAPYTH=-1                  # Lambda_5; negative for default
 === added file 'Template/NLO/Cards/param_card_default.dat'
 --- Template/NLO/Cards/param_card_default.dat	1970-01-01 00:00:00 +0000
 +++ Template/NLO/Cards/param_card_default.dat	2012-09-28 12:29:27 +0000
@@ -0,0 +1,71 @@
++#*********************************************************************
++#                        MadGraph/MadEvent                           *
++#                   http://madgraph.hep.uiuc.edu                     *
++#                                                                    *
++#                         param_card.dat                             *
++#                                                                    *
++#   Les Houches friendly file for the SM parameters of MadGraph      *
++#        Spectrum and decay widths produced by SMCalc                *
++#                                                                    *
++#  Please note the following IMPORTANT issues:                       *
++#                                                                    *
++# 0. REFRAIN from editing this file by hand! Some of the parame-     *
++#    ters are not independent                                        *
++#    (such as G_Fermi, alpha_em, sin(theta_W),MZ,MW) and serious     *
++#    problems might be encountered (such as violation of unitarity   *
++#    or gauge invariance).  Always use a calculator.                 *
++#                                                                    *
++# 1. alpha_S(MZ) has been used in the calculation of the parameters  *
++#    but, for consistency, it will be reset by madgraph to the       *
++#    value expected IF the pdfs for collisions with hadrons are      *
++#    used. This value is KEPT by madgraph when no pdf are used       *
++#    lpp(i)=0 .                                                      *
++#                                                                    *
++#  2. Values of the charm and bottom kinematic (pole) masses are     *
++#     those used in the matrix elements and phase space UNLESS they  *
++#     are set to ZERO from the start in the model (particles.dat)    *
++#     This happens, for example,  when using 5-flavor QCD where      *
++#     charm and bottom are treated as partons in the initial state   *
++#     and a zero mass might be hardwired in the model definition.    *
++#                                                                    *
++##********************************************************************
++Block MODSEL # Select Model
++     0   1   #  0 1 = SM
++Block SMINPUTS      # Standard Model inputs
++     1         1.27900000E+02   # alpha_em(MZ)(-1) SM MSbar
++     2         1.16600000E-05   # G_Fermi
++     3         1.18000000E-01   # alpha_s(MZ) SM MSbar
++     4         9.15445065E+01   # Z mass (as input parameter)
++Block MGSMPARAM      # Standard Model parameters for MadGraph
++     1         2.31200000E-01   # sin(theta_W)^2
++     2         8.02673592E+01   # W mass (as input parameter)
++Block MGYUKAWA     # Yukawa masses m/v=y/sqrt(2)
++#    PDG          YMASS
++     5         4.20000000E+00   # mbottom for the Yukawa  y_b
++     4         1.25000000E+00   # mcharm  for the Yukawa  y_c
++     6         1.74300000E+02   # mtop    for the Yukawa  y_t
++    15         1.77700000E+00   # mtau    for the Yukawa  y_ta
++Block MGCKM     # CKM elements for MadGraph
++     1   1     9.75000000E-01   # Vud for Cabibbo matrix
++Block MASS      #  Mass spectrum (kinematic masses)
++#       PDG       Mass
++         4     1.40000000E+00   # charm    pole mass
++         5     4.20000000E+00   # bottom   pole mass
++         6     1.74300000E+02   # top      pole mass
++        15     1.77700000E+00   # tau      mass
++        23     9.15445065E+01   # Z        mass
++        24     8.02673592E+01   # W        mass
++        25     1.00000000E+02   # H        mass
++#            PDG       Width
++DECAY         6     1.51013490E+00   # top width
++DECAY        23     2.44639985E+00   # Z   width
++DECAY        24     2.03535570E+00   # W   width
++DECAY        25     4.27608700E-03   # H   width
++#        BR           NDA        ID1       ID2
++     7.18385415E-02    2           4        -4   # BR( H -> c  cbar  )
++     8.03404251E-01    2           5        -5   # BR( H -> b  bbar  )
++     0.00000000E+00    2           6        -6   # BR( H -> t  tbar  )
++     4.83591503E-02    2          15       -15   # BR( H -> tau- tau+)
++     2.69892403E-05    2          23        23   # BR( H -> Z   Z^(*))
++     3.67605190E-03    2          24       -24   # BR( H -> W   W^(*))
++     2.43358656E-02    2          21        21   # BR( H -> g   g    )
 === added file 'Template/NLO/Cards/plot_card.dat'
 --- Template/NLO/Cards/plot_card.dat	1970-01-01 00:00:00 +0000
 +++ Template/NLO/Cards/plot_card.dat	2012-09-28 12:29:27 +0000
@@ -0,0 +1,203 @@
++#**************************************************************************
++#                      Card for MadAnalysis                               *
++#                                                                         *
++# This file is used to set the classes and options for                    *
++# the MadAnalysis program.                                                *
++#                                                                         *
++#                                                                         *
++# Some comments about the classes                                         *
++# 1. Plots are for classes of particles.                                  *
++# 2. Each particle is identified by its PDG code.                         *
++# 3. Classes names are arbitrary (4 symbols max, no spaces allowed).      *
++# 4. Particles in the same class will be ordered with the 'ordering       *
++#    function' in the file in_func.f.                                     *
++# 5. Classes can be added/edited/removed at will, and given a name        *
++#    that will then appear in the plots.                                  *
++# 6. A particle can be put in one class only. Putting a particle in       *
++#    two or more classes can lead to double counting of events.           *
++# 7. The class name mET is missing Energy and its name is reserved.       *
++#    If used, it must be put last in the classes list below.              *
++# 8. If events contain particles not belonging to an existing class,      *
++#    a new class will automatically be generated.                         *
++# 9. For LHCO events the PDG code 21 is assigned to a jet (not            *
++#    b-tagged), 5 to a b-tagged jet and 12 to missing ET.                 *
++#                                                                         *
++#                                                                         *
++# Some comments about the cuts                                            *
++# 1. In the file kin_func.f the functions on which cuts can be applied    *
++#    are given.                                                           *
++# 2. The syntax is as follows.                                            *
++#      etmin 1 3 30d0                                                     *
++#     means that from the first class the Et of the first three particles *
++#     has to be greater than 30 GeV.                                      *
++#                                                                         *
++#      etmissmin 20d0                                                     *
++#     means that there must be at least 20 GeV of missing Et              *
++#                                                                         *
++#      dRmin 2 1 4 3 3d0                                                  *
++#     means that the distance between the first particle in the second    *
++#     class and the first three particles in the fourth class has to be   *
++#     greater than 3.                                                     *
++#                                                                         *
++#      ptmax 1 3 10d0                                                     *
++#      ptmax 1 2 15d0                                                     *
++#     means that the maximum pt of the third particle in the first class  *
++#     has to smaller than 10 GeV, and the first two particles of this     *
++#     class has to be smaller than 15 GeV                                 *
++# 3. The ordering of the particles within a class can be set with the     *
++#    'ordering function' in the file kin_func.f.                          *
++# 4. For all the 'min' cuts, an event will be thrown away if the particle *
++#    does not exist. On the other hand, for all the 'max' cuts the cut    *
++#    will be ignored if the particle does not exist                       *
++#    (Only dRij is an exception, for which it is the other way around)    *
++#                                                                         *
++#                                                                         *
++#                                                                         *
++# Some comments about the plotting options                                *
++# 1. In the file kin_func.f the functions can be found that can be        *
++#    plotted. (only for off-line usage)                                   *
++# 2. With the plotting options one can set the number of plots for each   *
++#    of these functions.                                                  *
++# 3. One has to specify for each variable which particles from which      *
++#    class are used to set the plots. Syntax:                             *
++#    	et  2 4                                                           *
++#    means that the transverse energy of the first four particles in the  *
++#    second class will be plotted.                                        *
++#       mij 1 3                                                           *
++#	mij 2 2                                                           *
++#    means that for the invariant mass plots the first three particles    *
++#    from the first class and the first two from the second class will be *
++#    used to plot the invariant mass of two particles. (10 plots)         *
++# 4. The ordering of the particles in a class can be set with the         *
++#    'ordering_function'. pt, e and et are valid functions. (For off-line *
++#    users X1, X2 and X3 can also be used, if defined in kin_func.f.)     *
++# 5. Max number of plots is 200.                                          *
++#                                                                         *
++#                                                                         *
++#**************************************************************************
++# Put here your list of classes
++#**************************************************************************
++# Do NOT put spaces before class names!
++# Begin Classes # This is TAG. Do not modify this line
++jet  1 -1 2 -2 3 -3 4 -4 21   # Class number 1
++b    5 -5                     # Class number 2
++mET  12 -12 14 -14 16 -16 1000022    # Missing ET class, name is reserved
++# End Classes # This is TAG. Do not modify this line
++#**************************************************************************
++ordering_function pt  # orders particles in classes according to their pt
++normalization xsec    # histogram normalization, xsec or number (e.g. 1)
++#**************************************************************************
++# Put here list of minimum pt for the classes
++#**************************************************************************
++# Begin Minpts # This is TAG. Do not modify this line
++#1  30
++#2  40
++#3  10
++# End Minpts # This is TAG. Do not modify this line
++#**************************************************************************
++# Cuts on plotted events
++#**************************************************************************
++# Modify the cuts and remove the pounds/hashes to apply those cuts
++# Do NOT put spaces at the beginning of the following lines!
++# Begin Cuts # This is TAG. Do not modify this line
++#etmin     2 2 40d0
++#etmin     2 1 80d0
++#etmin     1 3 20d0
++#etmax     2 1 200d0
++#ptmin     3 1 0d0
++#etmissmin 20d0
++#etmissmax 80d0
++#etamax    1 1 1d0
++#etamax    2 1 2d0
++#etamin    2 2 1.5d0
++#etamin    2 1 2d0
++#mijmax    2 1 2 2 200d0
++#mijmin    2 1 2 2 100d0
++#X1min     2 1 40d0
++#X1max     2 2 50d0
++#dRijmin     2 1 2 2 0.7d0
++#dRijmax     1 3 2 2 0.7d0
++#XY1min    2 2 2 2 20d0
++#XYZA2max  2 2 2 2 4 1 5 1 40d0
++# End Cuts # This is TAG. Do not modify this line
++#**************************************************************************
++# Put here the required plots
++#**************************************************************************
++# Do NOT put spaces at the beginning of the following lines!
++# Begin PlotDefs # This is TAG. Do not modify this line
++pt   1 4   # plot pt for the first four particles in class 1
++pt   2 4   # plot pt for the first four particles in class 2
++pt   3 4   # plot pt for the first four particles in class 3
++pt   4 4   # plot pt for the first four particles in class 4
++pt   5 4   # etc.
++pt   6 4
++pt   7 4
++#e    2 2
++y    1 4   # plot rapidity for the first four particles in class 1
++y    2 4
++y    3 4
++y    4 4
++y    5 4
++y    6 4
++y    7 4
++#eta  2 2   # plot pseudo-rapidity for the first two part in the 2nd class
++#mom  4 1
++#costh 5 1
++#phi   2 2
++#delta_eta 2 2
++#delta_eta 4 1
++mij  1 4   # use the first four particles in the 1st class to plot inv. mass
++mij  2 2   # use the first two particles from the second class as well
++mij  3 1   # etc.
++mij  4 1
++mij  5 1
++mij  6 1
++mij  7 1
++#cosij  1 2
++#cosij  2 2
++#cosij  3 1
++#cosij  4 1
++dRij 1 4
++dRij 2 2
++dRij 3 1
++dRij 4 1
++dRij 5 1
++dRij 6 1
++dRij 7 1
++#delta_phi 2 2
++#delta_phi 4 1
++#delta_phi 5 1
++#X1       2 2  # plot X1 (defined in kin_func.f)
++#XYZA1   2 2
++#XYZA1   4 1
++#XYZA1   5 1
++# End PlotDefs # This is TAG. Do not modify this line
++#**************************************************************************
++#**************************************************************************
++# Put here the plot ranges
++#**************************************************************************
++# Do NOT put spaces at the beginning of the following lines!
++# Begin PlotRange # This is TAG. Do not modify this line
++pt        10    0  500   # bin size, min value, max value
++et        10    0  500   # bin size, min value, max value
++etmiss    10    0  500   # bin size, min value, max value
++ht        20    0 1500
++y         0.2 -5  5     # etc.
++mij       20   0  1500
++dRij      0.1  0  5
++#delta_phi 0.1  0  3.1
++#X1        1    0  100
++#XYZA1     1    0  100
++# End PlotRange # This is TAG. Do not modify this line
++#**************************************************************************
++#**************************************************************************
++# Output for plots
++#**************************************************************************
++# Do NOT put spaces at the beginning of the following lines!
++# Begin PlotOutput # This is TAG. Do not modify this line
++output        topdrawer  # set to topdrawer or gnuplot
++plot_decayed  no         # plot (and cut) dec. res.? (Only for LHE events)
++# End PlotOutput # This is TAG. Do not modify this line
++#**************************************************************************
++#
++#
 === added file 'Template/NLO/Cards/plot_card_default.dat'
 --- Template/NLO/Cards/plot_card_default.dat	1970-01-01 00:00:00 +0000
 +++ Template/NLO/Cards/plot_card_default.dat	2012-09-28 12:29:27 +0000
@@ -0,0 +1,192 @@
++#**************************************************************************
++#                      Card for MadAnalysis                               *
++#                                                                         *
++# This file is used to set the classes and options for                    *
++# the MadAnalysis program.                                                *
++#                                                                         *
++#                                                                         *
++# Some comments about the classes                                         *
++# 1. Plots are for classes of particles.                                  *
++# 2. Each particle is identified by its PDG code.                         *
++# 3. Classes names are arbitrary (4 symbols max, no spaces allowed).      *
++# 4. Particles in the same class will be ordered with the 'ordering       *
++#    function' in the file in_func.f.                                     *
++# 5. Classes can be added/edited/removed at will, and given a name        *
++#    that will then appear in the plots.                                  *
++# 6. A particle can be put in one class only. Putting a particle in       *
++#    two or more classes can lead to double counting of events.           *
++# 7. The class name mET is missing Energy and its name is reserved.       *
++#    If used, it must be put last in the classes list below.              *
++# 8. If events contain particles not belonging to an existing class,      *
++#    a new class will automatically be generated.                         *
++# 9. For LHCO events the PDG code 21 is assigned to a jet (not            *
++#    b-tagged), 5 to a b-tagged jet and 12 to missing ET.                 *
++#                                                                         *
++#                                                                         *
++# Some comments about the cuts                                            *
++# 1. In the file kin_func.f the functions on which cuts can be applied    *
++#    are given.                                                           *
++# 2. The syntax is as follows.                                            *
++#      etmin 1 3 30d0                                                     *
++#     means that from the first class the Et of the first three particles *
++#     has to be greater than 30 GeV.                                      *
++#                                                                         *
++#      etmissmin 20d0                                                     *
++#     means that there must be at least 20 GeV of missing Et              *
++#                                                                         *
++#      dRmin 2 1 4 3 3d0                                                  *
++#     means that the distance between the first particle in the second    *
++#     class and the first three particles in the fourth class has to be   *
++#     greater than 3.                                                     *
++#                                                                         *
++#      ptmax 1 3 10d0                                                     *
++#      ptmax 1 2 15d0                                                     *
++#     means that the maximum pt of the third particle in the first class  *
++#     has to smaller than 10 GeV, and the first two particles of this     *
++#     class has to be smaller than 15 GeV                                 *
++# 3. The ordering of the particles within a class can be set with the     *
++#    'ordering function' in the file kin_func.f.                          *
++# 4. For all the 'min' cuts, an event will be thrown away if the particle *
++#    does not exist. On the other hand, for all the 'max' cuts the cut    *
++#    will be ignored if the particle does not exist                       *
++#    (Only dRij is an exception, for which it is the other way around)    *
++#                                                                         *
++#                                                                         *
++#                                                                         *
++# Some comments about the plotting options                                *
++# 1. In the file kin_func.f the functions can be found that can be        *
++#    plotted. (only for off-line usage)                                   *
++# 2. With the plotting options one can set the number of plots for each   *
++#    of these functions.                                                  *
++# 3. One has to specify for each variable which particles from which      *
++#    class are used to set the plots. Syntax:                             *
++#    	et  2 4                                                           *
++#    means that the transverse energy of the first four particles in the  *
++#    second class will be plotted.                                        *
++#       mij 1 3                                                           *
++#	mij 2 2                                                           *
++#    means that for the invariant mass plots the first three particles    *
++#    from the first class and the first two from the second class will be *
++#    used to plot the invariant mass of two particles. (10 plots)         *
++# 4. The ordering of the particles in a class can be set with the         *
++#    'ordering_function'. pt, e and et are valid functions. (For off-line *
++#    users X1, X2 and X3 can also be used, if defined in kin_func.f.)     *
++# 5. Max number of plots is 200.                                          *
++#                                                                         *
++#                                                                         *
++#**************************************************************************
++# Put here your list of classes
++#**************************************************************************
++# Do NOT put spaces before class names!
++# Begin Classes # This is TAG. Do not modify this line
++jet  1 -1 2 -2 3 -3 4 -4 21   # Class number 1
++b    5 -5                     # Class number 2
++mET  12 -12 14 -14 16 -16     # Missing ET class, name is reserved
++# End Classes # This is TAG. Do not modify this line
++#**************************************************************************
++ordering_function pt  # orders particles in classes according to their pt
++#**************************************************************************
++# Cuts on plotted events
++#**************************************************************************
++# Modify the cuts and remove the pounds/hashes to apply those cuts
++# Do NOT put spaces at the beginning of the following lines!
++# Begin Cuts # This is TAG. Do not modify this line
++#etmin     2 2 40d0
++#etmin     2 1 80d0
++#etmin     1 3 20d0
++#etmax     2 1 200d0
++#ptmin     3 1 0d0
++#etmissmin 20d0
++#etmissmax 80d0
++#etamax    1 1 1d0
++#etamax    2 1 2d0
++#etamin    2 2 1.5d0
++#etamin    2 1 2d0
++#mijmax    2 1 2 2 200d0
++#mijmin    2 1 2 2 100d0
++#X1min     2 1 40d0
++#X1max     2 2 50d0
++#dRijmin     2 1 2 2 0.7d0
++#dRijmax     1 3 2 2 0.7d0
++#XY1min    2 2 2 2 20d0
++#XYZA2max  2 2 2 2 4 1 5 1 40d0
++# End Cuts # This is TAG. Do not modify this line
++#**************************************************************************
++# Put here the required plots
++#**************************************************************************
++# Do NOT put spaces at the beginning of the following lines!
++# Begin PlotDefs # This is TAG. Do not modify this line
++pt   1 4   # plot pt for the first four particles in class 1
++pt   2 4   # plot pt for the first four particles in class 2
++pt   3 4   # plot pt for the first four particles in class 3
++pt   4 4   # plot pt for the first four particles in class 4
++pt   5 4   # etc.
++pt   6 4
++pt   7 4
++#e    2 2
++y    1 4   # plot rapidity for the first four particles in class 1
++y    2 4
++y    3 4
++y    4 4
++y    5 4
++y    6 4
++y    7 4
++#eta  2 2   # plot pseudo-rapidity for the first two part in the 2nd class
++#mom  4 1
++#costh 5 1
++#phi   2 2
++#delta_eta 2 2
++#delta_eta 4 1
++mij  1 4   # use the first four particles in the 1st class to plot inv. mass
++mij  2 2   # use the first two particles from the second class as well
++mij  3 1   # etc.
++mij  4 1
++mij  5 1
++mij  6 1
++mij  7 1
++cosij 1 2
++cosij 2 2
++cosij 3 1
++cosij 4 1
++dRij 1 4
++dRij 2 2
++dRij 3 1
++dRij 4 1
++dRij 5 1
++dRij 6 1
++dRij 7 1
++#delta_phi 2 2
++#delta_phi 4 1
++#delta_phi 5 1
++#X1       2 2  # plot X1 (defined in kin_func.f)
++#XYZA1   2 2
++#XYZA1   4 1
++#XYZA1   5 1
++# End PlotDefs # This is TAG. Do not modify this line
++#**************************************************************************
++#**************************************************************************
++# Put here the plot ranges
++#**************************************************************************
++# Do NOT put spaces at the beginning of the following lines!
++# Begin PlotRange # This is TAG. Do not modify this line
++pt        4    0  200   # bin size, min value, max value
++et        4    0  200   # bin size, min value, max value
++y         0.2 -5  5     # etc.
++mij       10   0  500
++dRij      0.1  0  5
++#delta_phi 0.1  0  3.1
++#X1        1    0  100
++#XYZA1     1    0  100
++# End PlotRange # This is TAG. Do not modify this line
++#**************************************************************************
++#**************************************************************************
++# Output for plots
++#**************************************************************************
++# Do NOT put spaces at the beginning of the following lines!
++# Begin PlotOutput # This is TAG. Do not modify this line
++output        topdrawer  # set to topdrawer or gnuplot
++plot_decayed  no         # plot (and cut) dec. res.? (Only for LHE events)
++# End PlotOutput # This is TAG. Do not modify this line
++#**************************************************************************
++#
++#
 === added file 'Template/NLO/Cards/pythia_card_default.dat'
 --- Template/NLO/Cards/pythia_card_default.dat	1970-01-01 00:00:00 +0000
 +++ Template/NLO/Cards/pythia_card_default.dat	2012-09-28 12:29:27 +0000
@@ -0,0 +1,12 @@
++!...Parton showering on or off
++      MSTP(61)=1
++      MSTP(71)=1
++
++!...Fragmentation/hadronization on or off
++      MSTJ(1)=1
++
++!...Multiple interactions on or off
++      MSTP(81)=20
++
++!...Don't stop execution after 10 errors
++      MSTU(21)=1
 === added file 'Template/NLO/Cards/replace_card1.dat'
 --- Template/NLO/Cards/replace_card1.dat	1970-01-01 00:00:00 +0000
 +++ Template/NLO/Cards/replace_card1.dat	2012-09-28 12:29:27 +0000
@@ -0,0 +1,4 @@
++# Enter here any particles you want replaced in the event file after ME run
++# In the syntax PID : PID1 PID2 PID3 ...
++# End with "done" or <newline>
++
 === added file 'Template/NLO/Cards/run_card.dat'
 --- Template/NLO/Cards/run_card.dat	1970-01-01 00:00:00 +0000
 +++ Template/NLO/Cards/run_card.dat	2012-09-28 12:29:27 +0000
@@ -0,0 +1,103 @@
++#*********************************************************************
++#                       MadGraph/MadEvent                            *
++#                  http://madgraph.hep.uiuc.edu                      *
++#                                                                    *
++#                        run_card.dat                                *
++#                                                                    *
++#  This file is used to set the parameters of the run.               *
++#                                                                    *
++#  Some notation/conventions:                                        *
++#                                                                    *
++#   Lines starting with a '# ' are info or comments                  *
++#                                                                    *
++#   mind the format:   value    = variable     ! comment             *
++#*********************************************************************
++#
++#*******************
++# Running parameters
++#*******************
++#
++#*********************************************************************
++# Number of events                                                   *
++#*********************************************************************
++ 10000    = nevents     ! Number of unweighted events requested
++     0    = iseed       ! rnd seed (0=assigned automatically=default))
++#*********************************************************************
++# Collider type and energy                                           *
++#*********************************************************************
++    1   = lpp1    ! beam 1 type (0 = no PDF)
++    1   = lpp2    ! beam 2 type (0 = no PDF)
++ 4000   = ebeam1  ! beam 1 energy in GeV
++ 4000   = ebeam2  ! beam 2 energy in GeV
++#*********************************************************************
++# PDF choice: this automatically fixes also alpha_s(MZ) and its evol.*
++#*********************************************************************
++ 'cteq6_m'   = pdlabel     ! PDF set
++  10042      = lhaid
++#*********************************************************************
++# Include the NLO Monte Carlo subtr. terms for the following parton  *
++# shower (HERWIG6 | HERWIGPP | PYTHIA6Q )                            *
++#*********************************************************************
++  HERWIG6   = parton_shower
++#*********************************************************************
++# Renormalization and factorization scales                           *
++# (Default functional form for the non-fixed scales is the sum of    *
++# the transverse masses of all final state particles & partons. This *
++# can be changed in SubProcesses/set_scales.f)                       *
++#*********************************************************************
++ F        = fixed_ren_scale  ! if .true. use fixed ren scale
++ F        = fixed_fac_scale  ! if .true. use fixed fac scale
++ 91.188   = muR_ref_fixed    ! fixed ren reference scale
++ 91.188   = muF1_ref_fixed   ! fixed fact reference scale for pdf1
++ 91.188   = muF2_ref_fixed   ! fixed fact reference scale for pdf2
++#*********************************************************************
++# Renormalization and factorization scales (advanced and NLO options)*
++#*********************************************************************
++ F        = fixed_QES_scale  ! if .true. use fixed Ellis-Sexton scale
++ 91.188   = QES_ref_fixed    ! fixed Ellis-Sexton reference scale
++ 1        = muR_over_ref     ! ratio of current muR over reference muR
++ 1        = muF1_over_ref    ! ratio of current muF1 over reference muF1
++ 1        = muF2_over_ref    ! ratio of current muF2 over reference muF2
++ 1        = QES_over_ref     ! ratio of current QES over reference QES
++#*********************************************************************
++# Reweight flags to get scale dependence and PDF uncertainty         *
++# For scale dependence: factor rw_scale_up/down around central scale *
++# For PDF uncertainty: use LHAPDF with supported set                 *
++#*********************************************************************
++ .true.   = reweight_scale   ! reweight to get scale dependence
++  0.5     = rw_Rscale_down   ! lower bound for ren scale variations
++  2.0     = rw_Rscale_up     ! upper bound for ren scale variations
++  0.5     = rw_Fscale_down   ! lower bound for fact scale variations
++  2.0     = rw_Fscale_up     ! upper bound for fact scale variations
++ .false.  = reweight_PDF     ! reweight to get PDF uncertainty
++  21101   = PDF_set_min      ! First of the error PDF sets
++  21140   = PDF_set_max      ! Last of the error PDF sets
++#*********************************************************************
++#
++#*********************************************************************
++# BW cutoff (M+/-bwcutoff*Gamma)                                     *
++#*********************************************************************
++ 15  = bwcutoff
++#*********************************************************************
++# Cuts on the jets                                                   *
++# When matching to a parton shower, these generation cuts should be  *
++# considerably softer than the analysis cuts.                        *
++# (more specific cuts can be specified in SubProcesses/cuts.f)       *
++#*********************************************************************
++    1  = jetalgo    ! FastJet jet algorithm (1=kT, 0=C/A, -1=anti-kT)
++  0.7  = jetradius  ! The radius parameter for the jet algorithm
++   10  = ptj        ! Minimal jet transverse momentum
++   -1  = etaj       ! Maximal jet pseudo-rapidity (absolute value)
++#*********************************************************************
++# Cuts on the charged leptons (e+, e-, mu+, mu-, tau+ and tau-)      *
++# (more specific gen cuts can be specified in SubProcesses/cuts.f)   *
++#*********************************************************************
++   0  = ptl   ! Min lepton transverse momentum
++  -1  = etal  ! Max lepton pseudo rapidity
++   0  = drll  ! Min distance between opposite sign lepton pairs
++  30  = mll   ! Min inv. mass of all oppositely charged lepton pairs
++#*********************************************************************
++# maximal pdg code for quark to be considered as a jet               *
++#*********************************************************************
++ 5 = maxjetflavor
++#*********************************************************************
 === added file 'Template/NLO/Cards/run_card_default.dat'
 --- Template/NLO/Cards/run_card_default.dat	1970-01-01 00:00:00 +0000
 +++ Template/NLO/Cards/run_card_default.dat	2012-09-28 12:29:27 +0000
@@ -0,0 +1,198 @@
++#*********************************************************************
++#                       MadGraph/MadEvent                            *
++#                  http://madgraph.hep.uiuc.edu                      *
++#                                                                    *
++#                        run_card.dat                                *
++#                                                                    *
++#  This file is used to set the parameters of the run.               *
++#                                                                    *
++#  Some notation/conventions:                                        *
++#                                                                    *
++#   Lines starting with a '# ' are info or comments                  *
++#                                                                    *
++#   mind the format:   value    = variable     ! comment             *
++#*********************************************************************
++#
++#*******************
++# Running parameters
++#*******************
++#
++#*********************************************************************
++# Tag name for the run (one word)                                    *
++#*********************************************************************
++  'fermi'     = run_tag ! name of the run
++#*********************************************************************
++# Run to generate the grid pack                                      *
++#*********************************************************************
++  .false.     = gridpack  !True = setting up the grid pack
++#*********************************************************************
++# Number of events and rnd seed                                      *
++#*********************************************************************
++  10000       = nevents ! Number of unweighted events requested
++      0       = iseed   ! rnd seed (0=assigned automatically=default))
++#*********************************************************************
++# Collider type and energy                                           *
++#*********************************************************************
++        1     = lpp1  ! beam 1 type (0=NO PDF)
++        1     = lpp2  ! beam 2 type (0=NO PDF)
++     7000     = ebeam1  ! beam 1 energy in GeV
++     7000     = ebeam2  ! beam 2 energy in GeV
++#*********************************************************************
++# Beam polarization from -100 (left-handed) to 100 (right-handed)    *
++#*********************************************************************
++        0     = polbeam1 ! beam polarization for beam 1
++        0     = polbeam2 ! beam polarization for beam 2
++#*********************************************************************
++# PDF CHOICE: this automatically fixes also alpha_s and its evol.    *
++#*********************************************************************
++ 'cteq6l1'    = pdlabel     ! PDF set
++#*********************************************************************
++# Renormalization and factorization scales                           *
++#*********************************************************************
++ F        = fixed_ren_scale  ! if .true. use fixed ren scale
++ F        = fixed_fac_scale  ! if .true. use fixed fac scale
++ 91.1880  = scale            ! fixed ren scale
++ 91.1880  = dsqrt_q2fact1    ! fixed fact scale for pdf1
++ 91.1880  = dsqrt_q2fact2    ! fixed fact scale for pdf2
++ 1        = scalefact        ! scale factor for event-by-event scales
++#*********************************************************************
++# Matching - Warning! ickkw > 1 is still beta
++#*********************************************************************
++ 0        = ickkw            ! 0 no matching, 1 MLM, 2 CKKW matching
++ 1        = highestmult      ! for ickkw=2, highest mult group
++ 1        = ktscheme         ! for ickkw=1, 1 Durham kT, 2 Pythia pTE
++ 1        = alpsfact         ! scale factor for QCD emission vx
++ F        = chcluster        ! cluster only according to channel diag
++ F        = pdfwgt           ! for ickkw=1, perform pdf reweighting
++#*********************************************************************
++#
++#**********************************
++# BW cutoff (M+/-bwcutoff*Gamma)
++#**********************************
++  15  = bwcutoff
++#*******************
++# Standard Cuts
++#*******************
++#
++#*********************************************************************
++# Minimum and maximum pt's                                           *
++#*********************************************************************
++ 20  = ptj       ! minimum pt for the jets
++  0  = ptb       ! minimum pt for the b
++ 10  = pta       ! minimum pt for the photons
++ 10  = ptl       ! minimum pt for the charged leptons
++  0  = misset    ! minimum missing Et (sum of neutrino's momenta)
++  0  = ptheavy   ! minimum pt for one heavy final state
++ 1.0 = ptonium   ! minimum pt for the quarkonium states
++ 1d5 = ptjmax    ! maximum pt for the jets
++ 1d5 = ptbmax    ! maximum pt for the b
++ 1d5 = ptamax    ! maximum pt for the photons
++ 1d5 = ptlmax    ! maximum pt for the charged leptons
++ 1d5 = missetmax ! maximum missing Et (sum of neutrino's momenta)
++#*********************************************************************
++# Minimum and maximum E's (in the lab frame)                         *
++#*********************************************************************
++  0  = ej     ! minimum E for the jets
++  0  = eb     ! minimum E for the b
++  0  = ea     ! minimum E for the photons
++  0  = el     ! minimum E for the charged leptons
++ 1d5  = ejmax ! maximum E for the jets
++ 1d5  = ebmax ! maximum E for the b
++ 1d5  = eamax ! maximum E for the photons
++ 1d5  = elmax ! maximum E for the charged leptons
++#*********************************************************************
++# Maximum and minimum rapidity                                       *
++#*********************************************************************
++   5  = etaj    ! max rap for the jets
++ 1d2  = etab    ! max rap for the b
++ 2.5  = etaa    ! max rap for the photons
++ 2.5  = etal    ! max rap for the charged leptons
++ 0.6  = etaonium ! max rap for the quarkonium states
++ 0d0  = etajmin ! min rap for the jets
++ 0d0  = etabmin ! min rap for the b
++ 0d0  = etaamin ! min rap for the photons
++ 0d0  = etalmin ! main rap for the charged leptons
++#*********************************************************************
++# Minimum and maximum DeltaR distance                                *
++#*********************************************************************
++ 0.4 = drjj    ! min distance between jets
++ 0   = drbb    ! min distance between b's
++ 0.4 = drll    ! min distance between leptons
++ 0.4 = draa    ! min distance between gammas
++ 0   = drbj    ! min distance between b and jet
++ 0.4 = draj    ! min distance between gamma and jet
++ 0.4 = drjl    ! min distance between jet and lepton
++ 0   = drab    ! min distance between gamma and b
++ 0   = drbl    ! min distance between b and lepton
++ 0.4 = dral    ! min distance between gamma and lepton
++ 1d2 = drjjmax ! max distance between jets
++ 1d2 = drbbmax ! max distance between b's
++ 1d2 = drllmax ! max distance between leptons
++ 1d2 = draamax ! max distance between gammas
++ 1d2 = drbjmax ! max distance between b and jet
++ 1d2 = drajmax ! max distance between gamma and jet
++ 1d2 = drjlmax ! max distance between jet and lepton
++ 1d2 = drabmax ! max distance between gamma and b
++ 1d2 = drblmax ! max distance between b and lepton
++ 1d2 = dralmax ! maxdistance between gamma and lepton
++#*********************************************************************
++# Minimum and maximum invariant mass for pairs                       *
++#*********************************************************************
++ 0   = mmjj    ! min invariant mass of a jet pair
++ 0   = mmbb    ! min invariant mass of a b pair
++ 0   = mmaa    ! min invariant mass of gamma gamma pair
++ 0   = mmll    ! min invariant mass of l+l- (same flavour) lepton pair
++ 1d5 = mmjjmax ! max invariant mass of a jet pair
++ 1d5 = mmbbmax ! max invariant mass of a b pair
++ 1d5 = mmaamax ! max invariant mass of gamma gamma pair
++ 1d5 = mmllmax ! max invariant mass of l+l- (same flavour) lepton pair
++#*********************************************************************
++# Minimum and maximum invariant mass for all letpons                 *
++#*********************************************************************
++ 0   = mmnl    ! min invariant mass for all letpons (l+- and vl)
++ 1d5 = mmnlmax ! max invariant mass for all letpons (l+- and vl)
++#*********************************************************************
++# Inclusive cuts                                                     *
++#*********************************************************************
++ 0  = xptj ! minimum pt for at least one jet
++ 0  = xptb ! minimum pt for at least one b
++ 0  = xpta ! minimum pt for at least one photon
++ 0  = xptl ! minimum pt for at least one charged lepton
++#*********************************************************************
++# Control the pt's of the jets sorted by pt                          *
++#*********************************************************************
++ 0   = ptj1min ! minimum pt for the leading jet in pt
++ 0   = ptj2min ! minimum pt for the second jet in pt
++ 0   = ptj3min ! minimum pt for the third jet in pt
++ 0   = ptj4min ! minimum pt for the fourth jet in pt
++ 1d5 = ptj1max ! maximum pt for the leading jet in pt
++ 1d5 = ptj2max ! maximum pt for the second jet in pt
++ 1d5 = ptj3max ! maximum pt for the third jet in pt
++ 1d5 = ptj4max ! maximum pt for the fourth jet in pt
++ 0   = cutuse  ! reject event if fails any (0) / all (1) jet pt cuts
++#*********************************************************************
++# Control the Ht(k)=Sum of k leading jets                            *
++#*********************************************************************
++ 0   = htjmin ! minimum jet HT=Sum(jet pt)
++ 1d5 = htjmax ! maximum jet HT=Sum(jet pt)
++ 0   = ht2min ! minimum Ht for the two leading jets
++ 0   = ht3min ! minimum Ht for the three leading jets
++ 0   = ht4min ! minimum Ht for the four leading jets
++ 1d5 = ht2max ! maximum Ht for the two leading jets
++ 1d5 = ht3max ! maximum Ht for the three leading jets
++ 1d5 = ht4max ! maximum Ht for the four leading jets
++#*********************************************************************
++# WBF cuts                                                           *
++#*********************************************************************
++ 0   = xetamin ! minimum rapidity for two jets in the WBF case
++ 0   = deltaeta ! minimum rapidity for two jets in the WBF case
++#*********************************************************************
++# maximal pdg code for quark to be considered as a jet               *
++# otherwise b cuts are applied                                       *
++#*********************************************************************
++ 4 = maxjetflavor
++#*********************************************************************
++# Jet measure cuts                                                   *
++#*********************************************************************
++ 0   = xqcut   ! minimum kt jet measure between partons
++#*********************************************************************
 === added directory 'Template/NLO/Events'
 === added file 'Template/NLO/Events/banner_header.txt'
 --- Template/NLO/Events/banner_header.txt	1970-01-01 00:00:00 +0000
 +++ Template/NLO/Events/banner_header.txt	2012-09-28 12:29:27 +0000
@@ -0,0 +1,31 @@
++<LesHouchesEvents version="1.0">
++<header>
++<!--
++#*********************************************************************
++#                                                                    *
++#                       MadGraph/MadEvent                            *
++#                                                                    *
++#                      The new web generation                        *
++#                                                                    *
++#                   http://madgraph.hep.uiuc.edu                     *
++#                   http://madgraph.phys.ucl.ac.be                   *
++#                   http://madgraph.roma2.infn.it                    *
++#                                                                    *
++#            CP3 team                      Tim Stelzer               *
++#      Universite de Louvain          University of Illinois         *
++#                                                                    *
++#....................................................................*
++#                                                                    *
++# This file contains all the information necessary to reproduce      *
++# the events generated:                                              *
++#                                                                    *
++# 1. software version                                                *
++# 2. proc_card.dat      : code generation info including model       *
++# 3. param_card.dat     : model primary parameters in the LH format  *
++# 4. run_card.dat       : running parameters (collider and cuts)     *
++# 5. pythia_card.dat    : present only in the pythia event file      *
++# 6. pgs_card.dat       : present only in the pgs event file         *
++#                                                                    *
++#                                                                    *
++#*********************************************************************
++-->
 === added directory 'Template/NLO/HTML'
 === added file 'Template/NLO/HTML/card.jpg'
 Binary files Template/NLO/HTML/card.jpg	1970-01-01 00:00:00 +0000 and Template/NLO/HTML/card.jpg	2012-09-28 12:29:27 +0000 differ
 === added file 'Template/NLO/HTML/crossx.html'
 === added file 'Template/NLO/HTML/info-default.html'
 --- Template/NLO/HTML/info-default.html	1970-01-01 00:00:00 +0000
 +++ Template/NLO/HTML/info-default.html	2012-09-28 12:29:27 +0000
@@ -0,0 +1,13 @@
++<HTML>
++<HEAD>
++<TITLE>Info file</TITLE>
++<META HTTP-EQUIV="EXPIRES" CONTENT="20" ></HEAD>
++<BODY>
++<P> <H2 ALIGN=CENTER> SubProcesses and Feynman diagrams </H2>
++<P> <H4 ALIGN=CENTER> Information not available yet: </H4>
++<P> <H4 ALIGN=CENTER> Process might still be generated or has failed.</H4>
++<P> <H4 ALIGN=CENTER> Please check the <a href="../proc_log.txt">process generation log</a> and the process information status on the
++<a href="../index.html">main page</a>.</H4>
++<P> <H4 ALIGN=CENTER> If generation failed, please check the <a href="../Cards/proc_card.dat">process card</a> for mistakes in syntax.</H4>
++<H4 align=center> <A  HREF="card.html"> Main Page </A> </h4>
++</HTML>
 === added file 'Template/NLO/HTML/mgstyle.css'
 --- Template/NLO/HTML/mgstyle.css	1970-01-01 00:00:00 +0000
 +++ Template/NLO/HTML/mgstyle.css	2012-09-28 12:29:27 +0000
@@ -0,0 +1,34 @@
++th a:link{
++    color:black;
++}
++
++table {
++             border-width: 1px;
++             border-spacing: 0px;
++             border-style: outset;
++             border-color: black;
++             border-collapse: collapse;
++             background-color: white;
++}
++table th {
++             border-width: 2px;
++             padding: 1px;
++             border-style: solid;
++             border-color: black;
++             background-color: white;
++}
++
++table td {
++             border-width: 2px;
++             padding: 1px;
++             border-style: solid;
++             border-color: black;
++}
++
++input {
++            display: inline;
++}
++
++form {
++            display: inline;
++}
 === added file 'Template/NLO/HTML/sortable.js'
 --- Template/NLO/HTML/sortable.js	1970-01-01 00:00:00 +0000
 +++ Template/NLO/HTML/sortable.js	2012-09-28 12:29:27 +0000
@@ -0,0 +1,335 @@
++/*
++Table sorting script  by Joost de Valk, check it out at http://www.joostdevalk.nl/code/sortable-table/.
++Based on a script from http://www.kryogenix.org/code/browser/sorttable/.
++Distributed under the MIT license: http://www.kryogenix.org/code/browser/licence.html .
++Modify by the MG team for compatibility issue
++
++Copyright (c) 1997-2007 Stuart Langridge, Joost de Valk.
++
++Version 1.5.7
++*/
++
++/* You can change these values */
++var europeandate = true;
++var alternate_row_colors = true;
++
++/* Don't change anything below this unless you know what you're doing */
++addEvent(window, "load", sortables_init);
++
++var SORT_COLUMN_INDEX;
++var thead = false;
++
++function sortables_init() {
++	// Find all tables with class sortable and make them sortable
++	if (!document.getElementsByTagName) return;
++	tbls = document.getElementsByTagName("table");
++	for (ti=0;ti<tbls.length;ti++) {
++		thisTbl = tbls[ti];
++		if (((' '+thisTbl.className+' ').indexOf("sortable") != -1) && (thisTbl.id)) {
++			ts_makeSortable(thisTbl);
++			// make it sortable according to the second column
++			if (thisTbl.tHead && thisTbl.tHead.rows.length > 0) {
++			    var firstRow = thisTbl.tHead.rows[thisTbl.tHead.rows.length-1];
++			} else {
++			    var firstRow = thisTbl.rows[0];
++			}
++
++			for (var ci=0;ci<firstRow.cells[1].childNodes.length;ci++) {
++			    if (firstRow.cells[1].childNodes[ci].tagName && firstRow.cells[1].childNodes[ci].tagName.toLowerCase() == 'a') var lnk = firstRow.cells[1].childNodes[ci];
++			}
++                        ts_resortTable(lnk, 1); //order by cross-section
++                        ts_resortTable(lnk, 1); //order by cross-section
++		}
++	}
++}
++
++function ts_makeSortable(t) {
++	if (t.rows && t.rows.length > 0) {
++		if (t.tHead && t.tHead.rows.length > 0) {
++			var firstRow = t.tHead.rows[t.tHead.rows.length-1];
++			thead = true;
++		} else {
++			var firstRow = t.rows[0];
++		}
++	}
++	if (!firstRow) return;
++
++	// We have a first row: assume it's the header, and make its contents clickable links
++	for (var i=0;i<firstRow.cells.length;i++) {
++		var cell = firstRow.cells[i];
++		var txt = ts_getInnerText(cell);
++		if (cell.className != "unsortable" && cell.className.indexOf("unsortable") == -1) {
++			cell.innerHTML = '<a href="#" class="sortheader" onclick="ts_resortTable(this, '+i+');return false;">'+txt+'<span class="sortarrow"></span></a>';
++		}
++	}
++	if (alternate_row_colors) {
++		alternate(t);
++	}
++}
++
++function ts_getInnerText(el) {
++	if (typeof el == "string") return el;
++	if (typeof el == "undefined") { return el };
++	if (el.innerText) return el.innerText;	//Not needed but it is faster
++	var str = "";
++
++	var cs = el.childNodes;
++	var l = cs.length;
++	for (var i = 0; i < l; i++) {
++		switch (cs[i].nodeType) {
++			case 1: //ELEMENT_NODE
++				str += ts_getInnerText(cs[i]);
++				break;
++			case 3:	//TEXT_NODE
++				str += cs[i].nodeValue;
++				break;
++		}
++	}
++	return str;
++}
++
++function ts_resortTable(lnk, clid) {
++	var span;
++	for (var ci=0;ci<lnk.childNodes.length;ci++) {
++		if (lnk.childNodes[ci].tagName && lnk.childNodes[ci].tagName.toLowerCase() == 'span') span = lnk.childNodes[ci];
++	}
++	var spantext = ts_getInnerText(span);
++	var td = lnk.parentNode;
++	var column = clid || td.cellIndex;
++	var t = getParent(td,'TABLE');
++	// Work out a type for the column
++	if (t.rows.length <= 1) return;
++	var itm = "";
++	var i = 1;
++	while (itm == "" && i < t.tBodies[0].rows.length) {
++		var itm = ts_getInnerText(t.tBodies[0].rows[i].cells[column]);
++		itm = trim(itm);
++		if (itm.substr(0,4) == "<!--" || itm.length == 0) {
++			itm = "";
++		}
++		i++;
++	}
++	if (itm == "") return;
++	sortfn = ts_sort_caseinsensitive;
++	if (itm.match(/^\d\d[\/\.-][a-zA-z][a-zA-Z][a-zA-Z][\/\.-]\d\d\d\d$/)) sortfn = ts_sort_date;
++	if (itm.match(/^\d\d[\/\.-]\d\d[\/\.-]\d\d\d{2}?$/)) sortfn = ts_sort_date;
++	if (itm.match(/^-?[£$€Û¢´]\d/)) sortfn = ts_sort_numeric;
++	if (itm.match(/^-?(\d+[,\.]?)+(E[-+][\d]+)?%?$/)) sortfn = ts_sort_numeric;
++	if (itm.match(/^-?(\d+[,\.]?\d+e[-+][\d]+)?%?$/)) sortfn = ts_sort_numeric;
++	if (itm.match(/^-?(\d+[,\.]?)+([\d]+)?%?$/)) sortfn = ts_sort_numeric;
++	SORT_COLUMN_INDEX = column;
++	var firstRow = new Array();
++	var newRows = new Array();
++	for (k=0;k<t.tBodies.length;k++) {
++		for (i=0;i<t.tBodies[k].rows[0].length;i++) {
++			firstRow[i] = t.tBodies[k].rows[0][i];
++		}
++	}
++	for (k=0;k<t.tBodies.length;k++) {
++		if (!thead) {
++			// Skip the first row
++			for (j=1;j<t.tBodies[k].rows.length;j++) {
++				newRows[j-1] = t.tBodies[k].rows[j];
++			}
++		} else {
++			// Do NOT skip the first row
++			for (j=0;j<t.tBodies[k].rows.length;j++) {
++				newRows[j] = t.tBodies[k].rows[j];
++			}
++		}
++	}
++	newRows.sort(sortfn);
++	if (span.getAttribute("sortdir") == 'down') {
++			ARROW = '&nbsp;&nbsp;&darr;';
++			newRows.reverse();
++			span.setAttribute('sortdir','up');
++	} else {
++			ARROW = '&nbsp;&nbsp;&uarr;';
++			span.setAttribute('sortdir','down');
++	}
++    // We appendChild rows that already exist to the tbody, so it moves them rather than creating new ones
++    // don't do sortbottom rows
++    for (i=0; i<newRows.length; i++) {
++		if (!newRows[i].className || (newRows[i].className && (newRows[i].className.indexOf('sortbottom') == -1))) {
++			t.tBodies[0].appendChild(newRows[i]);
++		}
++	}
++    // do sortbottom rows only
++    for (i=0; i<newRows.length; i++) {
++		if (newRows[i].className && (newRows[i].className.indexOf('sortbottom') != -1))
++			t.tBodies[0].appendChild(newRows[i]);
++	}
++	// Delete any other arrows there may be showing
++	var allspans = document.getElementsByTagName("span");
++	for (var ci=0;ci<allspans.length;ci++) {
++		if (allspans[ci].className == 'sortarrow') {
++			if (getParent(allspans[ci],"table") == getParent(lnk,"table")) { // in the same table as us?
++				allspans[ci].innerHTML = '';
++			}
++		}
++	}
++	span.innerHTML = ARROW;
++	alternate(t);
++}
++
++function getParent(el, pTagName) {
++	if (el == null) {
++		return null;
++	} else if (el.nodeType == 1 && el.tagName.toLowerCase() == pTagName.toLowerCase()) {
++		return el;
++	} else {
++		return getParent(el.parentNode, pTagName);
++	}
++}
++
++function sort_date(date) {
++	// y2k notes: two digit years less than 50 are treated as 20XX, greater than 50 are treated as 19XX
++	dt = "00000000";
++	if (date.length == 11) {
++		mtstr = date.substr(3,3);
++		mtstr = mtstr.toLowerCase();
++		switch(mtstr) {
++			case "jan": var mt = "01"; break;
++			case "feb": var mt = "02"; break;
++			case "mar": var mt = "03"; break;
++			case "apr": var mt = "04"; break;
++			case "may": var mt = "05"; break;
++			case "jun": var mt = "06"; break;
++			case "jul": var mt = "07"; break;
++			case "aug": var mt = "08"; break;
++			case "sep": var mt = "09"; break;
++			case "oct": var mt = "10"; break;
++			case "nov": var mt = "11"; break;
++			case "dec": var mt = "12"; break;
++			// default: var mt = "00";
++		}
++		dt = date.substr(7,4)+mt+date.substr(0,2);
++		return dt;
++	} else if (date.length == 10) {
++		if (europeandate == false) {
++			dt = date.substr(6,4)+date.substr(0,2)+date.substr(3,2);
++			return dt;
++		} else {
++			dt = date.substr(6,4)+date.substr(3,2)+date.substr(0,2);
++			return dt;
++		}
++	} else if (date.length == 8) {
++		yr = date.substr(6,2);
++		if (parseInt(yr) < 50) {
++			yr = '20'+yr;
++		} else {
++			yr = '19'+yr;
++		}
++		if (europeandate == true) {
++			dt = yr+date.substr(3,2)+date.substr(0,2);
++			return dt;
++		} else {
++			dt = yr+date.substr(0,2)+date.substr(3,2);
++			return dt;
++		}
++	}
++	return dt;
++}
++
++function ts_sort_date(a,b) {
++	dt1 = sort_date(ts_getInnerText(a.cells[SORT_COLUMN_INDEX]));
++	dt2 = sort_date(ts_getInnerText(b.cells[SORT_COLUMN_INDEX]));
++
++	if (dt1==dt2) {
++		return 0;
++	}
++	if (dt1<dt2) {
++		return -1;
++	}
++	return 1;
++}
++function ts_sort_numeric(a,b) {
++	var aa = ts_getInnerText(a.cells[SORT_COLUMN_INDEX]);
++        aa = clean_num(aa);
++	var bb = ts_getInnerText(b.cells[SORT_COLUMN_INDEX]);
++	bb = clean_num(bb);
++	return compare_numeric(aa,bb);
++}
++function compare_numeric(a,b) {
++	var a = parseFloat(a);
++	a = (isNaN(a) ? 0 : a);
++	var b = parseFloat(b);
++	b = (isNaN(b) ? 0 : b);
++	return a - b;
++}
++function ts_sort_caseinsensitive(a,b) {
++	aa = ts_getInnerText(a.cells[SORT_COLUMN_INDEX]).toLowerCase();
++	bb = ts_getInnerText(b.cells[SORT_COLUMN_INDEX]).toLowerCase();
++	if (aa==bb) {
++		return 0;
++	}
++	if (aa<bb) {
++		return -1;
++	}
++	return 1;
++}
++function ts_sort_default(a,b) {
++	aa = ts_getInnerText(a.cells[SORT_COLUMN_INDEX]);
++	bb = ts_getInnerText(b.cells[SORT_COLUMN_INDEX]);
++	if (aa==bb) {
++		return 0;
++	}
++	if (aa<bb) {
++		return -1;
++	}
++	return 1;
++}
++
++function addEvent(elm, evType, fn, useCapture)
++// addEvent and removeEvent
++// cross-browser event handling for IE5+,	NS6 and Mozilla
++// By Scott Andrew
++{
++	if (elm.addEventListener){
++		elm.addEventListener(evType, fn, useCapture);
++		return true;
++	} else if (elm.attachEvent){
++		var r = elm.attachEvent("on"+evType, fn);
++		return r;
++	} else {
++		alert("Handler could not be removed");
++	}
++}
++function clean_num(str) {
++	str = str.replace(new RegExp(/[^-?0-9.eE]/g),"");
++	return str;
++}
++function trim(s) {
++	return s.replace(/^\s+|\s+$/g, "");
++}
++function alternate(table) {
++	// Take object table and get all it's tbodies.
++	var tableBodies = table.getElementsByTagName("tbody");
++	// Loop through these tbodies
++	for (var i = 0; i < tableBodies.length; i++) {
++		// Take the tbody, and get all it's rows
++		var tableRows = tableBodies[i].getElementsByTagName("tr");
++		// Loop through these rows
++		// Start at 1 because we want to leave the heading row untouched
++		for (var j = 0; j < tableRows.length; j++) {
++			// Check if j is even, and apply classes for both possible results
++			if ( (j % 2) == 0  ) {
++				if ( !(tableRows[j].className.indexOf('odd') == -1) ) {
++					tableRows[j].className = tableRows[j].className.replace('odd', 'even');
++				} else {
++					if ( tableRows[j].className.indexOf('even') == -1 ) {
++						tableRows[j].className += " even";
++					}
++				}
++			} else {
++				if ( !(tableRows[j].className.indexOf('even') == -1) ) {
++					tableRows[j].className = tableRows[j].className.replace('even', 'odd');
++				} else {
++					if ( tableRows[j].className.indexOf('odd') == -1 ) {
++						tableRows[j].className += " odd";
++					}
++				}
++			}
++		}
++	}
++}
 === added file 'Template/NLO/HTML/stop.jpg'
 Binary files Template/NLO/HTML/stop.jpg	1970-01-01 00:00:00 +0000 and Template/NLO/HTML/stop.jpg	2012-09-28 12:29:27 +0000 differ
 === added file 'Template/NLO/HTML/thinking.gif'
 Binary files Template/NLO/HTML/thinking.gif	1970-01-01 00:00:00 +0000 and Template/NLO/HTML/thinking.gif	2012-09-28 12:29:27 +0000 differ
 === added file 'Template/NLO/MGMEVersion.txt'
 --- Template/NLO/MGMEVersion.txt	1970-01-01 00:00:00 +0000
 +++ Template/NLO/MGMEVersion.txt	2012-09-28 12:29:27 +0000
@@ -0,0 +1,1 @@
++4.5.0
 === added file 'Template/NLO/README'
 --- Template/NLO/README	1970-01-01 00:00:00 +0000
 +++ Template/NLO/README	2012-09-28 12:29:27 +0000
@@ -0,0 +1,69 @@
++MadGraph/MadEvent 4.0
++By Fabio Maltoni, Tim Stelzer and the CP3 development team
++
++http://madgraph.phys.ucl.ac.be/
++http://madgraph.hep.uiuc.edu/
++http://madgraph.roma2.infn.it/
++
++Information on the process to be generated is found in the file
++index.html in this directory, which should be viewed using your web
++browser. If the file index.html is missing, you need to generate a
++process. Please refer to the README file one directory above this
++(MG_ME_V?.?.?/) for instructions on how to generate a process.
++
++
++To generate events:
++-------------------
++
++1) Specify the model parameters. The model parameters include masses
++and widths for the particles and coupling constants. They are given by
++the file param_card.dat in the Cards directory. Although it is
++possible to edit this file manually, this is not recommended since
++there are dependencies among the parameters which need to be taken
++into account. Instead the param_card.dat should be generated using one
++of the Calculators found on the MG/ME homepages (stated above).  Click
++Calculators, choose model and follow the instructions. Place the
++resulting param_card.dat in the Cards directory.
++
++2) Specify the run parameters. The run parameters includes collider
++type and energy, choice of parton distribution functions and scales.
++They are given by the file run_card.dat in the Cards directory. This
++file should be edited manually, following the syntax given in the
++example file.
++**Warning!** For several reasons, avoid running more than 100,000
++events per run. Instead perform several runs to reach the luminosity
++you need. Subsequent runs automatically update the random seed, so the
++results from different runs are statistically independent.
++
++3) Run bin/generate_events to generate the events and calculate the
++cross-section.
++
++4) Follow the generation and look at the results in the file
++HTML/crossx.html, using your web browser.
++
++5) If you want to run Pythia and/or PGS/Delphes on the events,
++download the Pythia/PGS package (and Delphes) and untar one directory
++above this (the MG_ME directory) and run make. Make sure the cards
++pythia_card.dat and pgs_card.dat are present in the Cards/ directory.
++If this is the case, Pythia and PGS will automatically be run by
++generate_events, or, for an existing run, use bin/run_pythia and
++bin/run_pgs.
++
++
++To use LHAPDF with MadGraph/MadEvent
++------------------------------------
++
++Please follow the steps below to run MadEvent with LHAPDF support:
++
++1) Download and compile LHAPDF
++
++2) Link (or copy) the following files from the LHAPDF directory to the lib/ directory:
++- libLHAPDF.a
++- libLHAPDF.so and libLHAPDF.so.0 (if you are running dynamic compilation for a grid pack)
++- PDFsets
++
++3) Set the pdlabel and define the LHA pdf number you want to use in your run_card.dat
++ 'lhapdf'    = pdlabel     ! PDF set
++ 10042       = lhaid       ! PDF number used ONLY for LHAPDF
++
++4) Run generate_events (or run.sh/...) as usual
 === added directory 'Template/NLO/Source'
 === added directory 'Template/NLO/Source/CERNLIB'
 === added file 'Template/NLO/Source/CERNLIB/abend.f'
 --- Template/NLO/Source/CERNLIB/abend.f	1970-01-01 00:00:00 +0000
 +++ Template/NLO/Source/CERNLIB/abend.f	2012-09-28 12:29:27 +0000
@@ -0,0 +1,19 @@
++*
++* $Id: abend.f,v 1.1 2009/07/30 22:46:16 madgraph Exp $
++*
++* $Log: abend.f,v $
++* Revision 1.1  2009/07/30 22:46:16  madgraph
++* JA: Implemented CKKW-style matching with Pythia pT-ordered showers
++*
++* Revision 1.1.1.1  1996/02/15 17:50:37  mclareni
++* Kernlib
++*
++*
++      SUBROUTINE ABEND
++C
++C CERN PROGLIB# Z035    ABEND           .VERSION KERNFOR  4.31  911111
++C ORIG.  8/02/88  JZ
++C
++
++      STOP  7
++      END
 === added file 'Template/NLO/Source/CERNLIB/dlsqp2.f'
 --- Template/NLO/Source/CERNLIB/dlsqp2.f	1970-01-01 00:00:00 +0000
 +++ Template/NLO/Source/CERNLIB/dlsqp2.f	2012-09-28 12:29:27 +0000
@@ -0,0 +1,69 @@
++*
++* $Id: dlsqp2.f,v 1.1 2009/07/30 22:46:16 madgraph Exp $
++*
++* $Log: dlsqp2.f,v $
++* Revision 1.1  2009/07/30 22:46:16  madgraph
++* JA: Implemented CKKW-style matching with Pythia pT-ordered showers
++*
++* Revision 1.1.1.1  1996/04/01 15:02:24  mclareni
++* Mathlib gen
++*
++*
++      SUBROUTINE DLSQP2(N,X,Y,A0,A1,A2,SD,IFAIL)
++      IMPLICIT DOUBLE PRECISION (A-H,O-Z)
++
++      DIMENSION X(*),Y(*)
++
++      PARAMETER (R0 = 0)
++
++      A0=0
++      A1=0
++      A2=0
++      SD=0
++      IF(N .LE. 2) THEN
++       IFAIL=1
++      ELSE
++       FN=N
++       XM=0
++       DO 1 K = 1,N
++       XM=XM+X(K)
++    1  CONTINUE
++       XM=XM/FN
++       SX=0
++       SXX=0
++       SXXX=0
++       SXXXX=0
++       SY=0
++       SYY=0
++       SXY=0
++       SXXY=0
++       DO 2 K = 1,N
++       XK=X(K)-XM
++       YK=Y(K)
++       XK2=XK**2
++       SX=SX+XK
++       SXX=SXX+XK2
++       SXXX=SXXX+XK2*XK
++       SXXXX=SXXXX+XK2**2
++       SY=SY+YK
++       SYY=SYY+YK**2
++       SXY=SXY+XK*YK
++       SXXY=SXXY+XK2*YK
++    2  CONTINUE
++       DET=(FN*SXXXX-SXX**2)*SXX-FN*SXXX**2
++       IF(DET .GT. 0) THEN
++        A2=(SXX*(FN*SXXY-SXX*SY)-FN*SXXX*SXY)/DET
++        A1=(SXY-SXXX*A2)/SXX
++        A0=(SY-SXX*A2)/FN
++        IFAIL=0
++       ELSE
++        IFAIL=-1
++       ENDIF
++      ENDIF
++      IF(IFAIL .EQ. 0 .AND. N .GT. 3)
++     1   SD=SQRT(MAX(R0,SYY-A0*SY-A1*SXY-A2*SXXY)/(N-3))
++      A0=A0+XM*(XM*A2-A1)
++      A1=A1-2*XM*A2
++      RETURN
++      END
++
 === added file 'Template/NLO/Source/CERNLIB/lenocc.f'
 --- Template/NLO/Source/CERNLIB/lenocc.f	1970-01-01 00:00:00 +0000
 +++ Template/NLO/Source/CERNLIB/lenocc.f	2012-09-28 12:29:27 +0000
@@ -0,0 +1,30 @@
++*
++* $Id: lenocc.f,v 1.1 2009/07/30 22:46:16 madgraph Exp $
++*
++* $Log: lenocc.f,v $
++* Revision 1.1  2009/07/30 22:46:16  madgraph
++* JA: Implemented CKKW-style matching with Pythia pT-ordered showers
++*
++* Revision 1.1.1.1  1996/02/15 17:49:49  mclareni
++* Kernlib
++*
++*
++      FUNCTION LENOCC (CHV)
++C
++C CERN PROGLIB# M507    LENOCC          .VERSION KERNFOR  4.21  890323
++C ORIG. March 85, A.Petrilli, re-write 21/02/89, JZ
++C
++C-    Find last non-blank character in CHV
++
++      CHARACTER    CHV*(*)
++
++      N = LEN(CHV)
++
++      DO 17  JJ= N,1,-1
++      IF (CHV(JJ:JJ).NE.' ') GO TO 99
++   17 CONTINUE
++      JJ = 0
++
++   99 LENOCC = JJ
++      RETURN
++      END
 === added file 'Template/NLO/Source/CERNLIB/makefile'
 --- Template/NLO/Source/CERNLIB/makefile	1970-01-01 00:00:00 +0000
 +++ Template/NLO/Source/CERNLIB/makefile	2012-09-28 12:29:27 +0000
@@ -0,0 +1,17 @@
++# Note that optimization doesn't work on all machines
++
++include ../make_opts
++
++LIBRARY	= libcernlib.a
++LIBDIR  = ../../lib/
++SOURCES = abend.o dlsqp2.o lenocc.o mtlprt.o mtlset.o radmul.o
++
++all: $(LIBDIR)$(LIBRARY)
++
++%.o : %.f makefile
++	$(F77) $(FFLAGS) -c $<
++
++$(LIBDIR)$(LIBRARY): $(SOURCES)
++	ar cru $(LIBRARY) $^
++	ranlib $(LIBRARY)
++	mv $(LIBRARY) $(LIBDIR)
 === added file 'Template/NLO/Source/CERNLIB/mtlprt.f'
 --- Template/NLO/Source/CERNLIB/mtlprt.f	1970-01-01 00:00:00 +0000
 +++ Template/NLO/Source/CERNLIB/mtlprt.f	2012-09-28 12:29:27 +0000
@@ -0,0 +1,30 @@
++*
++* $Id: mtlprt.f,v 1.1 2009/07/30 22:46:16 madgraph Exp $
++*
++* $Log: mtlprt.f,v $
++* Revision 1.1  2009/07/30 22:46:16  madgraph
++* JA: Implemented CKKW-style matching with Pythia pT-ordered showers
++*
++* Revision 1.1.1.1  1996/04/01 15:02:52  mclareni
++* Mathlib gen
++*
++*
++      SUBROUTINE MTLPRT(NAME,ERC,TEXT)
++      CHARACTER*(*) NAME,ERC,TEXT
++      LOGICAL LMF,LRF
++
++      IF(ERC(5:6).NE.'.0') THEN
++        CALL MTLMTR(ERC,MLG,LMF,LRF)
++      ELSE
++        LMF=.TRUE.
++        LRF=.FALSE.
++      ENDIF
++      IF(LMF) THEN
++        LT=LENOCC(TEXT)
++        IF(MLG .LT. 1) WRITE(  *,100) ERC(1:4),NAME,ERC,TEXT(1:LT)
++        IF(MLG .GE. 1) WRITE(MLG,100) ERC(1:4),NAME,ERC,TEXT(1:LT)
++      ENDIF
++      IF(.NOT.LRF) CALL ABEND
++      RETURN
++100   FORMAT(7X,'***** CERN ',A,1X,A,' ERROR ',A,': ',A)
++      END
 === added file 'Template/NLO/Source/CERNLIB/mtlset.f'
 --- Template/NLO/Source/CERNLIB/mtlset.f	1970-01-01 00:00:00 +0000
 +++ Template/NLO/Source/CERNLIB/mtlset.f	2012-09-28 12:29:27 +0000
@@ -0,0 +1,197 @@
++*
++* $Id: mtlset.f,v 1.1 2009/07/30 22:46:16 madgraph Exp $
++*
++* $Log: mtlset.f,v $
++* Revision 1.1  2009/07/30 22:46:16  madgraph
++* JA: Implemented CKKW-style matching with Pythia pT-ordered showers
++*
++* Revision 1.1.1.1  1996/04/01 15:02:53  mclareni
++* Mathlib gen
++*
++*
++      SUBROUTINE MTLSET(ERC,NLG,MXM,MXR)
++
++      PARAMETER (KTE = 132)
++      CHARACTER*6 ERC,CODE(KTE)
++      LOGICAL LMF,LRF
++      DIMENSION KNTM(KTE),KNTR(KTE)
++
++      DATA ILG /0/
++
++C     renumber the data statements after putting new codes in Unix with:
++C     awk -F'[()]' '{ printf"%s(%s)%s(%s)%s(%s)%s\n",$1,NR,$3,NR,$5,NR,$7 }'
++C     and modify KTE to the number of lines below
++
++      DATA CODE(1),KNTM(1),KNTR(1) / 'B100.1', 255, 255 /
++      DATA CODE(2),KNTM(2),KNTR(2) / 'B300.1', 255, 255 /
++      DATA CODE(3),KNTM(3),KNTR(3) / 'B300.2', 255, 255 /
++      DATA CODE(4),KNTM(4),KNTR(4) / 'C200.0', 255, 255 /
++      DATA CODE(5),KNTM(5),KNTR(5) / 'C200.1', 255, 255 /
++      DATA CODE(6),KNTM(6),KNTR(6) / 'C200.2', 255, 255 /
++      DATA CODE(7),KNTM(7),KNTR(7) / 'C200.3', 255, 255 /
++      DATA CODE(8),KNTM(8),KNTR(8) / 'C201.0', 255, 255 /
++      DATA CODE(9),KNTM(9),KNTR(9) / 'C202.0', 255, 255 /
++      DATA CODE(10),KNTM(10),KNTR(10) / 'C202.1', 255, 255 /
++      DATA CODE(11),KNTM(11),KNTR(11) / 'C202.2', 255, 255 /
++      DATA CODE(12),KNTM(12),KNTR(12) / 'C205.1', 255, 255 /
++      DATA CODE(13),KNTM(13),KNTR(13) / 'C205.2', 255, 255 /
++      DATA CODE(14),KNTM(14),KNTR(14) / 'C207.0', 255, 255 /
++      DATA CODE(15),KNTM(15),KNTR(15) / 'C208.0', 255, 255 /
++      DATA CODE(16),KNTM(16),KNTR(16) / 'C209.0', 255, 255 /
++      DATA CODE(17),KNTM(17),KNTR(17) / 'C209.1', 255, 255 /
++      DATA CODE(18),KNTM(18),KNTR(18) / 'C209.2', 255, 255 /
++      DATA CODE(19),KNTM(19),KNTR(19) / 'C209.3', 255, 255 /
++      DATA CODE(20),KNTM(20),KNTR(20) / 'C210.1', 255, 255 /
++      DATA CODE(21),KNTM(21),KNTR(21) / 'C302.1', 255, 255 /
++      DATA CODE(22),KNTM(22),KNTR(22) / 'C303.1', 255, 255 /
++      DATA CODE(23),KNTM(23),KNTR(23) / 'C304.1', 255, 255 /
++      DATA CODE(24),KNTM(24),KNTR(24) / 'C305.1', 255, 255 /
++      DATA CODE(25),KNTM(25),KNTR(25) / 'C306.1', 255, 255 /
++      DATA CODE(26),KNTM(26),KNTR(26) / 'C307.1', 255, 255 /
++      DATA CODE(27),KNTM(27),KNTR(27) / 'C312.1', 255, 255 /
++      DATA CODE(28),KNTM(28),KNTR(28) / 'C313.1', 255, 255 /
++      DATA CODE(29),KNTM(29),KNTR(29) / 'C315.1', 255, 255 /
++      DATA CODE(30),KNTM(30),KNTR(30) / 'C316.1', 255, 255 /
++      DATA CODE(31),KNTM(31),KNTR(31) / 'C316.2', 255, 255 /
++      DATA CODE(32),KNTM(32),KNTR(32) / 'C320.1', 255, 255 /
++      DATA CODE(33),KNTM(33),KNTR(33) / 'C321.1', 255, 255 /
++      DATA CODE(34),KNTM(34),KNTR(34) / 'C323.1', 255, 255 /
++      DATA CODE(35),KNTM(35),KNTR(35) / 'C327.1', 255, 255 /
++      DATA CODE(36),KNTM(36),KNTR(36) / 'C328.1', 255, 255 /
++      DATA CODE(37),KNTM(37),KNTR(37) / 'C328.2', 255, 255 /
++      DATA CODE(38),KNTM(38),KNTR(38) / 'C328.3', 255, 255 /
++      DATA CODE(39),KNTM(39),KNTR(39) / 'C330.1', 255, 255 /
++      DATA CODE(40),KNTM(40),KNTR(40) / 'C330.2', 255, 255 /
++      DATA CODE(41),KNTM(41),KNTR(41) / 'C330.3', 255, 255 /
++      DATA CODE(42),KNTM(42),KNTR(42) / 'C331.1', 255, 255 /
++      DATA CODE(43),KNTM(43),KNTR(43) / 'C331.2', 255, 255 /
++      DATA CODE(44),KNTM(44),KNTR(44) / 'C334.1', 255, 255 /
++      DATA CODE(45),KNTM(45),KNTR(45) / 'C334.2', 255, 255 /
++      DATA CODE(46),KNTM(46),KNTR(46) / 'C334.3', 255, 255 /
++      DATA CODE(47),KNTM(47),KNTR(47) / 'C334.4', 255, 255 /
++      DATA CODE(48),KNTM(48),KNTR(48) / 'C334.5', 255, 255 /
++      DATA CODE(49),KNTM(49),KNTR(49) / 'C334.6', 255, 255 /
++      DATA CODE(50),KNTM(50),KNTR(50) / 'C336.1', 255, 255 /
++      DATA CODE(51),KNTM(51),KNTR(51) / 'C337.1', 255, 255 /
++      DATA CODE(52),KNTM(52),KNTR(52) / 'C338.1', 255, 255 /
++      DATA CODE(53),KNTM(53),KNTR(53) / 'C340.1', 255, 255 /
++      DATA CODE(54),KNTM(54),KNTR(54) / 'C343.1', 255, 255 /
++      DATA CODE(55),KNTM(55),KNTR(55) / 'C343.2', 255, 255 /
++      DATA CODE(56),KNTM(56),KNTR(56) / 'C343.3', 255, 255 /
++      DATA CODE(57),KNTM(57),KNTR(57) / 'C343.4', 255, 255 /
++      DATA CODE(58),KNTM(58),KNTR(58) / 'C344.1', 255, 255 /
++      DATA CODE(59),KNTM(59),KNTR(59) / 'C344.2', 255, 255 /
++      DATA CODE(60),KNTM(60),KNTR(60) / 'C344.3', 255, 255 /
++      DATA CODE(61),KNTM(61),KNTR(61) / 'C344.4', 255, 255 /
++      DATA CODE(62),KNTM(62),KNTR(62) / 'C345.1', 255, 255 /
++      DATA CODE(63),KNTM(63),KNTR(63) / 'C346.1', 255, 255 /
++      DATA CODE(64),KNTM(64),KNTR(64) / 'C346.2', 255, 255 /
++      DATA CODE(65),KNTM(65),KNTR(65) / 'C346.3', 255, 255 /
++      DATA CODE(66),KNTM(66),KNTR(66) / 'C347.1', 255, 255 /
++      DATA CODE(67),KNTM(67),KNTR(67) / 'C347.2', 255, 255 /
++      DATA CODE(68),KNTM(68),KNTR(68) / 'C347.3', 255, 255 /
++      DATA CODE(69),KNTM(69),KNTR(69) / 'C347.4', 255, 255 /
++      DATA CODE(70),KNTM(70),KNTR(70) / 'C347.5', 255, 255 /
++      DATA CODE(71),KNTM(71),KNTR(71) / 'C347.6', 255, 255 /
++      DATA CODE(72),KNTM(72),KNTR(72) / 'C348.1', 255, 255 /
++      DATA CODE(73),KNTM(73),KNTR(73) / 'C349.1', 255, 255 /
++      DATA CODE(74),KNTM(74),KNTR(74) / 'C349.2', 255, 255 /
++      DATA CODE(75),KNTM(75),KNTR(75) / 'C349.3', 255, 255 /
++      DATA CODE(76),KNTM(76),KNTR(76) / 'D101.1', 255, 255 /
++      DATA CODE(77),KNTM(77),KNTR(77) / 'D103.1', 255, 255 /
++      DATA CODE(78),KNTM(78),KNTR(78) / 'D104.1', 255, 255 /
++      DATA CODE(79),KNTM(79),KNTR(79) / 'D104.2', 255, 255 /
++      DATA CODE(80),KNTM(80),KNTR(80) / 'D105.1', 255, 255 /
++      DATA CODE(81),KNTM(81),KNTR(81) / 'D105.2', 255, 255 /
++      DATA CODE(82),KNTM(82),KNTR(82) / 'D107.1', 255, 255 /
++      DATA CODE(83),KNTM(83),KNTR(83) / 'D110.0', 255, 255 /
++      DATA CODE(84),KNTM(84),KNTR(84) / 'D110.1', 255, 255 /
++      DATA CODE(85),KNTM(85),KNTR(85) / 'D110.2', 255, 255 /
++      DATA CODE(86),KNTM(86),KNTR(86) / 'D110.3', 255, 255 /
++      DATA CODE(87),KNTM(87),KNTR(87) / 'D110.4', 255, 255 /
++      DATA CODE(88),KNTM(88),KNTR(88) / 'D110.5', 255, 255 /
++      DATA CODE(89),KNTM(89),KNTR(89) / 'D110.6', 255, 255 /
++      DATA CODE(90),KNTM(90),KNTR(90) / 'D113.1', 255, 255 /
++      DATA CODE(91),KNTM(91),KNTR(91) / 'D201.1', 255, 255 /
++      DATA CODE(92),KNTM(92),KNTR(92) / 'D202.1', 255, 255 /
++      DATA CODE(93),KNTM(93),KNTR(93) / 'D401.1', 255, 255 /
++      DATA CODE(94),KNTM(94),KNTR(94) / 'D601.1', 255, 255 /
++      DATA CODE(95),KNTM(95),KNTR(95) / 'E210.1', 255, 255 /
++      DATA CODE(96),KNTM(96),KNTR(96) / 'E210.2', 255, 255 /
++      DATA CODE(97),KNTM(97),KNTR(97) / 'E210.3', 255, 255 /
++      DATA CODE(98),KNTM(98),KNTR(98) / 'E210.4', 255, 255 /
++      DATA CODE(99),KNTM(99),KNTR(99) / 'E210.5', 255, 255 /
++      DATA CODE(100),KNTM(100),KNTR(100) / 'E210.6', 255, 255 /
++      DATA CODE(101),KNTM(101),KNTR(101) / 'E210.7', 255, 255 /
++      DATA CODE(102),KNTM(102),KNTR(102) / 'E211.0', 255, 255 /
++      DATA CODE(103),KNTM(103),KNTR(103) / 'E211.1', 255, 255 /
++      DATA CODE(104),KNTM(104),KNTR(104) / 'E211.2', 255, 255 /
++      DATA CODE(105),KNTM(105),KNTR(105) / 'E211.3', 255, 255 /
++      DATA CODE(106),KNTM(106),KNTR(106) / 'E211.4', 255, 255 /
++      DATA CODE(107),KNTM(107),KNTR(107) / 'E406.0', 255, 255 /
++      DATA CODE(108),KNTM(108),KNTR(108) / 'E406.1', 255, 255 /
++      DATA CODE(109),KNTM(109),KNTR(109) / 'E407.0', 255, 255 /
++      DATA CODE(110),KNTM(110),KNTR(110) / 'E408.0', 255, 255 /
++      DATA CODE(111),KNTM(111),KNTR(111) / 'E408.1', 255, 255 /
++      DATA CODE(112),KNTM(112),KNTR(112) / 'F500.0', 255, 255 /
++      DATA CODE(113),KNTM(113),KNTR(113) / 'F500.1', 255, 255 /
++      DATA CODE(114),KNTM(114),KNTR(114) / 'F500.2', 255, 255 /
++      DATA CODE(115),KNTM(115),KNTR(115) / 'F500.3', 255, 255 /
++      DATA CODE(116),KNTM(116),KNTR(116) / 'G100.1', 255, 255 /
++      DATA CODE(117),KNTM(117),KNTR(117) / 'G100.2', 255, 255 /
++      DATA CODE(118),KNTM(118),KNTR(118) / 'G101.1', 255, 255 /
++      DATA CODE(119),KNTM(119),KNTR(119) / 'G101.2', 255, 255 /
++      DATA CODE(120),KNTM(120),KNTR(120) / 'G105.1', 255, 255 /
++      DATA CODE(121),KNTM(121),KNTR(121) / 'G106.1', 255, 255 /
++      DATA CODE(122),KNTM(122),KNTR(122) / 'G106.2', 255, 255 /
++      DATA CODE(123),KNTM(123),KNTR(123) / 'G116.1', 255, 255 /
++      DATA CODE(124),KNTM(124),KNTR(124) / 'G116.2', 255, 255 /
++      DATA CODE(125),KNTM(125),KNTR(125) / 'H101.0', 255, 255 /
++      DATA CODE(126),KNTM(126),KNTR(126) / 'H101.1', 255, 255 /
++      DATA CODE(127),KNTM(127),KNTR(127) / 'H101.2', 255, 255 /
++      DATA CODE(128),KNTM(128),KNTR(128) / 'H301.1', 255, 255 /
++      DATA CODE(129),KNTM(129),KNTR(129) / 'U501.1', 255, 255 /
++      DATA CODE(130),KNTM(130),KNTR(130) / 'V202.1', 255, 255 /
++      DATA CODE(131),KNTM(131),KNTR(131) / 'V202.2', 255, 255 /
++      DATA CODE(132),KNTM(132),KNTR(132) / 'V202.3', 255, 255 /
++
++      ILG=NLG
++      L=0
++      IF(ERC .NE. ' ') THEN
++       DO 10 L = 1,6
++       IF(ERC(1:L) .EQ. ERC) GOTO 12
++   10  CONTINUE
++   12  CONTINUE
++      ENDIF
++      DO 14 I = 1,KTE
++      IF(L .EQ. 0 .OR. CODE(I)(1:L) .EQ. ERC(1:L)) THEN
++       IF(MXM .GE. 0) KNTM(I)=MXM
++       IF(MXR .GE. 0) KNTR(I)=MXR
++      ENDIF
++   14 CONTINUE
++      RETURN
++
++      ENTRY MTLMTR(ERC,MLG,LMF,LRF)
++
++      MLG=ILG
++      DO 20 I = 1,KTE
++      IF(ERC .EQ. CODE(I))  GOTO 21
++   20 CONTINUE
++      WRITE(*,100) ERC
++      CALL ABEND
++      RETURN
++
++   21 LMF=KNTM(I) .GE. 1
++      LRF=KNTR(I) .GE. 1
++      IF(LMF .AND. KNTM(I) .LT. 255)  KNTM(I)=KNTM(I)-1
++      IF(LRF .AND. KNTR(I) .LT. 255)  KNTR(I)=KNTR(I)-1
++      IF(.NOT.LRF) THEN
++       IF(ILG .LT. 1) WRITE(  *,101) CODE(I)
++       IF(ILG .GE. 1) WRITE(ILG,101) CODE(I)
++      ENDIF
++      RETURN
++  100 FORMAT(7X,'***** CERN N002 MTLSET ... ERROR N002: ',
++     1'ERROR CODE ',A6,' NOT RECOGNIZED BY ERROR MONITOR. RUN ABORTED.')
++  101 FORMAT(7X,'***** CERN N002 MTLSET ... ERROR NOO2.1: ',
++     1'RUN TERMINATED BY LIBRARY ERROR CONDITION ',A6)
++      END
 === added file 'Template/NLO/Source/CERNLIB/radmul.f'
 --- Template/NLO/Source/CERNLIB/radmul.f	1970-01-01 00:00:00 +0000
 +++ Template/NLO/Source/CERNLIB/radmul.f	2012-09-28 12:29:27 +0000
@@ -0,0 +1,207 @@
++*
++* $Id
++*
++* $Log
++*
++      SUBROUTINE RADMUL
++     1 (F,N,A,B,MINPTS,MAXPTS,EPS,WK,IWK,RESULT,RELERR,NFNEVL,IFAIL)
++      CHARACTER NAME*(*)
++      PARAMETER (NAME = 'RADMUL')
++      CALL MTLPRT(NAME,'D120',
++     +'not available on this machine - see documentation')
++      RETURN
++      END
++
++      SUBROUTINE DADMUL
++     1 (F,N,A,B,MINPTS,MAXPTS,EPS,WK,IWK,RESULT,RELERR,NFNEVL,IFAIL)
++      IMPLICIT DOUBLE PRECISION (A-H,O-Z)
++
++      LOGICAL LDV
++
++      DIMENSION A(*),B(*),WK(*)
++      DIMENSION CTR(15),WTH(15),WTHL(15),Z(15)
++      DIMENSION W(2:15,5),WP(2:15,3)
++
++      PARAMETER (R1 = 1, HF = R1/2)
++
++      PARAMETER (XL2 =  0.35856 85828 00318 073D0)
++      PARAMETER (XL4 =  0.94868 32980 50513 796D0)
++      PARAMETER (XL5 =  0.68824 72016 11685 289D0)
++
++      PARAMETER (W2 =  980*R1/6561, W4 = 200*R1/19683)
++      PARAMETER (WP2 =  245*R1/486, WP4 = 25*R1/729)
++
++      DATA (W(N,1),W(N,3),N=2,15)
++     1/-0.193872885230909911D+00,  0.518213686937966768D-01,
++     2 -0.555606360818980835D+00,  0.314992633236803330D-01,
++     3 -0.876695625666819078D+00,  0.111771579535639891D-01,
++     4 -0.115714067977442459D+01, -0.914494741655235473D-02,
++     5 -0.139694152314179743D+01, -0.294670527866686986D-01,
++     6 -0.159609815576893754D+01, -0.497891581567850424D-01,
++     7 -0.175461057765584494D+01, -0.701112635269013768D-01,
++     8 -0.187247878880251983D+01, -0.904333688970177241D-01,
++     9 -0.194970278920896201D+01, -0.110755474267134071D+00,
++     A -0.198628257887517146D+01, -0.131077579637250419D+00,
++     B -0.198221815780114818D+01, -0.151399685007366752D+00,
++     C -0.193750952598689219D+01, -0.171721790377483099D+00,
++     D -0.185215668343240347D+01, -0.192043895747599447D+00,
++     E -0.172615963013768225D+01, -0.212366001117715794D+00/
++
++      DATA (W(N,5),W(N+1,5),N=2,14,2)
++     1/ 0.871183254585174982D-01,  0.435591627292587508D-01,
++     2  0.217795813646293754D-01,  0.108897906823146873D-01,
++     3  0.544489534115734364D-02,  0.272244767057867193D-02,
++     4  0.136122383528933596D-02,  0.680611917644667955D-03,
++     5  0.340305958822333977D-03,  0.170152979411166995D-03,
++     6  0.850764897055834977D-04,  0.425382448527917472D-04,
++     7  0.212691224263958736D-04,  0.106345612131979372D-04/
++
++      DATA (WP(N,1),WP(N,3),N=2,15)
++     1/-0.133196159122085045D+01,  0.445816186556927292D-01,
++     2 -0.229218106995884763D+01, -0.240054869684499309D-01,
++     3 -0.311522633744855959D+01, -0.925925925925925875D-01,
++     4 -0.380109739368998611D+01, -0.161179698216735251D+00,
++     5 -0.434979423868312742D+01, -0.229766803840877915D+00,
++     6 -0.476131687242798352D+01, -0.298353909465020564D+00,
++     7 -0.503566529492455417D+01, -0.366941015089163228D+00,
++     8 -0.517283950617283939D+01, -0.435528120713305891D+00,
++     9 -0.517283950617283939D+01, -0.504115226337448555D+00,
++     A -0.503566529492455417D+01, -0.572702331961591218D+00,
++     B -0.476131687242798352D+01, -0.641289437585733882D+00,
++     C -0.434979423868312742D+01, -0.709876543209876532D+00,
++     D -0.380109739368998611D+01, -0.778463648834019195D+00,
++     E -0.311522633744855959D+01, -0.847050754458161859D+00/
++
++      RESULT=0
++      ABSERR=0
++      IFAIL=3
++      IF(N .LT. 2 .OR. N .GT. 15) RETURN
++      IF(MINPTS .GT. MAXPTS) RETURN
++
++      IFNCLS=0
++      LDV=.FALSE.
++      TWONDM=2**N
++      IRGNST=2*N+3
++      IRLCLS=2**N+2*N*(N+1)+1
++      ISBRGN=IRGNST
++      ISBRGS=IRGNST
++      IF(MAXPTS .LT. IRLCLS) RETURN
++      DO 10 J = 1,N
++      CTR(J)=(B(J)+A(J))*HF
++   10 WTH(J)=(B(J)-A(J))*HF
++
++   20 RGNVOL=TWONDM
++      DO 30 J = 1,N
++      RGNVOL=RGNVOL*WTH(J)
++   30 Z(J)=CTR(J)
++      SUM1=F(N,Z)
++
++      DIFMAX=0
++      SUM2=0
++      SUM3=0
++      DO 40 J = 1,N
++      Z(J)=CTR(J)-XL2*WTH(J)
++      F2=F(N,Z)
++      Z(J)=CTR(J)+XL2*WTH(J)
++      F2=F2+F(N,Z)
++      WTHL(J)=XL4*WTH(J)
++      Z(J)=CTR(J)-WTHL(J)
++      F3=F(N,Z)
++      Z(J)=CTR(J)+WTHL(J)
++      F3=F3+F(N,Z)
++      SUM2=SUM2+F2
++      SUM3=SUM3+F3
++      DIF=ABS(7*F2-F3-12*SUM1)
++      DIFMAX=MAX(DIF,DIFMAX)
++      IF(DIFMAX .EQ. DIF) IDVAXN=J
++   40 Z(J)=CTR(J)
++
++      SUM4=0
++      DO 70 J = 2,N
++      J1=J-1
++      DO 60 K = J,N
++      DO 50 L = 1,2
++      WTHL(J1)=-WTHL(J1)
++      Z(J1)=CTR(J1)+WTHL(J1)
++      DO 50 M = 1,2
++      WTHL(K)=-WTHL(K)
++      Z(K)=CTR(K)+WTHL(K)
++   50 SUM4=SUM4+F(N,Z)
++   60 Z(K)=CTR(K)
++   70 Z(J1)=CTR(J1)
++
++      SUM5=0
++      DO 80 J = 1,N
++      WTHL(J)=-XL5*WTH(J)
++   80 Z(J)=CTR(J)+WTHL(J)
++   90 SUM5=SUM5+F(N,Z)
++      DO 100 J = 1,N
++      WTHL(J)=-WTHL(J)
++      Z(J)=CTR(J)+WTHL(J)
++      IF(WTHL(J) .GT. 0) GO TO 90
++  100 CONTINUE
++
++      RGNCMP=RGNVOL*(WP(N,1)*SUM1+WP2*SUM2+WP(N,3)*SUM3+WP4*SUM4)
++      RGNVAL=W(N,1)*SUM1+W2*SUM2+W(N,3)*SUM3+W4*SUM4+W(N,5)*SUM5
++      RGNVAL=RGNVOL*RGNVAL
++      RGNERR=ABS(RGNVAL-RGNCMP)
++      RESULT=RESULT+RGNVAL
++      ABSERR=ABSERR+RGNERR
++      IFNCLS=IFNCLS+IRLCLS
++
++      IF(LDV) THEN
++  110  ISBTMP=2*ISBRGN
++       IF(ISBTMP .GT. ISBRGS) GO TO 160
++       IF(ISBTMP .LT. ISBRGS) THEN
++        ISBTPP=ISBTMP+IRGNST
++        IF(WK(ISBTMP) .LT. WK(ISBTPP)) ISBTMP=ISBTPP
++       ENDIF
++       IF(RGNERR .GE. WK(ISBTMP)) GO TO 160
++       DO 130 K = 0,IRGNST-1
++  130  WK(ISBRGN-K)=WK(ISBTMP-K)
++       ISBRGN=ISBTMP
++       GO TO 110
++      ENDIF
++  140 ISBTMP=(ISBRGN/(2*IRGNST))*IRGNST
++      IF(ISBTMP .GE. IRGNST .AND. RGNERR .GT. WK(ISBTMP)) THEN
++       DO 150 K = 0,IRGNST-1
++  150  WK(ISBRGN-K)=WK(ISBTMP-K)
++       ISBRGN=ISBTMP
++       GO TO 140
++      ENDIF
++
++  160 WK(ISBRGN)=RGNERR
++      WK(ISBRGN-1)=RGNVAL
++      WK(ISBRGN-2)=IDVAXN
++      DO 170 J = 1,N
++      ISBTMP=ISBRGN-2*J-2
++      WK(ISBTMP+1)=CTR(J)
++  170 WK(ISBTMP)=WTH(J)
++      IF(LDV) THEN
++       LDV=.FALSE.
++       CTR(IDVAX0)=CTR(IDVAX0)+2*WTH(IDVAX0)
++       ISBRGS=ISBRGS+IRGNST
++       ISBRGN=ISBRGS
++       GO TO 20
++      ENDIF
++      RELERR=ABSERR/ABS(RESULT)
++      IF(ISBRGS+IRGNST .GT. IWK) IFAIL=2
++      IF(IFNCLS+2*IRLCLS .GT. MAXPTS) IFAIL=1
++      IF(RELERR .LT. EPS .AND. IFNCLS .GE. MINPTS) IFAIL=0
++      IF(IFAIL .EQ. 3) THEN
++       LDV=.TRUE.
++       ISBRGN=IRGNST
++       ABSERR=ABSERR-WK(ISBRGN)
++       RESULT=RESULT-WK(ISBRGN-1)
++       IDVAX0=WK(ISBRGN-2)
++       DO 190 J = 1,N
++       ISBTMP=ISBRGN-2*J-2
++       CTR(J)=WK(ISBTMP+1)
++  190  WTH(J)=WK(ISBTMP)
++       WTH(IDVAX0)=HF*WTH(IDVAX0)
++       CTR(IDVAX0)=CTR(IDVAX0)-WTH(IDVAX0)
++       GO TO 20
++      ENDIF
++      NFNEVL=IFNCLS
++      RETURN
++      END
 === added directory 'Template/NLO/Source/DHELAS'
 === added file 'Template/NLO/Source/DHELAS/.keepthisdir'
 === added directory 'Template/NLO/Source/MODEL'
 === added file 'Template/NLO/Source/MODEL/.keepme'
 === added directory 'Template/NLO/Source/PDF'
 === added file 'Template/NLO/Source/PDF/Ctq4Fn.f'
 --- Template/NLO/Source/PDF/Ctq4Fn.f	1970-01-01 00:00:00 +0000
 +++ Template/NLO/Source/PDF/Ctq4Fn.f	2012-09-28 12:29:27 +0000
@@ -0,0 +1,122 @@
++C*****Butchered by RKE to remove polint and readtbl which are common to
++C*****Ctq4Fn and Ctq5Pdf
++
++C============================================================================
++C                CTEQ Parton Distribution Functions: Version 4
++C                          June 21, 1996
++C
++C   By: H.L. Lai, J. Huston, S. Kuhlmann, F. Olness, J. Owens, D. Soper
++C       W.K. Tung, H. Weerts
++C   Ref: MSUHEP-60426, CTEQ-604, e-Print Archive: hep-ph/9606399
++C
++C   This package contains 9 sets of CTEQ4 PDF's. Details are:
++C ---------------------------------------------------------------------------
++C   Iset   PDF      Description             Alpha_s(Mz)  Q0(GeV)  Table_File
++C ---------------------------------------------------------------------------
++C   1      CTEQ4M   Standard MSbar scheme   0.116        1.6      cteq4m.tbl
++C   2      CTEQ4D   Standard DIS scheme     0.116        1.6      cteq4d.tbl
++C   3      CTEQ4L   Leading Order           0.116        1.6      cteq4l.tbl
++C   4      CTEQ4A1  Alpha_s series          0.110        1.6      cteq4a1.tbl
++C   5      CTEQ4A2  Alpha_s series          0.113        1.6      cteq4a2.tbl
++C   6      CTEQ4A3  same as CTEQ4M          0.116        1.6      cteq4m.tbl
++C   7      CTEQ4A4  Alpha_s series          0.119        1.6      cteq4a4.tbl
++C   8      CTEQ4A5  Alpha_s series          0.122        1.6      cteq4a5.tbl
++C   9      CTEQ4HJ  High Jet                0.116        1.6      cteq4hj.tbl
++C   10     CTEQ4LQ  Low Q0                  0.114        0.7      cteq4lq.tbl
++C ---------------------------------------------------------------------------
++C
++C   The available applied range is 10^-5 < x < 1 and 1.6 < Q < 10,000 (GeV)
++C   except CTEQ4LQ for which Q starts at a lower value of 0.7 GeV.
++C   The Table_Files are assumed to be in the working directory.
++C
++C   The function Ctq4Fn (Iset, Iparton, X, Q)
++C   returns the parton distribution inside the proton for parton [Iparton]
++C   at [X] Bjorken_X and scale [Q] (GeV) in PDF set [Iset].
++C   Iparton  is the parton label (5, 4, 3, 2, 1, 0, -1, ......, -5)
++C                            for (b, c, s, d, u, g, u_bar, ..., b_bar)
++C
++C   For detailed information on the parameters used, e.q. quark masses,
++C   QCD Lambda, ... etc.,  see info lines at the beginning of the
++C   Table_Files.
++
++C   These programs, as provided, are in double precision.  By removing the
++C   "Implicit Double Precision" lines, they can also be run in single
++C   precision.
++C
++C   If you have detailed questions concerning these CTEQ4 distributions,
++C   or if you find problems/bugs using this package, direct inquires to
++C   Hung-Liang Lai(Lai_H@pa.msu.edu) or Wu-Ki Tung(Tung@pa.msu.edu).
++C
++C===========================================================================
++
++      Function Ctq4Fn (Iset, Iparton, X, Q)
++      Implicit Double Precision (A-H,O-Z)
++      Character Flnm(10)*11,TableFile*40
++
++      Common
++     > / CtqPar2 / Nx, Nt, NfMx
++     > / QCDtable /  Alambda, Nfl, Iorder
++      Data (Flnm(I), I=1,10)
++     > / 'cteq4m.tbl ', 'cteq4d.tbl ', 'cteq4l.tbl '
++     > , 'cteq4a1.tbl', 'cteq4a2.tbl', 'cteq4m.tbl ', 'cteq4a4.tbl'
++     > , 'cteq4a5.tbl', 'cteq4hj.tbl', 'cteq4lq.tbl' /
++      Data Isetold, Isetmin, Isetmax / -987, 1, 10 /
++      save
++
++C             If data file not initialized, do so.
++      If(Iset.ne.Isetold) then
++         If (Iset.lt.Isetmin .or. Iset.gt.Isetmax) Then
++	    Print *, 'Invalid Iset number in Ctq4Fn :', Iset
++	    Stop
++	 Endif
++	 IU= NextUt()
++c         Open(IU, File='Pdfdata/'//Flnm(Iset), Status='OLD', Err=100)
++	 TableFile=Flnm(Iset)
++            call OpenData(TableFile)
++c	write (*,*) TableFile
++c	write(*,*) 'iu',iu
++         Call ReadTbl (IU)
++         Close (IU)
++	 Isetold=Iset
++      Endif
++
++      If (X .lt. 0D0 .or. X .gt. 1D0) Then
++	Print *, 'X out of range in Ctq4Fn: ', X
++	Stop
++      Endif
++      If (Q .lt. Alambda) Then
++	Print *, 'Q out of range in Ctq4Fn: ', Q
++	Stop
++      Endif
++      If (Iparton .lt. -NfMx .or. Iparton .gt. NfMx) Then
++	Print *, 'Iparton out of range in Ctq4Fn: ', Iparton
++	Stop
++      Endif
++
++      Ctq4Fn = PartonX (Iparton, X, Q)
++      if(Ctq4Fn.lt.0.D0)  Ctq4Fn = 0.D0
++
++      Return
++
++ 100  Print *, ' Data file ', Flnm(Iset), ' cannot be opened '
++     >//'in Ctq4Fn!!'
++      Stop
++C                             ********************
++      End
++
++      Function NextUt()
++C                                 Returns an unallocated FORTRAN i/o unit.
++      Logical EX
++C
++      Do 10 N = 10, 300
++         INQUIRE (UNIT=N, OPENED=EX)
++         If (.NOT. EX) then
++            NextUt = N
++            Return
++         Endif
++ 10   Continue
++      Stop ' There is no available I/O unit. '
++C               *************************
++      End
++C
++
 === added file 'Template/NLO/Source/PDF/Ctq5Par.f'
 --- Template/NLO/Source/PDF/Ctq5Par.f	1970-01-01 00:00:00 +0000
 +++ Template/NLO/Source/PDF/Ctq5Par.f	2012-09-28 12:29:27 +0000
@@ -0,0 +1,711 @@
++C   CTEQ5M1 and CTEQ5L Parton Distribution Functions in Parametrized Form
++C
++C               September 15, 1999
++C
++C   Ref: "GLOBAL QCD ANALYSIS OF PARTON STRUCTURE OF THE NUCLEON:
++C         CTEQ5 PPARTON DISTRIBUTIONS"
++C   hep-ph/9903282
++C
++C   The CTEQ5M1 set given here is an updated version of the original CTEQ5M
++C     set posted, in the table version, on the Web page of CTEQ.
++C     The differences between CTEQ5M and CTEQ5M1 are insignificant for almost
++C     all applications.
++C   The improvement is in the QCD evolution which is now more accurate, and
++C   which agrees completely with the benchmark work of the HERA 96/97 Workshop.
++
++C   The differences between the parametrized and the corresponding table ver-
++C sions (on which it is based) are of similar order as between the two version.
++C
++C!! Because accurate parametrizations over a wide range of (x,Q) is hard to
++C   obtain, only the most widely used sets CTEQ5M and CTEQ5L are available
++C   in parametrized form for now.
++
++C   These parametrizations were obtained by Jon Pumplin.
++C
++C                    ******************************
++C  Iset   PDF        Description                 Alpha_s(Mz)  Lam4  Lam5
++C ---------------------------------------------------------------------------
++C   1    CTEQ5M1  Standard NLO MSbar scheme         0.118     326   226
++C   3    CTEQ5L   Leading Order                     0.127     192   146
++C ---------------------------------------------------------------------------
++C   Note the Qcd-lambda values given for CTEQ5L is for the leading order
++C     form of Alpha_s!!  Alpha_s(Mz) gives the absolute calibration.
++
++C  The two Iset value are adopted to agree with the standard table versions.
++
++C   The following user-callable routines are provided:
++C
++C     FUNCTION Ctq5Pd (Iset, Iprtn, X, Q, Irt)
++C         returns the PROBABILITY density for a GIVEN flavor;
++C
++C     FUNCTION Ctq5df (Iset, Iprtn, X, Q, Irt)
++C         returns the MOMENTUM density of a GIVEN valence or sea distribution.
++C
++C     SUBROUTINE Ctq5Pds(Iset, Pdf, X, Q, Irt)
++C         returns an array of MOMENTUM densities for ALL flavors;
++C****************************************************************************
++C     Added by Tim Stelzer
++c               subroutine pftopdg(x,Q,pdf)
++c               subroutine pdfset(parm,val)
++c
++c
++C
++C   The arguments of these routines are as follows:
++C
++C   Iset is the set number:  1 for CTEQ5M1 or 3 for CTEQ5L
++C
++C   Iprtn  is the parton label (6, 5, 4, 3, 2, 1, 0, -1, ......, -6)
++C                          for (t, b, c, s, d, u, g, u_bar, ..., t_bar)
++C  *** WARNING: We use the parton label 2 as D-quark and 1 as U-quark,
++C               which might be different from your labels.
++C
++C   X, Q are the usual x, Q;
++C
++C   Irt is an error code: 0 if there was no error; 1 or more if (x,q) was
++C   outside the range of validity of the parametrization.
++C
++C  Range of validity:
++C
++C     The range of (x, Q) covered by this parametrization of the QCD evolved
++C     parton distributions is 1E-6 < x < 1 ; 1.1 GeV < Q < 10 TeV.  Of course,
++C     the PDF's are constrained by data only in a subset of that region; and
++C     the assumed DGLAP evolution is unlikely to be valid for all of it either.
++C
++C     The range of (x, Q) used in the CTEQ5 round of global analysis is
++C     approximately 0.01 < x < 0.75 ; and 4 GeV^2 < Q^2 < 400 GeV^2 for
++C     fixed target experiments; 0.0001 < x < 0.3 from HERA data; and
++C     Q^2 up to 40,000 GeV^2 from Tevatron inclusive Jet data.
++C
++C   DOUBLE PRECISION is used throughout in these routines, but conversion to
++C   SINGLE PRECISION is possible by removing the Implicit Double Precision statements.
++C
++C **************************************************************************
++
++
++C ********************************************************
++      FUNCTION CTQ5PD(ISET, IPARTON, X, Q, IRT)
++C ********************************************************
++      IMPLICIT DOUBLE PRECISION (A-H, O-Z)
++
++c if called at a point (x,q) that is outside the region that was
++c actually parametrized, return a value of 0, and set the error code IRT=1.
++c The user can remove the following IF statement to receive instead an
++c extrapolated value, which may be wildly unphysical.
++      if((x .lt. 1.e-6). or. (x .gt. 1.)
++     &	 .or. (q .lt. .99) .or. (q .gt. 10000.)) then
++         ctq5pd = 0.d0
++         irt = 1
++         return
++      endif
++
++      irt = 0
++      if(iset .eq. 3) then
++         ctq5pd = ctq5L(iparton,x,q)
++      elseif(iset .eq. 1) then
++         ctq5pd = ctq5Mi(iparton,x,q)
++      else
++         print *,'iset=',iset,' has not been parametrized.'
++	   print '(/A)', 'Use the interpolation-table version instead.'
++         stop
++      endif
++
++      return
++      end
++
++C ********************************************************
++      FUNCTION CTQ5DF(ISET, IFL, X, Q, IRT)
++C ********************************************************
++      IMPLICIT DOUBLE PRECISION (A-H, O-Z)
++
++      CTQ5DF = X * CTQ5PD(ISET, IPARTON, X, Q, IRT)
++
++      RETURN
++      END
++
++C ********************************************************
++      SUBROUTINE CTQ5PDS(ISET, PDF, X, Q, IRT)
++C ********************************************************
++      IMPLICIT DOUBLE PRECISION (A-H, O-Z)
++      DIMENSION PDF (-6:6)
++
++      IRT = 0
++
++      DO IFL= -6,2
++         PDF(IFL) = CTQ5PD(ISET,IFL,X,Q,IRT1)
++         IRT = IRT + IRT1
++
++         IF (IFL .LE. -3) THEN
++            PDF(-IFL) = PDF(IFL)
++         ENDIF
++
++      ENDDO
++
++      RETURN
++      END
++
++c --------------------------------------------------------------------------
++	double precision function ctq5MI(ifl,x,q)
++c Parametrization of cteq5MI parton distribution functions (J. Pumplin 9/99).
++c ifl: 1=u,2=d,3=s,4=c,5=b;0=gluon;-1=ubar,-2=dbar,-3=sbar,-4=cbar,-5=bbar.
++c --------------------------------------------------------------------------
++	implicit double precision (a-h,o-z)
++	integer ifl
++
++	ii = ifl
++	if(ii .gt. 2) then
++	   ii = -ii
++	endif
++
++	if(ii .eq. -1) then
++	   sum = faux5MI(-1,x,q)
++	   ratio = faux5MI(-2,x,q)
++	   ctq5MI = sum/(1.d0 + ratio)
++
++	elseif(ii .eq. -2) then
++	   sum = faux5MI(-1,x,q)
++	   ratio = faux5MI(-2,x,q)
++	   ctq5MI = sum*ratio/(1.d0 + ratio)
++
++	elseif(ii .ge. -5) then
++	   ctq5MI = faux5MI(ii,x,q)
++
++	else
++	   ctq5MI = 0.d0
++
++	endif
++
++	return
++	end
++
++c ---------------------------------------------------------------------
++      double precision function faux5MI(ifl,x,q)
++c auxiliary function for parametrization of CTEQ5MI (J. Pumplin 9/99).
++c ---------------------------------------------------------------------
++      implicit double precision (a-h,o-z)
++      integer ifl
++
++      parameter (nex=8, nlf=2)
++      dimension am(0:nex,0:nlf,-5:2)
++      dimension alfvec(-5:2), qmavec(-5:2)
++      dimension mexvec(-5:2), mlfvec(-5:2)
++      dimension ut1vec(-5:2), ut2vec(-5:2)
++      dimension af(0:nex)
++
++      data mexvec( 2) / 8 /
++      data mlfvec( 2) / 2 /
++      data ut1vec( 2) /  0.5141718E+01 /
++      data ut2vec( 2) / -0.1346944E+01 /
++      data alfvec( 2) /  0.5260555E+00 /
++      data qmavec( 2) /  0.0000000E+00 /
++      data (am( 0,k, 2),k=0, 2)
++     & /  0.4289071E+01, -0.2536870E+01, -0.1259948E+01 /
++      data (am( 1,k, 2),k=0, 2)
++     & /  0.9839410E+00,  0.4168426E-01, -0.5018952E-01 /
++      data (am( 2,k, 2),k=0, 2)
++     & / -0.1651961E+02,  0.9246261E+01,  0.5996400E+01 /
++      data (am( 3,k, 2),k=0, 2)
++     & / -0.2077936E+02,  0.9786469E+01,  0.7656465E+01 /
++      data (am( 4,k, 2),k=0, 2)
++     & /  0.3054926E+02,  0.1889536E+01,  0.1380541E+01 /
++      data (am( 5,k, 2),k=0, 2)
++     & /  0.3084695E+02, -0.1212303E+02, -0.1053551E+02 /
++      data (am( 6,k, 2),k=0, 2)
++     & / -0.1426778E+02,  0.6239537E+01,  0.5254819E+01 /
++      data (am( 7,k, 2),k=0, 2)
++     & / -0.1909811E+02,  0.3695678E+01,  0.5495729E+01 /
++      data (am( 8,k, 2),k=0, 2)
++     & /  0.1889751E-01,  0.5027193E-02,  0.6624896E-03 /
++
++      data mexvec( 1) / 8 /
++      data mlfvec( 1) / 2 /
++      data ut1vec( 1) /  0.4138426E+01 /
++      data ut2vec( 1) / -0.3221374E+01 /
++      data alfvec( 1) /  0.4960962E+00 /
++      data qmavec( 1) /  0.0000000E+00 /
++      data (am( 0,k, 1),k=0, 2)
++     & /  0.1332497E+01, -0.3703718E+00,  0.1288638E+00 /
++      data (am( 1,k, 1),k=0, 2)
++     & /  0.7544687E+00,  0.3255075E-01, -0.4706680E-01 /
++      data (am( 2,k, 1),k=0, 2)
++     & / -0.7638814E+00,  0.5008313E+00, -0.9237374E-01 /
++      data (am( 3,k, 1),k=0, 2)
++     & / -0.3689889E+00, -0.1055098E+01, -0.4645065E+00 /
++      data (am( 4,k, 1),k=0, 2)
++     & /  0.3991610E+02,  0.1979881E+01,  0.1775814E+01 /
++      data (am( 5,k, 1),k=0, 2)
++     & /  0.6201080E+01,  0.2046288E+01,  0.3804571E+00 /
++      data (am( 6,k, 1),k=0, 2)
++     & / -0.8027900E+00, -0.7011688E+00, -0.8049612E+00 /
++      data (am( 7,k, 1),k=0, 2)
++     & / -0.8631305E+01, -0.3981200E+01,  0.6970153E+00 /
++      data (am( 8,k, 1),k=0, 2)
++     & /  0.2371230E-01,  0.5372683E-02,  0.1118701E-02 /
++
++      data mexvec( 0) / 8 /
++      data mlfvec( 0) / 2 /
++      data ut1vec( 0) / -0.1026789E+01 /
++      data ut2vec( 0) / -0.9051707E+01 /
++      data alfvec( 0) /  0.9462977E+00 /
++      data qmavec( 0) /  0.0000000E+00 /
++      data (am( 0,k, 0),k=0, 2)
++     & /  0.1191990E+03, -0.8548739E+00, -0.1963040E+01 /
++      data (am( 1,k, 0),k=0, 2)
++     & / -0.9449972E+02,  0.1074771E+01,  0.2056055E+01 /
++      data (am( 2,k, 0),k=0, 2)
++     & /  0.3701064E+01, -0.1167947E-02,  0.1933573E+00 /
++      data (am( 3,k, 0),k=0, 2)
++     & /  0.1171345E+03, -0.1064540E+01, -0.1875312E+01 /
++      data (am( 4,k, 0),k=0, 2)
++     & / -0.1014453E+03, -0.5707427E+00,  0.4511242E-01 /
++      data (am( 5,k, 0),k=0, 2)
++     & /  0.6365168E+01,  0.1275354E+01, -0.4964081E+00 /
++      data (am( 6,k, 0),k=0, 2)
++     & / -0.3370693E+01, -0.1122020E+01,  0.5947751E-01 /
++      data (am( 7,k, 0),k=0, 2)
++     & / -0.5327270E+01, -0.9293556E+00,  0.6629940E+00 /
++      data (am( 8,k, 0),k=0, 2)
++     & /  0.2437513E-01,  0.1600939E-02,  0.6855336E-03 /
++
++      data mexvec(-1) / 8 /
++      data mlfvec(-1) / 2 /
++      data ut1vec(-1) /  0.5243571E+01 /
++      data ut2vec(-1) / -0.2870513E+01 /
++      data alfvec(-1) /  0.6701448E+00 /
++      data qmavec(-1) /  0.0000000E+00 /
++      data (am( 0,k,-1),k=0, 2)
++     & /  0.2428863E+02,  0.1907035E+01, -0.4606457E+00 /
++      data (am( 1,k,-1),k=0, 2)
++     & /  0.2006810E+01, -0.1265915E+00,  0.7153556E-02 /
++      data (am( 2,k,-1),k=0, 2)
++     & / -0.1884546E+02, -0.2339471E+01,  0.5740679E+01 /
++      data (am( 3,k,-1),k=0, 2)
++     & / -0.2527892E+02, -0.2044124E+01,  0.1280470E+02 /
++      data (am( 4,k,-1),k=0, 2)
++     & / -0.1013824E+03, -0.1594199E+01,  0.2216401E+00 /
++      data (am( 5,k,-1),k=0, 2)
++     & /  0.8070930E+02,  0.1792072E+01, -0.2164364E+02 /
++      data (am( 6,k,-1),k=0, 2)
++     & / -0.4641050E+02,  0.1977338E+00,  0.1273014E+02 /
++      data (am( 7,k,-1),k=0, 2)
++     & / -0.3910568E+02,  0.1719632E+01,  0.1086525E+02 /
++      data (am( 8,k,-1),k=0, 2)
++     & / -0.1185496E+01, -0.1905847E+00, -0.8744118E-03 /
++
++      data mexvec(-2) / 7 /
++      data mlfvec(-2) / 2 /
++      data ut1vec(-2) /  0.4782210E+01 /
++      data ut2vec(-2) / -0.1976856E+02 /
++      data alfvec(-2) /  0.7558374E+00 /
++      data qmavec(-2) /  0.0000000E+00 /
++      data (am( 0,k,-2),k=0, 2)
++     & / -0.6216935E+00,  0.2369963E+00, -0.7909949E-02 /
++      data (am( 1,k,-2),k=0, 2)
++     & /  0.1245440E+01, -0.1031510E+00,  0.4916523E-02 /
++      data (am( 2,k,-2),k=0, 2)
++     & / -0.7060824E+01, -0.3875283E-01,  0.1784981E+00 /
++      data (am( 3,k,-2),k=0, 2)
++     & / -0.7430595E+01,  0.1964572E+00, -0.1284999E+00 /
++      data (am( 4,k,-2),k=0, 2)
++     & / -0.6897810E+01,  0.2620543E+01,  0.8012553E-02 /
++      data (am( 5,k,-2),k=0, 2)
++     & /  0.1507713E+02,  0.2340307E-01,  0.2482535E+01 /
++      data (am( 6,k,-2),k=0, 2)
++     & / -0.1815341E+01, -0.1538698E+01, -0.2014208E+01 /
++      data (am( 7,k,-2),k=0, 2)
++     & / -0.2571932E+02,  0.2903941E+00, -0.2848206E+01 /
++
++      data mexvec(-3) / 7 /
++      data mlfvec(-3) / 2 /
++      data ut1vec(-3) /  0.4518239E+01 /
++      data ut2vec(-3) / -0.2690590E+01 /
++      data alfvec(-3) /  0.6124079E+00 /
++      data qmavec(-3) /  0.0000000E+00 /
++      data (am( 0,k,-3),k=0, 2)
++     & / -0.2734458E+01, -0.7245673E+00, -0.6351374E+00 /
++      data (am( 1,k,-3),k=0, 2)
++     & /  0.2927174E+01,  0.4822709E+00, -0.1088787E-01 /
++      data (am( 2,k,-3),k=0, 2)
++     & / -0.1771017E+02, -0.1416635E+01,  0.8467622E+01 /
++      data (am( 3,k,-3),k=0, 2)
++     & / -0.4972782E+02, -0.3348547E+01,  0.1767061E+02 /
++      data (am( 4,k,-3),k=0, 2)
++     & / -0.7102770E+01, -0.3205337E+01,  0.4101704E+00 /
++      data (am( 5,k,-3),k=0, 2)
++     & /  0.7169698E+02, -0.2205985E+01, -0.2463931E+02 /
++      data (am( 6,k,-3),k=0, 2)
++     & / -0.4090347E+02,  0.2103486E+01,  0.1416507E+02 /
++      data (am( 7,k,-3),k=0, 2)
++     & / -0.2952639E+02,  0.5376136E+01,  0.7825585E+01 /
++
++      data mexvec(-4) / 7 /
++      data mlfvec(-4) / 2 /
++      data ut1vec(-4) /  0.2783230E+01 /
++      data ut2vec(-4) / -0.1746328E+01 /
++      data alfvec(-4) /  0.1115653E+01 /
++      data qmavec(-4) /  0.1300000E+01 /
++      data (am( 0,k,-4),k=0, 2)
++     & / -0.1743872E+01, -0.1128921E+01, -0.2841969E+00 /
++      data (am( 1,k,-4),k=0, 2)
++     & /  0.3345755E+01,  0.3187765E+00,  0.1378124E+00 /
++      data (am( 2,k,-4),k=0, 2)
++     & / -0.2037615E+02,  0.4121687E+01,  0.2236520E+00 /
++      data (am( 3,k,-4),k=0, 2)
++     & / -0.4703104E+02,  0.5353087E+01, -0.1455347E+01 /
++      data (am( 4,k,-4),k=0, 2)
++     & / -0.1060230E+02, -0.1551122E+01, -0.1078863E+01 /
++      data (am( 5,k,-4),k=0, 2)
++     & /  0.5088892E+02, -0.8197304E+01,  0.8083451E+01 /
++      data (am( 6,k,-4),k=0, 2)
++     & / -0.2819070E+02,  0.4554086E+01, -0.5890995E+01 /
++      data (am( 7,k,-4),k=0, 2)
++     & / -0.1098238E+02,  0.2590096E+01, -0.8062879E+01 /
++
++      data mexvec(-5) / 6 /
++      data mlfvec(-5) / 2 /
++      data ut1vec(-5) /  0.1619654E+02 /
++      data ut2vec(-5) / -0.3367346E+01 /
++      data alfvec(-5) /  0.5109891E-02 /
++      data qmavec(-5) /  0.4500000E+01 /
++      data (am( 0,k,-5),k=0, 2)
++     & / -0.6800138E+01,  0.2493627E+01, -0.1075724E+01 /
++      data (am( 1,k,-5),k=0, 2)
++     & /  0.3036555E+01,  0.3324733E+00,  0.2008298E+00 /
++      data (am( 2,k,-5),k=0, 2)
++     & / -0.5203879E+01, -0.8493476E+01, -0.4523208E+01 /
++      data (am( 3,k,-5),k=0, 2)
++     & / -0.1524239E+01, -0.3411912E+01, -0.1771867E+02 /
++      data (am( 4,k,-5),k=0, 2)
++     & / -0.1099444E+02,  0.1320930E+01, -0.2353831E+01 /
++      data (am( 5,k,-5),k=0, 2)
++     & /  0.1699299E+02, -0.3565802E+02,  0.3566872E+02 /
++      data (am( 6,k,-5),k=0, 2)
++     & / -0.1465793E+02,  0.2703365E+02, -0.2176372E+02 /
++
++      if(q .le. qmavec(ifl)) then
++         faux5MI = 0.d0
++         return
++      endif
++
++      if(x .ge. 1.d0) then
++         faux5MI = 0.d0
++         return
++      endif
++
++      tmp = log(q/alfvec(ifl))
++      if(tmp .le. 0.d0) then
++         faux5MI = 0.d0
++         return
++      endif
++
++      sb = log(tmp)
++      sb1 = sb - 1.2d0
++      sb2 = sb1*sb1
++
++      do i = 0, nex
++         af(i) = 0.d0
++         sbx = 1.d0
++         do k = 0, mlfvec(ifl)
++            af(i) = af(i) + sbx*am(i,k,ifl)
++            sbx = sb1*sbx
++         enddo
++      enddo
++
++      y = -log(x)
++      u = log(x/0.00001d0)
++
++      part1 = af(1)*y**(1.d0+0.01d0*af(4))*(1.d0+ af(8)*u)
++      part2 = af(0)*(1.d0 - x) + af(3)*x
++      part3 = x*(1.d0-x)*(af(5)+af(6)*(1.d0-x)+af(7)*x*(1.d0-x))
++      part4 = ut1vec(ifl)*log(1.d0-x) +
++     &	      AF(2)*log(1.d0+exp(ut2vec(ifl))-x)
++
++      faux5MI = exp(log(x) + part1 + part2 + part3 + part4)
++
++c include threshold factor...
++      faux5MI = faux5MI * (1.d0 - qmavec(ifl)/q)
++
++      return
++      end
++c --------------------------------------------------------------------------
++	double precision function ctq5L(ifl,x,q)
++c Parametrization of cteq5L parton distribution functions (J. Pumplin 9/99).
++c ifl: 1=u,2=d,3=s,4=c,5=b;0=gluon;-1=ubar,-2=dbar,-3=sbar,-4=cbar,-5=bbar.
++c --------------------------------------------------------------------------
++	implicit double precision (a-h,o-z)
++	integer ifl
++
++	ii = ifl
++	if(ii .gt. 2) then
++	   ii = -ii
++	endif
++
++	if(ii .eq. -1) then
++	   sum = faux5L(-1,x,q)
++	   ratio = faux5L(-2,x,q)
++	   ctq5L = sum/(1.d0 + ratio)
++
++	elseif(ii .eq. -2) then
++	   sum = faux5L(-1,x,q)
++	   ratio = faux5L(-2,x,q)
++	   ctq5L = sum*ratio/(1.d0 + ratio)
++
++	elseif(ii .ge. -5) then
++	   ctq5L = faux5L(ii,x,q)
++
++	else
++	   ctq5L = 0.d0
++
++	endif
++
++	return
++	end
++
++c ---------------------------------------------------------------------
++      double precision function faux5L(ifl,x,q)
++c auxiliary function for parametrization of CTEQ5L (J. Pumplin 9/99).
++c ---------------------------------------------------------------------
++      implicit double precision (a-h,o-z)
++      integer ifl
++
++      parameter (nex=8, nlf=2)
++      dimension am(0:nex,0:nlf,-5:2)
++      dimension alfvec(-5:2), qmavec(-5:2)
++      dimension mexvec(-5:2), mlfvec(-5:2)
++      dimension ut1vec(-5:2), ut2vec(-5:2)
++      dimension af(0:nex)
++
++      data mexvec( 2) / 8 /
++      data mlfvec( 2) / 2 /
++      data ut1vec( 2) /  0.4971265E+01 /
++      data ut2vec( 2) / -0.1105128E+01 /
++      data alfvec( 2) /  0.2987216E+00 /
++      data qmavec( 2) /  0.0000000E+00 /
++      data (am( 0,k, 2),k=0, 2)
++     & /  0.5292616E+01, -0.2751910E+01, -0.2488990E+01 /
++      data (am( 1,k, 2),k=0, 2)
++     & /  0.9714424E+00,  0.1011827E-01, -0.1023660E-01 /
++      data (am( 2,k, 2),k=0, 2)
++     & / -0.1651006E+02,  0.7959721E+01,  0.8810563E+01 /
++      data (am( 3,k, 2),k=0, 2)
++     & / -0.1643394E+02,  0.5892854E+01,  0.9348874E+01 /
++      data (am( 4,k, 2),k=0, 2)
++     & /  0.3067422E+02,  0.4235796E+01, -0.5112136E+00 /
++      data (am( 5,k, 2),k=0, 2)
++     & /  0.2352526E+02, -0.5305168E+01, -0.1169174E+02 /
++      data (am( 6,k, 2),k=0, 2)
++     & / -0.1095451E+02,  0.3006577E+01,  0.5638136E+01 /
++      data (am( 7,k, 2),k=0, 2)
++     & / -0.1172251E+02, -0.2183624E+01,  0.4955794E+01 /
++      data (am( 8,k, 2),k=0, 2)
++     & /  0.1662533E-01,  0.7622870E-02, -0.4895887E-03 /
++
++      data mexvec( 1) / 8 /
++      data mlfvec( 1) / 2 /
++      data ut1vec( 1) /  0.2612618E+01 /
++      data ut2vec( 1) / -0.1258304E+06 /
++      data alfvec( 1) /  0.3407552E+00 /
++      data qmavec( 1) /  0.0000000E+00 /
++      data (am( 0,k, 1),k=0, 2)
++     & /  0.9905300E+00, -0.4502235E+00,  0.1624441E+00 /
++      data (am( 1,k, 1),k=0, 2)
++     & /  0.8867534E+00,  0.1630829E-01, -0.4049085E-01 /
++      data (am( 2,k, 1),k=0, 2)
++     & /  0.8547974E+00,  0.3336301E+00,  0.1371388E+00 /
++      data (am( 3,k, 1),k=0, 2)
++     & /  0.2941113E+00, -0.1527905E+01,  0.2331879E+00 /
++      data (am( 4,k, 1),k=0, 2)
++     & /  0.3384235E+02,  0.3715315E+01,  0.8276930E+00 /
++      data (am( 5,k, 1),k=0, 2)
++     & /  0.6230115E+01,  0.3134639E+01, -0.1729099E+01 /
++      data (am( 6,k, 1),k=0, 2)
++     & / -0.1186928E+01, -0.3282460E+00,  0.1052020E+00 /
++      data (am( 7,k, 1),k=0, 2)
++     & / -0.8545702E+01, -0.6247947E+01,  0.3692561E+01 /
++      data (am( 8,k, 1),k=0, 2)
++     & /  0.1724598E-01,  0.7120465E-02,  0.4003646E-04 /
++
++      data mexvec( 0) / 8 /
++      data mlfvec( 0) / 2 /
++      data ut1vec( 0) / -0.4656819E+00 /
++      data ut2vec( 0) / -0.2742390E+03 /
++      data alfvec( 0) /  0.4491863E+00 /
++      data qmavec( 0) /  0.0000000E+00 /
++      data (am( 0,k, 0),k=0, 2)
++     & /  0.1193572E+03, -0.3886845E+01, -0.1133965E+01 /
++      data (am( 1,k, 0),k=0, 2)
++     & / -0.9421449E+02,  0.3995885E+01,  0.1607363E+01 /
++      data (am( 2,k, 0),k=0, 2)
++     & /  0.4206383E+01,  0.2485954E+00,  0.2497468E+00 /
++      data (am( 3,k, 0),k=0, 2)
++     & /  0.1210557E+03, -0.3015765E+01, -0.1423651E+01 /
++      data (am( 4,k, 0),k=0, 2)
++     & / -0.1013897E+03, -0.7113478E+00,  0.2621865E+00 /
++      data (am( 5,k, 0),k=0, 2)
++     & / -0.1312404E+01, -0.9297691E+00, -0.1562531E+00 /
++      data (am( 6,k, 0),k=0, 2)
++     & /  0.1627137E+01,  0.4954111E+00, -0.6387009E+00 /
++      data (am( 7,k, 0),k=0, 2)
++     & /  0.1537698E+00, -0.2487878E+00,  0.8305947E+00 /
++      data (am( 8,k, 0),k=0, 2)
++     & /  0.2496448E-01,  0.2457823E-02,  0.8234276E-03 /
++
++      data mexvec(-1) / 8 /
++      data mlfvec(-1) / 2 /
++      data ut1vec(-1) /  0.3862583E+01 /
++      data ut2vec(-1) / -0.1265969E+01 /
++      data alfvec(-1) /  0.2457668E+00 /
++      data qmavec(-1) /  0.0000000E+00 /
++      data (am( 0,k,-1),k=0, 2)
++     & /  0.2647441E+02,  0.1059277E+02, -0.9176654E+00 /
++      data (am( 1,k,-1),k=0, 2)
++     & /  0.1990636E+01,  0.8558918E-01,  0.4248667E-01 /
++      data (am( 2,k,-1),k=0, 2)
++     & / -0.1476095E+02, -0.3276255E+02,  0.1558110E+01 /
++      data (am( 3,k,-1),k=0, 2)
++     & / -0.2966889E+01, -0.3649037E+02,  0.1195914E+01 /
++      data (am( 4,k,-1),k=0, 2)
++     & / -0.1000519E+03, -0.2464635E+01,  0.1964849E+00 /
++      data (am( 5,k,-1),k=0, 2)
++     & /  0.3718331E+02,  0.4700389E+02, -0.2772142E+01 /
++      data (am( 6,k,-1),k=0, 2)
++     & / -0.1872722E+02, -0.2291189E+02,  0.1089052E+01 /
++      data (am( 7,k,-1),k=0, 2)
++     & / -0.1628146E+02, -0.1823993E+02,  0.2537369E+01 /
++      data (am( 8,k,-1),k=0, 2)
++     & / -0.1156300E+01, -0.1280495E+00,  0.5153245E-01 /
++
++      data mexvec(-2) / 7 /
++      data mlfvec(-2) / 2 /
++      data ut1vec(-2) /  0.1895615E+00 /
++      data ut2vec(-2) / -0.3069097E+01 /
++      data alfvec(-2) /  0.5293999E+00 /
++      data qmavec(-2) /  0.0000000E+00 /
++      data (am( 0,k,-2),k=0, 2)
++     & / -0.6556775E+00,  0.2490190E+00,  0.3966485E-01 /
++      data (am( 1,k,-2),k=0, 2)
++     & /  0.1305102E+01, -0.1188925E+00, -0.4600870E-02 /
++      data (am( 2,k,-2),k=0, 2)
++     & / -0.2371436E+01,  0.3566814E+00, -0.2834683E+00 /
++      data (am( 3,k,-2),k=0, 2)
++     & / -0.6152826E+01,  0.8339877E+00, -0.7233230E+00 /
++      data (am( 4,k,-2),k=0, 2)
++     & / -0.8346558E+01,  0.2892168E+01,  0.2137099E+00 /
++      data (am( 5,k,-2),k=0, 2)
++     & /  0.1279530E+02,  0.1021114E+00,  0.5787439E+00 /
++      data (am( 6,k,-2),k=0, 2)
++     & /  0.5858816E+00, -0.1940375E+01, -0.4029269E+00 /
++      data (am( 7,k,-2),k=0, 2)
++     & / -0.2795725E+02, -0.5263392E+00,  0.1290229E+01 /
++
++      data mexvec(-3) / 7 /
++      data mlfvec(-3) / 2 /
++      data ut1vec(-3) /  0.3753257E+01 /
++      data ut2vec(-3) / -0.1113085E+01 /
++      data alfvec(-3) /  0.3713141E+00 /
++      data qmavec(-3) /  0.0000000E+00 /
++      data (am( 0,k,-3),k=0, 2)
++     & /  0.1580931E+01, -0.2273826E+01, -0.1822245E+01 /
++      data (am( 1,k,-3),k=0, 2)
++     & /  0.2702644E+01,  0.6763243E+00,  0.7231586E-02 /
++      data (am( 2,k,-3),k=0, 2)
++     & / -0.1857924E+02,  0.3907500E+01,  0.5850109E+01 /
++      data (am( 3,k,-3),k=0, 2)
++     & / -0.3044793E+02,  0.2639332E+01,  0.5566644E+01 /
++      data (am( 4,k,-3),k=0, 2)
++     & / -0.4258011E+01, -0.5429244E+01,  0.4418946E+00 /
++      data (am( 5,k,-3),k=0, 2)
++     & /  0.3465259E+02, -0.5532604E+01, -0.4904153E+01 /
++      data (am( 6,k,-3),k=0, 2)
++     & / -0.1658858E+02,  0.2923275E+01,  0.2266286E+01 /
++      data (am( 7,k,-3),k=0, 2)
++     & / -0.1149263E+02,  0.2877475E+01, -0.7999105E+00 /
++
++      data mexvec(-4) / 7 /
++      data mlfvec(-4) / 2 /
++      data ut1vec(-4) /  0.4400772E+01 /
++      data ut2vec(-4) / -0.1356116E+01 /
++      data alfvec(-4) /  0.3712017E-01 /
++      data qmavec(-4) /  0.1300000E+01 /
++      data (am( 0,k,-4),k=0, 2)
++     & / -0.8293661E+00, -0.3982375E+01, -0.6494283E-01 /
++      data (am( 1,k,-4),k=0, 2)
++     & /  0.2754618E+01,  0.8338636E+00, -0.6885160E-01 /
++      data (am( 2,k,-4),k=0, 2)
++     & / -0.1657987E+02,  0.1439143E+02, -0.6887240E+00 /
++      data (am( 3,k,-4),k=0, 2)
++     & / -0.2800703E+02,  0.1535966E+02, -0.7377693E+00 /
++      data (am( 4,k,-4),k=0, 2)
++     & / -0.6460216E+01, -0.4783019E+01,  0.4913297E+00 /
++      data (am( 5,k,-4),k=0, 2)
++     & /  0.3141830E+02, -0.3178031E+02,  0.7136013E+01 /
++      data (am( 6,k,-4),k=0, 2)
++     & / -0.1802509E+02,  0.1862163E+02, -0.4632843E+01 /
++      data (am( 7,k,-4),k=0, 2)
++     & / -0.1240412E+02,  0.2565386E+02, -0.1066570E+02 /
++
++      data mexvec(-5) / 6 /
++      data mlfvec(-5) / 2 /
++      data ut1vec(-5) /  0.5562568E+01 /
++      data ut2vec(-5) / -0.1801317E+01 /
++      data alfvec(-5) /  0.4952010E-02 /
++      data qmavec(-5) /  0.4500000E+01 /
++      data (am( 0,k,-5),k=0, 2)
++     & / -0.6031237E+01,  0.1992727E+01, -0.1076331E+01 /
++      data (am( 1,k,-5),k=0, 2)
++     & /  0.2933912E+01,  0.5839674E+00,  0.7509435E-01 /
++      data (am( 2,k,-5),k=0, 2)
++     & / -0.8284919E+01,  0.1488593E+01, -0.8251678E+00 /
++      data (am( 3,k,-5),k=0, 2)
++     & / -0.1925986E+02,  0.2805753E+01, -0.3015446E+01 /
++      data (am( 4,k,-5),k=0, 2)
++     & / -0.9480483E+01, -0.9767837E+00, -0.1165544E+01 /
++      data (am( 5,k,-5),k=0, 2)
++     & /  0.2193195E+02, -0.1788518E+02,  0.9460908E+01 /
++      data (am( 6,k,-5),k=0, 2)
++     & / -0.1327377E+02,  0.1201754E+02, -0.6277844E+01 /
++
++      if(q .le. qmavec(ifl)) then
++         faux5L = 0.d0
++         return
++      endif
++
++      if(x .ge. 1.d0) then
++         faux5L = 0.d0
++         return
++      endif
++
++      tmp = log(q/alfvec(ifl))
++      if(tmp .le. 0.d0) then
++         faux5L = 0.d0
++         return
++      endif
++
++      sb = log(tmp)
++      sb1 = sb - 1.2d0
++      sb2 = sb1*sb1
++
++      do i = 0, nex
++         af(i) = 0.d0
++         sbx = 1.d0
++         do k = 0, mlfvec(ifl)
++            af(i) = af(i) + sbx*am(i,k,ifl)
++            sbx = sb1*sbx
++         enddo
++      enddo
++
++      y = -log(x)
++      u = log(x/0.00001d0)
++
++      part1 = af(1)*y**(1.d0+0.01d0*af(4))*(1.d0+ af(8)*u)
++      part2 = af(0)*(1.d0 - x) + af(3)*x
++      part3 = x*(1.d0-x)*(af(5)+af(6)*(1.d0-x)+af(7)*x*(1.d0-x))
++      part4 = ut1vec(ifl)*log(1.d0-x) +
++     &	      AF(2)*log(1.d0+exp(ut2vec(ifl))-x)
++
++      faux5L = exp(log(x) + part1 + part2 + part3 + part4)
++
++c include threshold factor...
++      faux5L = faux5L * (1.d0 - qmavec(ifl)/q)
++
++      return
++      end
 === added file 'Template/NLO/Source/PDF/Ctq5Pdf.f'
 --- Template/NLO/Source/PDF/Ctq5Pdf.f	1970-01-01 00:00:00 +0000
 +++ Template/NLO/Source/PDF/Ctq5Pdf.f	2012-09-28 12:29:27 +0000
@@ -0,0 +1,344 @@
++C============================================================================
++C                CTEQ Parton Distribution Functions: Version 5.0
++C                             Nov. 1, 1999
++C
++C   Ref: "GLOBAL QCD ANALYSIS OF PARTON STRUCTURE OF THE NUCLEON:
++C         CTEQ5 PPARTON DISTRIBUTIONS"
++C
++C  hep-ph/9903282; to be published in Eur. Phys. J. C 1999.
++C
++C  These PDF's use quadratic interpolation of attached tables. A parametrized
++C  version of the same PDF's without external tables is under construction.
++C  They will become available later.
++C
++C   This package contains 7 sets of CTEQ5 PDF's; plus two updated ones.
++C   The undated CTEQ5M1 and CTEQHQ1 use an improved evolution code.
++C   Both the original and the updated ones fit current data with comparable
++C   accuracy.  The CTEQHQ1 set also involve a different choice of scale,
++C   hence differs from CTEQHQ slightly more.  It is preferred over CTEQ5HQ.
++
++C   Details are:
++C ---------------------------------------------------------------------------
++C  Iset   PDF        Description       Alpha_s(Mz)  Lam4  Lam5   Table_File
++C ---------------------------------------------------------------------------
++C   1    CTEQ5M   Standard MSbar scheme   0.118     326   226    cteq5m.tbl
++C   2    CTEQ5D   Standard DIS scheme     0.118     326   226    cteq5d.tbl
++C   3    CTEQ5L   Leading Order           0.127     192   146    cteq5l.tbl
++C   4    CTEQ5HJ  Large-x gluon enhanced  0.118     326   226    cteq5hj.tbl
++C   5    CTEQ5HQ  Heavy Quark             0.118     326   226    cteq5hq.tbl
++C   6    CTEQ5F3  Nf=3 FixedFlavorNumber  0.106     (Lam3=395)   cteq5f3.tbl
++C   7    CTEQ5F4  Nf=4 FixedFlavorNumber  0.112     309   XXX    cteq5f4.tbl
++C         --------------------------------------------------------
++C   8    CTEQ5M1  Improved CTEQ5M         0.118     326   226    cteq5m1.tbl
++C   9    CTEQ5HQ1 Improved CTEQ5HQ        0.118     326   226    ctq5hq1.tbl
++C ---------------------------------------------------------------------------
++C
++C  The available applied range is 10^-5 << x << 1 and 1.0 << Q << 10,000 (GeV).
++C   Lam5 (Lam4, Lam3) represents Lambda value (in MeV) for 5 (4,3) flavors.
++C   The matching alpha_s between 4 and 5 flavors takes place at Q=4.5 GeV,
++C   which is defined as the bottom quark mass, whenever it can be applied.
++C
++C   The Table_Files are assumed to be in the working directory.
++C
++C   Before using the PDF, it is necessary to do the initialization by
++C       Call SetCtq5(Iset)
++C   where Iset is the desired PDF specified in the above table.
++C
++C   The function Ctq5Pdf (Iparton, X, Q)
++C   returns the parton distribution inside the proton for parton [Iparton]
++C   at [X] Bjorken_X and scale [Q] (GeV) in PDF set [Iset].
++C   Iparton  is the parton label (5, 4, 3, 2, 1, 0, -1, ......, -5)
++C                            for (b, c, s, d, u, g, u_bar, ..., b_bar),
++C      whereas CTEQ5F3 has, by definition, only 3 flavors and gluon;
++C              CTEQ5F4 has only 4 flavors and gluon.
++C
++C   For detailed information on the parameters used, e.q. quark masses,
++C   QCD Lambda, ... etc.,  see info lines at the beginning of the
++C   Table_Files.
++C
++C   These programs, as provided, are in double precision.  By removing the
++C   "Implicit Double Precision" lines, they can also be run in single
++C   precision.
++C
++C   If you have detailed questions concerning these CTEQ5 distributions,
++C   or if you find problems/bugs using this package, direct inquires to
++C   Hung-Liang Lai(lai@phys.nthu.edu.tw) or Wu-Ki Tung(Tung@pa.msu.edu).
++C
++C===========================================================================
++
++      Function Ctq5Pdf (Iparton, X, Q)
++      Implicit Double Precision (A-H,O-Z)
++      Logical Warn
++      Common
++     > / CtqPar2 / Nx, Nt, NfMx
++     > / QCDtable /  Alambda, Nfl, Iorder
++
++      Data Warn /.true./
++      save Warn
++
++      If (X .lt. 0D0 .or. X .gt. 1D0) Then
++	Print *, 'X out of range in Ctq5Pdf: ', X
++	Stop
++      Endif
++      If (Q .lt. Alambda) Then
++	Print *, 'Q out of range in Ctq5Pdf: ', Q
++	Stop
++      Endif
++      If ((Iparton .lt. -NfMx .or. Iparton .gt. NfMx)) Then
++         If (Warn) Then
++C        put a warning for calling extra flavor.
++	     Warn = .false.
++	     Print *, 'Warning: Iparton out of range in Ctq5Pdf: '
++     >              , Iparton
++         Endif
++         Ctq5Pdf = 0D0
++         Return
++      Endif
++
++      Ctq5Pdf = PartonX (Iparton, X, Q)
++      if(Ctq5Pdf.lt.0.D0)  Ctq5Pdf = 0.D0
++
++      Return
++
++C                             ********************
++      End
++
++      FUNCTION PartonX_orig (IPRTN, X, Q)
++C
++C   Given the parton distribution function in the array Upd in
++C   COMMON / CtqPar1 / , this routine fetches u(fl, x, q) at any value of
++C   x and q using Mth-order polynomial interpolation for x and Ln(Q/Lambda).
++C
++      IMPLICIT DOUBLE PRECISION (A-H, O-Z)
++C
++      PARAMETER (MXX = 105, MXQ = 25, MXF = 6)
++      PARAMETER (MXPQX = (MXF *2 +2) * MXQ * MXX)
++      PARAMETER (M= 2, M1 = M + 1)
++C
++      Logical First
++      Common
++     > / CtqPar1 / Al, XV(0:MXX), QL(0:MXQ), UPD(MXPQX)
++     > / CtqPar2 / Nx, Nt, NfMx
++     > / XQrange / Qini, Qmax, Xmin
++C
++      Dimension Fq(M1), Df(M1)
++
++      Data First /.true./
++      save First
++C                                                 Work with Log (Q)
++      QG  = LOG (Q/AL)
++
++C                           Find lower end of interval containing X
++      JL = -1
++      JU = Nx+1
++ 11   If (JU-JL .GT. 1) Then
++         JM = (JU+JL) / 2
++         If (X .GT. XV(JM)) Then
++            JL = JM
++         Else
++            JU = JM
++         Endif
++         Goto 11
++      Endif
++
++      Jx = JL - (M-1)/2
++      If (X .lt. Xmin .and. First ) Then
++         First = .false.
++         Print '(A, 2(1pE12.4))',
++     >     ' WARNING: X << Xmin, extrapolation used; X, Xmin =', X, Xmin
++         If (Jx .LT. 0) Jx = 0
++      Elseif (Jx .GT. Nx-M) Then
++         Jx = Nx - M
++      Endif
++C                                    Find the interval where Q lies
++      JL = -1
++      JU = NT+1
++ 12   If (JU-JL .GT. 1) Then
++         JM = (JU+JL) / 2
++         If (QG .GT. QL(JM)) Then
++            JL = JM
++         Else
++            JU = JM
++         Endif
++         Goto 12
++      Endif
++
++      Jq = JL - (M-1)/2
++      If (Jq .LT. 0) Then
++         Jq = 0
++         If (Q .lt. Qini)  Print '(A, 2(1pE12.4))',
++     >     ' WARNING: Q << Qini, extrapolation used; Q, Qini =', Q, Qini
++      Elseif (Jq .GT. Nt-M) Then
++         Jq = Nt - M
++         If (Q .gt. Qmax)  Print '(A, 2(1pE12.4))',
++     >     ' WARNING: Q > Qmax, extrapolation used; Q, Qmax =', Q, Qmax
++      Endif
++
++      If (Iprtn .GE. 3) Then
++         Ip = - Iprtn
++      Else
++         Ip = Iprtn
++      EndIf
++C                             Find the off-set in the linear array Upd
++      JFL = Ip + NfMx
++      J0  = (JFL * (NT+1) + Jq) * (NX+1) + Jx
++C
++C                                           Now interpolate in x for M1 Q's
++      Do 21 Iq = 1, M1
++         J1 = J0 + (Nx+1)*(Iq-1) + 1
++         Call Polint (XV(Jx), Upd(J1), M1, X, Fq(Iq), Df(Iq))
++ 21   Continue
++C                                          Finish off by interpolating in Q
++      Call Polint (QL(Jq), Fq(1), M1, QG, Ftmp, Ddf)
++
++      PartonX_orig = Ftmp
++C
++      RETURN
++C                        ****************************
++      END
++
++      Subroutine SetCtq5 (Iset)
++      Implicit Double Precision (A-H,O-Z)
++      Parameter (Isetmax=9)
++      Character Flnm(Isetmax)*12, Tablefile*40
++      Data (Flnm(I), I=1,Isetmax)
++     > / 'cteq5m.tbl', 'cteq5d.tbl', 'cteq5l.tbl', 'cteq5hj.tbl'
++     > , 'cteq5hq.tbl', 'cteq5f3.tbl', 'cteq5f4.tbl'
++     > , 'cteq5m1.tbl', 'ctq5hq1.tbl'  /
++      Data Tablefile / 'test.tbl' /
++      Data Isetold, Isetmin, Isettest / -987, 1, 911 /
++      save
++
++C             If data file not initialized, do so.
++      If(Iset.ne.Isetold) then
++	 IU= NextUn()
++         If (Iset .eq. Isettest) then
++            Print* ,'Opening ', Tablefile
++ 21         Open(IU, File=Tablefile, Status='OLD', Err=101)
++            GoTo 22
++ 101        Print*, Tablefile, ' cannot be opened '
++            Print*, 'Please input the .tbl file:'
++            Read (*,'(A)') Tablefile
++            Goto 21
++ 22         Continue
++         ElseIf (Iset.lt.Isetmin .or. Iset.gt.Isetmax) Then
++	    Print *, 'Invalid Iset number in SetCtq5 :', Iset
++	    Stop
++         Else
++            Tablefile=Flnm(Iset)
++c            Open(IU, File='Pdfdata/'//Tablefile, Status='OLD', Err=100)
++            call OpenData(TableFile)
++	 Endif
++         Call ReadTbl (IU)
++         Close (IU)
++	 Isetold=Iset
++      Endif
++      Return
++
++ 100  Print *, ' Data file ', Tablefile, ' cannot be opened '
++     >//'in SetCtq5!!'
++      Stop
++C                             ********************
++      End
++
++      Subroutine ReadTbl (Nu)
++      Implicit Double Precision (A-H,O-Z)
++      Character Line*80
++      PARAMETER (MXX = 105, MXQ = 25, MXF = 6)
++      PARAMETER (MXPQX = (MXF *2 +2) * MXQ * MXX)
++      Common
++     > / CtqPar1 / Al, XV(0:MXX), QL(0:MXQ), UPD(MXPQX)
++     > / CtqPar2 / Nx, Nt, NfMx
++     > / XQrange / Qini, Qmax, Xmin
++     > / QCDtable /  Alambda, Nfl, Iorder
++     > / Masstbl / Amass(6)
++
++      Read  (Nu, '(A)') Line
++      Read  (Nu, '(A)') Line
++      Read  (Nu, *) Dr, Fl, Al, (Amass(I),I=1,6)
++      Iorder = Nint(Dr)
++      Nfl = Nint(Fl)
++      Alambda = Al
++
++      Read  (Nu, '(A)') Line
++      Read  (Nu, *) NX,  NT, NfMx
++
++      Read  (Nu, '(A)') Line
++      Read  (Nu, *) QINI, QMAX, (QL(I), I =0, NT)
++
++      Read  (Nu, '(A)') Line
++      Read  (Nu, *) XMIN, (XV(I), I =0, NX)
++
++      Do 11 Iq = 0, NT
++         QL(Iq) = Log (QL(Iq) /Al)
++   11 Continue
++C
++C                  Since quark = anti-quark for nfl>2 at this stage,
++C                  we Read  out only the non-redundent data points
++C     No of flavors = NfMx (sea) + 1 (gluon) + 2 (valence)
++
++      Nblk = (NX+1) * (NT+1)
++      Npts =  Nblk  * (NfMx+3)
++      Read  (Nu, '(A)') Line
++      Read  (Nu, *, IOSTAT=IRET) (UPD(I), I=1,Npts)
++
++      Return
++C                        ****************************
++      End
++
++      Function NextUn()
++C                                 Returns an unallocated FORTRAN i/o unit.
++      Logical EX
++C
++      Do 10 N = 10, 300
++         INQUIRE (UNIT=N, OPENED=EX)
++         If (.NOT. EX) then
++            NextUn = N
++            Return
++         Endif
++ 10   Continue
++      Stop ' There is no available I/O unit. '
++C               *************************
++      End
++C
++
++      SUBROUTINE POLINT (XA,YA,N,X,Y,DY)
++
++      IMPLICIT DOUBLE PRECISION (A-H, O-Z)
++C                                        Adapted from "Numerical Recipes"
++      PARAMETER (NMAX=10)
++      DIMENSION XA(N),YA(N),C(NMAX),D(NMAX)
++      NS=1
++      DIF=ABS(X-XA(1))
++      DO 11 I=1,N
++        DIFT=ABS(X-XA(I))
++        IF (DIFT.LT.DIF) THEN
++          NS=I
++          DIF=DIFT
++        ENDIF
++        C(I)=YA(I)
++        D(I)=YA(I)
++11    CONTINUE
++      Y=YA(NS)
++      NS=NS-1
++      DO 13 M=1,N-1
++        DO 12 I=1,N-M
++          HO=XA(I)-X
++          HP=XA(I+M)-X
++          W=C(I+1)-D(I)
++          DEN=HO-HP
++          IF(DEN.EQ.0.) STOP
++          DEN=W/DEN
++          D(I)=HP*DEN
++          C(I)=HO*DEN
++12      CONTINUE
++        IF (2*NS.LT.N-M)THEN
++          DY=C(NS+1)
++        ELSE
++          DY=D(NS)
++          NS=NS-1
++        ENDIF
++        Y=Y+DY
++13    CONTINUE
++      RETURN
++      END
 === added file 'Template/NLO/Source/PDF/Ctq6Pdf.f'
 --- Template/NLO/Source/PDF/Ctq6Pdf.f	1970-01-01 00:00:00 +0000
 +++ Template/NLO/Source/PDF/Ctq6Pdf.f	2012-09-28 12:29:27 +0000
@@ -0,0 +1,480 @@
++C============================================================================
++C                CTEQ Parton Distribution Functions: Version 6
++C                             January 24, 2002, v6.0
++C                             April 10, 2002, v6.1
++C
++C   Ref: "New Generation of Parton Distributions with
++C         Uncertainties from Global QCD Analysis"
++C   By: J. Pumplin, D.R. Stump, J.Huston, H.L. Lai, P. Nadolsky, W.K. Tung
++C       hep-ph/0201195
++C
++C   This package contains 3 standard sets of CTEQ6 PDF's and 40 up/down sets
++C   with respect to CTEQ6M PDF's. Details are:
++C ---------------------------------------------------------------------------
++C  Iset   PDF        Description       Alpha_s(Mz)**Lam4  Lam5   Table_File
++C ---------------------------------------------------------------------------
++C   1    CTEQ6M   Standard MSbar scheme   0.118     326   226    cteq6m.tbl
++C   2    CTEQ6D   Standard DIS scheme     0.118     326   226    cteq6d.tbl
++C   3    CTEQ6L   Leading Order           0.118**   326** 226    cteq6l.tbl
++C   4    CTEQ6L1  Leading Order           0.130     215   165    cteq6l1.tbl
++C     ------------------------------
++C   1xx  CTEQ6M1xx  +/- w.r.t. CTEQ6M     0.118     326   226    cteq6m1xx.tbl
++C    (where xx=01--40)
++C ---------------------------------------------------------------------------
++C   ** ALL fits are obtained by using the same coupling strength
++C   \alpha_s(Mz)=0.118 and the NLO running \alpha_s formula, except CTEQ6L1
++C   which uses the LO running \alpha_s and its value determined from the fit.
++C   For the LO fits, the evolution of the PDF and the hard cross sections are
++C   calculated at LO.  More detailed discussions are given in hep-ph/0201195.
++C
++C   The table grids are generated for 10^-6 < x < 1 and 1.3 < Q < 10,000 (GeV).
++C   PDF values outside of the above range are returned using extrapolation.
++C   Lam5 (Lam4) represents Lambda value (in MeV) for 5 (4) flavors.
++C   The matching alpha_s between 4 and 5 flavors takes place at Q=4.5 GeV,
++C   which is defined as the bottom quark mass, whenever it can be applied.
++C
++C   The Table_Files are assumed to be in the working directory.
++C
++C   Before using the PDF, it is necessary to do the initialization by
++C       Call SetCtq6(Iset)
++C   where Iset is the desired PDF specified in the above table.
++C
++C   The function Ctq6Pdf (Iparton, X, Q)
++C   returns the parton distribution inside the proton for parton [Iparton]
++C   at [X] Bjorken_X and scale [Q] (GeV) in PDF set [Iset].
++C   Iparton  is the parton label (5, 4, 3, 2, 1, 0, -1, ......, -5)
++C                            for (b, c, s, d, u, g, u_bar, ..., b_bar),
++C
++C   For detailed information on the parameters used, e.q. quark masses,
++C   QCD Lambda, ... etc.,  see info lines at the beginning of the
++C   Table_Files.
++C
++C   These programs, as provided, are in double precision.  By removing the
++C   "Implicit Double Precision" lines, they can also be run in single
++C   precision.
++C
++C   If you have detailed questions concerning these CTEQ6 distributions,
++C   or if you find problems/bugs using this package, direct inquires to
++C   Pumplin@pa.msu.edu or Tung@pa.msu.edu.
++C
++C===========================================================================
++
++      Function Ctq6Pdf (Iparton, X, Q)
++      Implicit Double Precision (A-H,O-Z)
++      Logical Warn
++      Common
++     > / CtqPar2 / Nx, Nt, NfMx
++     > / QCDtable /  Alambda, Nfl, Iorder
++
++      Data Warn /.true./
++      save Warn
++
++      If (X .lt. 0D0 .or. X .gt. 1D0) Then
++        Print *, 'X out of range in Ctq6Pdf: ', X
++        Stop
++      Endif
++      If (Q .lt. Alambda) Then
++        Print *, 'Q out of range in Ctq6Pdf: ', Q
++        Stop
++      Endif
++      If ((Iparton .lt. -NfMx .or. Iparton .gt. NfMx)) Then
++         If (Warn) Then
++C        put a warning for calling extra flavor.
++             Warn = .false.
++             Print *, 'Warning: Iparton out of range in Ctq6Pdf: '
++     >              , Iparton
++         Endif
++         Ctq6Pdf = 0D0
++         Return
++      Endif
++
++      Ctq6Pdf = PartonX6 (Iparton, X, Q)
++      if(Ctq6Pdf.lt.0.D0)  Ctq6Pdf = 0.D0
++
++      Return
++
++C                             ********************
++      End
++
++      Subroutine SetCtq6 (Iset)
++      Implicit Double Precision (A-H,O-Z)
++      Parameter (Isetmax0=4)
++      Character Flnm(Isetmax0)*6, nn*3, Tablefile*40
++      Data (Flnm(I), I=1,Isetmax0)
++     > / 'cteq6m', 'cteq6d', 'cteq6l', 'cteq6l'/
++      Data Isetold, Isetmin0, Isetmin1, Isetmax1 /-987,1,101,140/
++      save
++
++C             If data file not initialized, do so.
++      If(Iset.ne.Isetold) then
++         IU= NextUn6()
++         If (Iset.ge.Isetmin0 .and. Iset.le.3) Then
++            Tablefile=Flnm(Iset)//'.tbl'
++         Elseif (Iset.eq.Isetmax0) Then
++            Tablefile=Flnm(Iset)//'1.tbl'
++         Elseif (Iset.ge.Isetmin1 .and. Iset.le.Isetmax1) Then
++            write(nn,'(I3)') Iset
++            Tablefile=Flnm(1)//nn//'.tbl'
++         Else
++            Print *, 'Invalid Iset number in SetCtq6 :', Iset
++            Stop
++         Endif
++c     Open(IU, File='Pdfdata/'//Tablefile, Status='OLD', Err=100)
++            call OpenData(TableFile)
++ 21      Call ReadTbl6 (IU)
++         Close (IU)
++         Isetold=Iset
++      Endif
++      Return
++
++ 100  Print *, ' Data file ', Tablefile, ' cannot be opened '
++     >//'in SetCtq6!!'
++      Stop
++C                             ********************
++      End
++
++      Subroutine ReadTbl6 (Nu)
++      Implicit Double Precision (A-H,O-Z)
++      Character Line*80
++      PARAMETER (MXX = 96, MXQ = 20, MXF = 5)
++      PARAMETER (MXPQX = (MXF + 3) * MXQ * MXX)
++      Common
++     > / CtqPar1 / Al, XV(0:MXX), TV(0:MXQ), UPD(MXPQX)
++     > / CtqPar2 / Nx, Nt, NfMx
++     > / XQrange / Qini, Qmax, Xmin
++     > / QCDtable /  Alambda, Nfl, Iorder
++     > / Masstbl / Amass(6)
++
++      Read  (Nu, '(A)') Line
++      Read  (Nu, '(A)') Line
++      Read  (Nu, *) Dr, Fl, Al, (Amass(I),I=1,6)
++      Iorder = Nint(Dr)
++      Nfl = Nint(Fl)
++      Alambda = Al
++
++      Read  (Nu, '(A)') Line
++      Read  (Nu, *) NX,  NT, NfMx
++
++      Read  (Nu, '(A)') Line
++      Read  (Nu, *) QINI, QMAX, (TV(I), I =0, NT)
++
++      Read  (Nu, '(A)') Line
++      Read  (Nu, *) XMIN, (XV(I), I =0, NX)
++
++      Do 11 Iq = 0, NT
++         TV(Iq) = Log(Log (TV(Iq) /Al))
++   11 Continue
++C
++C                  Since quark = anti-quark for nfl>2 at this stage,
++C                  we Read  out only the non-redundent data points
++C     No of flavors = NfMx (sea) + 1 (gluon) + 2 (valence)
++
++      Nblk = (NX+1) * (NT+1)
++      Npts =  Nblk  * (NfMx+3)
++      Read  (Nu, '(A)') Line
++      Read  (Nu, *, IOSTAT=IRET) (UPD(I), I=1,Npts)
++
++      Return
++C                        ****************************
++      End
++
++      Function NextUn6()
++C                                 Returns an unallocated FORTRAN i/o unit.
++      Logical EX
++C
++      Do 10 N = 10, 300
++         INQUIRE (UNIT=N, OPENED=EX)
++         If (.NOT. EX) then
++            NextUn6 = N
++            Return
++         Endif
++ 10   Continue
++      Stop ' There is no available I/O unit. '
++C               *************************
++      End
++C
++
++      SUBROUTINE POLINT6 (XA,YA,N,X,Y,DY)
++
++      IMPLICIT DOUBLE PRECISION (A-H, O-Z)
++C                                        Adapted from "Numerical Recipes"
++      PARAMETER (NMAX=10)
++      DIMENSION XA(N),YA(N),C(NMAX),D(NMAX)
++      NS=1
++      DIF=ABS(X-XA(1))
++      DO 11 I=1,N
++        DIFT=ABS(X-XA(I))
++        IF (DIFT.LT.DIF) THEN
++          NS=I
++          DIF=DIFT
++        ENDIF
++        C(I)=YA(I)
++        D(I)=YA(I)
++11    CONTINUE
++      Y=YA(NS)
++      NS=NS-1
++      DO 13 M=1,N-1
++        DO 12 I=1,N-M
++          HO=XA(I)-X
++          HP=XA(I+M)-X
++          W=C(I+1)-D(I)
++          DEN=HO-HP
++          IF(DEN.EQ.0.) stop
++          DEN=W/DEN
++          D(I)=HP*DEN
++          C(I)=HO*DEN
++12      CONTINUE
++        IF (2*NS.LT.N-M)THEN
++          DY=C(NS+1)
++        ELSE
++          DY=D(NS)
++          NS=NS-1
++        ENDIF
++        Y=Y+DY
++13    CONTINUE
++      RETURN
++      END
++
++      Function PartonX6 (IPRTN, XX, QQ)
++
++c  Given the parton distribution function in the array U in
++c  COMMON / PEVLDT / , this routine interpolates to find
++c  the parton distribution at an arbitray point in x and q.
++c
++      Implicit Double Precision (A-H,O-Z)
++
++      Parameter (MXX = 96, MXQ = 20, MXF = 5)
++      Parameter (MXQX= MXQ * MXX,   MXPQX = MXQX * (MXF+3))
++
++      Common
++     > / CtqPar1 / Al, XV(0:MXX), TV(0:MXQ), UPD(MXPQX)
++     > / CtqPar2 / Nx, Nt, NfMx
++     > / XQrange / Qini, Qmax, Xmin
++
++      Dimension fvec(4), fij(4)
++      Dimension xvpow(0:mxx)
++      Data OneP / 1.00001 /
++      Data xpow / 0.3d0 /       !**** choice of interpolation variable
++      Data nqvec / 4 /
++      Data ientry / 0 /
++      Save ientry,xvpow
++
++c store the powers used for interpolation on first call...
++      if(ientry .eq. 0) then
++         ientry = 1
++
++         xvpow(0) = 0D0
++         do i = 1, nx
++            xvpow(i) = xv(i)**xpow
++         enddo
++      endif
++
++      X = XX
++      Q = QQ
++      tt = log(log(Q/Al))
++
++c      -------------    find lower end of interval containing x, i.e.,
++c                       get jx such that xv(jx) .le. x .le. xv(jx+1)...
++      JLx = -1
++      JU = Nx+1
++ 11   If (JU-JLx .GT. 1) Then
++         JM = (JU+JLx) / 2
++         If (X .Ge. XV(JM)) Then
++            JLx = JM
++         Else
++            JU = JM
++         Endif
++         Goto 11
++      Endif
++C                     Ix    0   1   2      Jx  JLx         Nx-2     Nx
++C                           |---|---|---|...|---|-x-|---|...|---|---|
++C                     x     0  Xmin               x                 1
++C
++      If     (JLx .LE. -1) Then
++        Print '(A,1pE12.4)', 'Severe error: x <= 0 in PartonX6! x = ', x
++        Stop
++      ElseIf (JLx .Eq. 0) Then
++         Jx = 0
++      Elseif (JLx .LE. Nx-2) Then
++
++C                For interrior points, keep x in the middle, as shown above
++         Jx = JLx - 1
++      Elseif (JLx.Eq.Nx-1 .or. x.LT.OneP) Then
++
++C                  We tolerate a slight over-shoot of one (OneP=1.00001),
++C              perhaps due to roundoff or whatever, but not more than that.
++C                                      Keep at least 4 points >= Jx
++         Jx = JLx - 2
++      Else
++        Print '(A,1pE12.4)', 'Severe error: x > 1 in PartonX6! x = ', x
++        Stop
++      Endif
++C          ---------- Note: JLx uniquely identifies the x-bin; Jx does not.
++
++C                       This is the variable to be interpolated in
++      ss = x**xpow
++
++      If (JLx.Ge.2 .and. JLx.Le.Nx-2) Then
++
++c     initiation work for "interior bins": store the lattice points in s...
++      svec1 = xvpow(jx)
++      svec2 = xvpow(jx+1)
++      svec3 = xvpow(jx+2)
++      svec4 = xvpow(jx+3)
++
++      s12 = svec1 - svec2
++      s13 = svec1 - svec3
++      s23 = svec2 - svec3
++      s24 = svec2 - svec4
++      s34 = svec3 - svec4
++
++      sy2 = ss - svec2
++      sy3 = ss - svec3
++
++c constants needed for interpolating in s at fixed t lattice points...
++      const1 = s13/s23
++      const2 = s12/s23
++      const3 = s34/s23
++      const4 = s24/s23
++      s1213 = s12 + s13
++      s2434 = s24 + s34
++      sdet = s12*s34 - s1213*s2434
++      tmp = sy2*sy3/sdet
++      const5 = (s34*sy2-s2434*sy3)*tmp/s12
++      const6 = (s1213*sy2-s12*sy3)*tmp/s34
++
++      EndIf
++
++c         --------------Now find lower end of interval containing Q, i.e.,
++c                          get jq such that qv(jq) .le. q .le. qv(jq+1)...
++      JLq = -1
++      JU = NT+1
++ 12   If (JU-JLq .GT. 1) Then
++         JM = (JU+JLq) / 2
++         If (tt .GE. TV(JM)) Then
++            JLq = JM
++         Else
++            JU = JM
++         Endif
++         Goto 12
++       Endif
++
++      If     (JLq .LE. 0) Then
++         Jq = 0
++      Elseif (JLq .LE. Nt-2) Then
++C                                  keep q in the middle, as shown above
++         Jq = JLq - 1
++      Else
++C                         JLq .GE. Nt-1 case:  Keep at least 4 points >= Jq.
++        Jq = Nt - 3
++
++      Endif
++C                                   This is the interpolation variable in Q
++
++      If (JLq.GE.1 .and. JLq.LE.Nt-2) Then
++c                                        store the lattice points in t...
++      tvec1 = Tv(jq)
++      tvec2 = Tv(jq+1)
++      tvec3 = Tv(jq+2)
++      tvec4 = Tv(jq+3)
++
++      t12 = tvec1 - tvec2
++      t13 = tvec1 - tvec3
++      t23 = tvec2 - tvec3
++      t24 = tvec2 - tvec4
++      t34 = tvec3 - tvec4
++
++      ty2 = tt - tvec2
++      ty3 = tt - tvec3
++
++      tmp1 = t12 + t13
++      tmp2 = t24 + t34
++
++      tdet = t12*t34 - tmp1*tmp2
++
++      EndIf
++
++
++c get the pdf function values at the lattice points...
++
++      If (Iprtn .GE. 3) Then
++         Ip = - Iprtn
++      Else
++         Ip = Iprtn
++      EndIf
++      jtmp = ((Ip + NfMx)*(NT+1)+(jq-1))*(NX+1)+jx+1
++
++      Do it = 1, nqvec
++
++         J1  = jtmp + it*(NX+1)
++
++       If (Jx .Eq. 0) Then
++C                          For the first 4 x points, interpolate x^2*f(x,Q)
++C                           This applies to the two lowest bins JLx = 0, 1
++C            We can not put the JLx.eq.1 bin into the "interrior" section
++C                           (as we do for q), since Upd(J1) is undefined.
++         fij(1) = 0
++         fij(2) = Upd(J1+1) * XV(1)**2
++         fij(3) = Upd(J1+2) * XV(2)**2
++         fij(4) = Upd(J1+3) * XV(3)**2
++C
++C                 Use Polint6 which allows x to be anywhere w.r.t. the grid
++
++         Call Polint6 (XVpow(0), Fij(1), 4, ss, Fx, Dfx)
++
++         If (x .GT. 0D0)  Fvec(it) =  Fx / x**2
++C                                              Pdf is undefined for x.eq.0
++       ElseIf  (JLx .Eq. Nx-1) Then
++C                                                This is the highest x bin:
++
++        Call Polint6 (XVpow(Nx-3), Upd(J1), 4, ss, Fx, Dfx)
++
++        Fvec(it) = Fx
++
++       Else
++C                       for all interior points, use Jon's in-line function
++C                              This applied to (JLx.Ge.2 .and. JLx.Le.Nx-2)
++         sf2 = Upd(J1+1)
++         sf3 = Upd(J1+2)
++
++         g1 =  sf2*const1 - sf3*const2
++         g4 = -sf2*const3 + sf3*const4
++
++         Fvec(it) = (const5*(Upd(J1)-g1)
++     &               + const6*(Upd(J1+3)-g4)
++     &               + sf2*sy3 - sf3*sy2) / s23
++
++       Endif
++
++      enddo
++C                                   We now have the four values Fvec(1:4)
++c     interpolate in t...
++
++      If (JLq .LE. 0) Then
++C                         1st Q-bin, as well as extrapolation to lower Q
++        Call Polint6 (TV(0), Fvec(1), 4, tt, ff, Dfq)
++
++      ElseIf (JLq .GE. Nt-1) Then
++C                         Last Q-bin, as well as extrapolation to higher Q
++        Call Polint6 (TV(Nt-3), Fvec(1), 4, tt, ff, Dfq)
++      Else
++C                         Interrior bins : (JLq.GE.1 .and. JLq.LE.Nt-2)
++C       which include JLq.Eq.1 and JLq.Eq.Nt-2, since Upd is defined for
++C                         the full range QV(0:Nt)  (in contrast to XV)
++        tf2 = fvec(2)
++        tf3 = fvec(3)
++
++        g1 = ( tf2*t13 - tf3*t12) / t23
++        g4 = (-tf2*t34 + tf3*t24) / t23
++
++        h00 = ((t34*ty2-tmp2*ty3)*(fvec(1)-g1)/t12
++     &    +  (tmp1*ty2-t12*ty3)*(fvec(4)-g4)/t34)
++
++        ff = (h00*ty2*ty3/tdet + tf2*ty3 - tf3*ty2) / t23
++      EndIf
++
++      PartonX6 = ff
++
++      Return
++C                                       ********************
++      End
 === added file 'Template/NLO/Source/PDF/Partonx5.f'
 --- Template/NLO/Source/PDF/Partonx5.f	1970-01-01 00:00:00 +0000
 +++ Template/NLO/Source/PDF/Partonx5.f	2012-09-28 12:29:27 +0000
@@ -0,0 +1,94 @@
++      FUNCTION PartonX (IPRTN, X, Q)
++C
++C   Given the parton distribution function in the array Upd in
++C   COMMON / CtqPar1 / , this routine fetches u(fl, x, q) at any value of
++C   x and q using Mth-order polynomial interpolation for x and Ln(Q/Lambda).
++C
++      IMPLICIT DOUBLE PRECISION (A-H, O-Z)
++C
++      PARAMETER (MXX = 105, MXQ = 25, MXF = 6)
++      PARAMETER (MXPQX = (MXF *2 +2) * MXQ * MXX)
++      PARAMETER (M= 2, M1 = M + 1)
++C
++      Logical First
++      Common
++     > / CtqPar1 / Al, XV(0:MXX), QL(0:MXQ), UPD(MXPQX)
++     > / CtqPar2 / Nx, Nt, NfMx
++     > / XQrange / Qini, Qmax, Xmin
++C
++      Dimension Fq(M1), Df(M1)
++
++      Data First /.true./
++      save First
++C                                                 Work with Log (Q)
++      QG  = LOG (Q/AL)
++
++C                           Find lower end of interval containing X
++      JL = -1
++      JU = Nx+1
++ 11   If (JU-JL .GT. 1) Then
++         JM = (JU+JL) / 2
++         If (X .GT. XV(JM)) Then
++            JL = JM
++         Else
++            JU = JM
++         Endif
++         Goto 11
++      Endif
++
++      Jx = JL - (M-1)/2
++      If (X .lt. Xmin .and. First ) Then
++         First = .false.
++         Print '(A, 2(1pE12.4))',
++     >     ' WARNING: X < Xmin, extrapolation used; X, Xmin =', X, Xmin
++         If (Jx .LT. 0) Jx = 0
++      Elseif (Jx .GT. Nx-M) Then
++         Jx = Nx - M
++      Endif
++C                                    Find the interval where Q lies
++      JL = -1
++      JU = NT+1
++ 12   If (JU-JL .GT. 1) Then
++         JM = (JU+JL) / 2
++         If (QG .GT. QL(JM)) Then
++            JL = JM
++         Else
++            JU = JM
++         Endif
++         Goto 12
++      Endif
++
++      Jq = JL - (M-1)/2
++      If (Jq .LT. 0) Then
++         Jq = 0
++         If (Q .lt. Qini)  Print '(A, 2(1pE12.4))',
++     >     ' WARNING: Q < Qini, extrapolation used; Q, Qini =', Q, Qini
++      Elseif (Jq .GT. Nt-M) Then
++         Jq = Nt - M
++         If (Q .gt. Qmax)  Print '(A, 2(1pE12.4))',
++     >     ' WARNING: Q > Qmax, extrapolation used; Q, Qmax =', Q, Qmax
++      Endif
++
++      If (Iprtn .GE. 3) Then
++         Ip = - Iprtn
++      Else
++         Ip = Iprtn
++      EndIf
++C                             Find the off-set in the linear array Upd
++      JFL = Ip + NfMx
++      J0  = (JFL * (NT+1) + Jq) * (NX+1) + Jx
++C
++C                                           Now interpolate in x for M1 Q's
++      Do 21 Iq = 1, M1
++         J1 = J0 + (Nx+1)*(Iq-1) + 1
++         Call Polint (XV(Jx), Upd(J1), M1, X, Fq(Iq), Df(Iq))
++ 21   Continue
++C                                          Finish off by interpolating in Q
++      Call Polint (QL(Jq), Fq(1), M1, QG, Ftmp, Ddf)
++
++      PartonX = Ftmp
++C
++      RETURN
++C                        ****************************
++      END
++
 === added file 'Template/NLO/Source/PDF/PhotonFlux.f'
 --- Template/NLO/Source/PDF/PhotonFlux.f	1970-01-01 00:00:00 +0000
 +++ Template/NLO/Source/PDF/PhotonFlux.f	2012-09-28 12:29:27 +0000
@@ -0,0 +1,87 @@
++c/* ********************************************************* */
++c/*  Equivalent photon approximation structure function.   * */
++c/*     Improved Weizsaecker-Williams formula              * */
++c/*   V.M.Budnev et al., Phys.Rep. 15C (1975) 181          * */
++c/* ********************************************************* */
++c   provided by Tomasz Pierzchala - UCL
++
++      real*8 function epa_electron(x,q2max)
++      integer i
++      real*8 x,phi_f
++      real*8 xin
++      real*8 alpha
++      real*8 f, q2min,q2max
++      real*8 PI
++      data PI/3.14159265358979323846/
++
++      data xin/0.511d-3/ !electron mass in GeV
++
++      alpha = .0072992701
++
++C     // x = omega/E = (E-E')/E
++      if (x.lt.1) then
++         q2min= xin*xin*x*x/(1-x)
++         if(q2min.lt.q2max) then
++            f = alpha/2d0/PI*
++     &           (2d0*xin*xin*x*(-1/q2min+1/q2max)+
++     &           (2-2d0*x+x*x)/x*dlog(q2max/q2min))
++
++         else
++           f = 0.
++         endif
++      else
++         f= 0.
++      endif
++c      write (*,*) x,dsqrt(q2min),dsqrt(q2max),f
++      if (f .lt. 0) f = 0
++      epa_electron= f
++
++      end
++
++      real*8 function epa_proton(x,q2max)
++      integer i
++      real*8 x,phi_f
++      real*8 xin
++      real*8 alpha,qz
++      real*8 f, qmi,qma, q2max
++      real*8 PI
++      data PI/3.14159265358979323846/
++
++      data xin/0.938/ ! proton mass in GeV
++
++      alpha = .0072992701
++      qz = 0.71
++
++C     // x = omega/E = (E-E')/E
++      if (x.lt.1) then
++         qmi= xin*xin*x*x/(1-x)
++         if(qmi.lt.q2max) then
++            f = alpha/PI*(phi_f(x,q2max/qz)-phi_f(x,qmi/qz))*(1-x)/x
++         else
++            f=0.
++         endif

MadGraph5_aMC@NLO

Merge lp:~maddevelopers/mg5amcnlo/FKS5 into lp:mg5amcnlo/lts

Commit message

Description of the change

Preview Diff

Subscribers