Package Details: madgraph 3.5.7-1

Git Clone URL: https://aur.archlinux.org/madgraph.git (read-only, click to copy)
Package Base: madgraph
Description: MadGraph5_aMC@NLO is a framework that aims at providing all the elements necessary for SM and BSM phenomenology
Upstream URL: https://launchpad.net/mg5amcnlo
Licenses: MIT
Submitter: JP-Ellis
Maintainer: Dylan14
Last Packager: Dylan14
Votes: 4
Popularity: 0.000000
First Submitted: 2016-05-29 14:27 (UTC)
Last Updated: 2024-12-23 21:02 (UTC)

Pinned Comments

ronin commented on 2021-04-06 00:23 (UTC) (edited on 2021-04-06 00:29 (UTC) by ronin)

I updated the package to version 3.1.0. However, the python2 patch is not currently working as of the moment so the only way to run this package and use python2 is to python2 /usr/bin/mg5_aMC. Sorry for the incovenience. I am adopting other madgraph packages as well but for some reason, the sources are all over the place. Not the fault of the previous maintainer, they just updated their website and some of packages are now deprecated (e.g. pythia-pgs). If someone can help, pls contact or comment down below.

EDIT: Notice that when you run the program in python2, it will give you a warning that python2 will be deprecated soon on the last quarter of 2021. It might not be feasible to patch it with python2 but feel free to comment. This is my third package and I am quite new to Arch. Thanks.

Latest Comments

1 2 Next › Last »

aman.up26 commented on 2024-12-23 20:51 (UTC)

ERROR: Failure while downloading https://launchpad.net/mg5amcnlo/3.0/3.5.x/+download/MG5_aMC_v3.5.4.tar.gz Aborting... Failed to build madgraph

MarsSeed commented on 2023-09-06 16:59 (UTC) (edited on 2023-09-06 17:00 (UTC) by MarsSeed)

Hi @Dylan14,

Do you need the madanalysis5 package (optional dependency)?

If so, would you consider adopting and updating that very old orphan with the latest GitHub release?

If not, then I would suggest that you remove the optdepend declaration for that here. In such a case, the currently defunct madanalysis5 PKGBUILD can be dropped from AUR.

ronin commented on 2021-04-06 02:02 (UTC)

Yeah. I saw that announcement. However, MadAnalysis5 still needs python2 to work. I wonder when they will drop support for python2 on that or is MadAnalysis5 still needed?

Note: I am not a Physics student. I am helping a friend so that he can use this package. :D

JP-Ellis commented on 2021-04-06 01:49 (UTC)

@ronin I believe that Python 3 is meant to be supported from MadGraph v3.0 so it is no longer necessary to include the patch (see this announcement). Note that you might want to update the configuration patch to account for any major changes from v2.x to v3.0.

I no longer use MadGraph, hence the lack of updates.

ronin commented on 2021-04-06 00:23 (UTC) (edited on 2021-04-06 00:29 (UTC) by ronin)

I updated the package to version 3.1.0. However, the python2 patch is not currently working as of the moment so the only way to run this package and use python2 is to python2 /usr/bin/mg5_aMC. Sorry for the incovenience. I am adopting other madgraph packages as well but for some reason, the sources are all over the place. Not the fault of the previous maintainer, they just updated their website and some of packages are now deprecated (e.g. pythia-pgs). If someone can help, pls contact or comment down below.

EDIT: Notice that when you run the program in python2, it will give you a warning that python2 will be deprecated soon on the last quarter of 2021. It might not be feasible to patch it with python2 but feel free to comment. This is my third package and I am quite new to Arch. Thanks.

admiralswan commented on 2018-06-25 18:51 (UTC) (edited on 2018-06-25 19:29 (UTC) by admiralswan)

There appears to be a bug in version 8.x of gfortran that causes at least the tutorial process (p p > t t~) to fail to compile for me, as well as additional processes for others.

See here: https://answers.launchpad.net/mg5amcnlo/+question/668703

edit: Actually, this doesn't appear to be a bug. It's more of a was-a-warning now-an-error type thing. You can force it to compile anyway with the "-std=legacy" option.

For this package, a patch to change line 16 of Templates/LO/Source/make_opts from

FFLAGS= -O -w -fbounds-check -fPIC

to

FFLAGS= -O -w -fbounds-check -fPIC -std=legacy

should fix the issue until it gets fixed upstream.

1 2 Next › Last »