I joined this list on time to see the discussion of the merge, so I'm
expecting the update, but thanks for the heads up. Until I saw the mail
about that, I hadn't realized the ORTE stuff was developed separately...now I
understand why the trunk version was left uncompilable so long :-).
What
On Feb 12, 2008, at 4:09 PM, ejon wrote:
I'll definitely plan an upgrade to the latest LSF release (7.0
update 2),
then. Given the roadmap, I think I'm way better off forging ahead
with MPI
on LSF than implementing a separate solution. I didn't really expect
production-ready code at this p
Thanks for response, Jeff.
I'll definitely plan an upgrade to the latest LSF release (7.0 update 2),
then. Given the roadmap, I think I'm way better off forging ahead with MPI
on LSF than implementing a separate solution. I didn't really expect
production-ready code at this point. Just chec
There are two issues:
- You must have a recent enough version of LSF. I'm afraid I don't
remember the LSF version number offhand, but we both (OMPI and LSF)
had to make some changes/fixes to achieve compatibility.
- LSF compatibility in OMPI is scheduled for v1.3 (i.e., it doesn't
exist
Jeff and I chatted about this today, in fact. We know the LSF support is
borked, but neither of us had time right now to fix it. We plan to do so,
though, before the 1.3 release - just can't promise when.
Ralph
On 2/11/08 8:00 AM, "Eric Jones" wrote:
> Greetings, MPI mavens,
>
> Perhaps this
Greetings, MPI mavens,
Perhaps this belongs on users@, but since it's about development status
I thought I start here. I've fairly recently gotten involved in getting
an MPI environment configured for our institute. We have an existing
LSF cluster because most of our work is more High-Throug
