spectre wrapper and SGE

M

Mark Valery

Guest
I've used a shell script wrapper in the past to run spectre
with SGE. Soon after setting it up that way, I remember
reading somewhere about using envSetVal or something else
to change what the spectre executable name would be. I
stored it into my porous brain to be used later on
for dynamically changing the executable name.

Well, it leaked out and searching the newsgroups failed.
Does anyone know the command or was I dreaming again?

Thanks,
Mark
 
On Sun, 31 Oct 2004 15:28:04 -0800, Erik Wanta wrote:

Using the following instead of envSetVal gets the option to change for
the current session:
asiSetEnvOptionVal(asiGetCurrentSession() "simExecName" "bsub
spectre")
---
Erik,
Thanks for debugging this. It has taken we longer to fix the
underlying setup of the computers and software that I was
going to try this on. So hopefully next week I'll start to
use what you wrote.
Thanks,
Mark
 
On Wed, 03 Nov 2004 19:48:28 +0100, fogh wrote:

Mark,
do you have no issues with message passing ?
do you also define mpshost ?

I can't remember the command at the moment, but I turned
off interprocess communication with spectre. There are 2
ways that I know of for running spectre from artist. One
keeps a spectre process running inbetween sims and artist
communicates with this process with IPC calls. I don't believe
you would get this to work with SGE without a lot of work.
The second starts up a spectre process for each simulation
run. That was the method I used for SGE.
Mark
 
Mark Valery wrote:
On Wed, 03 Nov 2004 19:48:28 +0100, fogh wrote:


Mark,
do you have no issues with message passing ?
do you also define mpshost ?


I can't remember the command at the moment, but I turned
off interprocess communication with spectre. There are 2
ways that I know of for running spectre from artist. One
keeps a spectre process running inbetween sims and artist
communicates with this process with IPC calls. I don't believe
you would get this to work with SGE without a lot of work.
The second starts up a spectre process for each simulation
run. That was the method I used for SGE.
OK, so you are using batch mode for
spectre.envOpts controlMode
 
Mark,

will you tell your findings to the newsgroups ? I remeber from an
older post that at least Erik is interested too.

Most of what you need is in anasimhelp->env variables->spectre. The one
you mentioned is simExecName
But you will probably have to deal with the "host" or "mpshost" , so
that communication with artist works properlly. You can also set the
mode to "batch", but this slows down parametrics and montecarlos too much.

Mark Valery wrote:
I've used a shell script wrapper in the past to run spectre
with SGE. Soon after setting it up that way, I remember
reading somewhere about using envSetVal or something else
to change what the spectre executable name would be. I
stored it into my porous brain to be used later on
for dynamically changing the executable name.

Well, it leaked out and searching the newsgroups failed.
Does anyone know the command or was I dreaming again?

Thanks,
Mark
 
I set the following while ADE was up and noticed that the simulation
still ran locally.
envSetVal("spectre.envOpts" "simExecName" 'string "bsub spectre")

If I close and reopen ADE then it takes the simExecName setting. Why
doesn't spectre see the envOpts change I made while ADE is up? Any
ideas on how to get spectre to know I changed simExecName while ADE is
up? If so, we could write a simple form that would allow the user to
prefix the run command with any SGE or LSF command.
---
Erik

oghdayan <oghdayan_AT@xs4all_dot.nl> wrote in message news:<41850b16$0$59950$e4fe514c@dreader10.news.xs4all.nl>...
Mark,

will you tell your findings to the newsgroups ? I remeber from an
older post that at least Erik is interested too.

Most of what you need is in anasimhelp->env variables->spectre. The one
you mentioned is simExecName
But you will probably have to deal with the "host" or "mpshost" , so
that communication with artist works properlly. You can also set the
mode to "batch", but this slows down parametrics and montecarlos too much.

Mark Valery wrote:
I've used a shell script wrapper in the past to run spectre
with SGE. Soon after setting it up that way, I remember
reading somewhere about using envSetVal or something else
to change what the spectre executable name would be. I
stored it into my porous brain to be used later on
for dynamically changing the executable name.

Well, it leaked out and searching the newsgroups failed.
Does anyone know the command or was I dreaming again?

Thanks,
Mark
 
Using the following instead of envSetVal gets the option to change for
the current session:
asiSetEnvOptionVal(asiGetCurrentSession() "simExecName" "bsub
spectre")
---
Erik

oghdayan <oghdayan_AT@xs4all_dot.nl> wrote in message news:<41850b16$0$59950$e4fe514c@dreader10.news.xs4all.nl>...
Mark,

will you tell your findings to the newsgroups ? I remeber from an
older post that at least Erik is interested too.

Most of what you need is in anasimhelp->env variables->spectre. The one
you mentioned is simExecName
But you will probably have to deal with the "host" or "mpshost" , so
that communication with artist works properlly. You can also set the
mode to "batch", but this slows down parametrics and montecarlos too much.

Mark Valery wrote:
I've used a shell script wrapper in the past to run spectre
with SGE. Soon after setting it up that way, I remember
reading somewhere about using envSetVal or something else
to change what the spectre executable name would be. I
stored it into my porous brain to be used later on
for dynamically changing the executable name.

Well, it leaked out and searching the newsgroups failed.
Does anyone know the command or was I dreaming again?

Thanks,
Mark
 
Mark,
do you have no issues with message passing ?
do you also define mpshost ?

Mark Valery wrote:
On Sun, 31 Oct 2004 15:28:04 -0800, Erik Wanta wrote:


Using the following instead of envSetVal gets the option to change for
the current session:
asiSetEnvOptionVal(asiGetCurrentSession() "simExecName" "bsub
spectre")
---


Erik,
Thanks for debugging this. It has taken we longer to fix the
underlying setup of the computers and software that I was
going to try this on. So hopefully next week I'll start to
use what you wrote.
Thanks,
Mark
 

Welcome to EDABoard.com

Sponsor

Back
Top