Running jobs on the local clusterA detailed description is provided by the computing group in their pages. If it's small you can of course run interactively. If you want to run in btch the easiest is to use Tim's magic commands which look similar to bsub | ||||||||
Added: | ||||||||
> > | bqsub ./job1.sh | |||||||
Deleted: | ||||||||
< < | bqsub ./job1.sh | |||||||
I noticed with RootCore I needed to allocate more memory than the default if I run over large statistics. Also note the time is the wall time not the CPU time here. <br> To find out if your jobs are running | ||||||||
Deleted: | ||||||||
< < | ||||||||
qjobsIf you submitted crap and want to delete jobs use the condor commands | ||||||||
Deleted: | ||||||||
< < | ||||||||
condor_rm <jobid>-- Monika Wielers - 2015-07-02 Comments |
Running jobs on the local clusterA detailed description is provided by the computing group in their pages. If it's small you can of course run interactively. If you want to run in btch the easiest is to use Tim's magic commands which look similar to bsubbqsub ./job1.shI noticed with RootCore I needed to allocate more memory than the default if I run over large statistics. Also note the time is the wall time not the CPU time here. <br> To find out if your jobs are running qjobsIf you submitted crap and want to delete jobs use the condor commands condor_rm <jobid>-- Monika Wielers - 2015-07-02 Comments |