-
Notifications
You must be signed in to change notification settings - Fork 37
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Starting MUSIC with too many MPI process generates cryptic message #43
Comments
This is a bug and should be trivial to fix.
Thank you for the report!
…On Wed, Oct 18, 2017 at 4:25 PM, Jakob Jordan ***@***.***> wrote:
When running a music script in which x executables are defined with x + 1
MPI processes, the following error message results:
music: ../../src/application_mapper.cc:187: void MUSIC::ApplicationMapper::mapApplications(): Assertion `config_->getDict().size() != 0' failed.
This should be replaced with a more informative error message, as it is
the case when not enough MPI processes are passed.
Error in MUSIC library: configuration file specifies 3 MPI processes but MUSIC was given 2
I this a genuine bug or just me misinterpeting the output?
I haven't looked at the code yet, so I can't promise a PR.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#43>, or mute the thread
<https://github.com/notifications/unsubscribe-auth/ADcfCWW77BiKNP1AeHYQAg0Y7LjMqzv7ks5stgpXgaJpZM4P9zLc>
.
|
OK, I'll look into it. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When running a music script in which x executables are defined with x + 1 MPI processes, the following error message results:
This should be replaced with a more informative error message, as it is the case when not enough MPI processes are passed.
Error in MUSIC library: configuration file specifies 3 MPI processes but MUSIC was given 2
I this a genuine bug or just me misinterpeting the output?
I haven't looked at the code yet, so I can't promise a PR.
The text was updated successfully, but these errors were encountered: