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
rv1 and JGF can sometimes disagree on what properties a node has, and also what rank it represents. This can lead to very ugly problems.
For instance, if nodes are given queue properties in R but node vertices in JGF don't have those same properties, jobs will never be scheduled, but no error occurs (see #1350). Also, nodes can be given ranks in JGF that don't align with their ranks in R, raising execution-time problems.
For properties, one idea would be to add all properties from R in addition to whatever properties are found in JGF. Ranks should be validated.
See also #1219, for some discussion of a case where this occurred.
The text was updated successfully, but these errors were encountered:
rv1 and JGF can sometimes disagree on what properties a node has, and also what rank it represents. This can lead to very ugly problems.
For instance, if nodes are given queue properties in
R
but node vertices in JGF don't have those same properties, jobs will never be scheduled, but no error occurs (see #1350). Also, nodes can be given ranks in JGF that don't align with their ranks in R, raising execution-time problems.For properties, one idea would be to add all properties from
R
in addition to whatever properties are found in JGF. Ranks should be validated.See also #1219, for some discussion of a case where this occurred.
The text was updated successfully, but these errors were encountered: