Too verbose output command

[stloufra]

As we have decided not to print all the DEBUG, should we also omit naming the specific ALOHA routines or at least the <class ... > redundant info? Or is there point of giving this information to ordinary user? @theoheimel @oliviermattelaer @Qubitol

ALOHA: aloha starts to compute helicity amplitudes
ALOHA: aloha creates VVV1 routines
ALOHA: aloha creates FFV1 routines
ALOHA: aloha creates VVVV1 routines
ALOHA: aloha creates VVVV3 routines
ALOHA: aloha creates VVVV4 routines
ALOHA: aloha creates 5 routines in  0.082 s
<class 'aloha.create_aloha.AbstractRoutine'> VVV1
<class 'aloha.create_aloha.AbstractRoutine'> VVV1
<class 'aloha.create_aloha.AbstractRoutine'> FFV1
<class 'aloha.create_aloha.AbstractRoutine'> FFV1
<class 'aloha.create_aloha.AbstractRoutine'> FFV1
<class 'aloha.create_aloha.AbstractRoutine'> FFV1
<class 'aloha.create_aloha.AbstractRoutine'> VVVV1
<class 'aloha.create_aloha.AbstractRoutine'> VVVV1
<class 'aloha.create_aloha.AbstractRoutine'> VVVV3
<class 'aloha.create_aloha.AbstractRoutine'> VVVV3
<class 'aloha.create_aloha.AbstractRoutine'> VVVV4
<class 'aloha.create_aloha.AbstractRoutine'> VVVV4

[stloufra]

Also we could solve:

DEBUG:  [Errno 2] No such file or directory: '**/MadGraph7/input/authors.md' [misc.py at line 2276]

and

❯ ./bin/madgraph
Running MG5 in debug mode

and

load MG5 configuration from input/mg7_configuration.txt

also not sure about:

INFO: Change particles name to pass to MG5 convention

Last suggestion to discuss - wouldn't it be nice if we different colour command prompt then rest of the print (given we have lost the rocket) for ease of use?

[oliviermattelaer]

The "DEBUG: [Errno 2] No such file or directory: '**/MadGraph7/input/authors.md' [misc.py at line 2276]"
is a file created by the release script. Running from github indeed means that such file does not exists, we can mute the error in that case but not that important

[Qubitol]

In general I don't mind having all the debug statements when using a development branch from GitHub, instead of a release.
I support reducing the output logging anyway, knowing the exact classes is maybe too much, even if it crashes it would still show the traceback pointing to the routines creation loop (I'd rather improve the error logging there).