Pedro,
Back in 2003 I had a script to run Nastran
with LAM and SGE. I no longer have SGE on
any of my systems, so I can’t verify
it works now, but here is the script.
#! /bin/ksh
#
# sge_nast:
SunGridEngine script to use with
#
MSC.Nastran V2001.0.9 and greater.
#
# Usage: qsub -pe
$PAR_ENV $Nproc sge_nast
#
#Set input file,
can be an argument, but hardcoded for this test:
DAT=/lhome/jjg/TEST.dat
#
cd
${SGE_O_WORKDIR}
#
#Set up hosts:
#
HOSTS=""
while read FILE
do
NODE=`echo $FILE | awk '{ print $1}'`
HOST0="$HOSTS"
HOSTS="$HOST0:$NODE"
done <
$PE_HOSTFILE
# Remove leading
':'
HOSTS=`echo
$HOSTS | sed 's/://'`
#
# Got hosts, now
run Nastran:
nast2003t2 ${DAT}
dmp=${NSLOTS} scr=yes bat=no hosts=$HOSTS
#
# End
Regards,
From:
users-bounces@open-mpi.org [mailto:users-bounces@open-mpi.org] On Behalf Of Pedro G
Sent: Monday, October 20, 2008
6:21 AM
To:
Subject: Re: [OMPI users] Question
about openmpi and msc nastran
Ok I will try it.
Thank you very much.
On 10/20/08, Reuti
<reuti@staff.uni-marburg.de>
wrote:
Am 20.10.2008 um 14:17
schrieb Pedro G:
On 10/20/08, Reuti <reuti@staff.uni-marburg.de> wrote: Hi,
Am 20.10.2008 um 12:18 schrieb Pedro G:
I would like to know if Msc Nastran
I have been searching in google about Nastran and Openmpi but I couldn't find
if it works or not.
Now I'm using lam/mpi for nastran parallel jobs, but I have some problems with
lam, nastran and sge, so I'd like to upgrade to openmpi.
do you have the source code of the application? If you have only the binary compiled
for LAM, then you can't do anything to change. You checked the LAM/MPI Howto at
the SGE website?
No, I don't have the source code, the application seems to be able to work with
openmpi since it has an option openmpi=yes in the command line, but I couldn't
make it to work. Anyway, I think it is not fully
About LAM/MPI I have already read the howto and did a tight integration. The
problem is that Msc Nastran in parallel jobs start a new lam environment get
I contacted with Nastran and they told that was a LAM/MPI or SGE problem.
No, IMO it's not. When they start a new LAM/MPI environment, they are viola
- Suppose you have a tight LAM/MPI integration for other MPI programs.
- In your jobscript, change the $PATH, so that the found "lamboot"
points to e.g. /bin/true - i.e. doing nothing.
- When they then call "mpirun C", they should get the already started
LAM daemons.
- If mpiexec is not working, maybe the found mpiexec must also point to a
script to supply the proper "-np ..." values.
- When they call "mpiexec" in one-shot-mode, it must also be mapped
to a script to execute just the program, but not to do a "lamboot".
-- Reuti
-- Reuti
_______________________________________________
users mailing list
users@open-mpi.org
http://www.open-mpi.org/mailman/listinfo.cgi/users
_______________________________________________
users mailing list
users@open-mpi.org
http://www.open-mpi.org/mailman/listinfo.cgi/users
_______________________________________________
users mailing list
users@open-mpi.org
http://www.open-mpi.org/mailman/listinfo.cgi/users