11 | | || MadEvent interface || ** || J+M || MadEvent subprocess directories automatically generated by MG5 || |
12 | | || MG5 fully scriptable || ** || O || Possibility to create/clean/export/create web page whitout leaving MG5 (i.e. you don't need a script newprocess_mg5 and/or to make cp Template My_run) || |
13 | | || decay chains || ** || J || Definition of decay chains, reusing the helas calls for the different ingredient processes (core process and decay processes). || |
| 11 | || automatic comparison of matrix elements with MG4 || ** || M || Scripts for running automatic comparison of the matrix elements for a set of processes between MG4 and MG5 || |
| 12 | || MG5 on the Web || ** || O || Possibility to choose MG5 instead of MG4 for the Web interface. Make sure also MG5-style decay chain syntax is supported! || |
| 13 | || test cmdline || * || O || Possibility to test the cmd_interface module. || |
| 14 | || C++ output || * || J || Generation of matrix element files and Helas calls in C++ || |
| 15 | || Pythia 8 process interface || ** || J || Generation of matrix elements for Pythia 8 || |
18 | | || memory and time profiling and optimization || ** || J+M || Time and memory profiling should be done, to find possible simple improvements. In particular memory might be(come) crucial for generation of e.g. pp > X jjjj and similar multiprocesses with huge numbers of diagrams. || |
19 | | || automatic comparison of matrix elements with MG4 || ** || M || Scripts for running automatic comparison of the matrix elements for a set of processes between MG4 and MG5 || |
20 | | || MG4->MG5 proc_card || ** || O || Translation of the MG4 proc_card into cmd_interface calls for MG5. || |
21 | | || MG5 on the Web || ** || O || Possibility to choose MG5 instead of MG4 for the Web interface. Make sure also MG5-style decay chain syntax is supported! || |
22 | | || history || * || O || Possibility to see the history of command and to write those in a files. |
23 | | || test cmdline || * || O || Possibility to test the cmd_interface module. || |
24 | | |
45 | | || save amps || * || T+J || 0.3.0 || All the generated amplitudes are saved using a proprietary format which can be read back. || |
46 | | || export amps || *** || T+J || 0.3.0 || The generated amplitudes are exported to various formats which can be read by ME/Pythia8/... || |
47 | | || color || *** || F+M || 0.3.0 || Given a specific diagram, with specific vertices and particles, MG computes the color contribution by contracting the various color "strings" || |
48 | | || save diagrams || * || J || 0.3.0 || The generated diagrams are saved with a specific proprietary format. || |
49 | | || multiprocesses || ** || J+T || 0.3.0 || Multiparticle labels and multiple processes. Identical processes are grouped in an efficient way. Possibility to run multiprocess generation in parallel? || |
50 | | || orders || ** || M+J || 0.3.0 || User can enter max order for diagram generation || |
51 | | || save model || * || J || 0.3.0 || All the model content is saved using a proprietary format which can be read back. || |
| 40 | || save amps || * || 0.3.0 || T+J|| All the generated amplitudes are saved using a proprietary format which can be read back. || |
| 41 | || export amps || *** || 0.3.0 || T+J || The generated amplitudes are exported to various formats which can be read by ME/Pythia8/... || |
| 42 | || color || *** || 0.3.0 || F+M || Given a specific diagram, with specific vertices and particles, MG computes the color contribution by contracting the various color "strings" || |
| 43 | || save diagrams || * || 0.3.0 || J || The generated diagrams are saved with a specific proprietary format. || |
| 44 | || multiprocesses || ** || 0.3.0 || J+T || Multiparticle labels and multiple processes. Identical processes are grouped in an efficient way. Possibility to run multiprocess generation in parallel? || |
| 45 | || orders || ** || 0.3.0 || M+J || User can enter max order for diagram generation || |
| 46 | || save model || * || 0.3.0 || J || All the model content is saved using a proprietary format which can be read back. || |
| 47 | || MadEvent interface || ** || 0.4.0 || J+M || MadEvent subprocess directories automatically generated by MG5 || |
| 48 | || MG5 fully scriptable || ** || 0.4.0 || O || Possibility to create/clean/export/create web page whitout leaving MG5 (i.e. you don't need a script newprocess_mg5 and/or to make cp Template My_run) || |
| 49 | || decay chains || ** || 0.4.0 || J || Definition of decay chains, reusing the helas calls for the different ingredient processes (core process and decay processes). || |
| 50 | || memory and time profiling and optimization || ** || 0.4.0 || J+M || Time and memory profiling should be done, to find possible simple improvements. In particular memory might be(come) crucial for generation of e.g. pp > X jjjj and similar multiprocesses with huge numbers of diagrams. || |
| 51 | || MG4->MG5 proc_card || ** || 0.4.0 || O || Translation of the MG4 proc_card into cmd_interface calls for MG5. || |
| 52 | || history || * || 0.4.0 || O || Possibility to see the history of command and to write those in a files. |