Hi Andrew,
It submits fine 66 jobs, one bpx_preproc, one job array of 64 bedpostx jobs and one bpx_postproc.
But it seems the jobs never start, they are kept queued (qw status). I think you need to talk to your administrator to find out why your jobs never start.
Cheers
Stam
On 2 Jul 2013, at 17:11, Andrew James wrote:
> When I run qstat, I see jobs from the past week, all of which I have canceled (except for a bedpost started at 11:01).
>
> [ajames@priclus commandline]$ qstat
> job-ID prior name user state submit/start at queue slots ja-task-ID
> -----------------------------------------------------------------------------------------------------------------
> 6954178 0.55500 bpx_prepro ajames qw 06/27/2013 09:51:48 1
> 6954199 0.55500 bpx_prepro ajames qw 07/01/2013 14:36:00 1
> 6954205 0.55500 bpx_prepro ajames qw 07/02/2013 10:55:10 1
> 6954211 0.55500 bpx_prepro ajames qw 07/02/2013 11:01:10 1
> 6954179 0.00000 bedpostx ajames hqw 06/27/2013 09:51:50 1 1-64:1
> 6954180 0.00000 bpx_postpr ajames hqw 06/27/2013 09:51:50 1
> 6954200 0.00000 bedpostx ajames hqw 07/01/2013 14:36:02 1 1-64:1
> 6954201 0.00000 bpx_postpr ajames hqw 07/01/2013 14:36:02 1
> 6954206 0.00000 bedpostx ajames hqw 07/02/2013 10:55:12 1 1-64:1
> 6954207 0.00000 bpx_postpr ajames hqw 07/02/2013 10:55:12 1
> 6954212 0.00000 bedpostx ajames hqw 07/02/2013 11:01:12 1 1-64:1
> 6954213 0.00000 bpx_postpr ajames hqw 07/02/2013 11:01:12 1
>
> When I canceled a bedpost attempt from this morning, (using the directory.bedpostX/cancel command), I received the following message:
> ajames has deleted job 6954210
> ajames has deleted job 6954209
> ajames has deleted job 6954208
>
> I have not seen 66 different jobs submitted for the same bedpostX attempt - at most, 3.
>
|