You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If in the config file, one section is missing the np enttry, in ApplicationMapper::mapApplications () it is assigned a random(?) value. The resulting error reads something like the following:
Error in MUSIC library: configuration file specifies 32579 MPI processes but MUSIC was given 3
Instead, MUSIC should raise a proper error message complaining that np is missing.
It seems like there should in general be a function right after (cfile_->load (*configFile)) in ApplicationMapper::map that checks the validity of the config file. That way one could also check for all other errors arising from wrong specifications in the config file. Is there something like that already and I'm missing it?
The text was updated successfully, but these errors were encountered:
I would like to revise my opinion. I think no error should be thrown, instead MUSIC should assume that if np is not provided, this application only uses one process. Other opinions?
On Thu, Oct 19, 2017 at 3:33 PM, Jakob Jordan ***@***.***> wrote:
I would like to revise my opinion. I think no error should be thrown,
instead MUSIC should assume the if np is not provided, this application
only uses one process. Opinions?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#45 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/ADcfCQRFQ3Vqoqgl3_U2eGp0QEECRNypks5st0-XgaJpZM4P9-eG>
.
If in the config file, one section is missing the
np
enttry, inApplicationMapper::mapApplications ()
it is assigned a random(?) value. The resulting error reads something like the following:Instead, MUSIC should raise a proper error message complaining that
np
is missing.It seems like there should in general be a function right after
(cfile_->load (*configFile))
inApplicationMapper::map
that checks the validity of the config file. That way one could also check for all other errors arising from wrong specifications in the config file. Is there something like that already and I'm missing it?The text was updated successfully, but these errors were encountered: