Re: [OMPI devel] Q: Using a hostfile in managed environment?

Hi Ralph, OK, that's pretty much what I thought but wanted to get a sanity check. :-) I'll see if I can reproduce the issue in a more precise manner and open an issue if I find something off in the mapping. Thanks, --tjn

Re: [OMPI devel] Q: Using a hostfile in managed environment?

> On Feb 24, 2017, at 11:57 AM, Thomas Naughton wrote: > > Hi, > > We're trying to track down some curious behavior and decided to take a step > back and check a base assumption. > > When running within a managed environment (job allocation): > >Q: Should you be able

Re: [OMPI devel] define a new ENV variable in etc/openmpi-mca-params.conf

Please re-read my prior email (MCA parameters are not always set as environment variables): https://www.mail-archive.com/devel@lists.open-mpi.org/msg19958.html If you want to read the value of MCA parameters in MPI applications, you should be using the MPI_T API. That will work regardless

[OMPI devel] Q: Using a hostfile in managed environment?

Hi, We're trying to track down some curious behavior and decided to take a step back and check a base assumption. When running within a managed environment (job allocation): Q: Should you be able to use `--hostfile` or `--host` options to operate on a subset of the resources in the

Re: [OMPI devel] define a new ENV variable in etc/openmpi-mca-params.conf

Basically, I like to set apath in the param conf file, and let OMPI broadcast it to each MPI rank.   In the following example, it prints the value as NULL, if I just set it in the conf file. So My question is how to update some ompi base code to make it right?   If I set it in mpirun -mca

Re: [OMPI devel] define a new ENV variable in etc/openmpi-mca-params.conf

It's still not clear what you're trying to do. Are you setting an MCA parameter, or are you trying to forward arbitrary environment variables? Are you working in MPI processes (or executables launched by MPI processes), or in the Open MPI code base itself? Also, Ralph and I chatted: what he

Re: [OMPI devel] define a new ENV variable in etc/openmpi-mca-params.conf

I need this parameter used in my other codes related to ompi,  do I need to register "OMPI_MCA_apath" in some codes in OMPI? if so, usually in which codes?   Dahai  From: "r...@open-mpi.org" To: OpenMPI Devel Sent: Friday, February 24,

Re: [OMPI devel] define a new ENV variable in etc/openmpi-mca-params.conf

I think Jeff got lost in the weeds here. If you define a new MCA param in the default param file, we will automatically pick it up and it will be in the environment of your application. You don’t need to do anything. However, you checked for the wrong envar. Anything you provide is going to

Re: [OMPI devel] define a new ENV variable in etc/openmpi-mca-params.conf

On Feb 24, 2017, at 10:11 AM, Dahai Guo wrote: > > oops, I should use the word "MCA parameters". If I define a MCA parameter > (apath, for example) in etc/openmpi-mca-params.conf, how can function > setup_fork in ompi/orte/mca/schizo/ompi/schizo_ompi.c get its value? I

Re: [OMPI devel] define a new ENV variable in etc/openmpi-mca-params.conf

I mean getenv("OMPI_MCA_apath") in setup_fork. From: Dahai Guo via devel To: Jeff Squyres (jsquyres) ; Dahai Guo ; Open MPI Developers List Cc: Dahai Guo Sent:

Re: [OMPI devel] define a new ENV variable in etc/openmpi-mca-params.conf

oops, I should use the word "MCA parameters". If I define a MCA parameter (apath, for example) in etc/openmpi-mca-params.conf, how can function setup_fork in ompi/orte/mca/schizo/ompi/schizo_ompi.c get its value?  I tried to call getenv("apath") there, which return null.  However, If I defined

Re: [OMPI devel] define a new ENV variable in etc/openmpi-mca-params.conf

On Feb 23, 2017, at 5:44 PM, Dahai Guo via devel wrote: > > If I define a new ENV variable in etc/openmpi-mca-params.conf, what OMPI > codes should I modify in order for this parameter to be delivered to each > rank? I'm not quite sure what you're asking. The

Re: [OMPI devel] ABI Navigator for OpenMPI

That's pretty cool! One minor request: our project's name is "Open MPI", not "OpenMPI". Could you update your listings to reflect the correct name? Thank you! > On Feb 23, 2017, at 11:17 PM, Andrey Ponomarenko > wrote: > > Hello, > > I'd like to present a new