mpirun usually accepts many different arguments, but it seems like this packages assumes that users will only ever use the bare minimum arguments.
In testing GitHub actions with ARM64 macOS runners with OpenMPI, I am not able to run the tests with 4 MPI processes because there are not 4 MPI "slots" on the runner. One workaround for this would be to pass the --oversubscribe flag to mpirun. However, I presently cannot.
On other projects, I usually pass arguments that dictate how to map MPI processes to hardware and how to configure the internode communication.
Should the MPI command interface be expanded to include an arbitrary number of optional keyword arguments that allow users to pass arguments to mpirun? Is this a security issue?
mpirunusually accepts many different arguments, but it seems like this packages assumes that users will only ever use the bare minimum arguments.In testing GitHub actions with ARM64 macOS runners with OpenMPI, I am not able to run the tests with 4 MPI processes because there are not 4 MPI "slots" on the runner. One workaround for this would be to pass the
--oversubscribeflag tompirun. However, I presently cannot.On other projects, I usually pass arguments that dictate how to map MPI processes to hardware and how to configure the internode communication.
Should the MPI command interface be expanded to include an arbitrary number of optional keyword arguments that allow users to pass arguments to
mpirun? Is this a security issue?