Ah, I see - yes, you'd get_attribute to retrieve it. Alternatively, you have it sitting right there in an array, so you could just use the array to order the list
On Jun 18, 2014, at 3:47 PM, Pritchard, Howard P <howa...@lanl.gov> wrote: > Hi Ralph, > > It is setting the attribute, but then for some reason there seems to be a > need to have the node ids (nids) in > ascending order, so there’s some code looking at the old launch_id field, > which no longer exists. > > I’m fixing it. I’d like to learn the cycle of getting fixes in to trunk. > > Thanks, > > Howard > > > From: devel [mailto:devel-boun...@open-mpi.org] On Behalf Of Ralph Castain > Sent: Wednesday, June 18, 2014 4:45 PM > To: Open MPI Developers > Subject: Re: [OMPI devel] r31916 question > > Huh - thought I got that. Sorry I missed it. Let me take a look and ensure > that the alps ras module is setting that attribute > > On Jun 18, 2014, at 2:40 PM, Pritchard, Howard P <howa...@lanl.gov> wrote: > > > Hello Folks, > > I’m looking at commit 31916 and notice a lot of fields were remote from > orte_node_t. > This is now preventing ras_alps_module.c from compiling owing to use of a > “launch_id” > field. > > In lieu of the direct use of launch_id, should I replace the code around 587 > of this file with > use of orte_get_attribute with ORTE_NODE_LAUNCH_ID for the attribute to be > retrieved? > > Thanks, > > Howard > > > ------------------------------------------------- > Howard Pritchard > HPC-5 > Los Alamos National Laboratory > > > _______________________________________________ > devel mailing list > de...@open-mpi.org > Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/devel > Link to this post: > http://www.open-mpi.org/community/lists/devel/2014/06/15008.php > > _______________________________________________ > devel mailing list > de...@open-mpi.org > Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/devel > Link to this post: > http://www.open-mpi.org/community/lists/devel/2014/06/15010.php
