NetQMPI programs currently lack a standardized way to receive program arguments (argc/argv) or equivalent, unlike MPI where applications can access command-line parameters passed via MPI_Init/main.
This makes it hard to run parameterized NetQMPI examples (e.g., varying problem size, runtime options) without ad-hoc environment hacks.
Running an MPI example typically allows mpirun -n 4 ./app arg1 arg2 and each process receives argv.
With NetQMPI there is no documented, consistent mechanism to pass arg1 arg2 through the runtime and adapters (e.g., NetQASM adapter).
NetQMPI programs currently lack a standardized way to receive program arguments (argc/argv) or equivalent, unlike MPI where applications can access command-line parameters passed via MPI_Init/main.
This makes it hard to run parameterized NetQMPI examples (e.g., varying problem size, runtime options) without ad-hoc environment hacks.
Running an MPI example typically allows
mpirun -n 4 ./app arg1 arg2and each process receives argv.With NetQMPI there is no documented, consistent mechanism to pass arg1 arg2 through the runtime and adapters (e.g., NetQASM adapter).