From: Jose M. G. <jos...@un...> - 2014-11-24 14:45:49
|
Dear rDock communauty, I noticed a strange behavior of rDock recently. Here is the short story... I tried to dock a database on multiple CPUs without using a job scheduler, as none was already installed on this particular computer and I needed to start the docking quickly for the weekend... To do so, I followed this tutorial (1). I have 4 CPUs on my computer, so I splitted the input ligands file in 4 even parts and I 'submitted' 4 jobs using the following syntax in a bash script (snippet at reference 2). When I checked, all jobs were running simultaneously, as I wished. However, I noticed a very strange behavior when I came back this morning. No job finished but all stopped without printing any error message at very different times (3). Here is an example of the relevant part of one of the log files : (4). Did anyone try the tutorial (1) and noticed the same behavior? Do you have insight about what could have caused it? Could this be resolved by a job scheduler, such as PBS or Condor? Thank you for your help!!! Jose Manuel Additional Informations : OS: Centos 6.5 CPUs type : Intel(R) Core(TM) i7 CPU 950 @ 3.07GH REFERENCES : (1) http://rdock.sourceforge.net/how-to-run-rdock-in-parallel/ (2) #/bin/bash for file in *sd; do out=$(echo $file | cut -d. -f1)'_out' rbdock -i $file -o $out -r $protein.prm -p dock.prm -n 20 > $out.log 2>&1 & done (3) job1 - Nov 23 11:22 job2 - Nov 20 16:06 job3 - Nov 21 00:29 job4 - Nov 21 10:09 (4) ************************************************** RECORD #4577 NAME: previousLigand RANDOM_NUMBER_SEED: 1164231034 ************************************************** RECORD #4578 |