Closed hernando closed 7 years ago
Ive got the same issue some weeks back, I think it occurs when the number of processes in the music script and the cluster allocation does not match.
Thanks for your reports. Yes, this is due to some new code lacking proper error reporting. It is easy to fix and should be fixed. Den 22 feb 2016 14:56 skrev "Martin Schulze" notifications@github.com:
Ive got the same issue some weeks back, I think it occurs when the number of processes in the music script and the running environment does not match.
— Reply to this email directly or view it on GitHub https://github.com/INCF/MUSIC/issues/11#issuecomment-187185618.
Any news on this? Thanks!
Not that I'm aware
I'll fix this ASAP.
On Wed, Aug 30, 2017 at 3:44 PM, hernando notifications@github.com wrote:
Not that I'm aware
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/INCF/MUSIC/issues/11#issuecomment-325994392, or mute the thread https://github.com/notifications/unsubscribe-auth/ADcfCSfQ21Jx-ZQOukwOcjJ5cQPCqpGpks5sdWckgaJpZM4HfaM- .
Fixed in commit 4ce74c9.
Running music without mpirun (or equivalent) produces this output:
As far as I remember, the error message used to be clear. This message is not informative to identify the problem.