Michael and Reuti made some good suggestions.
- Don't confuse OpenMP with Open MPI.
- The OMPI_NUM_THREADS environment variable is an OpenMP thing, not
an Open MPI thing, so it will have no effect here. You might as well
remove it from your PBS script (it won't have any effect on LAM,
eit
On Oct 12, 2006, at 8:23 AM, amane001 wrote:
Thanks for your reply. I actually meant OpenMPI
Am 12.10.2006 um 09:52 schrieb amane001:
> the code below. Even if I set the OMP_NUM_THREADS = 2, the print
> setenv OMP_NUM_THREADS 2
These are OpenMP, not OpenMPI environmental variables.
/u
Thanks for your reply. I actually meant OpenMPI (from open-mpi.org) and I
have compiled that using
./configure FC=ifort F77=ifort F90=ifort --prefix=$OPENMP_DIR
I may be asking some dumb questions here, but I'm really a beginner to
please bear with me.
~Amane
On 10/12/06, Reuti wrote:
Hi,
Hi,
Am 12.10.2006 um 09:52 schrieb amane001:
Hello all,
I recently switched to OpenMP from LAM-MPI for my code. I'm trying
to run my test code with a PBS scheduler on our local cluster. The
PBS script is shown below. When the job is executed however, only
one CPU is used for running the
Hello all,
I recently switched to OpenMP from LAM-MPI for my code. I'm trying to run my
test code with a PBS scheduler on our local cluster. The PBS script is shown
below. When the job is executed however, only one CPU is used for running
the test.exe. Another more confusing aspect is the fact th
