libraries getting a sub-communicator cannot reliably use yogrt

Nobody has claimed this yet.

Tom writes:

> When writing a library rather than an application, we only get a sub-communicator, so we don't know if we have rank 0 of MPI_COMM_WORLD or not. If we don't, we can't get the time remaining. If the restriction is to avoid n simultaneous queries to the scheduler, perhaps a request from rank 0 of any subcommunicator could get the right value.

The reasons for the current restriction that only rank 0 can call yogrt_remaining() and get the remaining time are described in yogrt_remaining(3).

Since not all resource managers have the same limitations on their ability to handle such queries, and the other concerns could be managed by library or application authors, it may be reasonable to relax this restriction for library authors.

Start with the yogrt_remaining(3) documentation and then locate the implementation of yogrt_remaining(). Determine how rank 0 is identified and how scheduler queries are issued for MPI communicators. Done means establishing and implementing a safe policy for rank 0 of a sub-communicator, with corresponding documentation and tests where the behavior is covered.

Written by the indexing model from the issue text.