Sciences and methods > Chemistry > Materials Studio related files > How to run standalone jobs in Murska
 
Tehdyt toimenpiteet

How to run standalone jobs in Murska

This page describes how to run standalone serial and parallel jobs in murska.csc.fi.

Preparing the job

First you should prepare your system and set all parameters for the calculation in Materials Studio Visualizer. Then, instead of running the job on your desktop computer, press "files" (next to the "run" button). This will write all necessary files to run the job remotely in standalone mode on your hard disk. Before this make sure the job name is sensible - not too long, and without white spaces in it. This will be the "basename" of your files. The name can be changed in the left panel (project browser, by right clicking) in Visualizer. We now assume you changed it into

ms_basename

If you don't know where the files ended up, you can study this by right clicking one of the files in the project browser and choosing "properties". The next step is to transfer the files onto Murska. The easiest way is to zip all files together, and copy them with scp to Murska (your ssh-client might also have a file transger functionality). In Murska, create a subdirectory for the calculation in your work-area ($WRKDIR) and copy the zip file there. A windows zip-file can be opened with the

 unzip

command. The files are in dos-format. You must first convert them into unix format. This is done with the command:

dos2unix ms_basename*

Note that some of the files (at least *.car) are "hidden" in WindowsXP by default. This means that those files would not be included in the zip-file. If you do not see a file called ms_basename.car in the directory with the other files do the following:

1) Go to the folder where you have the files with windows explorer.

2) Select "tools" from the pull-down menus and there "folder options".

3) Now select the "view" leaf (or page), click "show hidden files" active, and create the zip-file again.

Now the input-files for DMol3 are ready and all we need is the script to submit the job for the PBS queuing system.

Note also, that before you zip and copy back the result files to your Windows computer into the original project folder, remember to convert the files back to dos-format (with unix2dos *)

Serial DMol3-job

#!/bin/bash
#BSUB -oo job.out
#BSUB -W 24:00
#BSUB -J hommaa

DMOL3PATH=/fs/local/linux26_x86_64/appl/chem/accelrys/MS/latest/etc/DMol3/bin
BASENAME=ms_basename

$DMOL3PATH/RunDMol3.sh $BASENAME

In the script you must replace the ms_basename with the "basename" of the files printed out by Materials Studio as described above. If there are a lot of jobs running on the machine, guessing the requested time well will shorten the time it takes for your job to get running. If you want to give additional input to the RunDMol3.sh script, you can get the help message by giving

/fs/local/linux26_x86_64/appl/chem/accelrys/MS/latest/etc/DMol3/bin/RunDMol3.sh

without any arguments.

Parallel DMol3 jobs


Example of a script file for running DMol3 in parallel in Murska:

#!/bin/bash
#BSUB -n 4
#BSUB -oo job.out
#BSUB -W 12:00
#BSUB -J hommaa

DMOL3PATH=/fs/local/linux26_x86_64/appl/chem/accelrys/MS/latest/etc/DMol3/bin
BASENAME=ms_basename

$DMOL3PATH/RunDMol3.sh -np $SLURM_NPROCS $BASENAME

Submitting the job into the queuing system

Supposing that you have put a script like those above in a file called nobel.job, it can be submitted with command

bsub < nobel.job

The job status can be displayed by command

bjobs

A running or queuing job can be cancelled

bkill job_id

Running other module jobs

Also some other Materials Studio modules can be run in standalone mode. All steps to accomplish this is as above for DMol3, but only running the jobs has a different command. For example, to run a CASTEP job you would need to replace the final lines in the job script to point to the following exectables.

Note. In CASTEP you also need the pseudopotential files in the running directory. This can be achieved by adding the following lines in the submit script:

PPATH=/fs/local/linux26_x86_64/appl/chem/accelrys/MS/latest/share/Resources/Quantum/Castep/Potentials
# finding pseudopotentials and copying them in running directory
pps=`grep -E 'usp|rec' ${BASENAME}.cell| awk '{print $2}'`
echo copying following potentials in running dir: $pps
for pp in $pps
do
cp ${PPATH}$pp .
done

CASTEPPATH=/fs/local/linux26_x86_64/appl/chem/accelrys/MS/latest/etc/CASTEP/bin
$CASTEPPATH/RunCASTEP.sh $BASENAME

to run Amorphous Cell you need instead:

/fs/local/linux26_x86_64/appl/chem/accelrys/MS/latest/etc/AmorphousCell/bin/RunAmorphousCell.sh ms_basename

for Discover:

/fs/local/linux26_x86_64/appl/chem/accelrys/MS/latest/etc/Discover/bin/RunDiscover.sh ms_basename

and for VAMP:

/fs/local/linux26_x86_64/appl/chem/accelrys/MS/latest/etc/VAMP/bin/RunVAMP.sh ms_basename

Additional information

More information about the Murska queuing system can be in the Murska Guide or simply by

man bsub

If you have further questions on running Materials Studio please contact helpdesk or Atte Sillanpää.