You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have a suggestion if the %r mentioned in the FAQ is still open for discussion.
I have implemented on the application end a generalization of the idea of %r.
Let attribute values contain additional nodename format strings of the form %NT.
N is an integer value 0-9. At present, even a cray does not use more than 10 segments in a name.
T is a segment type
%NT is replaced by the Nth segment of type T appearing in the node name.
In my initial implementation the supported values of T are 'd' (integer substrings), 'm' (substrings separated by '-'), and 'u' (substrings separated by '_'). Note that multiple separators of the - or _ types are collapsed to one, so '--' is equivalent to '-' in this scheme.
I have a suggestion if the %r mentioned in the FAQ is still open for discussion.
I have implemented on the application end a generalization of the idea of %r.
Let attribute values contain additional nodename format strings of the form %NT.
N is an integer value 0-9. At present, even a cray does not use more than 10 segments in a name.
T is a segment type
%NT is replaced by the Nth segment of type T appearing in the node name.
In my initial implementation the supported values of T are 'd' (integer substrings), 'm' (substrings separated by '-'), and 'u' (substrings separated by '_'). Note that multiple separators of the - or _ types are collapsed to one, so '--' is equivalent to '-' in this scheme.
E.g.
yields
This notation allows collapsing definitions in a manner similar to the FAQ %r idea, but with more control.
The exact semantics are given by a bash script below. Equivalent c/c++ are not hard to cook up (I have a c++ version).
The text was updated successfully, but these errors were encountered: