|Message: Re: Issue running GEANT4 on Linux cluster - libG4Tree.so isn't loaded||Not Logged In (login)|
Click on the Forum title, e.g. on the "Forums by Category" page, to read a sequence of postings to the Forum and its threads all in one page. If you are only interested in one thread or the thread following a specific posting, click the thread or the posting, which takes you to a smaller page, which contains only the part you are interested in and may be easier to navigate.
Messages are "chained" if there are only replies at the first level, i.e. 1/1.html, 1/1/1.html etc. In case of "chained" messages the message number is replaced by the icon and there is no indentation.
Inline: Display the subject line only or also the text of the posting(s); for the choice "All" the "Outline" choices are switched off.
|1||0||1||no text / full text of posting|
|2||1||All||text for level 1 only / text for All postings|
Outline: Choose the depth of the posting thread, successive toggle controls provide increasing detail.
|1||2||1||2 levels / 1 level (original posting)|
|2||3||2||3 levels / 2 levels|
|3||3||All||3 levels / all levels (all postings)|
Matt Halstead writes: > I have checked on that path in the interactive session on the terminal, > and it is set properly. And if you run the executable, it does find the shared library and starts? > As far as I know, the "#PBS -V" directive in the job file is supposed to > set all the GEANT environment variables when the cluster runs the > executable. Well, that'll be the case provided you interactively configured your G4 environment already (e.g., in your .login or .profile). > From what I've read (namely, the man page for qsub), it says that the -V > option passes "all environment variables in the qsub command's > environment". I've had similar confusion with the LSF batch system we use at SLAC. Try a simple test, submitting a job file with just the command "printenv". Make sure it returns exactly the same results as when you do so interactively. One thing for you to look for is whether you (directly or indirectly) change your LD_LIBRARY_PATH in your .bashrc or .cshrc files. Those script are run for every single process (including child processes or launched batch jobs). If you inappropriately set environment variables in them, you can get weird and unexpected results from batch jobs, from GMake, and from anything else which fork()'s children. Good luck! -- Michael Kelsey
|Inline Depth:||Outline Depth:||Add message:|