Received from Ralph Castain on Wed, Apr 08, 2015 at 12:23:28PM EDT:
> Sounds reasonable - I don't have time to work thru it right now, but we can
> look at it once Jeff returns as he wrote all that stuff and might see where to
> make the changes more readily than me.
Made a note of the suggestion
Sounds reasonable - I don’t have time to work thru it right now, but we can
look at it once Jeff returns as he wrote all that stuff and might see where to
make the changes more readily than me.
> On Apr 8, 2015, at 8:43 AM, Lev Givon wrote:
>
> Received from Ralph Castain on Wed, Apr 08, 2015
Received from Ralph Castain on Wed, Apr 08, 2015 at 10:46:58AM EDT:
>
> > On Apr 8, 2015, at 7:23 AM, Lev Givon wrote:
> >
> > The output of ompi_info --parsable is somewhat difficult to parse
> > programmatically because it doesn't escape or quote fields that contain
> > colons,
> > e.g.,
> >
I think the assumption was that people would parse this as follows:
* entry before the first colon is the category
* entry between first and second colons is the subcategory
* everything past the second colon is the value
You are right, however, that the current format precludes the use of an
The output of ompi_info --parsable is somewhat difficult to parse
programmatically because it doesn't escape or quote fields that contain colons,
e.g.,
build:timestamp:Tue Dec 23 15:47:28 EST 2014
option:threads:posix (MPI_THREAD_MULTIPLE: no, OPAL support: yes, OMPI
progress: no, ORTE progress:
