Learning Forum

[CMCsupport1]

Good morning,

We have used your Fluent Launcher to develop a quick'n'dirty job scheduler script for our LSF HPC testing environment. Unfortunately, when we try to use it with certain BSUB commands, our Scheduler tells us that our LINUX environment variable FLUENT_ARCH is unknown.

We have tried to use the 'setenv' command after using our known method of creating the ANSYS configuration ('module load ansys'). This doesn't work for us. Why does this error occur? Does this variable have to be set on the command line? We used the standard 'x86_64' environment variable setting for our node, as this was the descriptor that popped up when we used an 'lshosts' command within our LSF system. 

We noticed there is another environment variable setting for our node: 'Inamd64'. Is this the proper designation? Presumably 'Inamd64' stands for 'Intel AMD 64'. If this is also not correct, is there a third designation we could try?

We don't see this error if we launch stand-alone Fluent in this LSF environment. We also don't see this error if we run HPC simulations from within stand-alone Fluent. Please help.

Operating system: CentOS 7.5.x

ANSYS Release: 2019 R1

Node Processors: Intel Xeon w/2 GB RAM per node

Set Simulation Environment: Use 'module load ansys' string in LSF

Simulations: Provided by ANSYS staff as part of your 2019 R1 help

[JakeC]

Hi greigp,

We usually see that error if fluent is being launched from the /ansys_inc/v193/fluent/flient19.3.0/bin directory.

You should be launching from /ansys_inc/v193/fluent/bin

This sets up more of the environment for you as well as adds the version flag:

-r19.3.0

eg:

[testuser@VMHeadNode bin]$ ./fluent

/ansys_inc/v193/fluent/fluent19.3.0/bin/fluent -r19.3.0

 

What is the actual final launch command where you are seeing the issue?

 

Thank you,

Jake

[CMCsupport1]

Good afternoon, Mr. Callery,

We are using a *.sh file piped into a BSUB command. Within this shell file, we are using the incorrect path to the bin/ directory, as you guessed.

Prompt> BSUB < my_fluent_script.sh

Ignoring the simulation-specific settings, the ANSYS start command we included is:

/lsf-share/tools/ansys/ansys.2019r1/v193/fluent/fluent19.3.0/bin/fluent -r19.3.0

Thank you for suggesting this change. Always grateful for ANSYS staff support.

 

 

[JakeC]

Hi greigp,

My pleasure.  Are you all set now?

If so, could you please mark this thread as solved?

Otherwise, please let us know how else we may assist.

Thank you,

Jake

 

[CMCsupport1]

Hello,

Yes, we're moving on to new LSF adventures. Thank you again.