Hi Elie
I really think you need to direct your questions to the EPW and QE lists
or developers.
This is clearly a problem in their configuration scripts and makefiles,
which they should address.
Otherwise, since it works here it should work for you also,
assuming you follow the same recipe that
Something else I have realized. Within the make.sys file of espresso-4.0.3, I
have got:
IFLAGS = -I../includeMODFLAGS = -I./ -I../Modules -I../iotk/src
\ -I../PW -I../PH
Which are lacking other stuff such as
LIBOBJS = ../../flib/ptools.a ../../flib/flib.a \
> ../
Jeff,
Some limited testing shows that that srun does seem to work where the
quote-y one did not. I'm working with our admins now to make sure it let's
the prolog work as expected as well.
I'll keep you informed,
Matt
On Thu, Sep 4, 2014 at 1:26 PM, Jeff Squyres (jsquyres)
wrote:
> Try this (t
Dear Gus,
Firstly I really need to thank you for the effort you are doing to help me and
write all these e-mails and in details explaining every step.Secondly, I did
all what you wrote; the EPW is indeed inside the QE espresso but I still get
the same annoying error. I actually deleted all the t
Try this (typed in editor, not tested!):
#! /usr/bin/perl -w
use strict;
use warnings;
use FindBin;
# Specify the path to the prolog.
my $prolog = '--task-prolog=/gpfsm//.task.prolog';
# Build the path to the SLURM srun command.
my $srun_slurm = "${FindBin::Bin}/srun.slurm";
# Add the
Jeff,
Here is the script (with a bit of munging for safety's sake):
#! /usr/bin/perl -w
use strict;
use warnings;
use FindBin;
# Specify the path to the prolog.
my $prolog = '--task-prolog=/gpfsm//.task.prolog';
# Build the path to the SLURM srun command.
my $srun_slurm = "${FindBin::
Hi Elie
The executable generated in my computer will be useless to you,
because these days most if not all libraries linked to an executable are
dynamic/shared libraries.
You won't have the same in your computer, or the equivalent will be
located in different places, may be from different version
Still begs the bigger question, though, as others have used script wrappers
before - and I'm not sure we (OMPI) want to be in the business of dictating the
scripting language they can use. :-)
Jeff and I will argue that one out
On Sep 4, 2014, at 7:38 AM, Jeff Squyres (jsquyres) wrote:
> Ah,
Ah, if it's perl, it might be easy. It might just be the difference between
system("...string...") and system(@argv).
Sent from my phone. No type good.
On Sep 4, 2014, at 8:35 AM, "Matt Thompson"
mailto:fort...@gmail.com>> wrote:
Jeff,
I actually misspoke earlier. It turns out our srun is a *
Just to help separate out the issues, you might try running the hello_c program
in the OMPI examples directory - this will verify whether the problem is in the
mpirun command or in your program
On Sep 4, 2014, at 6:26 AM, Donato Pera wrote:
> Hi,
>
> the text was on the file.err file in the
Hi,
the text was on the file.err file in the file.out file I get only the name
of the node where the program run.
Thanks Donato.
On 04/09/2014 15:14, Reuti wrote:
> Hi,
>
> Am 04.09.2014 um 14:43 schrieb Donato Pera:
>
>> using this script :
>>
>> #!/bin/bash
>> #$ -S /bin/bash
>> #$ -pe orte 6
Hi,
Am 04.09.2014 um 14:43 schrieb Donato Pera:
> using this script :
>
> #!/bin/bash
> #$ -S /bin/bash
> #$ -pe orte 64
> #$ -cwd
> #$ -o ./file.out
> #$ -e ./file.err
>
> export LD_LIBRARY_PATH=/home/SWcbbc/openmpi-1.6.5/lib:$LD_LIBRARY_PATH
> export OMP_NUM_THREADS=1
>
> CPMD_PATH=/home/tan
Hi,
using this script :
#!/bin/bash
#$ -S /bin/bash
#$ -pe orte 64
#$ -cwd
#$ -o ./file.out
#$ -e ./file.err
export LD_LIBRARY_PATH=/home/SWcbbc/openmpi-1.6.5/lib:$LD_LIBRARY_PATH
export OMP_NUM_THREADS=1
CPMD_PATH=/home/tanzi/myroot/X86_66intel-mpi/
PP_PATH=/home/tanzi
/home/SWcbbc/openmpi-1.6
Jeff,
I actually misspoke earlier. It turns out our srun is a *Perl* script
around the SLURM srun. I'll speak with our admins to see if they can
massage the script to not interpret the arguments. If possible, I'll ask
them if I can share the script with you (privately or on the list) and
maybe you
On Sep 3, 2014, at 9:27 AM, Matt Thompson wrote:
> Just saw this, sorry. Our srun is indeed a shell script. It seems to be a
> wrapper around the regular srun that runs a --task-prolog. What it
> does...that's beyond my ken, but I could ask. My guess is that it probably
> does something that h
15 matches
Mail list logo
