On 05/16/2013 10:13 PM, Tim Prince wrote:
On 5/16/2013 2:16 PM, Geraldine Hochman-Klarenberg wrote:
Maybe I should add that my Intel C++ and Fortran compilers are
different versions. C++ is 12.0.2 and Fortran is 13.0.2. Could that
be an issue? Also, when I check for the location of ifort, it se
Hi Edgar,
wow, lets try again in english :-)
can you maybe detail more precisely what scenario you are particularly
worried about? I would think that the return code of the operation
is reliable on whether opening the file was successful or not (i.e.
MPI_SUCCESS vs. anything else).
If I open
wow, lets try again in english :-)
can you maybe detail more precisely what scenario you are particularly
worried about? I would think that the return code of the operation
is reliable on whether opening the file was successful or not (i.e.
MPI_SUCCESS vs. anything else).
Edgar
On 5/17/2013 7:55
can you maybe detail more precisely what scenario you are particularly
worried about? I would think that the return code of the operation
should be reliable on whether opening the file successful or (i.e.
MPI_SUCCESS vs. anything else).
Edgar
On 5/17/2013 4:00 AM, Peter van Hoof wrote:
> Dear use
Guys,
Many thanks for your replies. It has been confirmed by Torque people
that the version 2.5.x has this limitation and they are recommending to
upgrade it to 4.2.x.
Qamar Nazir
Best Regards,
*Qamar Nazir*
On 05/16/2013 05:52 PM, Gus Correa wrote:
Hi Qamar
I don't have a cluster as lar
Dear users,
I have been banging my head against the wall for some time to find a
reliable and portable way to determine if a call to MPI::File::Open()
was successful or not.
Let me give some background information first. We develop an open-source
astrophysical modeling code called Cloudy. Th
