SciClone Local Manual
Because every instance of Möbius accesses network configuration information through the same file ($HOME/.mobius/network.cp), simultaneous execution of more than one copy of Möbius by a single user through PBS or TORQUE is problematic. pbsmobius partially circumvents this problem by creating a .network.cp file in the user's local scratch directory (/local/scr/$USER) and then installing a symbolic link in ~/.mobius/network.cp to reference this local file. This will permit multiple Möbius jobs belonging to a single user to execute properly on different nodes, but care should be taken to ensure that the nodespecs used with qlogin or "qsub -I" cannot be mapped to the same node at runtime. One simple way to ensure this is to request all of the available processors on a node. For example, on SciClone's dual processor "c8" nodes, the nodespecs used in the following commands would allocate both processors, thereby preventing TORQUE from scheduling any other jobs on the same node:
Note that this technique is inefficient if the Möbius job is essentially serial, i.e,. unable to effectively exploit multiple processors in the back end simulator or solver. In this case the extra allocated processor(s) will be held idle and unavailable for other work.
qlogin -t 120 1:c8:ppn=2
qsub -I -l walltime=02:00:00 -l nodes=1:c8:ppn=2
MOBIUS_HOMEenvironment variable to determine which version of Möbius to use. This variable is automatically set when the user loads the mobius environment module. For more info, see the Möbius documentation page. pbsmobius also depends on several environment variables which are automatically set when running within a TORQUE or PBS environment.