this is a very related question/observation so I did not want to start a new thread.
I have the feeling that something went wrong when you had to change the StdHep format. Under vendor/StdHEP/ in the Madgraph installation I see that even though version v5_06_01 is quoted, the StdHep code is modified. This is fine, but in my case it seems that the standard commands provided by StdHep to read events from the hep file lead to errors, i.e. one cannot read the event files anymore.
For instance the program vendor/StdHEP/example/testCInOut.c cannot read the HERWIG hep file produced by the current version of MG5 - StdHepXdrRead() does not read the event. The same thing worked in prior versions of MG5, I explicitly checked.
This is also why the conversion program no longer works. Is this behaviour intended or possible to evade?
Hi Pavel, hi Olivier,
this is a very related question/ observation so I did not want to start a new thread.
I have the feeling that something went wrong when you had to change the StdHep format. Under vendor/StdHEP/ in the Madgraph installation I see that even though version v5_06_01 is quoted, the StdHep code is modified. This is fine, but in my case it seems that the standard commands provided by StdHep to read events from the hep file lead to errors, i.e. one cannot read the event files anymore.
For instance the program vendor/ StdHEP/ example/ testCInOut. c cannot read the HERWIG hep file produced by the current version of MG5 - StdHepXdrRead() does not read the event. The same thing worked in prior versions of MG5, I explicitly checked.
This is also why the conversion program no longer works. Is this behaviour intended or possible to evade?
Best
emmanuel